Prototyping and solution development
We turn a defined problem into a working prototype that decision-makers can test before they fund a build.
A prototype answers the question a slide deck cannot: does this work with our data and our people? We build one on controlled data, put it in front of the people who will use it, and recommend build, buy or stop.
What this covers
- Problem framing and success criteria
- Prototype on controlled data
- Proof of concept with the people who will use it
- Build, buy or stop recommendation
- Path from prototype to production build
Typical engagements
- A prototype before a business case
- A proof of concept against a vendor claim
- A build, buy or stop review of an existing idea
How an engagement runs
Enquiry
You describe what has to change. We reply in writing with questions.
Scoping
One conversation to agree the problem, the people affected and how the result will be accepted.
Proposal
A written scope, acceptance criteria, a price and a start date.
Delivery
We lead the work. Decisions, risks and changes are recorded as they happen.
Acceptance
The result is checked against the criteria agreed at the start.
Handover
Documents, access and records pass to your organisation.
Close
A short written close-out, and a support retainer if you want one.
Who this suits
Executives who must decide on a build and want evidence before the business case.
Teams with a problem that existing products do not fit.
We build on: Vercel, Neon, Supabase, Clerk.