What custom software actually costs a small business.

If you are looking for a number, here is the honest problem: any figure printed on a web page is a marketing number. Nobody can price your software without knowing your data, your users and the systems it has to talk to — and a supplier who gives you one anyway is telling you something about how they work.

What is genuinely useful is the thing nobody hands you: how software pricing actually works, what moves it, and how to judge the quote in front of you. Get that right and you can evaluate any supplier, including us.

The three ways software gets priced

Almost every quote you receive is one of these.

Fixed price. One number for an agreed scope. Feels safest. It is a bet the supplier is making, and you are paying for that bet.

Time and materials. You pay for hours actually worked. Feels riskier. Whether it is riskier depends entirely on whether you can see the hours.

Retainer. A monthly amount that buys a standing relationship and an agreed amount of capacity. Suits ongoing work rather than one-off builds, and is usually what small businesses actually need — more on that below.

Which one you are offered tells you more about the supplier than about the work.

What actually drives the cost

Four things move the number far more than the feature list does.

Integrations. Software that stands alone is straightforward. Software that must talk to your accounting system, your CRM and a supplier’s twenty-year-old API is not. Every integration is a system you do not control, with its own failure modes and its own bad days.

Whether strangers use it. An internal tool for five colleagues who can be shown how it works is one job. Something customers touch — logins, payments, permissions, no training, no patience — is a substantially larger one. This is the single most common reason quotes differ wildly for what sounds like the same request.

The data you already have. Migrating messy historical records is routinely the most underestimated part of any project. If it lives in spreadsheets with inconsistent formatting and three versions of every customer name, that is real work before anything new gets built.

How settled your decisions are. The most expensive thing in software is not complexity — it is changing direction after something is built. Rebuilding finished work costs full price, every time.

What makes it cheaper

Start with the bottleneck, not the vision. The version that solves your one worst problem costs a fraction of the platform you are imagining, and it tells you whether the platform is worth building at all. Most of the time it turns out you needed the small thing.

Use boring components for the boring parts. We do not build a payment system; we integrate one. The bespoke engineering should sit only where your business is genuinely different from everyone else’s.

Give one person the authority to decide. Projects needing three people to agree on every question are not expensive because of the software.

Define “done” in writing before anyone starts. In plain language, agreed by both sides. Most overruns are disagreements about scope that were never disagreements about scope until the invoice arrived.

Fixed price or hourly — which one protects you?

Most small businesses ask for a fixed price, reasonably, because it feels like protection. It is worth understanding what you are actually buying.

A fixed price is a risk transfer. The supplier absorbs the uncertainty, and to do that safely they price in a margin for everything that might go wrong. If the project runs smoothly, you paid for risk that never materialised. If it runs badly, their incentive flips: every extra hour now comes out of their margin, so the rational move is to deliver the minimum that satisfies the contract. You are protected from overspend and exposed to under-delivery.

Hourly billing inverts both. There is no padding for imagined risk, and no incentive to stop early. The fair objection is obvious — what stops the hours running away? — and the answer cannot be a promise. It has to be structural.

The real question is not fixed versus hourly. It is whether you can see the work while it happens. A fixed price is what you ask for when you cannot see inside the supplier. Make the hours visible and the protection becomes unnecessary, because you are never surprised by an invoice for work you have already watched being done.

How to read a quote you have been given

Whoever it is from, these five checks are worth ten minutes.

1. Does it separate thinking from building? Deciding what to build is different work from building it, and quotes that blur them usually under-price the first.
2. What happens after launch? If maintenance, hosting and support are not mentioned, they have not been priced — and they are not optional.
3. Who owns the code and the data? Ask explicitly. Ask how you would leave. The answer tells you most of what you need to know.
4. What is excluded? The exclusions list is more informative than the inclusions list. A quote with no exclusions has not been thought about.
5. What does “done” mean here? If you cannot tell from the document how you would know the work is finished, neither can they.

When you should not build custom software

We say no to work for these reasons regularly.

• Something off-the-shelf already does it. If an existing tool covers the large majority of what you need, building the rest is rarely worth the difference — and you inherit maintenance forever.
• The process is broken, not the software. Automating a bad process gives you a faster bad process, and now it is expensive to change.
• Nobody owns it internally. Software without an owner falls out of use within a year regardless of how good it is.
• The requirement is still moving. If what you need will look materially different in three months, wait three months. That is free.

Buying instead of building is a perfectly good outcome of a first conversation, and a cheaper one for you. We would rather say it early than take the work. When building is the answer, this is how we do it. If the question is bigger than the build — what to make at all, or whether to buy — that is what our consultancy work is for.

How we price it

We price by the hour, not by the project — and we make the hours visible, which is the part that matters.

• Every hour is logged against a project and visible to you in your portal as it happens. The number on the invoice is the number you have already been watching. No reconstruction at month end.
• Unused included hours roll over once, so a quiet month is not money burnt.
• No setup fees and no multi-year contracts. Change tier or pause monthly.
• No rush fees and no weekend surcharges. Charging extra for urgency is a tax on your worst week, and we would rather not have that conversation with you.
• Our rates are published on a public page, not held back until a discovery call. You can see what an hour costs, and what a month costs, before you speak to anyone.

That last one is the real test, and you can apply it to any supplier you are considering. A firm that will not tell you its rate until it has qualified you is deciding what to charge based on what it thinks you can pay.

Common questions

How much does custom software cost for a small business?

It is priced by the hour, so the cost is the hourly rate multiplied by how long your specific problem genuinely takes. The number depends on integrations, who uses it, and how clean your existing data is — which is why a credible figure comes after a conversation, not before.

Is custom software cheaper than off-the-shelf?

Usually not, and cost should not be why you choose it. You build custom when the off-the-shelf option forces you to work in a way that costs more than the software saves.

How long does it take to build?

Ask for the estimate in hours rather than weeks, plus a written definition of done. Hours you can check against reality; a delivery date depends on availability you cannot see.

Do I own the code?

You should — along with your data, exportable whenever you want it. Ask this of anyone you are considering, and treat hesitation as an answer.

What if it costs more than estimated?

Estimates move; that is normal. What matters is whether you find out while it is happening or when the invoice arrives. That is the whole argument for visible hours.

If you want a real number for your situation, tell us the problem and we will tell you what we think it takes — including when the answer is that you should not build it.