Custom builds

Bring the idea. Leave with something running.

Thirty minutes to work out what the thing actually is and what it would take to build. Then, if it is worth building, a fixed scope agreed in writing that ends at a real URL — the repository, the tests and the deploy included. You do not need a specification to start: producing one is the first thing the conversation does.

Book a 30-min idea review See what I have built

The review costs nothing, and the write-up is yours whether or not we work together.

Two ways to start How it works Proof Questions

Have an idea?

Two ways to start

Almost every project on the builds page began as somebody describing a problem out loud. If you have one, there are two ways in, and the first one costs nothing.

Start here

Idea review

Thirty minutes on a call, and you leave with a written page: what the thing actually is, what it would take to build, and whether it should be built at all.

30 minutes no charge

The write-up is yours whether or not we work together.

What the thing actually is, once the vague version is out of the way
The shortest version that still solves the problem
What it would take to build, and what would make it expensive
An honest answer if it should not be built

Book the review →

Build sprint

A fixed scope, agreed in writing before anything starts, ending with something deployed and running rather than a prototype you still have to finish.

2–6 weeks fixed scope

Scoped on the deliverable, priced on enquiry.

Something deployed at a real URL, not a demo on my machine
The repository, the tests, and the deploy that puts it there
A walkthrough, and a revision window after handover
You own all of it — nothing is locked to a platform you rent from me

Send a brief instead →

Process

Five steps, and you can stop after the second

The first two are free and end in a document. Nothing is committed until the scope is on paper.

The call

Thirty minutes. You describe the problem out loud and I ask the questions that separate what you want from what you have been told to want. No preparation, no specification.

The written page

Yours whether or not we go further: what the thing actually is, the shortest version that still solves the problem, what it would take, and what would make it expensive.

The scope

If it is worth building, what is in and what is out goes in writing before anything starts. Named deliverables, a date, and a price on the deliverable rather than on the hour — told to you before you commit.

The build

Two to six weeks, with something you can open in a browser well before the end. Agents do the volume; I read every diff and stay responsible for the architecture.

Handover

The repository, the tests and the deploy that puts it there, a walkthrough, and a revision window afterwards. You own all of it.

Proof

None of this is hypothetical

Fourteen products in eight months: market data pipelines, planning and supply-chain systems, browser games and rendering engines, workflow automation. Some of them you can open right now and use without an account. If you want to know how somebody works, look at their code rather than their claims.

See the builds

The repositories are private; the code is yours to read on request. Request repo access

Questions

The things people ask before booking

What does it cost?

The review is free. A build sprint is priced on the deliverable rather than by the hour, and you get the number in writing alongside the scope before you commit to anything. I do not publish rates because the same two-week sprint is a different job depending on what it has to talk to.

Who owns the code?

You do. The repository, the commit history, the deploy configuration — all of it, on your account. Nothing is locked to a platform you rent from me, and nothing needs my permission to keep running.

What if it does not work out?

The scope says what “done” means before anything starts, which is the point of writing it down. And if the honest answer at the review stage is that the thing should not be built, that is what the written page will say — it has happened, and it is a cheaper outcome than finding out later.

What do you build it with?

Whatever the problem needs and you can maintain. Mostly Python and JavaScript over Postgres, deployed as containers; every card on the builds page names its stack. I will not pick something exotic that leaves you dependent on me.

Does it have to be construction?

No. The lineup runs from market data to browser games, and the habit is the same in all of them: take something manual and opaque, and turn it into something somebody else can operate. Bring the idea, not the sector.