Sample-data onboarding pattern

How the pattern works

On first login, the user's workspace is seeded with sample data (sample customers, sample reports, sample documents). The user explores the populated product, sees what it can do, and then either clears the sample data or migrates it into real data.

Activation metric

Time-to-first-meaningful-interaction. Users with sample data should hit a meaningful interaction (filter, drill-down, configuration tweak) within 60 seconds of first login.

Implementation considerations

1. Create realistic sample data that reflects what real customers see. Generic 'Lorem Ipsum'-style data fails to show the product's value.
2. Mark sample data clearly — visual indicator (color, badge, watermark) so users do not mistake it for real.
3. Make 'clear sample data' a one-click action accessible from the dashboard.
4. Provide a 'replace with your real data' path that is at least as obvious as the 'keep sample' path.

Common mistakes

• Sample data that looks too perfect ('every metric is in the green'). Users intuit fakery and discount the product.
• No clear way to clear sample data. Users get stuck with mixed real + sample data.
• Sample data that does not reflect the user's likely use case. A B2B CRM seeded with retail-store customers loses credibility.

Variations

• Persona-based sample data — different sample sets for different user types, selected via initial questionnaire.
• Time-bombed sample data — automatically clears after 14 days if user has not imported real data.

Frequently asked

Does sample-data onboarding hurt retention?

Only if the transition to real data is poor. Done well, sample data accelerates time-to-aha and improves activation; done badly, users explore the sample, never set up real data, and churn.

Other onboarding patterns

• Linear walkthrough onboarding pattern
• In-product checklist onboarding pattern
• Just-in-time onboarding pattern
• Guided setup wizard onboarding pattern