B2B software
Focused Pulse from a sprawling SaaS idea into a shippable MVP
Pulse · 2025 · 14 weeks
Pulse had a long feature board and a tight runway. Adexcell helped them choose one workflow buyers would pay to finish, prototype onboarding with real operators, and ship a multi-tenant MVP with billing, roles, and activation analytics.
Role
Product discovery, UX, full-stack MVP build
Timeline
14 weeks
Delivery
North America · Remote-first founding team
1 core workflow
MVP scope
5 validated before build
Design partners
Under 12 minutes
Time to first value
Week-2 return 68%
Beta retention
Challenge
The founding team disagreed on the first customer, the activation moment, and what evidence investors needed next. The roadmap mixed admin tools, reporting, integrations, and edge cases. Building everything would have burned six months before a single qualified user completed a job in the product.
Solution
We ran a short discovery sprint, picked one end-to-end workflow, and designed the product around that path. The MVP included multi-tenant accounts, roles, Stripe subscriptions, an admin surface, and event tracking for signup → first value. Everything else stayed on a dated roadmap with explicit “not now” rationale.
Approach
- 01
Interview target operators and map the costly manual process Pulse replaces
- 02
Define one activation event and the screens required to reach it
- 03
Prototype onboarding and validate with five design partners
- 04
Build the multi-tenant core, billing, and observability layer
- 05
Run a closed beta, instrument activation, then plan the public release
Project timeline
Weeks 1–2
Problem framing
Stakeholder workshops, competitor teardown, and a written MVP brief with success metrics.
Weeks 3–4
Prototype & partner tests
Clickable onboarding prototype tested with design partners; scope locked against the activation event.
Weeks 5–10
MVP engineering
Auth, tenancy, core workflow, Stripe billing, admin tools, and production observability.
Weeks 11–12
Closed beta
Invite-only usage, weekly office hours, and a punch list for onboarding friction.
Weeks 13–14
Release readiness
Docs, support macros, pricing page, and a public launch checklist.
Project notes
Engagement
Tell us the problem. We will return with a plan.
Share goals, constraints, timeline, and the systems you already run. You get a clear recommendation — fit, approach, and next step — without a theatrical pitch.