Custom builds

Sometimes no off-the-shelf tool fits — the workflow is yours alone, and bending a generic product around it costs more than building the right thing. That's a custom build.

Every custom build starts with the free call and a written spec: what it does, what it doesn't, what it costs. The price is fixed once the spec is signed off — no day-rate meter running, no surprises after. It runs on your accounts and the code is yours.

What a custom quote gets you

• Software built for your exact workflow — not adapted from a template
• Scoped and specced with you before any code is written
• Hosted on your accounts — you own the code and the data
• A fixed price agreed up front, once the spec is signed off

No price until the job is defined, no surprises after.

Fair use applies to every published scope — what's included, and what's quoted separately.

Questions people ask

How much does custom software cost?

It depends entirely on the spec, which is why we won't name a number before the job is defined. You get a fixed written price before any code is written, and it doesn't move unless the spec does.

Who owns the software afterwards?

You do — code, data, accounts, documentation. It runs on your infrastructure, and walking away with a working system is always possible.

How long does a custom build take?

The spec says — that's one of the things it exists to answer. Small tools take weeks; bigger systems are phased so something useful ships early.