Audit Your First 100 Users' Week One

You found the early users by hand. You wrote the emails, made the calls, sat in on the sessions, and probably fixed their setup while they watched. Now you have no distribution, no clear signal, and a next feature already in your head. The question is whether the product is real, not whether you can get more people.

The tempting fix is another feature: a new button, a new template, a new integration. If week one is weak, that feature will hide the problem. A feature can be the right move, but only after week one has been checked.

Acquisition speed will not tell you if the product is real

Amplitude's 2025 Product Benchmark Report analyzed a dataset of more than 2,600 companies. The B2B benchmark analysis used data from September 2023 through September 2024. Across the benchmark, acquisition performance was not meaningfully linked to retention performance, with products in each acquisition quartile, a quarter of the distribution, appearing across retention quartiles in roughly equal proportions. In that analysis, 69% of products that activated users quickly also performed well on three-month retention.

For a founder with no distribution, that changes the order of work. You do not need a growth plan yet. You need a clear answer about the users you already have. The manual work you did to find them gives you an advantage: you can ask them directly, watch them use the product, and notice where week one breaks. The notes you already took matter too: where they got stuck, what they asked for, what they did after the session.

Week one is the signal you can actually see

For your earliest users, the product is real only if week one produces repeated meaningful use. A login or a single completed task is not enough. You need to see the user come back, do something that matters, and have a reason to come back again. The audit below is the checklist you keep.

• Setup completed: the user reached a usable state without you fixing it.
• Second meaningful use: the user returned and did a second task that mattered to them.
• Third meaningful use: the user did a third task, not just checked in.
• A reason to return: the user can name a saved item, scheduled job, pending result, or next step.
• A stop/double-down rule: you have written the decision rule that says when to pause and when to expand.

Run the audit on a small group, not the whole base. Pick the users who signed up in the last few weeks and check each one against the list. Use call notes when you have them, and product events when they exist. If neither exists, ask the user what they did after the initial session and what they expect to do next.

The audit decides whether to stop or double down

If week one does not produce repeated meaningful use, stop. Do not buy traffic, add a feature, or ask for referrals. Fix setup, the initial task, or the reason to return. If week one does produce repeated meaningful use, double down on the path that led to third use. That path is the product.

When the audit says stop, spend the next cycle on repair: a shorter setup, a clearer initial task, a saved result, a scheduled reminder, or a better reason to return. When it says double down, protect the path. Do not redesign the onboarding, rename the core action, or add another workflow until the core path is boringly reliable.

In the B2B subset, top products retained 15.6% of customers at three months, compared with 2.5% for median products. Those top B2B products acquired new customers at a 9% monthly rate, compared with 0.3% for median products, a 30-times faster rate. The benchmark found that the top 10% of financial services products reached a 10.2% monthly acquisition rate and a 19.5% three-month retention rate.

Put the audit result in the ticket for the next feature. Make the decision there, before the code starts.