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.
Why this can grow a startup
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.
Company 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.
Source and metric
Source: PostHog Newsletter · Browse PostHog Newsletter tactics
PostHog reached its first 10 users mostly through personal networks before the self-serve path was ready
Source discovered: May 26, 2026
When to use it
Use this when Community, Founder-led, Product is relevant to design partners, activation, founder-led growth and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read PostHog Newsletter and identify what is directly supported.
- Choose one channel context: Community, Founder-led, Product.
- Define the test around PostHog reached its first 10 users mostly through personal networks before the self-serve path was ready.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.