# Concierge onboarding with direct messages before self-serve

> Before the product is truly self-serve, onboard early design partners by hand in direct messages so you learn the edge cases before you automate the path.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/concierge-onboarding-with-direct-messages-before-self-serve/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/how-we-got-our-first-1000-users)
- GrowthDex source hub: [PostHog Newsletter](/sources/posthog-newsletter-newsletter-posthog-com/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: free
- Channels: Community, Founder-led, Product
- Stages: design partners, activation, founder-led growth, user research
- Key metric: PostHog reached its first 10 users mostly through personal networks before the self-serve path was ready

## Why this can grow

A lot of teams try to hide the manual phase because it does not look scalable. That is backwards. The manual phase is often where the product learns what setup friction, missing context, and confusing defaults actually feel like. Direct-message onboarding also gives the founder or operator a much tighter read on whether the user would come back without a nudge. That is more valuable than a polished but blind launch path.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where concierge onboarding with direct messages before self-serve can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Founder-led channel.
3. Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

PostHog said it was not self-serve at first, created new users manually, and set early users up over Slack, WhatsApp, or in person before the team automated more of the path.

## Adjacent tactics in the same lane

- [Deadline-backed pivot sprint for first-user validation](/growth-ideas/deadline-backed-pivot-sprint-for-first-user-validation/) - same source, 2 shared channels
- [Manual chat onboarding before self-serve](/growth-ideas/manual-chat-onboarding-before-self-serve/) - same source, 1 shared channel, 1 shared stage
- [Founder 30-second reply SLA for early users](/growth-ideas/founder-30-second-reply-sla-for-early-users/) - same source, 1 shared channel, 1 shared stage
- [Post-launch user motive interviews with anti-goals map](/growth-ideas/post-launch-user-motive-interviews-with-anti-goals-map/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The first growth system usually looks manual](/blog/the-first-growth-system-usually-looks-manual/) - founder-led growth, brand trust, early-stage growth

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.