22 users — I’m testing what happens after the first opportunity

Adding one thing rather than repeating the good answer above. Split the drop by what the user does on the return visit, not just whether they return.

Opens, looks, leaves without starting anything. Nothing relevant was available, or it was there and did not read as relevant. Supply or presentation.
Opens, starts, abandons partway. The second opportunity was worse than the first, or the proof step is the wall.
Never opens at all. They had no reason to come back, which is timing and notification, not product.

All three of those collapse into one line on a retention chart and every one of them has a different fix.

Second thing, check your cadence assumption before you judge the number. I got this wrong this week. I was measuring day 2 return on a product whose real behavior happens every four or five days, so the number looked like a disaster when the metric was simply wrong for the rhythm. Your median days from first completion to second start tells you which window you should be grading yourself on. Compute that first, then decide whether the transition rate is bad.

At 22 users the interviews beat all of the above though. I am at 10 testers and the events I failed to log are the only information I cannot go back and get. The conversations I still can.

Are you seeing users complete the first opportunity but stop despite another relevant one being available, or is the bigger drop-off before they finish the first?

22 real users is already more signal than most launches get. What are you watching for after that first opportunity — retention, referrals, or something else?

Nice progress. What is the next thing you are focusing on?

You're asking the right question at exactly the right size. At 22 users, do the qualitative work while the numbers are still countable. Track three numbers and one conversation: 1. First-opportunity completion rate — your real activation line, not signup. 2. Second-opportunity availability — the marketplace-specific one most founders miss. If a user finishes #1 and there's nothing relevant available, that's a supply failure, not a motivation failure. Measure them separately. 3. Median days from first completion to second start — your natural re-engagement window. And the conversation: ask the 5–6 users who completed one but not two a single question — "what would have made you do another one right away?" One caution: improving task instructions can look like a retention fix while actually being an acquisition fix — clearer instructions get more first completions, inflating the top of your second-opportunity funnel without changing the transition rate. Keep the two rates separate or you'll fool yourself.

Worth fixing the instructions before you start measuring the first to second transition, otherwise the number mostly measures your copy rather than motivation. If some people were not sure how to complete a task or submit proof, that confusion sits inside every drop off you record, and you will not be able to separate somebody who stopped because the second opportunity was unappealing from somebody who found the first one stressful in a way you have since fixed. At twenty two users you also have the option nobody keeps later: message the ones who did not continue and ask. Ten replies will tell you more than the cohort chart can at this size.

Thanks for sharing the numbers, that makes it much easier to follow.

Solid lesson. Which channel has worked best for you so far?

How did you decide this was worth building in the first place?

Nice framing. At this size I’d define activation as a small state machine rather than one percentage: opportunity viewed → accepted → proof submitted → second opportunity viewed → second completed. Put timestamps and a reason code on each drop-off (unclear instructions, bad fit, no motivation). For an early marketplace, manually watch 5–10 sessions and ask right after completion what almost stopped them; that often gives better signal than cohort retention. The first-to-second transition is probably the earliest habit proxy you can measure. Are opportunities personalized enough that you can compare second-step conversion by category or source?

Still at the very early stage myself (2 real installs on a Chrome extension, one from a random user in India I didn't even reach out to). What's helped most so far isn't more channels, it's actually reading what the few real users say — got two independent requests for the same feature and that told me more than any traffic number would.

Thanks for writing this up. Bookmarking it for later.

The first to second transition is the right metric to isolate at this stage. Aggregate retention hides the activation gap. The cleaner framing is: what percentage of users who completed any opportunity went on to complete a second? That number tells you whether the product is leaking or whether the problem is supply.

For marketplaces the motivation in the second attempt is different from the first. The first attempt is curiosity. The second is a judgment on whether the reward-to-effort ratio is worth repeating. That means task clarity matters but reward clarity matters more. A user who is unsure how to submit proof is also probably unsure what they got for doing it.

I tracked something similar when building Genie. The question I cared about was not total active users but what share of users who completed the core action once came back and did it again within 48 hours. That became the proxy for whether the product was working.

Of your 22, how many have actually completed the first opportunity versus just signed up and not engaged with one yet?

Interesting take. Would you still recommend this approach to someone starting today?

Thanks for writing this up. Bookmarking it for later.

At 22 users the answer is not in a funnel, it is on the phone. Call the ones who stopped after one and ask what they expected to happen next, you will get the real reason in ten minutes and it is usually not motivation. My bet is that when they finished the first one there was no good second one sitting there waiting, which makes this a supply problem wearing a retention costume.

Thanks for writing this up. Bookmarking it for later.

try to get feedback from those early 22 users.

Thanks for writing this up. Bookmarking it for later.

The first opportunity is often only the beginning. What happens next depends on how well you evaluate the experience, follow up, and prepare for the next opportunity. Instead of focusing only on the initial result, consider what worked, what could be improved, and what actions can increase your chances going forward.

Keeping track of your progress and learning from each opportunity can help you make better decisions over time. Whether it relates to business, career growth, networking, or personal goals, consistent follow-up and preparation can turn an initial opportunity into a longer-term possibility.

I like separating the first action from the second. For an early product, “installed” tells us very little. The more revealing question is whether someone received enough value to take another meaningful step without being pushed.

As co-founder of SynDiary, I would also keep this very human with 22 users. Ask the people who stopped what they expected to happen next, and ask those who continued what made the second step worthwhile. At this stage, those explanations may be more valuable than a retention percentage.

Hey,. I’m speaking with a few early-stage builders to understand how they go about validating their ideas and what they find difficult. Would you be open to a quick chat about your experience? building something around

I like the first → second transition better than a generic “active user” number. I’d log whether the next opportunity is shown right after someone submits proof, because a gap there can look like lack of motivation. If they have to go hunt for the next thing, that’s probably a handoff problem in the product, not retention.

This resonates in an uncomfortable way. I've gone the opposite direction from "build for one specific person" — a handful of narrow, properly-priced B2B tools, built solo, each one genuinely solving something real. What I underinvested in wasn't the build quality or the pricing discipline, it was picking one and staying with it long enough for word-of-mouth to actually compound. Four narrow things just gets you four separate "nobody's found this yet" problems instead of one thing with years of patience behind it. Rereading this, the "long game" isn't really about waiting it out — it's about only having the discipline to play one game at a time.

Interesting. How are you measuring whether it is working?

Nice bro.

Worth flagging the size problem underneath peptide10's point: 22 users split into a first→second funnel probably means each bucket is under 10 people, which is small enough that one or two people's personal reason for stopping will look like a trend even when it isn't one. At this size, "ask the ones who didn't continue" isn't just cheaper than a cohort chart, it's more honest — the chart will show you a percentage before you have enough people for a percentage to mean anything.

Nice work shipping it. What has been the biggest challenge since launch?

At 22 users you can just ask them. I'm at 60 and someone on our team messages every new member on day one. What they say back tells us more than any dashboard. The ones who don't come back nearly always got stuck on something we thought was obvious.