DESIGN-01 · DESIGN
Proof Before You Build
A working sample on your own data, a fixed price, and a written plan your engineering team can follow — before you pay for the build.
The target is fixed in writing at kickoff: the named workflow, the named dataset, the path the spike must demonstrate in your stack. If it doesn't run, full refund. Disliking the recommendation is not a miss.
- 01Pay securely by card
- 02Pick a time that works
- 03Your written plan in a few days
- 01A clear design for the chosen workflow
- 02A written build plan an engineer can execute
- 03A fixed-price Build quote — the number, in writing
- 04A working sample that runs the whole job on your own data — or, where the law requires it, on safe stand-in data inside your own network
- 05A clear yes or no, with the reasons written down
In about two weeks, one chosen workflow turns into real proof. You get a working sample that runs on your own data and does the whole job, a fixed price for the full build, and a written plan any engineer could follow. What the sample must show — the workflow, the data, the result — is agreed in writing first, so "done" is never a matter of opinion. Where your data must stay private, the sample runs inside your own network on safe, stand-in data. You watch it work before you commit build money. The $20,000 counts toward the Build for 90 days after you get it.
BUILT FOR CTO, VP Engineering, or COO who needs working proof and a committed number before approving build budget — not another estimate.
WHEN YOU NEED THIS
- A build is proposed and the budget needs a defensible number
- Vendor quotes vary wildly and none come with working code
- The workflow is chosen, but the team disagrees on how to build it
- Compliance needs to see how data will be handled before any build
- Leadership wants it proven on your data, not in a demo
NOT FOR YOU IF
- The workflow is still undecided — start with the scoping call
- No one can grant data access in the first week
- You want a price without working proof — that is a guess, and we don't sell guesses
A fixed price and working proof on your own data before you commit build money — the two things an estimate can never give you.
Written targets. Watch it work. Full refund until you accept.
The target is fixed in writing at kickoff: the named workflow, the named dataset, the path the spike must demonstrate in your stack. If it doesn't run, full refund. Disliking the recommendation is not a miss.
Design's target is fixed in writing at kickoff: the named workflow, the named dataset, the path the spike must demonstrate against it. If it doesn't run, full refund. Disliking the recommendation is not a miss.
The $20,000 credits toward any Build tier — expires 90 days after delivery.
The full terms → Security & data handling →