Skip to content
Devolark

How an idea becomes a product

Four steps, each ending in a decision. Stopping early is a result, not a failure.

  1. Discover

    1–2 weeks

    Is this worth building, and for whom?

    What we do
    • Look at the market, competitors and constraints, including regulation
    • Interview the people who have the problem
    • Pick one priority customer and map their journey
    • Define the value: which pain, and why this beats what they use today
    • Sketch the business case: costs, revenue, risks
    • Test the riskiest assumption with real people
    What you get
    • A one-page product brief: problem, users, success metric
    • A minimum viable idea — small and specific enough to test
    • A scoped plan, or a clear reason to stop
    From your side
    • Whoever makes the go / no-go call
    • Someone who talks to your customers
    Decision

    Go, change the idea, or stop.

  2. Design

    1–2 weeks

    What is the smallest version that proves it?

    What we do
    • Write the product vision on one page
    • Set the success metrics for the MVP
    • Agree the MVP scope: what's in, and what's out
    • Design flows, data model and architecture
    • Build a clickable prototype and test it with users
    What you get
    • A prototype you can show to users or investors
    • MVP scope with success criteria
    • An architecture and delivery plan
    From your side
    • The decision-maker, to sign off the scope
    • Someone who knows your operations and systems
    Decision

    MVP scope and success criteria agreed.

  3. Build

    4–10 weeks

    Does it work for real users?

    What we do
    • Release working software every week
    • Demo every week — you see progress, not reports
    • Track progress against the agreed success criteria
    • Adjust the scope with you when we learn something
    What you get
    • A working MVP
    • Weekly releases you can try yourself
    From your side
    • Someone at the weekly demo who can make decisions
    Decision

    MVP measured against the success criteria.

  4. Launch & learn

    Ongoing

    What do we build next?

    What we do
    • Run a pilot with real users
    • Measure the few numbers that matter
    • Collect feedback and plan the next iteration
    What you get
    • Evidence from real use
    • A decision on what to build next
    From your side
    • Access to pilot users
    • The decision-maker for what comes next
    Decision

    Scale, change, or stop.

When we say stop

Sometimes the honest answer is not to build. We say so at the end of Discover, before the expensive part.

  • No one has the problem badly enough. People live with it, and won't change how they work to fix it.
  • It's already solved well enough. What people use today works, and a new product wouldn't be clearly better.
  • The smallest useful version is still too big. If the MVP can't be built in weeks, we look for a smaller idea first.

Not sure where your idea stands?

Check your idea

How we work with you

  • Weekly demos.

    You see working software every week, not status reports.

  • One accountable team.

    The people you meet are the people doing the work.

  • Yours to keep.

    When we build your product, the code, prototype and documents belong to you — whether we keep running it or hand it over to your team.