Skip to content

Process

A clear process, with something to keep at every stage

Six stages, each with an artifact you keep and a timeline you can hold us to. You always know which stage you are in, what it produces and what happens next.

This is the same process whether the project is a two-week automation or a six-month platform. The stages get shorter, not fewer, because skipping one is how projects end up expensive.

The six stages of a MIO Labs project

  1. 01

    Discover

    1 week

    We map the problem, the people who live with it and the numbers behind it. No proposal is written before we understand what is actually breaking.

    You get: Problem brief and scope options

  2. 02

    Define

    1 week

    Scope, priorities and success metrics agreed in writing before anything gets built, so nobody discovers the budget halfway through.

    You get: Written scope and fixed quote

  3. 03

    Design

    1 to 2 weeks

    Prototypes and product design before a line of production code. You click through the product and change your mind while it is still cheap.

    You get: Clickable prototype

  4. 04

    Build

    4 to 12 weeks

    Iterative development with security and code quality built in from the start, not bolted on before launch.

    You get: Working software every two weeks

  5. 05

    Launch

    1 week

    A measured release with monitoring, team training and a rollback plan. Going live is a planned event, not a leap.

    You get: Production launch and handover

  6. 06

    Evolve

    Ongoing

    We measure how the product performs, fix what the data exposes and keep building on what works. We do not disappear after launch.

    You get: Monthly review and roadmap

Where it applies

The same six stages, whatever we are building

What changes is the length of each stage, not the shape of the project.

FAQ

How the engagement works

Why is discovery paid?

Because it is real work, and because free discovery is priced into the build everywhere else. You get a written brief, scope options and a fixed price, and the document is yours whether or not you continue with us.

What if the scope changes halfway through?

It usually does, and the two-week rhythm exists for exactly that. Changes inside the agreed scope are normal; anything that grows it is quoted separately before we start it, never absorbed and invoiced later.

How involved does our team have to be?

Heavily during discovery, roughly an hour every two weeks during the build, and properly involved again at launch. Projects fail when the client disappears after the kickoff meeting.

What do we get if we stop after discovery?

The brief, the scope options and the estimates. You paid for the thinking, so you keep it, including the parts that argue against building anything.

Start with Discover.

One week, one written brief, one fixed price for what follows. Yours to keep either way.

Start a projectSee all services