Activation & onboarding review

MEMO

To: Onboarding squad Re: Where we lose people, and what to fix first

Where we lose people

• Signup to connect (100% to 41%): The largest loss. Most of our users are PMs and marketers who don't have database credentials, and the flow gives them no way forward without them.
• Connect to first chart (41% to 33%): About a fifth of people who connect never build a chart. Sync and the empty canvas are the likely causes.
• First chart to invite (33% to 9%): Expected, since invites come after value. Lower priority for now.

Retention is the reason to care about the first chart: 62% of users who reach one are active in week 2, versus 11% of those who don't. This is correlational, since engaged users may be the ones who build charts, but it is the strongest signal we have.

What to fix, in order

1. Add sample data and a skip at step 5. Users without credentials currently hit a dead end. Sample data gets them to a chart in minutes, which is the milestone that predicts retention. This also targets the top support ticket (41%). Reason: highest expected impact on the number that matters.

1. Let people in before email verification, and drop the role and team screens from the critical path. Step 2 blocks all progress, and steps 3–4 ask questions before the user has seen any value. Move role and team to after the first chart, where they can personalize templates. Reason: removes the earliest friction, when drop-off is highest.

1. Rebuild the credentials path. Replace the 14-page guide with short, per-warehouse steps for Postgres, BigQuery and Snowflake, and add a "send these instructions to your data engineer" link that delivers a connect-only invite. The person who has the credentials is often not the person signing up. Reason: addresses the remaining credential tickets and the step 6 drop-off.

1. Fix sync. Let leaving the page not cancel the sync. Show partial results as tables finish. Pre-select likely tables and add search to the step 7 list. Make CSV upload the fastest route to a first chart. Reason: sync failures are the second-largest ticket category (18%), and cancellation on exit loses users mid-setup.

1. Make the first chart appear without effort. Templates (step 9) should render a live chart immediately. Replace the empty canvas at step 10 with a suggested chart the user can edit. Reason: a blank canvas is the last hurdle before the retention milestone.

1. Move team invites after the first chart, and prompt for them there. Keep the skip link. Reason: invites are useful but come after value; test this once the upstream fixes land.

Measurement

Track signup-to-first-chart as the primary metric, with week-2 retention as the outcome. Run fixes 1 and 2 as separate experiments so we can see which one moves the funnel.

To: Onboarding squad Subject: Fix access and sync before optimising chart creation

Our biggest measured loss is before data connection: 59% of signups, roughly 7,300 people, never connect a source. We ask PMs and marketers to complete a database setup that many cannot do themselves, then make a lengthy sync depend on keeping a page open.

Another 8 percentage points disappear between connection and first chart: about 20% of those who connect. Teammate invitations fall to 9% of signups, but we should establish whether collaboration is necessary for value before treating that as our next bottleneck.

First-chart users have much higher week-2 retention, 62% versus 11%. That makes chart creation a promising activation milestone, but does not prove that pushing everyone through a chart will cause better retention.

Fix in this order

1. Give users a route forward without database credentials. Offer a clearly labelled sample-data experience and make CSV upload a prominent alternative.¹ Add a setup hand-off that lets users ask a colleague to connect the source, then resume when it is ready. Replace the generic setup guide with short, source-specific instructions.

This addresses the largest measured loss and the strongest support signal: missing credentials account for 41% of onboarding tickets. That is a share of tickets, not signups, so we cannot yet quantify how much drop-off it explains. Sample data should demonstrate value while preserving a clear path to the user’s own data.

2. Make syncing durable and recoverable. Run syncs in the background so closing the page does not cancel them. Show meaningful status, explain failures and allow retries without repeating setup. Notify users when their data is ready.

A 20-minute foreground wait is a fragile requirement. Sync failures generate 18% of onboarding tickets and can waste the effort users have already invested.

3. Turn connected data into a useful first chart. Help users identify relevant tables instead of presenting every table equally. Use their chosen template to produce an editable chart from compatible data, with guided choices where mapping is needed. Do not finish template selection with an empty canvas.

This targets the roughly one in five connected users who never reach a chart. Measure whether they produce something useful, not merely whether a chart renders.

4. Remove avoidable preliminary work. Defer role and team-size questions unless their answers immediately improve setup. Review whether email verification must block exploration, retaining verification where required for account security.

These steps add friction before value, but we lack evidence that they drive the main loss.

Measure alongside delivery: instrument each screen, connection method, error and return visit. Test changes against first charts using customers’ own data, week-2 retention and trial-to-paid conversion. Track sample-data charts separately. Revisit invitations once we understand whether users need collaboration to succeed. To: Onboarding squad Subject: Fix access and sync before optimising chart creation

Our biggest measured loss is before data connection: 59% of signups, roughly 7,300 people, never connect a source. We ask PMs and marketers to complete a database setup that many cannot do themselves, then make a lengthy sync depend on keeping a page open.

Another 8 percentage points disappear between connection and first chart: about 20% of those who connect. Teammate invitations fall to 9% of signups, but we should establish whether collaboration is necessary for value before treating that as our next bottleneck.

First-chart users have much higher week-2 retention, 62% versus 11%. That makes chart creation a promising activation milestone, but does not prove that pushing everyone through a chart will cause better retention.

Fix in this order

1. Give users a route forward without database credentials. Offer a clearly labelled sample-data experience and make CSV upload a prominent alternative. Add a setup hand-off that lets users ask a colleague to connect the source, then resume when it is ready. Replace the generic setup guide with short, source-specific instructions.

This addresses the largest measured loss and the strongest support signal: missing credentials account for 41% of onboarding tickets. That is a share of tickets, not signups, so we cannot yet quantify how much drop-off it explains. Sample data should demonstrate value while preserving a clear path to the user’s own data.

2. Make syncing durable and recoverable. Run syncs in the background so closing the page does not cancel them. Show meaningful status, explain failures and allow retries without repeating setup. Notify users when their data is ready.

A 20-minute foreground wait is a fragile requirement. Sync failures generate 18% of onboarding tickets and can waste the effort users have already invested.

3. Turn connected data into a useful first chart. Help users identify relevant tables instead of presenting every table equally. Use their chosen template to produce an editable chart from compatible data, with guided choices where mapping is needed. Do not finish template selection with an empty canvas.

This targets the roughly one in five connected users who never reach a chart. Measure whether they produce something useful, not merely whether a chart renders.

4. Remove avoidable preliminary work. Defer role and team-size questions unless their answers immediately improve setup. Review whether email verification must block exploration, retaining verification where required for account security.

These steps add friction before value, but we lack evidence that they drive the main loss.

Measure alongside delivery: instrument each screen, connection method, error and return visit. Test changes against first charts using customers’ own data, week-2 retention and trial-to-paid conversion. Track sample-data charts separately. Revisit invitations once we understand whether users need collaboration to succeed.