Four weeks from idea to a working, clickable product your fee earners and clients can try, and the evidence to proceed, pivot or pause before a full build.
4 weeks3 phases1 validated concept
Week 1 · The scope
We cut the idea down to the journeys that prove it
A concept workshop with the partners and fee earners behind the idea: the core value for the end client, the two or three user journeys that show it.
Weeks 2-3 · The build
Real prototypes your fee earners can click through
Rapid agile sprints on the foundations we use in production: real screens, real flows and simulated matter data, reviewed with you every few days.
Week 4 · Validation
Fee earners and clients use it while we watch
Sessions with the people who would use it day to day, and a small group of trusted clients where it helps. Evidence gathering so you can see what works.
The verdict · Proceed, pivot or pause
A decision with the evidence attached
A validation report and a recommendation the partnership can act on as a next step.
0102030405
Scroll
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 changing course costs a month at most. Each phase leaves a working document behind.
the cheapest point in the whole journey to change your mind
Phase 01 · Week 1
Cut the idea down until it fits four weeks
The concept workshop ends with an MVP specification that is deliberately small: the core value for the end client, the two or three journeys that prove it, and a Later list for everything else. That discipline is what makes the month possible.
Core value separated from the nice-to-haves
User journeys mapped with the delivery team
Technical feasibility checked before the build starts
MVP specification · Due diligenceWeek 1
Connect the data roomDocuments pulled straight from the VDRIn
Contracts flagged against the playbookChange of control, assignment, exclusivityIn
Partner sign-offOne click, with commentsIn
Red-flag report for the clientIn plain English, sent from the matterIn
SPA draftingLater
Billing exportLater
Client chatLater
Two journeys · data room to flags, flags to red-flag report
Phase 02 · Weeks 2-3
Build the screens people will actually click
Two rapid agile sprints turn the specification into a working product: real screens, real flows and simulated matter data, built on the foundations we use in production. You see it working every few days and steer it as it grows.
Clickable end to end, on real devices
Reviewed with you every few days
Built to carry on into a full build
Week 1 · WireframeWeek 3 · Working
drag me
Phase 03 · Week 4
Put it in front of fee earners and clients
The people who would use it day to day work through set tasks while we watch, and a small group of trusted clients joins where it helps. Every task is timed, every hesitation noted, and the findings are written up with the evidence behind them.
Task-based sessions with fee earners
Trusted clients invited in where it helps
Usability and adoption findings written up
Session notes · Due diligenceTime on task
Associate · Corporate
Found the change of control consents without being shown where to look.
Task 1 · 0:38
Partner
Wanted the red-flag report to go out on the firm's letterhead.
Task 3 · 1:12
Client · General counsel
Asked what the non-compete means for the rest of their group.plain-English labels for clients
Task 2 · 2:05
PSL
Checked that the playbook wording matches the firm's precedent.
Task 2 · 0:51
The verdict · End of week 4
Proceed, pivot or pause
The month ends with a recommendation the partnership can act on: proceed to a full build with the plan attached, pivot the concept with the changes named, or pause with the lessons written down for the next idea.
A recommendation with the reasons attached
A full build estimate if the answer is proceed
Every finding kept for the next idea
ProceedPivotPause
The reasons
Fee earners and clients finished the core journey
Clients asked for plain-English summaries of each flag, now in the build scope
Full build plan and estimate attached
What you leave with
Evidence you can hold in your hand
MVP specification
The core value, the features and the user journeys: the document a full build starts from.
The prototype
A working, clickable product with the key features and client touchpoints. Yours to keep showing.
Validation report
What users did, what they said and what the sessions show about adoption, analysed and written up.
The recommendation
Proceed, pivot or pause, with the reasons attached.
MVP specification
Validation report
Proceed · pivot · pause
decided on the evidence
From our work
The team that builds the prototype builds the product
Prototypes are built by the team that takes products to production, on the same foundations, so a proceed verdict carries straight into the full build. Every shortlisted team in the Global Innovation Accelerator left with a clickable prototype they had tested with real users.