Skip to content
Spark
Writing

How we work

A fixed price is fairer than hourly billing: how pricing a software build works

A fixed price for a software build puts the risk of overruns on the builder, who is best placed to judge it. Here’s what the price should cover, what sits outside it, how changes are handled, and why it’s the fairer deal for the business paying.

By Seb Lawson · 23 October 2026 · 5 min read

We price every build at a fixed fee, agreed in writing before the build starts. If it takes us longer than we planned to build what we agreed, that’s our cost to carry. If you want something different halfway through, we price the change first and you decide. We think that’s much fairer than hourly billing, because the builder knows far more about how long software takes than the client does, so the builder should carry the risk of getting it wrong.

Hourly billing puts the risk on the client

With hourly billing, every surprise costs you. A connection to Xero that’s fiddlier than expected, a developer who takes a wrong turn, a bug that eats a day: it all lands on your invoice. You can’t easily judge whether the hours were reasonable, because you’re not the software expert. That’s why you hired one.

It also sets up an awkward incentive. The slower the work goes, the more the builder earns. Most builders are honest and don’t take advantage of that, but you shouldn’t have to rely on it.

And it makes budgeting hard. An estimate of “somewhere between 80 and 140 hours” is a range with a big number at the top, and owners sensibly plan for the top.

A fixed price needs a clear, written scope

A fixed price only works when both sides agree exactly what’s being built. So before the price is fixed, the scope gets written down in plain English: which pieces the system will have, which tools they connect to, what each part does, which data comes across from your old tools, and what finished means for each one.

That scope comes from understanding your real work, which is why we start by following actual jobs through the business. There’s more on that in how we map a business. The written scope is what the price pays for. If something isn’t in the scope, it isn’t in the price, and both sides can see that.

The price should cover everything needed to get the agreed system live

A good fixed price covers the whole job of getting the agreed scope working in your business. For us, that means:

  • mapping your work and designing the system
  • building everything in the written scope, including the connections to tools such as Xero, Microsoft 365, Google Workspace or HubSpot
  • moving the agreed data across from your existing tools
  • testing it on your real data
  • training the people who’ll use it
  • plain-English documentation

There’s no hourly billing on top. Adjustments that come out of testing what we agreed, such as moving a field, renaming a status or rewording an email, are part of getting the build right and don’t count as changes. You’re paying for a working system, not for attempts at one.

Running costs sit outside the build price, and you see them up front

Some costs aren’t part of the build, and you should see them before you commit:

  • The monthly fee to run, monitor, support and improve the system once it’s live, including keeping the connections working when your other tools change.
  • Third-party running costs, such as subscriptions to the tools underneath, hosting, and any AI usage. We size these up front and show them next to our price, so the bill is never a surprise.
  • New work you ask for that isn’t in the agreed scope. That’s a change, and bigger pieces of new work get their own fixed price.

Changes are priced before anyone builds them

Your business will change while the system is being built, and you’ll have new ideas once you see it working. That’s normal, and it’s a good sign.

When you ask for something outside the scope, we tell you in writing what it would cost and what it would do to the timeline, before any work starts on it. You decide whether it’s worth it. If it is, it joins the scope at that price. If it isn’t, it goes on a list for later. Nothing new gets built and billed without your sign-off.

Often a change is really a swap: you’d rather have the new thing than something already agreed. If they’re a similar size, a straight swap is usually the simplest answer.

Why it’s fairer for the business paying

  • You know the cost before you commit. You can set it against what your current way of working costs and make a real decision.
  • Overruns are the builder’s problem. If we misjudge the work, we absorb it, which gives us every reason to scope carefully and build well.
  • The incentives line up. We do best by finishing on time with a system that works, which is exactly what you want too.
  • Changes are your choice. You see the price of every change before it happens, so the total never creeps up without you knowing.

The honest catch: the scope has to be right

A fixed price is only as good as the scope behind it. If the scope is vague, a builder either pads the price to cover the unknowns or argues about every change later, and neither is good for you. That’s why we put the effort into understanding the work first, and why the scope is written in plain English you can check line by line.

If a builder offers you a fixed price without having understood how your business works, ask what they’ve assumed.

It also helps to start small. Most clients begin with one fix: the process that hurts most, joined up properly, for a fixed price. It’s the cheapest way to find out whether a builder is right for you before committing to more.

Our recommendation: ask for a fixed price against a written scope

Whoever you work with, ask for a fixed price against a written, plain-English scope, with the way changes are handled set out in the agreement. If a builder will only work by the hour, ask why. And check what you’ll own at the end, which we cover in owning your system.

If you’d like to know what a system for your business might cost, book a review. In 30 minutes we’ll tell you honestly whether a build makes sense, where we’d start, and what we’d need to know to fix the price. You can also build your system first, so we come to the call prepared.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.