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.

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.

MEMORANDUM

To: Onboarding Squad From: Product Team Subject: Onboarding Funnel Analysis & Prioritized Fixes

Our last 90 days show 12,400 signups, but we face a steep 59% drop-off immediately after signup (reaching only 41% at data source connection), followed by a massive drop at team invites (down to 9%). Because week-2 retention jumps from 11% to 62% for users who build a first chart, removing friction before that milestone is critical.

Here is where we are losing people and the fixes, ordered by priority:

1. The Data Connection Blockade (Fix First)

• Where we lose people: We drop 59% of users right at the data connection step.² Support tickets confirm why: 41% lack database credentials, and 18% experience sync failures. Forcing product managers and marketers—who are not data engineers—to input host, port, SSL modes, and select from raw database tables while blocking the UI for up to 20 minutes is a conversion killer.
• What to fix:
• Add a pre-loaded Sample Data / Demo Workspace option so users can experience the product immediately without connecting a live database.
• Make data connection skippable or move it after the first chart experience.
• Simplify the CSV upload option or provide pre-built connectors with clear, inline tooltips instead of a 14-page setup guide.

2. The Premature Team Invite Wall (Fix Second)

• Where we lose people: Reaching a first chart drops to 33%, but inviting teammates plummets to 9%—a catastrophic 24-percentage-point drop right before value is fully realized.¹ Users are being asked to advocate for a tool before they’ve even proven its worth to themselves.
• What to fix:
• Remove the team invite step from the core linear onboarding path entirely.
• Relocate the invite prompt to the dashboard or settings menu once the user has successfully built and saved their first chart.

3. Redundant Survey Friction (Fix Third)

• Where we lose people: Screens 3 ("What's your role?") and 4 ("How big is your team?") add unnecessary micro-friction right after email verification.
• What to fix:
• Combine these into a single, clean optional screen or infer them from workspace setup later to streamline time-to-value.

Fixing data connection roadblocks and removing premature team invites will directly protect our week-2 retention (which hinges on reaching that first chart).