For founders outside the art world
A product shipped, not a deck about one.
Marketplaces, engines, AI agents and MCP servers. Coorie and Pooled were built this way: specified, built and published by one studio, with the thinking and the making as one job.
Start a build- Coorie
- Childcare marketplace, live 2026. Search, verification, booking, payments
- Pooled
- UK capital-gains engine applying HMRC rules exactly, with an audit trail
- 2011
- Shipping software since
- 1
- Studio from brief to production. No handoff
The problem
Every default is a judgement, and judgement does not survive a handoff.
A product goes through a strategist, a designer, a developer and a tester, and each one inherits the last one’s defaults without the reasons. The studio keeps the reasons and the build in one place.
What you get
1.1
A production product
Real users, real payments, real data. Not a prototype that needs rebuilding before launch.
1.2
The rules encoded exactly
Where the domain has rules, tax, compliance, verification, they are modelled precisely and tested, the way Pooled models HMRC share matching.
1.3
An agentic build pipeline
Specified in writing, built with an agentic workflow, published to production. The specification is the documentation.
Then
Ship
Published to production with the documentation and access to run it yourselves.
Asked before
What stack?
[Stack]. Chosen for the product, written into the scope, handed over fully.
Who owns the code?
You do, on delivery. The repository, the infrastructure and the documentation.
What if we have a team already?
The studio can build the first version alone or beside them. Either way the scope is written so the next person can read it.
How is it priced?
Fixed scope, fixed price, in writing before work starts. Ranges are on the project brief.