Activation & onboarding review

Onboarding review for Omar

Recommendation

We are measuring setup, not activation. Completing a checklist of preferences does not establish that someone has experienced Tidepool’s value: seeing where their money goes and taking control of it.

Redesign onboarding around that first useful financial insight. Treat the celebration screen and progress bar as supporting elements—not the main fix—and replace next quarter’s checklist-completion goal.

What activation should mean

Use “connected a bank and categorised at least 10 transactions within the first week” as our provisional activation definition.

This combines access to real financial data with an action that helps users understand their spending. It is a stronger approximation of delivered value than naming an account or picking a theme.

The threshold of 10 is a starting hypothesis, not a proven magic number. We should validate whether users actually gain an insight at this point and whether a different threshold or milestone—such as reviewing a spending summary—better predicts durable use. Creating a budget may become a subsequent milestone, but the current evidence does not support making it mandatory for initial activation.

What the evidence says

Among August’s 4,000 sign-ups, overall day-60 retention was 28%.

The strongest signal is the combined bank-and-categorisation milestone: 27% of sign-ups reached it, and those users accounted for 842 of our 1,120 retained users. Retention among everyone else was approximately 9.5%.

Checklist completion, by contrast, is associated with retention only slightly above the cohort average. Raising it could improve the reported activation rate without improving users’ outcomes.

These are observational, overlapping groups. Motivated users may both complete meaningful actions and remain active; the data does not prove that pushing everyone through those actions will cause retention. Nor can we infer exact step-by-step drop-off from these aggregates. The CSV also differs slightly from the funnel summary on checklist and categorisation counts; reconcile reporting before setting the baseline.

What to change in onboarding

1. Lead with the value proposition, then bank connection. Explain what users will get from connecting, how their data is handled, and what happens next. Instrument connection starts, failures, abandonment and successful imports; address reliability and trust barriers.

1. Replace the upfront preference checklist with a guided first-value journey. Move theme selection and account naming out of the critical path. Ask for notification permission when there is a clear benefit. Keep savings goals optional or introduce them after users understand their finances.

1. Guide users through real transactions. Provide sensible category suggestions, easy corrections and a short review flow. Then show a useful spending summary—not merely confirmation that ten items were completed.

1. Offer budgeting as the next step. Help users turn their spending insight into a realistic budget, without making budget creation another prerequisite that delays first value.

Measure the full journey and test changes against the existing experience, including first-week milestone attainment and day-60 retention.

Design proposal and next quarter’s goal

A progress bar is worth testing if it tracks meaningful value steps, not cosmetic setup tasks. A celebration screen belongs after the first useful insight, should be brief, and should not interrupt it. Neither proposal addresses the core problem on its own.

Replace “raise checklist completion from 61% to 75%” with “increase first-week bank-plus-10-transaction activation.” A provisional target of 27% to 35% is reasonable to plan against, subject to baseline reconciliation and experiment sizing—not a forecast supported by this dataset.

Success must also include improved day-60 retention, with bank-connection reliability, privacy complaints and abandonment monitored as guardrails. Keep checklist completion as a diagnostic metric, not the team’s definition of success.

Onboarding review: what activation should mean

To: Omar | From: Onboarding PM | Data: August cohort (4,000 sign-ups), day-60 retention

Summary

Activation is flat because we are measuring the wrong thing. Finishing the setup checklist barely predicts whether someone stays. Connecting a bank and categorising 10+ transactions in week one does predict it strongly. I recommend we redefine activation around that, rebuild onboarding to get people there faster, and replace next quarter's checklist goal.

What activation should mean

Activated = connected a bank AND categorised 10+ transactions in the first week.

This is the moment Tidepool delivers its core promise: seeing where your money goes. Only 27% of August sign-ups reached it, so our real activation rate is less than half the 61% we report.

The evidence

Day-60 retention by first-week behaviour (baseline: 28% of all sign-ups retained):

Five things stand out:

1. The checklist is a weak signal. Completers retain at 30% versus 24% for non-completers, close to the 28% baseline. 1,696 people completed it and still churned.
2. Bank plus categorisation is the strongest signal. Users who did both retain at 78%. They make up 27% of sign-ups but 75% of everyone retained at day 60.
3. Each half is weak on its own. About 920 people connected a bank without categorising, and they retained at 13%. About 300 categorised without a bank, and they retained at 16%. The value comes from real transactions that the user has made sense of.
4. The biggest leaks are at the steps that matter. Half of sign-ups never connect a bank. Of those who do, 46% never reach 10 categorised transactions.
5. Budget creation isn't a good activation metric. Its retention lift is small and only 31% do it. That is worth investigating separately for a budgeting app.

Caveats: this is one cohort and the data is correlational. Motivated users may simply do more of everything. The gaps are large enough to act on, but we should confirm cause with experiments rather than assume it.

What to change in onboarding

1. Put bank connection first. Today it comes after a four-item checklist that we lose 39% of users on. Naming the account and picking a theme add no value at signup and can move to settings. Ask for notifications later, once there is something worth notifying about, such as a first spending summary. The savings goal becomes optional after categorisation.
2. Make connecting a bank feel safe and fast. Address security concerns at the moment of asking, with plain-language reassurance about read-only access. Offer the most popular banks up front. Instrument the drop-off between starting and finishing the connection, which we can't currently see.
3. Guide the first 10 categorisations straight after connecting. Show recent transactions with suggested categories so each one is a one-tap confirm. End with an immediate payoff: "Here's where your money went this month."
4. Recover people who stall. Send a reminder to anyone who connected but hasn't categorised within 48 hours. That group is about 920 people a month retaining at 13%.

Each change should ship as an A/B test with day-60 retention as the outcome. That is how we confirm the relationship is causal.

The design team's proposal

A celebration screen and a progress bar are reasonable patterns, but aimed at the checklist they would polish a step that doesn't drive retention. I'd ask design to point the same ideas at the new milestone:

• A progress bar for "connect bank, then categorise 10 transactions."
• A celebration on the 10th categorisation, paired with the first spending insight.

That is a small redirect of their work, not a rejection of it.

Next quarter's goal

I recommend we retire the 61% → 75% checklist goal. Even if we hit it, and every extra completer gained the full 6-point retention gap (which is generous), that would mean roughly 30–35 more retained users per 4,000 sign-ups.

Compare moving just 10% of sign-ups (400 people) into the bank-plus-categorised group. If even a fraction of that 68-point retention gap is causal, the payoff is several times larger.

Proposed goal: raise week-one bank connection plus 10+ categorised transactions from 27% to 35%, with day-60 retention as the guardrail metric. We should set the final target once the first experiment shows how much the metric moves.

Next steps

• This week: confirm the new activation definition with you and analytics, and backfill it for June and July to check it holds across cohorts.
• Weeks 2–4: run an A/B test of bank-first onboarding with the checklist deferred, and add instrumentation to the bank connection flow.
• Weeks 4–8: test the guided categorisation flow and the redirected progress bar and celebration screen.

To: Omar | Re: Onboarding review

Recommendation

Activation should mean connecting a bank and categorising 10+ transactions in the first week. Our current definition, completing the setup checklist, barely predicts retention, so the 61% is flat for a reason: we're measuring the wrong thing. I'd fix the path to the real activation event, use the design team's ideas only on that path, and replace next quarter's goal.

Evidence (4,000 August sign-ups, day-60 retention)

Three things stand out:

• The checklist is a weak signal. Checklist completers retain at 30%, against 28% for everyone. The checklist is theme, notifications, account name and goal, so it's mostly cosmetic setup.
• The combination matters, not either step alone. Backing out the overlaps from the CSV:
• Bank only (no categorising): about 920 users, 13% retained.
• Categorised only (no bank): about 300 users, 16% retained.
• Neither: about 1,700 users, 6% retained.
• Both: 78% retained.

Users who connect but never see their spending sorted do worse than average. The value moment is seeing where the money goes, which needs both steps. - Budgets and app opens aren't the answer. Budget creators retain at 33%, close to baseline. Opening the app 4+ days (40%) is engagement, not a lever we can pull in onboarding.

Caveat: this is observational. Motivated users probably do everything, so these numbers show who retains, not what causes it. The recommendations below are therefore tests, not guarantees.

What to change

The funnel is 100% → 50% connect → 27% connect and categorise. There are two leaks:

1. Half of users never connect a bank, and they retain at 8%. Put bank connection first, straight after sign-up. Move theme, notifications and account name out of the critical path (defer or drop them). Look at where the connect flow fails and whether trust copy (read-only access, security) is needed. I can't tell from this data whether the checklist is causing bank drop-off, so I'd A/B test bank-first against the current order.
2. 46% of those who connect (920 of 2,000) never reach 10 categorised transactions. This is the biggest fixable gap, since 78% of those who finish retain. Auto-categorise on connect, pre-fill best guesses, and walk users through their first 10 with one-tap confirmations rather than leaving them to find the feature.

I'd also instrument the funnel by step and by time, so we can see where in the first week people stall.

The design team's proposal

A celebration screen and a progress bar for the checklist would probably raise checklist completion, but that metric barely relates to retention, so we'd likely see a "win" with no change in retained users. I wouldn't ship them as proposed. Both ideas are cheap and sound, though, so I'd redirect them:

• Make the progress bar track the real path (connect bank → categorise 10).
• Put the celebration at the moment of value, such as the 10th categorised transaction, ideally with a first insight ("here's where your money went").

This is a good way to involve design in the work above rather than rejecting their proposal.

Next quarter's goal

Drop "checklist completion 61% → 75%". Pushing it up could even pull effort toward low-value steps.

Replace it with: percentage of sign-ups who connect a bank and categorise 10+ transactions within 7 days. Baseline is 27%. I'd propose a target around 35%, but that is a judgment call until we've sized the effect of the first experiments, so let's set it after a few weeks of data. Guardrail: day-60 retention among those users should hold near its current 78% (if we widen the funnel with less-motivated users, it may dip, and we should watch that). Track the real outcome, overall day-60 retention (28% today), alongside it.

Next steps

• Run the bank-first vs current-order A/B.
• Prototype auto-categorisation and a guided first-10 flow.
• Work with design on the redirected progress bar and celebration.
• Agree the new activation definition and dashboard before the quarter starts.

I'm happy to walk through the numbers if useful.