From concept to proof.
Ninety days, four phases and milestones you can hold us to. We share our delivery and engineering standards with you during Shape. This transparency builds trust, more effective collaboration and better outcomes.
Every phase boundary is a demo of running software, and a decision that stays yours: proceed, pivot, or abandon, with no strings attached.
Days 0–14
Shape
Two weeks to turn your idea (or your prototype) into something we can price and you can hold us to: a fixed-price quote both sides can trust.
Shape runs inside the clock: the ninety days from concept to proof are all-inclusive.
You receive
- A product definition: what it is, who it’s for, what day 90 must prove
- The product architecture, with the first design decisions recorded
- A slice map: your product as releasable increments
- A clickable prototype of the product
- A fixed quote: the number, in writing, before we build
By day 30
Prove
A walking skeleton of your product, live on a production URL by day 30, with the first value slice built, tested and merged.
The skeleton is deliberately thin. Every part of your product’s path to production exists and runs end to end before the build scales.
You receive
- Your product’s repository, in your own organisation
- The delivery pipeline that takes every change safely to that URL
- The design system your product is built with
- The first value slices, delivered and live
By day 60
Build
Your product live and opened to a small set of real users for feedback, where that’s possible. Every week in between ends with something you can use.
Weekly update: week 6
Activity Pulse · Thu · 4 min read
- Live this week: board-level activity digest. See it live
- Tested: slice 09 passed its spec (14 checks) before merge
- Decision needed: weekly digest email, opt-in or default-on? By Mon.
- Next: slice 10, usage instrumentation
Every build gets this, every week. No decks, no “percent complete”.
You receive
- Every remaining slice on your slice map, delivered
- Your product hardened to meet our engineering quality gates
- A live beta: real users, real feedback, before day 60
Days 60–90
Run
Thirty days of real use, measured against what you set out to learn. It ends in a decision, not a shrug.
If the decision is continue, ongoing support beyond day 90 is there when you want it: see Pricing.
All three outcomes are wins. “Stop” at day 90 with evidence costs a fraction of “keep going” for a year without it.
You receive
- Full product instrumentation on the behaviour that matters
- The Proof report: what people actually did, and what it means
- A decision with evidence behind it: continue, hand over, or stop
One call a week
The decision call. Anything that needs your judgment comes to it, prepared.
Decisions in writing
Every decision goes in the decision record, with its date and its reasoning.
48-hour turnaround
You turn decisions around in 48 hours; we do the same with answers. That’s how 90 days stays 90 days.
How a small studio ships this fast, this safely
Proof runs an augmented engineering system: senior engineering judgment directing agentic tooling. The tools produce; the engineer decides.
Every change is reviewed by a human
A senior engineer reads every merge. Their name is on it.
Every slice is tested against its spec
Each slice ships with tests written from its specification, the one in your slice map.
Nothing merges without passing
Red doesn’t ship. Not late on a Friday, not the day before a milestone.
The fit, honestly
Proof is a fit if
- You’re building something new: web-first, mobile-first, or a monday.com marketplace app
- One decision-maker who can turn decisions around in 48 hours
- Ready to start within a month
- No regulated data in the first release
Not quite that?
Open Works is the advisory side of the house: strategy, diagnosis, larger or legacy environments, and the work before the build. If Proof isn’t the right instrument, we’ll point you the right way rather than take the job.
Talk to Open Works ↗