Service / 01 · Prototype sprint
Monday, an idea.
Friday, something you can click.
Most partners come back in six weeks with a deck. We come back in five working days with a prototype you can click through, break, and show to someone whose opinion matters. One senior team, one week, and a decision made against something real.
The week
A clickable product in five working days.
Real screens, real flows, real code — and a decision made against something you can hold.
The week Mon → Fri
The detail
What you actually get.
Deliverables
What exists at Friday, 5pm
- Mon
- A written scope: the users, the one journey that matters, and an agreed definition of “working”.
- Tue
- Key flows designed and pressure-tested — AI-drafted, senior-directed.
- Wed
- The core journey running as real code, not a linked-up mock-up.
- Thu
- Edge cases, polish, and a senior engineering review.
- Fri
- A clickable prototype in your hands, a recorded walkthrough, and a written path to v1.
The fork
Where the sprint goes next
- Continue to an MVP build — the prototype becomes the first increment, not a throwaway.
- Take it in-house — repo, designs and decisions hand over to your team.
- Stop — you keep 100% of the code, the designs and the IP, and you found out in a week instead of a quarter.
Team shape
The proof
Where this has already run.
Client-scale figures are the clients’ own public figures, shown as client context — never as Rubikal outcomes.
A transit brief that arrived as a requirements document and left as rider apps on three stores.
A grassroots delivery co-op, productized web-first and then carried to native apps.
Scope agreed in short cycles alongside a hardware release calendar, since 2019.
Before you ask
The questions that decide it.
My idea is bigger than one week.
Most are. We scope the sprint around the single journey that decides whether the thing is worth building, and park the rest in the v1 path. Bigger programmes run as consecutive sprints — the second one starts from working code rather than a blank page.
Who owns what comes out of it?
You do — 100% of the code, the designs and the IP, from the first commit. That is true whether you continue with us or never speak to us again. NDAs are signed before day one.
What happens on the Monday after?
You get a written path with options sized to where the prototype landed: a lean MVP, a scale-up, or nothing at all. There is no obligation attached to the sprint and no automatic rollover.
The other four.
A clickable product in five working days.
Three questions and twenty seconds gets you a recommended engagement, an indicative team and a timeline. No email required.