Skip to content
CAPSOLTECHNOLOGIES
MenuClose
03Service line

Product strategy & MVP development

Deciding what to build first, and being willing to argue about it.

At a glance
Disciplines
Design · Engineering · Growth
Stages
5 in sequence
Duration
Quoted after scoping
AFraming

An MVP is not a smaller version of the full product.

It is the smallest thing that can prove or kill the assumption the business is resting on. Those are different objects, and the difference between them is usually a quarter of runway.

This line is where we are most likely to disagree with you in the first month, and where that disagreement is worth the most.

BScope

What is in scope

MVP design and rapid prototyping
The narrowest build that produces a real signal.
Product thinking and feature prioritisation
What ships first, what waits, and what gets written down as explicitly out of scope.
User journey mapping and experience architecture
Where the product sits in a user's day, and what it is competing with for that minute.
Conversion-focused design
Designing the paths that have to convert as first-class objects, not as a landing page bolted on later.
Data-informed product decisions
Instrumentation designed in from the start, so the next decision has evidence behind it.
CSequence

The order the work runs in

Stages, not a schedule. We do not publish durations we have not agreed with you — the sequence is fixed, the length depends on what we find in scoping.

  1. 01

    Assumption

    What has to be true for this business to work, stated in one sentence.

  2. 02

    Scope

    The smallest build that tests it. Written as a list of what we are not building.

  3. 03

    Prototype

    Something clickable, fast, in front of real users.

  4. 04

    Build

    The MVP proper, instrumented from the first commit.

  5. 05

    Read

    What the data says, and an honest recommendation — including the one where we tell you it did not work.

DDeliverables

What you have at the end

  • A written scope, with an explicit out-of-scope list
  • Prioritised feature set with the reasoning attached
  • Journey maps for the paths that matter
  • A working, instrumented MVP
  • An analytics plan tied to the assumption being tested
ESpecific to this line

What we will argue with you about

Scope, in week one. Almost every MVP brief we see contains two products. Cutting one of them is the single highest-value thing that happens in a strategy engagement, and it is uncomfortable every time.

We will also push to keep the admin panel ugly. It is the most common place an MVP budget quietly disappears, and no user will ever see it.

FNext

Where to go from here

Start a project briefHow we work

Next line — 04 Engineering & technology