Activation & onboarding review

MEMO To: Onboarding Squad From: Product Leadership Subject: Fixing the Onboarding Funnel

Team,

Looking at the last 90 days, the story is clear: getting users to their first chart is everything. Week-2 retention jumps from 11% to 62% once a user builds a chart.

Right now, we are losing 59% of signups before they ever connect data, and another 8% before they build that first chart. Why? Because our signups are PMs and marketers, yet we are forcing them through a data-engineer onboarding flow.

Here is where we are losing people and what we need to fix, in priority order:

1. Add a “Send to an Engineer” flow & Sample Data (Screens 5–6) * The Problem: 59% of users drop off before connecting data, and 41% of support tickets are “I don’t have database credentials.” PMs and marketers don't have Postgres passwords or understand SSL modes, and a 14-page guide won't help them. Because there is no skip option, they hit a hard wall. * The Fix: Add two buttons to Screen 5: “Explore with Sample Data” and “Invite an Engineer to connect data.” Let the PM experience the "aha" moment immediately with a sandbox dataset while their engineer handles the credentials in parallel. This also instantly fixes our low 9% teammate-invite rate by giving users a real reason to invite a colleague early.

2. Make data syncing asynchronous (Screen 8) * The Problem: We lose 8% of our total signups (nearly 20% of those who actually manage to connect data) between connecting a source and building a chart. A 20-minute progress bar that cancels if you close the tab is a conversion killer, and it's driving 18% of our support tickets. * The Fix: Move syncing to the background. Let users close the tab (or play with sample data) and email them the moment their data is ready. Also, replace the raw list of every database table (Screen 7) with smart defaults so non-technical users aren't overwhelmed.

3. Eliminate the "Empty Canvas" (Screens 9–10) * The Problem: A user picks a dashboard template on Screen 9, only to be dropped into a blank chart builder on Screen 10. Blank canvases cause analysis paralysis. * The Fix: Make the templates on Screen 9 actually populate pre-built charts on Screen 10 using their data (or the sample data). Give them a working chart immediately that they can tweak, getting them across that 62% retention threshold automatically.

4. Remove pre-value friction (Screens 2–4) * The Problem: We pause the flow for email verification and ask two CRM-style profiling questions before the user has seen the product. Every step here costs us momentum. * The Fix: Let users into the product immediately and require email verification later (e.g., before they can share a chart). Cut the “team size” question entirely, and only keep “role” if we use it to auto-select their dashboard template in Step 9.

Let's scope Item #1 for this sprint.

To: Onboarding squad Subject: Prioritize getting users to a useful first chart

Our biggest leak is before data connection: 59% of signups—7,316 people—never connect a source. Another 8 percentage points disappear before the first chart. Only 9% invite a teammate, but collaboration should come after users see value.

First-chart users have 62% week-2 retention versus 11% for everyone else. That makes time-to-first-chart our priority, although this correlation does not prove that creating a chart causes retention.

Fixes, in priority order

1. Remove the database-credentials gate. Offer a prominent sample-data path and a clearly explained CSV path. Let users request access from a data owner without abandoning onboarding. For database connections, replace the 14-page guide with source-specific instructions, inline examples, and actionable error messages.

Why first: Our audience is mostly PMs and marketers, yet onboarding assumes database expertise and access. “I don’t have the credentials” accounts for 41% of onboarding tickets. Sample data can demonstrate value immediately, but we should separately measure whether those users eventually connect their own data.

2. Make syncing resilient and asynchronous. Run syncs server-side so leaving the page does not cancel them. Show status, provide completion notifications, and support retries with clear failure explanations. Where technically feasible, sync a useful subset first rather than requiring a full load.

Why second: A wait of up to 20 minutes is already costly; requiring an open tab makes it fragile. Sync failures account for another 18% of tickets and block users who have overcome the access hurdle.

3. Deliver a chart, not another blank canvas. Recommend relevant tables rather than listing everything. Reduce twelve templates to a few guided choices, then populate a starter chart that users can edit.

Why third: Choosing a template and then seeing an empty builder breaks the promise of guidance. About 20% of connected users fail to reach a first chart. Focus on a useful result, not merely recording a chart-creation event.

4. Shorten the route to value. Move role and team-size questions until after the first chart, unless they directly personalize onboarding. Allow users to explore before email verification where security requirements permit.

Why fourth: These steps add friction before any payoff, but we lack screen-level evidence that they explain the largest losses.

5. Make invitations contextual. Prompt users to share a useful chart after success; keep invitations optional. Distinguish “ask a data owner for access” from “invite a collaborator.”

Why fifth: Low invitation rates may reflect weak activation, not a broken invitation screen.

Instrument every screen, connection method, and sync failure. Evaluate changes on useful first-chart completion, time to value, own-data activation, and week-2 retention—not just step clicks.