Manual chat onboarding before self-serve
Set up the first users manually over chat or in person before you automate signup, so you can watch friction show up in real time.
Why this can grow a startup
Early onboarding is usually not a scale problem. It is a learning problem. Manual setup forces the team to see where users get stuck, what assumptions break, and which parts of the product are still too brittle for strangers. That gives you better product truth than polishing a self-serve funnel before anyone has really succeeded with it.
Source-backed example
PostHog manually created early user accounts in the database and set people up over Slack, WhatsApp, or in person, reaching its first 10 users mostly through personal networks before prioritizing self-serve onboarding.
Source-reported evidence
Source: PostHog Product for Engineers · Browse PostHog Product for Engineers tactics
First 10 users came largely through personal networks before self-serve onboarding
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 24, 2026
When to use it
Use this when Product, Onboarding, User Research is relevant to 0-10, activation, product-market-fit 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Product and Onboarding, using evidence from PostHog Product for Engineers as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from PostHog Product for Engineers
Explore related GrowthDex examples and evidence connected to PostHog Product for Engineers.
Open PostHog Product for Engineers source hub