Activation & onboarding review

Onboarding review: activate on financial value, not setup

Recommendation: Replace checklist completion as our activation metric with connecting a bank and categorising at least 10 transactions within seven days of signup. Reorient onboarding around that outcome. The celebration screen and progress bar are secondary; making the current checklist more engaging risks improving the wrong metric.

What activation should mean

For Tidepool, activation should mean a user has taken the first meaningful steps toward understanding their spending—not finished configuring the app.

Bank connection brings their financial data into Tidepool; categorisation makes that data useful. Together, these are our strongest available proxy for experiencing core value. This is a working definition, not proof that exactly 10 categorisations creates a lasting habit. We should validate the threshold and whether users actually understand something useful about their money.

Budget creation can follow that first insight. The evidence does not support making it a mandatory activation requirement today.

What the evidence says

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

The checklist has weak separation: completers retained at 30.4%, versus 24.2% for non-completers. Its 61% completion rate is therefore a poor headline measure of delivered value.

By contrast, only 27% of signups connected a bank and categorised 10+ transactions, but they accounted for 842 of 1,120 retained users—75% of everyone retained. Users who did not achieve both retained at 9.5%.

These are observational associations. More motivated users may both complete these actions and remain active; we cannot promise 78% retention simply by pushing people through them. Behaviour groups also overlap, so the reported steps should not be treated as a strictly sequential funnel. Before testing, reconcile the rounded onboarding figures with event counts and standardise the day-60 activity definition.

What to change

1. Remove configuration as a gate to value. Defer theme selection and account naming; make savings goals optional. Request notification permission when there is a clear benefit, such as a relevant budget alert—not as checklist work.

1. Bring bank connection forward. Explain why access is needed, what data is used, and how users retain control. Instrument connection starts, provider errors, unsupported banks, abandonment and successful imports. Preserve a skip/retry path rather than forcing consent.

1. Guide users from imported transactions to spending insight. Offer a short, low-effort review of suggested categories. Let users confirm or correct them, then show an understandable spending summary. Do not require ten arbitrary manual edits merely to satisfy the metric.

1. Offer a budget as the next useful action. Use the spending summary to suggest a realistic starting budget, rather than asking users to invent one before seeing their finances.

Test the redesigned flow against today’s onboarding. Measure seven-day activation first, then downstream retention; monitor connection failures, abandonment and user-reported trust and usefulness.

Design proposal and next quarter’s goal

A progress bar is worth testing if it tracks meaningful steps toward understanding spending. It should not encourage completion of low-value setup tasks. A celebration screen belongs after a genuine milestone and should reinforce the insight gained, not interrupt access to it. Neither should take priority over bank-connection and categorisation friction.

Replace the 61% → 75% checklist goal with a goal for the new activation definition. I propose 27% → 35% within seven days, provisionally, subject to instrumentation validation and early experiment results. That is a planning target—not a forecast supported by this dataset.

Keep checklist completion as a diagnostic. Judge success by increased meaningful activation without sacrificing trust or retention, and confirm the retention effect once next quarter’s cohorts mature.

To: Omar From: PM, Onboarding Re: Onboarding review

Summary

Our activation metric is measuring the wrong thing. Completing the setup checklist is 61% of sign-ups, but it barely separates users who stay from those who leave: 30% of completers are retained at day 60, against 24% of non-completers. The behaviours that matter are connecting a bank account and categorising transactions. Users who do both are retained at 78%. Users who do neither are retained at 6%. I recommend redefining activation, putting bank connection at the centre of onboarding, and reshaping the design proposal around it.

What activation should mean

Activation = connected a bank account and categorised 10+ transactions in the first 7 days.

Baseline: 27% of August sign-ups (1,080 of 4,000). This definition reflects the core value (seeing where money goes), is the only combination with a large retention gap, and is measurable from event data.

Evidence

Four things stand out:

• Bank connection and categorising are complementary. Each alone yields 13–16% retention; together they yield 78%. The value appears only when both happen.
• The biggest fixable leak is after bank connection. 46% of users who connect a bank never categorise 10 transactions.
• Budget creation is weak in week one. Its retention (33%) is barely above the 28% baseline, so it shouldn't define activation yet.
• App-open frequency is an outcome, not a cause. It's a useful engagement metric, but users who are already activated open the app more.

These are correlations. Users who do more are probably more motivated to begin with, so the 78% overstates the causal effect. We need experiments to confirm the lift, but the gap is large enough to act on now.

What to change in onboarding

1. Make bank connection the first real step. Only half of sign-ups connect, and the cosmetic steps (name, theme) come first. Move bank linking up, explain the payoff ("see where last month went"), and reduce friction: clear read-only reassurance, and recovery paths for failed connections.
2. Help users categorise 10 transactions quickly. Pre-suggest categories, allow one-tap confirmation, and show progress ("3 of 10: your spending is taking shape"). Target the 46% who stop short.
3. Demote checklist items that don't carry the value. Theme, name, and notifications should be optional. The savings goal is untested in our data, so test it before cutting it.
4. Move budget creation later. Prompt it after the user has categorised 10 transactions, and measure whether that lifts budget creation and retention in weeks 2–4.

The design team's proposal

The celebration screen and progress bar are good craft aimed at the wrong target. A progress bar on the current checklist will push users through theme and notifications faster. That raises the 61% number without touching the steps that predict retention, and may do nothing for bank connection.

The celebration is valuable, but only at a milestone that matters. I'd ask the design team to rebuild the progress bar around the two activation steps (bank connected, 10 transactions categorised), with the celebration triggered when both are done. We test it against the current flow and ship only if activation moves.

Next quarter's goal

Replace "checklist completion 61% → 75%" with "activation (bank connected and 10+ categorised in week one) 27% → 35%."

Sizing: in a 4,000-user cohort, 27% → 35% is about 320 more activated users. At 78% retention, that's roughly 250 more retained at day 60. A checklist point, by contrast, is worth about 10 retained users at current completer retention. Marginal users will retain worse than average, so treat 250 as an upper bound.

35% is ambitious but reachable: it requires bank connection to rise from 50% to about 60%, and categorising conversion from 54% to about 58%. The checklist stays as a leading indicator, not the goal.

Next steps

1. Adopt the new activation definition this week and add it to the onboarding dashboard.
2. Run an A/B test of bank-first onboarding against the current flow.
3. Ask design to rebuild the progress bar and celebration around the activation steps, and test before shipping.
4. Confirm the retention lift with a holdout or experiment, since current figures are correlational.

To Omar — onboarding review

What activation should mean

Activation should mean a new user has reached Tidepool’s core value: connected a bank account and categorized at least 10 transactions within their first seven days. Completing setup tasks is not the same as understanding where your money goes.

What the evidence says

Of 4,000 August sign-ups, 61% completed the checklist, 50% connected a bank, and 34% categorized 10+ transactions. The behavioral data points to which events are most associated with retention at day 60:

• All sign-ups: 28% retained (1,120/4,000)
• Completed the checklist: 30% (742/2,438)
• Connected a bank: 48% (964/2,000)
• Categorized 10+ transactions: 65% (891/1,380)
• Connected a bank and categorized 10+: 78% (842/1,080)

The combined behavior is the strongest signal and represents 27% of all sign-ups today. By contrast, checklist completion is barely above the overall retention rate. Creating a budget is associated with 33% retention, so it is not a better activation milestone on this evidence.

These are associations, not proof that onboarding changes will cause retention to rise: users who connect accounts or categorize transactions may already be more motivated. We should treat the numbers as a strong direction for what value to help users reach, then test changes and track outcomes.

What to change

• Move bank connection earlier. Defer account naming, theme choice, savings goals, and notifications until after users see value. Explain why connection helps, address security concerns, and make the flow as clear and low-friction as possible.
• Guide users to their first insight. After connection, help them review and categorize transactions with sensible suggestions. Measure progress toward 10 categorized transactions, not just completion of onboarding screens.
• Offer budgeting in context. Prompt users to create a budget after they have seen their spending, rather than treating it as a prerequisite.

Design proposal and next-quarter goal

A progress bar could help, but only if it tracks the path to value—connect a bank, review transactions, categorize 10—not the existing checklist. A celebration screen after checklist completion would celebrate the wrong milestone; consider celebrating the first meaningful spending insight instead. Test both against a control, measuring bank connection, 10+ categorization, and retention—not checklist completion alone.

Replace the goal of raising checklist completion from 61% to 75% with a provisional target: raise seven-day activation from 27% to 35% of sign-ups next quarter. Track day-60 retention as a lagging outcome and guardrail. This keeps the goal tied to Tidepool’s promise while making clear that improved activation is a hypothesis to validate, not a guaranteed retention lift.