We helped a B2B founder turn a broad product concept into a focused SaaS MVP. Before development started, we defined user roles, core journeys, MVP priorities and navigation, and built interactive prototypes and a reusable design system.
Industry: SaaS & TechnologyService: Design & StrategyUpdated
Overview
The challenge
The founder understood the customer problem well, but the feature list had grown quickly. Different types of user needed different workflows, and nobody was sure what had to be in the first release.
Starting development straight away would have raised costs and led to avoidable rework. The founder needed product decisions made visible before anyone wrote code.
Too many features were competing for a place in the first release.
Admins, managers and end users each needed their own journeys and permissions.
UX questions left open would only have come to light during engineering, when changes cost more.
The solution
We set out the user roles, business goals and core problems, then agreed which workflows the MVP had to include.
We designed flows, navigation, dashboards, forms and key product states around what each user is trying to get done.
Interactive prototypes let the founder try the real experience before spending more on engineering.
Before and after
Before
Everything feels important
The first release held too many competing ideas.
After
Focused MVP
Features are ranked by how directly they deliver the core value to customers.
Before
A feature list
Flows and navigation existed only as ideas.
After
End-to-end journeys
The team can see exactly how users complete each key task.
Before
Open questions
Engineers would have had to make product decisions while building.
After
Clear design system
Reusable components and documented flows leave less room for guesswork.
Key features
The first release focuses on the workflows that matter most for proving value to customers.
Business impact
Lower product risk
Roles, navigation, dashboards, forms and key states are designed as one joined-up product.
Business impact
Clearer product direction
The founder and other stakeholders can review and test the product before full development.
Business impact
Less rework
Results
Clearer Roadmap
The team knows what belongs in the first release and what can wait.
Before: BroadAfter: Focused
Faster Decisions
Flows and prototypes make product decisions visible, so they get made sooner.
Before: AbstractAfter: Tangible
Smoother Handoff
Engineers receive clear workflows, components, states and priorities.
Before: AmbiguousAfter: Defined
Faster delivery
Starting from tested patterns cut repeated design work, so the founder had a prototype to review sooner.
Gave us tested patterns for sign-in and role permissions, which we adapted for admins, managers and end users.
Provided proven layouts for account settings and connected tools, so these screens did not start from a blank page.
Covered the loading, empty and error states that every dashboard and form in the product needs.
Defined how the product tells each user that something needs their attention or that a task is done.
Trust and control
Admins, managers and end users each have their own journeys and permissions, agreed before any code is written.
Access controlledCustomer, day-to-day and product information is shown the same way across every screen and journey.
ConnectedKey product states, including errors, are designed up front, so engineers know how the product should behave.
ReliableThe founder owns all the product designs, workflows, prototypes and components created for the project.
100% ownedWe started by setting out the user roles, business goals and core customer problems with the founder. Each idea on the long feature list was then ranked by how directly it helped prove value to customers. Only the workflows that mattered most went into the first release, and the rest were kept for later.
The founder received personas, feature priorities, information architecture, key workflows, responsive screens, interactive prototypes and a set of reusable components. Together they show how admins, managers and end users each move through the product, so engineers start with clear workflows, states and priorities instead of open questions.
Starting development straight away would have raised costs and caused avoidable rework. An interactive prototype let the founder and stakeholders try the real experience and settle UX questions while changes were still cheap. Engineering could then begin with decisions already made, rather than finding open questions halfway through the build.
If your feature list keeps growing and the first release is still unclear, we can help you agree an MVP and test it as a prototype first.