What is bespoke software? The advantages and the disadvantages

What bespoke actually means

Off-the-shelf software is built once and sold to thousands. Bespoke software is built for one business. You are not buying a seat in somebody else’s product, you are commissioning a thing that did not exist before.

The trade is straightforward and worth stating plainly: you pay more at the start, you pay nothing per month for the licence, and you carry responsibilities you would otherwise have handed to a vendor.

Bespoke, custom and tailored: is there a difference?

In everyday use, no. Bespoke, custom and tailored software all mean software made for one business. Where people draw a line, “custom” sometimes means a standard product that has been configured or extended, while “bespoke” means written for you from the start. When you are being quoted, ask which one you are buying, because the answer changes who owns what.

Bespoke and off the shelf, side by side

What	Bespoke	Off the shelf
Up-front cost	Higher: you commission it	Low or none
Monthly cost	No licence. Hosting and support if you want them	A licence, often per user, that tends to rise
Fit to your process	Built around it	You adapt to the product
Time to start	Weeks	The same day
Ownership	You own the code, the data and the accounts, if the contract says so	The vendor owns the product and you rent access
Looking after it	You, or whoever you pay	The vendor

The advantages that are real

• +It fits the process you already run, rather than making you adopt the process the product assumes
• +The cost stops. A licence does not, and it rises
• +Rules can be enforced rather than requested. A booking system can be built so that two people cannot hold the same hour, not because the code checks but because the database refuses the second one
• +You own it, in the full sense: the code, the data, the payment account
• +It can join things up. The booking fills the customer record, the payment reconciles itself, and the reporting comes from one place instead of four

The disadvantages nobody selling it mentions

• +You are responsible for it. There is no vendor roadmap quietly improving it while you sleep
• +It costs more up front. Always. Anyone saying otherwise is comparing the wrong things
• +It takes weeks, not an afternoon. If you need it running on Monday, buy something
• +It needs maintaining, and the person who built it is a single point of failure unless the handover is genuine
• +A product with forty thousand customers has been tested by forty thousand customers. Yours has been tested by you
• +If your process is ordinary, you are paying to rebuild something you could have rented for the price of a coffee a week

What does bespoke software cost?

It depends on how much it has to do, and anyone quoting a figure before they understand your process is guessing.

For a sense of scale, our own builds start from £1,500 for a site that takes enquiries and payments, from £3,500 when customers book or order and pay for themselves, and from £6,000 for a full back office of customer records, job tracking and generated paperwork. Every price is published, with the monthly retainer beside it.

The cost that surprises people is not the build. It is what happens afterwards: who hosts it, who fixes it, and who answers the phone when it breaks. Ask that before you ask the price.

See every price
What a booking system costs: renting or building

The test worth applying

Would you describe how you work as normal for your trade? Then buy. There is a product for it and it is better than the one you would commission, because it has had years and thousands of complaints poured into it.

Is the awkward part of your week the thing customers are actually paying for? Then it is worth building, because that awkwardness is the business.

Are you considering it because you are irritated by a monthly fee? That is the worst reason on the list. Do the arithmetic first. The licence often wins, and it should.

The middle option most people miss

This is rarely all or nothing, and treating it that way is how budgets get wasted.

Buy the ordinary parts. Accounting is a solved problem and you should not commission one. Card payments are a solved problem and you should be on an account in your own name with a provider who does nothing else.

Then build only the part that is specific to how you work, and connect it to the bought parts. Most sensible systems are mostly bought, with something small and precise in the middle that is yours.

A worked example: ShotBot, our own booking system
Quoting and job management for trades: rent or build