Northwind Studios
Series A · 28 person team
From a 6-step wizard to a 90-second activation in 4 weeks
Cut signup-to-aha-moment from 9 minutes to under 90 seconds.
Replace a cluttered, multi-step trial signup with a focused activation flow that gets new users to their first piece of value before they have time to second-guess. Goal: lift trial-to-paid conversion measurably within the first 30 days post-launch and instrument the funnel so the next change can be made on data.
New · B2B SaaS
Onboarding rebuild.
Cut signup-to-aha-moment from 9 minutes to under 90 seconds.
Sample mockup · illustrative only
- Industry
- B2B SaaS
- Timeline
- 4 weeks
- Team
- 3
- Service
- Web + Software
- Project tier
- Web App MVP / $19,995
The Problem
What was broken.
The team had grown from 800 to 4,000 trial signups per month but trial-to-paid had drifted south. The existing onboarding was a six-step wizard built by the founding engineer in a hurry: account, workspace, invite teammates, pick a plan, integrations, then dashboard. Drop-off was concentrated at step three (teammates) and step five (integrations). The product analytics setup was patchy — the team knew conversion was bad but couldn't pinpoint why without re-running queries by hand.
Our Approach
How we framed it.
We treated the onboarding as one product, not a sequence of forms. Two founders interviewed eight recent trial users on Loom while we read the support backlog. We rebuilt the flow as a single-screen, progressively-disclosed activation experience: pick a starter template, see your first dashboard pre-populated with sample data, then optionally invite teammates after the aha moment. Stripe paywall moved from step four to a soft prompt after first value. Every meaningful step instrumented in PostHog with a documented event taxonomy.
Capability proof
What this case demonstrates.
This case makes the hidden work visible: strategy, architecture, delivery control, quality evidence, and handoff.
01 / Product judgment
Problem framed before UI
The team had grown from 800 to 4,000 trial signups per month but trial-to-paid had drifted south. The existing onboarding was a six-step wizard built by the founding engineer in a hurry: account, workspace, invite teammates, pick a plan, integrations, then dashboard. Drop-off was concentrated at step three (teammates) and step five (integrations). The product analytics setup was patchy — the team knew conversion was bad but couldn't pinpoint why without re-running queries by hand.
02 / Technical depth
8 stack decisions
Next.js 15, TypeScript, Postgres, Prisma, Stripe Billing, PostHog
03 / Delivery discipline
6 delivery checkpoints
Audit + interviews / Funnel taxonomy / Aha-moment prototype
04 / Handoff quality
6 shipped artifacts
Single-screen onboarding with three starter templates / Sample-data seeder shared between trial signup and the team's demo environment / PostHog event taxonomy + 4 named conversion funnels
Production artifacts
Inspect the work behind the visible result.
Each case exposes the surfaces, systems, evidence, and handoff package that make the shipped product usable after launch.
Experience layer
Buyer or user surface
Single screen. One headline: 'Start with a template'. Three large template cards (Marketing team, Sales team, Solo). Sample data pre-loaded in the dashboard within 8 seconds of click. Stripe paywall replaced with a soft 'Upgrade when you're ready' banner that appears after the user creates their first real artifact.
Proof 01
Cut signup-to-aha-moment from 9 minutes to under 90 seconds.
Proof 02
Read the last 90 days of support tickets, watched 30 Hotjar session recordings, ran 8 user interviews on...
Proof 03
Single-screen onboarding with three starter templates
Production signals
Instrumented
Events and funnels named before handoff.
Observable
Errors, logs, alerts, or dashboards included.
Release-ready
Deployment or store-release path included.
Handoff-ready
Owner can keep operating after delivery.
Before / after · product UI mockup
Industry · B2B SaaS
Before:Six-step modal wizard. Fields above the fold include first name, last name, company name, company size, role, and 'how did you hear about us'. Stripe paywall sits at step four with a 'choose a plan' selector and three pricing tiers in dense type. Visually busy, dense slate UI with no clear primary action.
After:Single screen. One headline: 'Start with a template'. Three large template cards (Marketing team, Sales team, Solo). Sample data pre-loaded in the dashboard within 8 seconds of click. Stripe paywall replaced with a soft 'Upgrade when you're ready' banner that appears after the user creates their first real artifact.
How the engagement ran.
- 01Day 1
Audit + interviews
Read the last 90 days of support tickets, watched 30 Hotjar session recordings, ran 8 user interviews on Loom. Wrote a one-pager mapping every drop-off point.
- 02Day 3
Funnel taxonomy
Defined the event schema in PostHog before writing any UI. Every CTA, every form submit, every error state gets a named event. No anonymous clicks.
- 03Week 1
Aha-moment prototype
Built three template-onboarding flows in Figma + a coded Storybook variant. Internal team voted; one variant won decisively.
- 04Week 2
Build + sample data
Implemented the template engine, sample-data seeder, and removed four wizard steps. Stripe checkout component refactored as a controlled drawer.
- 05Week 3
Instrument + soak
Wired PostHog funnels and saved them as named insights. Ran the new flow internally for 5 days, fixed three regressions, two copy issues.
- 06Week 4
Ramp + handoff
50% traffic ramp via feature flag, watched dashboards for 72 hours, cut to 100%. Handoff Loom + runbook for the in-house team.
- 1
Day 1
Audit + interviews
Read the last 90 days of support tickets, watched 30 Hotjar session recordings, ran 8 user interviews on Loom. Wrote a one-pager mapping every drop-off point.
- 2
Day 3
Funnel taxonomy
Defined the event schema in PostHog before writing any UI. Every CTA, every form submit, every error state gets a named event. No anonymous clicks.
- 3
Week 1
Aha-moment prototype
Built three template-onboarding flows in Figma + a coded Storybook variant. Internal team voted; one variant won decisively.
- 4
Week 2
Build + sample data
Implemented the template engine, sample-data seeder, and removed four wizard steps. Stripe checkout component refactored as a controlled drawer.
- 5
Week 3
Instrument + soak
Wired PostHog funnels and saved them as named insights. Ran the new flow internally for 5 days, fixed three regressions, two copy issues.
- 6
Week 4
Ramp + handoff
50% traffic ramp via feature flag, watched dashboards for 72 hours, cut to 100%. Handoff Loom + runbook for the in-house team.
Deliverables
What we shipped.
- ✓Single-screen onboarding with three starter templates
- ✓Sample-data seeder shared between trial signup and the team's demo environment
- ✓PostHog event taxonomy + 4 named conversion funnels
- ✓Stripe checkout drawer that defers commitment
- ✓Feature-flag wrapper for safe rollout
- ✓Handoff Loom + 14-page runbook + Linear backlog of next experiments
Outcomes.
engagement targetsTarget: cut median time-to-first-value from ~9 min to under 90 seconds
Goal: lift 14-day trial-to-paid conversion measurably (instrumented to prove it)
Plan: remove 4 of 6 mandatory onboarding steps without losing required data
Plan: move Stripe checkout post-aha-moment, default to monthly to lower commitment
Plan: document event taxonomy so the next 5 experiments can run without engineering
Plan: Loom-recorded handoff so the team can iterate without us in the room
Honest challenges
What we got wrong (or almost wrong).
The pretty version of any case study skips this part. We don't.
- 01
PostHog event names had to be back-ported into the legacy flow first so before/after could be measured fairly.
- 02
Sample data seeder had to look real enough to be useful but clearly fake enough that no one would email the fictional contacts. Solved with a watermark + clearly-labeled 'sample' badges.
- 03
Stripe billing component was load-bearing for revenue — refactor was done behind a feature flag with a fast rollback plan.
In our own words
We treat onboarding as the product, not a form. Five days post-cutover the funnel was already telling us which two copy lines to test next — that compounding clarity is the part the team will keep getting value from long after we're gone.
From the Hayaiti team
Engineering · design · security
Technical blueprint
How the work holds together.
Buyers should see that the visual layer is backed by architecture, quality gates, and operational ownership.
Experience
1Application
2Data
3Operations
4Security
5Stack used
8 technologiesRelated
Other cases like this.
Helix Health
HIPAA-ready intake portal
Replace clipboard intake with a 7-minute, accessible, HIPAA-ready web flow.
FintechFoundry Capital
Broker API + nightly reconciliation
Stand up a reliable broker integration with nightly reconciliation in three weeks.
DTC E-commerceAperture Goods
Shopify Hydrogen replatform
Move a slow, theme-bloated Shopify storefront to a fast Hydrogen build.
Want a case study like this?
Want this level of production quality on your project?
Send a short brief and we'll reply with scope, timeline, price direction, and the first technical recommendation.