The repository, the cloud account, the domain and the docs, from day one. Nothing runs on our side, and no retainer is needed afterwards.
A working product in your name in weeks, or the build that stalled finally in production. An MVP ships in seven days at a fixed price. A stuck codebase gets a written verdict in days, then gets finished. Behind it is one senior engineer setting the specification and a fleet of coding agents building it, so you deal with one accountable party from the data model to the deploy.
Both start at a fixed price, agreed in writing before any work begins. If we misjudge a fixed scope, the overrun is our cost and the agreed scope still ships.
Seven days from a scoped idea to a deployed product that real users can sign in to and use. One flow, built properly, in your own cloud account. Scope and price are fixed before any code is written; an overrun is our cost.
| For | Founders proving an idea |
|---|---|
| You get | A deployed product · The source code · Your infrastructure · A written next step |
| Term | 7 days · fixed scope |
Your build never reached production. In days, at a fixed price, we read the code and the cloud accounts and give you a written verdict (finish, harden or rewrite), each with a cost and a date. Then we do the work, or you take the verdict to whoever you choose.
| For | Teams with a build that never reached production |
|---|---|
| You get | A written assessment · A verdict, with a number against it · The production gap, itemised · Everything in your name |
| Term | Fixed-price assessment, then scoped work |
The manual work your team repeats every week, handed to agents wired into the systems you already run.
One party builds the whole product (data model, services, interface, deploy) and hands it over documented.
Routine deploys, a cloud bill you understand, and a platform that stops setting your pace.
Senior judgement on the decisions that are cheap now and expensive next year, billed by the hour.
Each links to a written account of what was built, how long it took, and what happened to the business after.
| Project | Result | Year |
|---|---|---|
| Live-streaming platform | Grew from a 2019 prototype into a global platform and a company of around fifty, and was acquired by an international group in 2024. | 2025 |
| Decentralized wallet | Over a million wallets created by community members, across four blockchains, without anyone leaving their Telegram group. | 2021 |
| Document output platform | Replaced a resold engine with an in-house one, ending the revenue share with the original vendor, and became a lower-cost alternative to the output stacks sold by Microsoft, SAP, Oracle and HP. | 2016 |
| Companion AI | Four live branded sites from one backend, built solo in about four months and maintained by one person. | 2026 |
| Socialog | A seven-network publishing product with exactly-once delivery and an agent API, built and operated by one person on a single Worker. | 2026 |
| Online gaming platform | Went live with 50+ games from outside studios, playable on one platform against a single token wallet. | 2023 |
One senior engineer writes the specification and reviews every change; a fleet of coding agents builds against it in parallel. Typing stops being the slow part, so day one goes on deciding exactly what to build and the rest goes on shipping it, tested and documented. We call it Specification-Led Delivery.
Read the full method →| Day 1 | Scope cut to one provable thing |
|---|---|
| Day 2–5 | Build, in parallel, under review |
| Day 6 | Deploy to your infrastructure |
| Day 7 | Handover, docs, what to build next |
A reply within one business day, from the person who would do the work.
You have the idea and the budget, not the engineers. Send the one thing it has to do; you get a scope, a fixed price and a date back.
Start a project →The code exists and production does not. A fixed-price assessment says finish, harden or rewrite, with a cost and a timeline against each.
Rescue & takeover →A decision you are about to commit to, and nobody above your developers to check it. Billed by the hour; one question is enough.
Consultancy & retainer →