What we do · Build

Prototype

Four weeks from idea to a working, clickable product your fee earners and clients can actually try - the evidence to proceed, pivot or pause before you commit to a full build.

4 weeks3 phases1 validated concept
The premise

A slide deck has never survived contact with a user

Ideas look strongest the moment before someone tries to use them. A prototype forces the question early: put a working, clickable version in front of fee earners and clients within four weeks, watch what they do with it, and decide - proceed, pivot or pause - on evidence rather than enthusiasm.

It is the cheapest point in the whole journey to be wrong, and the fastest way to make the full-build decision an easy one.

The build · Four weeks

Idea to clickable in a month

Three phases, hard-scoped to four weeks. Long enough to build something real, short enough that being wrong is cheap.

Week 1

Concept workshop

The MVP scope, pinned down: the core value for the end client, the user journeys that matter, and everything else cut to Later. Stakeholders aligned before a line of code.

Weeks 2-3

Rapid agile sprints

We build a functional, clickable prototype - real screens, real flows, simulated data. Not wireframes, and not a deck: software your fee earners can hold.

Week 4

User and client validation

Fee earners and a small group of trusted clients use it while we watch. Feedback captured, usability analysed, and the verdict written up with evidence.

The scope · Week 1

Cut until it fits in four weeks

The concept workshop ends with an MVP specification that is deliberately small: the core value proposition, the two or three journeys that prove it, and a Later column that keeps everything else honest. Scope discipline is what makes the month possible.

  • Core value isolated from nice-to-have
  • User journeys mapped with the delivery team
  • Technical feasibility checked before commitment
The verdict · Week 4

A decision, not a feeling

Validation week produces numbers and quotes, and both go into the verdict: proceed to a full build, pivot the concept, or pause with nothing lost but a month. Whichever way it lands, the partnership decides on evidence.

  • Internal sessions with the fee earners who would use it
  • Trusted clients invited in where it helps
  • Proceed, pivot or pause - with reasons attached
What you leave with

Evidence you can hold in your hand

  • MVP specification

    The product's core value, features and user journeys - the document a full build starts from.

  • The prototype

    A functional, clickable product simulating the key features and client touchpoints. Yours to keep showing.

  • Validation report

    What users did, what they said, and what the data says about adoption - analysed, not anecdotal.

  • The recommendation

    Proceed, pivot or pause - with the reasons attached, so the next decision is an easy one.

Why Purple

Built by the team that would build the product

Our prototypes are not throwaway mocks from a design agency - they are built by the same team that takes products to production, on the same foundations. If the verdict is proceed, nothing is wasted: the prototype becomes the blueprint.

See where prototypes have ended up in our work, or read what a full build involves when the answer is yes.

The first step

Put your idea in front of users

Four weeks, one clickable product, and a decision made on evidence. Bring the idea; we will bring the build.