We A/B tested value-first onboarding (generate before subscribe) — here is what happened

We've been running an A/B test on our onboarding flow and the early results are interesting enough to write up.

The old sequence

Voice setup → connect account → subscribe → generate posts. Classic SaaS — get commitment early, then show value.

The problem: users were dropping at the subscribe step having never seen a single piece of output. They were being asked to pay for something they'd only read about.

The value-first sequence

Pick topics → generate 5 posts in your voice → review them → THEN connect and subscribe.

By the time they hit the paywall, they've already seen their content calendar for next week. Drop-off on the subscribe step is lower. Makes sense — it's a lot easier to say yes to a tool when you're already holding the output.

Why it works

The subscribe step isn't a commitment to something abstract anymore. It's "do you want to keep the posts you just made?" That's a very different ask.

The implementation details

A few things worth noting if you're building something similar:

• We run the sequence via a PostHog feature flag (onboarding-v2, variant value-first) — easy to roll back or adjust the split without a deploy
• The full-tab onboarding (not a popup) was intentional — popups close if you click away, which kills any flow that involves a file upload or multi-step form
• Preferences sync locally first (chrome.storage), then backend — so the extension is usable even if the API is temporarily unreachable

Full breakdown of both sequences and the design decisions behind each step: https://xreplyai.com/blog/xreplyai-onboarding-wizard?utm_source=devto&utm_medium=social&utm_campaign=blog-2026-05-12