What custom software costs a small business, and how to tell if it is worth it

Somebody asks what it costs to build a booking system for their shop and gets a number between two thousand dollars and forty thousand dollars depending on who they ask. Which is useless, and it is also not anyone being evasive.

The honest reason is that "a booking system" describes about fifteen different things. One of them is a form that emails you. Another one handles deposits, multiple technicians, equipment scheduling, automated reminders and a customer account area, and connects to the software you already use for invoicing.

Those are not the same project and no price covers both.

What follows is how the pricing actually works, and more usefully, how to work out whether the thing you want is worth building before you talk to anybody.

Work out your own break-even first

Do this before you get a quote. It is the most useful twenty minutes available to you, and it tells you your own ceiling.

Custom software has to earn its cost in one of two ways. Either it saves time or it recovers money that is currently leaking. Sometimes both.

Time saved. Estimate the hours a week the current process eats. Double entering bookings into two systems, chasing confirmations by phone, rebuilding the same spreadsheet every Monday. Multiply by what an hour of that person's time costs the business, then by fifty.

Five hours a week at twenty five dollars an hour is $6,250 a year.

Money recovered. No-shows, jobs booked wrong, quotes that never got followed up, work lost because nobody could book outside business hours. Put a number on whichever applies.

Add them, multiply by three years, and you have a ceiling. If the annual figure is $6,000, a build costing $8,000 with ongoing support pays for itself inside two years and looks reasonable. If the annual figure is $1,200, almost nothing custom makes sense and you should be looking at off the shelf software.

That calculation is yours, it costs nothing, and it prevents the most common bad outcome, which is spending real money on something that was never going to pay it back.

What makes a project expensive

Broadly, cost tracks complexity in fairly predictable ways.

Cheap, relatively. One clear workflow. A handful of users who all work at the business. No payments. No connections to other software. A booking form with an admin screen behind it sits here.

More expensive. Customer accounts and logins. Anything customers use directly, because it has to be genuinely easy for people who will never be trained on it. Multiple user roles with different permissions.

Most expensive. Anything touching money. Payments, deposits, refunds, invoicing. Not because the code is harder, but because the consequences of getting it wrong are real, so it needs proper testing and careful handling. Integrations with other systems are the other one, because you are dependent on somebody else's software behaving predictably, and sometimes it does not.

If you want to control cost, the lever is not negotiating the price. It is cutting the scope.

The part people leave out of the budget

Custom software is not a purchase. It is a purchase plus an ongoing cost, and the second part is not optional.

Anything with a database, user accounts or payments needs somebody keeping it alive. Security updates. Dependencies that go out of date. Payment processors changing their systems. Things breaking at inconvenient times.

Budget for this from the start. A rough industry guide is fifteen to twenty percent of the build cost per year for ongoing support, though for a small system with light use it can be less.

The businesses that get burned by custom software are almost never the ones who paid too much for the build. They are the ones who did not budget for the years afterward, let it drift, and ended up four years later running something nobody maintains.

Start smaller than you think

The single best piece of advice on this, and the one most often ignored.

Do not scope the whole thing at once. Build the one part that hurts most, use it for three months, and see whether it actually gets used.

Two reasons this matters. First, software that gets built and then quietly not used is the most common outcome of small business custom projects, and finding that out for three thousand dollars is much better than finding it out for fifteen. Second, three months of real use will change your mind about what phase two should be. It always does.

The plan you write before anything exists is a guess. The plan you write after three months of using something is informed.

What a proper scoping call covers

If somebody quotes you without asking most of these, be careful.

• What exactly happens now, step by step, including the parts done on paper
• Who uses it, and how comfortable they are with software
• What happens when something goes wrong in the current process
• What other systems it needs to talk to
• How many bookings, jobs or customers a month, roughly
• What it needs to do on day one, and what could wait
• What would make you consider it a success

That last question is the important one, and a lot of people have never been asked it. If nobody can answer it, the project is not ready to start.

Why we do not publish prices for this

Every custom project we quote is different, and a published number would be wrong in both directions. It would scare off businesses whose actual need is smaller than the number, and it would anchor projects that are genuinely larger.

So we quote after a call, and the first thing that call establishes is whether you need custom software at all. Quite often the answer is that an off the shelf tool will do the job and we say so.

Run your own break-even first. Come to the conversation with a number. It makes everything after that much easier.

---

Call +1 506-801-9970 or email info@qhike.ca. We serve Fredericton, Moncton, Saint John and all of New Brunswick.