What to do in the two weeks after first users never come back
Members of the Growth work group debate whether a team with a few dozen users should stop acquisition, and how to tell an onboarding problem from a use case nobody needs.
Updated
Stop broad acquisition but keep a small, hand-picked flow of users from one segment, watch their first sessions to see where nothing valuable happened, and count only the return visits nobody prompted. If even hand-held users don't come back on their own, the use case is the problem.
- Check whether the business works at its retention. Gustaf Alströmer would put a number on retention before deciding the product is broken, a point he made with a co-presenter at a YC retreat. At 1% retention, he says, multiply CAC by 100 and see whether the business still works. Some products with low repeat use do. Most don't, and the math shows quickly which kind you have.
- Look for a first session where nothing happened. Gustaf gives an Uber example: new drivers who sat outside their house and got no requests didn't come back. When a supply-dependent product's first session delivers nothing, he would fix operations before the UI. He would also never log users out, and would audit the second visit as closely as the first. Brian Balfour adds that early AI products draw people who are only experimenting, so their churn can look like an onboarding failure when the product never had a lasting use for them.
- Check early wins against a year-long holdout. Archie Abrams says Shopify experiments that lifted first sales showed zero incremental GMV a year later, so he would measure early-retention wins with long-term holdouts. He also warns that making the step above a retaining segment harder raises activation rates without more people succeeding, and would skip wizards and carousels that set users up without teaching the product.
- With a few dozen users, keep a hand-picked trickle. Gustaf would stop launches, Product Hunt and paid ads but keep a hand-picked trickle of maybe 10 to 20 users a week from one segment. Over two weeks, the founders would call every one-time user, onboard each new one live on a screen share, and ship fixes for the two or three most common stalls. Casey Winters agrees that his own "stop all acquisition" is too strong for a team with 50 users.
- Prompt the second session and wait for the third. Casey would let a founder text a user back for a second session, since that shows whether the product delivers once someone reaches the key action. The third session has to come with no prompt, on the use case's natural cycle. Users who return only when the founder asks mean a concierge service, and the few who come back alone mark the segment to narrow onboarding and positioning around.
- Don't treat all messages as reminders. Hila Qu pushes back a little on leaving email and push for last. She agrees that pinging someone back to the same broken experience does nothing, but says messages that walk a new user to the key action are part of activation. She would also keep a small holdout on the biggest activation wins to confirm, a few months later, that the extra users stayed.
Ask a follow-up
Growth
Frequently Asked Questions
How do you choose a startup's first growth channel?
Pick a channel the product can feed, test it with one narrow segment on a set budget and date, and judge it by how many users reach value and come back.
What should a founder check first when growth stalls?
That the data is right, then cohort retention split by segment and channel. If curves trend toward zero in every slice, fix the product before spending more on acquisition.
How do you tell a growth problem from a product problem?
Bring in a small batch of users from one clean channel and read their cohorts. If they activate and return but there aren't many, it's distribution. If they leave within the first week, product owns the fix.
What moves activation in a new user's first few days?
Find where users drop, then match the lever: pre-answer setup for users who stall, make the first action an earned win for users who feel nothing, and bring back users who got value.
Who should own acquisition and retention, growth or marketing?
Most members would split near signup, with marketing on channels and the promise and growth on the path to first value. The line still has to follow the growth model, and both teams judge channels by the cohorts that stay.
Should a growth team report to product or marketing?
Wherever the biggest lever is. For most product-led companies that is product, next to core rather than inside it, and once paid spend matters too, one growth leader owns acquisition and activation.
Which lifecycle emails should a team build first?
The ones aimed at the steepest drop on the retention curve, usually the activation email. Depth and renewal emails come next, and win-back to fully churned users comes last.
How do you bring back signups who went quiet?
Watch a few try the next step and fix where they stall, then test the message with and without the fix against a holdout, and count retained use rather than opens.
When should a product-led company add sales?
A founder can start working accounts where usage is spreading and retaining. A sales team follows once deals need security reviews and procurement that self-serve can't handle.
Which self-serve accounts should a sales rep call?
Ones big enough to pay for a rep's time, with use spreading inside the company and a need self-serve can't meet. Hold some flagged accounts back to check that sales added value.
Which early action should count as activation?
Use two measures: an early action onboarding can move as the team's operating metric, and a later repeat action to check that those users came back. Randomize the onboarding change so motivated users don't skew the read.
What makes a good north star metric for an early product?
A retention measure built from how often the problem occurs, the action that solves it and the user it describes, with activation as an input. Drop it if the team can raise it without users getting more value.
Should a new marketplace build supply or demand first?
Whichever side gets a buyer to a completed transaction while giving the supplier a reason to stay. Start in one narrow market and track matches, supplier earnings and repeat buyers.
When can a marketplace copy its first city?
When service holds after subsidies come down, a new manager can run the launch playbook without the founders, and the team knows whether the channel behind market one's demand starts warm or cold in the next market.
How should you test a landing page?
Show visitors what they searched for before the ask, start with the page's first clear funnel drop, and count activated users per visitor alongside signups.
How does a B2B startup find its first paying customers?
Have founders sell by hand to one narrow buyer, starting with warm intros and asking for payment early. Then check who actually paid, and at what price, before choosing a channel to scale.
