Activation & onboarding review

To: Onboarding Squad Subject: Fixing Our Activation Funnel: Priorities & Action Plan

Where We Are Losing People

Our biggest drop-off occurs at Step 5–8 (Connect Data): 59% of signups leave without connecting a data source.

We are asking PMs and marketers for database ports, SSL modes, and passwords they do not possess. 41% of our support tickets are “I don't have credentials,” followed by 18% for failed syncs. Furthermore, requiring a 20-minute, open-tab sync kills momentum.

Because Week-2 retention jumps from 11% to 62% once a user builds their first chart, our sole objective is getting non-technical users to that "aha!" moment in under two minutes.

---

What to Fix (In Priority Order)

#### 1. Add “Explore with Sample Data” & a Clear “Skip” Button (Step 5) * What: Let users bypass database connection entirely using a fully populated e-commerce or SaaS demo dataset. * Why: This is the highest-leverage fix. It immediately unblocks the 59% who drop off at Step 5 and the 41% who lack DB credentials, giving them an instant path to create a first chart and experience the product’s value on Day 1.

#### 2. Introduce “Invite a Data Teammate” at Connection (Step 6) * What: Add a 1-click option: “Don't have credentials? Send an invite link to your data lead to connect your warehouse.” * Why: Replaces a dead end with collaboration. The PM stays in the app using sample data while the engineer handles credentials asynchronously.

#### 3. Make Syncing Asynchronous (Step 8) * What: Run syncing in the background. Notify users via email/in-app alert when ready instead of forcing them to keep a 20-minute tab open. * Why: Directly addresses our second-biggest support issue (18% sync failures/cancellations) and eliminates the drop-off caused by tab abandonment.

#### 4. Pre-Populate the Dashboard; Kill the Blank Canvas (Steps 9 & 10) * What: When a user selects a template, generate it automatically with 3–4 standard charts instead of dropping them onto an empty canvas. Prompt them to tweak one existing chart. * Why: Bridges the 8% drop-off between connecting data (41%) and creating a first chart (33%). Editing an existing chart is far lower friction than building from scratch.

#### 5. Defer Email Verification and Profiling Questions (Steps 2, 3, & 4) * What: Move verification to a non-blocking banner at the top of the app, and cut or defer the role/team-size questions until after the user creates their first chart. * Why: Every barrier before core value reduces trial-to-paid conversion. Let users reach the product before demanding administrative tasks.

---

Next Step

Let’s implement Priority 1 (Sample Data) this sprint. It requires zero infrastructure changes to our warehouse sync logic and directly targets our biggest activation leak.

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).

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.