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.

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

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.