Skip to content
MROOT

Focused Web MVP

Build the first version people can actually use.

Move beyond a feature list. Define one useful journey, build a working web application around it, and put a focused first version in front of the people it is for.

What you get

A useful deliverable. A scope you can review.

Move beyond a feature list. Define one useful journey, build a working web application around it, and put a focused first version in front of the people it is for.

Included in the starting scope

  • One core user journey with written acceptance criteria
  • Interface design and a working web application
  • Screens, data, access and integrations defined in the quote
  • Testing of the agreed journey and important failure states
  • Launch preparation and a documented technical handover

The starting point is one core web-product journey. Screens, data, access and integrations are written into the quote. Native apps, additional journeys and large migrations are separate scope.

Explore the thinking

Inspect the product decisions.

These fictional demos show approaches to a focused product. Their records explain what runs in the browser and what depends on a server.

Fictional product demo · FORMA 1.3

FORMA

Explore a guided product experience and its documented implementation boundaries.

A fictional demo, not evidence of a paid client launch, production authentication or business results.

Explore the demo record

Fictional product demo · RELAY 1.1

RELAY

A collaboration concept with its browser and server responsibilities documented separately.

A fictional demo. Its local illustrations do not establish live collaboration or delivery guarantees.

Explore the demo record

Examples explain design and implementation choices. Your product receives its own agreed scope and acceptance checks.

Working together

Know what happens next.

Work directly with Marc from the first brief to the agreed handover.

  1. Describe the goal

    Share what the business needs or what your first users should be able to do.

    A useful brief

  2. Agree the work

    Review a written scope, the deliverables, a schedule and a final quote before work begins.

    A written scope and quote

  3. Build and review

    Work directly with Marc and review the important decisions as the build takes shape.

    A working version to review

  4. Launch and hand over

    Check the agreed journey, approve publication and receive the access and documentation needed to continue.

    An agreed launch and handover

Scope, schedule and final quote agreed before work begins.

Before you decide

The practical questions.

Clear expectations make a better project.

Compare services and prices
What is included at this starting price?

The starting point is one core web-product journey. Screens, data, access and integrations are written into the quote. Native apps, additional journeys and large migrations are separate scope.

What costs are separate?

Domain, hosting, subscriptions, messaging and usage charges are separate. Additional pages, features, integrations and migrations are quoted separately.

When can we start?

Scope, schedule and final quote agreed before work begins.

Does sending a brief commit me?

No. The brief starts a conversation. Scope, timing and terms are confirmed before work begins.

Your next step

Tell me what needs to work better.

Describe the goal, what you have now and any practical constraints. We can work out the right starting point.

Scope an MVP