Activation & onboarding review

To: Onboarding Squad Subject: Where onboarding is leaking—and what to fix first

The biggest loss is before a data source is connected: only 41% of signups get that far. Another 8 percentage points drop before a first chart. Just 9% of signups invite a teammate. The strongest activation signal is the chart: week-2 retention is 62% for users who reach one, versus 11% for those who don’t. Prioritize getting people to a useful chart; treat invites as a later step.

Fixes, in priority order

1. Offer a sample-data path that reaches a real first chart. Let users skip connecting their own data and explore a preloaded dataset, with a clear route to connect later. Many signups are PMs and marketers, and the most common onboarding ticket is missing database credentials (41%). A required technical connection is an especially poor first step for them. This also gives users value while they wait for access.

1. Make connecting data simpler and recoverable. Replace or supplement the 14-page guide with short, connector-specific instructions and troubleshooting. Validate credentials early, explain the required access, and offer a clear retry path. Don’t cancel a sync when someone leaves the page; send progress and failure notices and let users resume. The credential and sync tickets point to concrete blockers, and successful connection is the gateway to the high-retention chart experience.

1. Get users to a chart with fewer decisions. Replace the database-wide table list with suggested tables and plain-language descriptions; cut the 12 dashboard templates to a few recommended starting points. Provide a prebuilt chart or guided first-chart flow rather than an empty canvas. The 8-point drop between connection and first chart, plus the sync burden, suggests too much work remains after connection.

1. Remove early friction that doesn’t create value. Test deferring email verification until after users enter the product, and move role/team questions until they can personalize something useful. These steps currently delay access before users see value.

1. Make inviting a teammate contextual, not a hurdle. Keep it optional; prompt after a user has made or shared a chart, and explain the benefit. Only 9% of signups invite someone, but chart reach—not inviting—is the clearest retention signal.

Track step conversion and time-to-first-chart by path, especially sample-data versus live connection, before expanding the changes.

Onboarding: where we lose people and what to fix first

Sep 25, 2026 · @Martin Slaney

To: Onboarding squad

Bottom line

Onboarding works for people who reach a first chart: 62% of them are still here in week 2, against 11% of everyone else. Two-thirds of signups never get there, and most of those stop at "Connect your data", where we ask product managers and marketers for database credentials they don't have.

Where we lose people (last 90 days, 12,400 signups)

• Signup → connect data: 59% lost (\~7,300 people). The biggest leak by far. The top support ticket (41%) is "I don't have the database credentials."
• Connect → first chart: \~990 more lost, a fifth of those who connected. Syncs take up to 20 minutes, die if you leave the page, and "my sync failed" is the second-biggest ticket (18%).
• First chart → invite: 33% → 9%. Real, but downstream of the first two.

Caveat: we have no step-level data for screens 2–8, so we can't split the 59% between verification, the two questions and the connection form. The ticket data points hard at the form.

What to fix, in order

1. Let people reach a first chart without their own data. Add a sample dataset and a skip on screen 5, and land them on a ready-made chart. Why: it goes around the step that loses most people, and the first chart is the moment that predicts retention.
2. Let them hand off the credentials step. "Ask a teammate to connect" sends an engineer a secure link to fill in the connection form. Why: it answers the 41% ticket directly and turns the blocker into an invite.
3. Make syncing forgiving. Run it in the background, keep it going when they leave, email them when it's ready, and load a small sample of rows first so a chart appears in minutes. Show plain-language errors with a retry. Why: a 20-minute wait that punishes leaving the page is where connected users die, and it's the 18% ticket.
4. Don't start from an empty canvas. Use the role answer from screen 3 to suggest two or three templates instead of twelve, and draw the first chart automatically. Why: we already ask the role and do nothing with it; a blank builder is hard for non-analysts.
5. Trim the steps before connecting. Let people in before they verify their email (verify within a day), and drop or defer the team-size question. Why: cheap to do, but unmeasured, so instrument first rather than assume it's a big win.
6. Move the invite prompt to after value is shown, such as when someone saves or shares a chart. Why: people invite colleagues to something useful, not to a setup screen.

How we'll know it worked

• Instrument every screen, 1 to 11, before shipping anything.¹
• Judge fix 1 by how many sample-data users go on to connect real data and are retained in week 2, not by first-chart rate. A chart of sample data can lift that metric without anyone sticking around, so don't assume the 62% carries over.

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

Summary: Reaching a first chart is what predicts retention (62% at week 2 versus 11% otherwise). Only 33% of signups get there, and the biggest loss, 59% of signups, happens before they connect data. Most of our users are PMs and marketers who can't complete a database connection alone.

Fixes, in priority order

1. Add sample data and a skip option on the "Connect your data" screen. The most common ticket (41%) is "I don't have the database credentials." We ask non-engineers for host, port and SSL mode before they've seen any value. Sample data lets them reach a chart in minutes, and they can connect real data later. Caveat: sample-data users may retain worse than the 62% figure, which likely reflects real data. Track them as a separate cohort and prompt them to connect real data after their first chart.

2. Make it easy to get credentials from someone else. Add a "Send this to your engineer" option: a shareable link or prefilled email containing the connection form and a short setup checklist. Replace the 14-page guide with inline, per-field help. Promote CSV upload as the no-engineer path, since it's currently one of four equal options.

3. Fix the sync experience and its failures. Syncs run up to 20 minutes and cancel if the user leaves. Run them in the background, send an email when they finish, and let users start exploring once the first tables land. Then look at the 18% of tickets that say "my sync failed" and surface specific error messages. In the table-selection step, preselect a sensible default instead of listing every table.

4. Get people to a first chart without an empty canvas. We show twelve templates, then a blank chart builder. Cut the choice to two or three based on role, and auto-generate a first chart from the synced data (or sample data) that the user can edit. This targets the 41% → 33% drop and shortens time to value.

5. Remove friction at the front. Let users into the product before email verification, and enforce it later (e.g., before inviting teammates). Move the role question ahead of template selection, where it drives the default, and drop or defer team size unless something uses it. These are cheap fixes, but I'm ranking them below the others because I can't yet show they're a big loss.

6. Move the invite prompt to after the first chart. The 9% invite rate is 27% of users who reach a chart, so it's mostly a downstream symptom. Fix activation first. Then trigger the invite prompt right after a first chart is created, with a message like "Share this chart," rather than as a generic final step.

Measure first The funnel jumps from signup straight to data connection, so we can't see how many people drop at email verification, role, team size, or the connection form. Add per-screen events this sprint, before changing anything, so we can confirm the ordering above and measure each fix.

Success metrics: signup → first chart (33% today), share of users who connect real data within 7 days, sync failure rate, and week-2 retention split by sample-data versus real-data users.