How I take your money 

the build

Fixed price, fixed date — from a signed spec

A build doesn't get a fixed price until what's being built is written down and signed. Once it is: a fixed price and a fixed date, paid in milestones against work you've actually accepted — not hours billed as they accrue. Requirements gaps show up on any non-trivial build; when they do, the change is scoped, priced and approved in writing before it's built, not absorbed quietly until quality is what gives.

if you're already holding a quote

Beating a quote you already have

Send a written, fixed-price quote from a named vendor for a scope I can match, and you'll get a straight answer within the week — no cost either way. The pattern so far: around half the price, and up to half the elapsed time, once the coordination overhead comes out. Not a promise — some quotes are already keen, and some work genuinely needs more than one pair of hands. When either is true, that's what you'll hear.

before any of this

Every build starts with a paid spec

Nothing gets a fixed build price until the architecture, data model, interface contracts, infrastructure plan and risk register are written down — and producing that is a paid engagement in its own right, a fixed fee set by the size of the system. It's the paid front door: the document is yours regardless of what you do next, and half the fee comes off the build price if you build with me. The figures are below.

what it costs

The numbers I publish

The build price isn't on this list, because it doesn't exist yet — it comes out of the signed specification, which is the entire point of the sequence above. These four are the ones fixed in advance, and what each bracket buys is set out in full on the-spec.

the terms, everywhere

What's true regardless of bracket