Bespoke software is software designed and built for one organisation, around its own processes, rules and existing systems. An off-the-shelf product is sold in the same form to thousands of companies, and each of them adjusts its way of working to fit it. Bespoke software is shaped to the company instead. "Bespoke" is the British and South African word; in the United States the same thing is usually called custom software.
If your company runs on a mix of spreadsheets, email and a few packages that don't share information, bespoke software is what someone means when they suggest "building something". It's also the work CBOS does: bespoke software development for South African companies whose operations have outgrown what they can buy. This article covers the meaning, four examples from CBOS projects, the trade-offs and when it's worth it.
What does bespoke software mean?
The word comes from tailoring. "Bespoke" grew out of "bespeak", in its old sense of arranging something beforehand, and a bespoke suit is one that was ordered and cut for one person. An off-the-peg suit fits most people reasonably well because it was made for an average body. A bespoke one fits you, because it was made from your measurements.
Software works the same way. An accounting package, an ERP or Microsoft 365 is designed for the average company in its market, and it does that job well. Bespoke software is designed from your measurements instead: who does what in your business, which approvals go to whom, how your branches differ and which systems the information has to pass through.
Setting up an ERP with your own chart of accounts, users and approval steps is configuration, and the product underneath is still off the shelf. Bespoke software starts when code is written for your business specifically. That might be a new platform, a customer portal, or a layer that connects the packages you've bought so that they behave as one system.
What's the difference between bespoke and off-the-shelf software?
The difference comes down to who the software was designed for, and that decides most of what follows. It shows in four places in a company:
- Fit. Off-the-shelf software expects your process to work the way it was designed. Bespoke software is built around the way your process works now, including the exceptions.
- Roadmap. With a product, the vendor decides what gets built next for all its customers. With bespoke software, your company decides.
- Connections. A product connects to other systems where its vendor has chosen to support them. Bespoke software can be built to connect to your ERP, accounting package, CRM or anything else with a way in.
- Cost over time. A product starts cheaper and then costs licences and workarounds, while bespoke software costs more up front and the company owns what it paid for.
Neither is better in general, and for a process that every company runs the same way, such as payroll, the product's average design is exactly what you want. Building your own payroll system would mean paying to solve a problem that's been solved many times over.
What are some examples of bespoke software?
Bespoke software takes whatever shape the problem needs, and the kinds CBOS builds give a sense of the range:
- operational platforms for running branches, depots or regions
- customer portals where clients check information, make requests and upload documents themselves
- mobile apps for teams working in the field
- workflow systems that route each request to the right person
- integration layers that connect existing systems so information is captured once
- supplier systems
- reporting and dashboards
- new digital products, taken from an idea to the market
Four CBOS projects show what these look like inside a real business, and each case study is public.
Supa Quick's franchise management system is the first. Supa Quick is a tyre and fitment franchise with more than 200 fitment centres across South Africa. Before the project, work was recorded on paper job cards, over the phone and in each store's own spreadsheets, so every store ran in its own silo.
CBOS built a Franchise Management System on Microsoft Azure that puts the stores, head office and fleet partners on one platform. Head office gets central oversight, and each franchise keeps room to work the way its market needs. CBOS still develops, supports and manages the system.
Gallo Images' content platform is a useful example because its old software was bespoke too. Gallo Images, the world's largest master delegate of Getty Images, had built custom systems over several years for content ingestion, asset management, billing, accounting and reporting. Over time those systems became outdated, hard to maintain and poorly connected. CBOS rebuilt them as one platform on Azure, serving markets in Africa and Central and Eastern Europe.
I&J's fleet data system brings bespoke software to sea. I&J, founded in Cape Town in 1910, runs 10 deep-sea trawlers, and its engineering and trawling logs used to be written down on board and sent to shore irregularly.
CBOS built an IoT framework that reads data from the onboard machines. It added a mobile app for the crew, a satellite link between the vessels and shore, and a shore platform that brings it all together for planning and maintenance.
Edge Factor's learning platform is bespoke software as a product. Edge Factor, a Canadian company, makes career education in manufacturing for students, educators and industry partners. CBOS built and maintains the cloud platform that hosts its videos, interactive tools and assessments, with badges and progress tracking. The platform holds thousands of learners online at once.
Each of these was built around something specific to the business: a franchise network, a content library spread over several countries, a fleet at sea or a learning product. A package designed for the average company in those markets would have had to be bent to fit, and bending it is where the cost of off-the-shelf software tends to hide.
What are the advantages of bespoke software?
The advantages of bespoke software all follow from it being designed around your company. These are the ones that matter most in practice:
- Process. The software follows the way your company works, so staff don't have to keep a workaround in their heads. The exceptions are part of the design.
- Rules. Approval limits, contract pricing and branch differences are written into the software, so nobody has to remember them and nobody can skip them.
- Data entry. Information is captured once. When the bespoke system connects your ERP, CRM, accounting package and Microsoft 365, an order typed in one place doesn't have to be typed again in three others.
- Growth. A new branch, product line or regulation becomes a change to your own system, made on your timeline instead of a vendor's.
- Difference. If the way you serve customers is what wins you business, software built around that way of working is something a competitor can't buy off the shelf.
What are the disadvantages of bespoke software?
The disadvantages are real, and they're the reason bespoke software is the wrong answer for plenty of processes. The first is cost and time up front. A product is ready on the day you sign, while a bespoke system has to be understood, designed, built and tested before anyone uses it, and somebody has to pay for that work.
The second is that it depends on decisions from your side. If your team hasn't agreed how a process should work, the developers end up building it twice, and the business pays for both. Naming one person with the authority to decide what the system should do costs very little and prevents most of that.
The third is that bespoke software has to be looked after. Gallo Images shows what happens over enough years, because the custom systems it had built became outdated, hard to maintain and poorly connected, and they had to be rebuilt. So bespoke software has to keep being developed after go-live, with a partner who stays involved, or it becomes the next legacy system.
The fourth is dependence on whoever built it. A company can protect itself by agreeing in writing who owns the code and the data. It also helps to have the system documented well enough that another team could take it over.
Is bespoke software different in South Africa?
The term is used differently, and so are some of the questions. "Bespoke" is the word South African and British buyers tend to use. Most of what's written about it comes from agencies in the UK, Poland and the United States, and those guides don't cover POPIA, local hosting or the systems South African companies tend to run.
POPIA is the first of those questions. Section 19 expects a company to protect personal information with appropriate, reasonable technical and organisational measures. Section 72 restricts sending that information outside the country.
With bespoke software, the company decides where its data is stored and processed, and who can see which records. Microsoft Azure has regions in Johannesburg and Cape Town, so CBOS can build a system whose data stays in South Africa. Where a business also serves other countries, the hosting can be split between South Africa and abroad. Gallo Images' platform, for example, runs with South African and international hosting.
Local systems are the second question. Sage is common in South African companies, and a bespoke system often has to work with it. CBOS has built Sage integrations for point-of-sale, sales invoices and inventory. That kind of connection decides whether a new system saves time or adds another place to type the same information.
How much does bespoke software cost?
Bespoke software has no list price, because the cost is mostly the time of the people who design, build, test and run it. That time grows with:
- how much of the business the system runs
- how many other systems it connects to
- whether it replaces a live system
- how many people, sites and roles use it
- how settled the process is
- how sensitive the data is
That's why CBOS doesn't put a figure on a first call. The price follows a consultancy session that looks at how your operation runs, and it arrives in a written proposal.
When is bespoke software worth it?
Bespoke software is worth it when the process it runs sets your company apart. Buying is rational for a process that's shared across industries and unlikely to give you an advantage. If the process is core to how you compete (your customer experience, how you handle your own data, or a service nobody else offers), building is essential. Our build vs buy guide goes through the decision properly, including the hidden costs on both sides.
The answer is often both, because accounting, payroll and email have mature products. The bespoke work then belongs in the processes that are specific to your business and in the connections between the products you've bought.
A few signs suggest that off-the-shelf software no longer fits your company:
- your process works differently from the way standard software expects it to
- you run several branches, regions or business units that each do the same work differently
- your approvals have more levels than your current system handles
- business-critical work lives in spreadsheets
- several systems need the same information, and people retype it between them
- your main application is getting harder and more expensive to maintain
If two or three of those sound like your company, the CBOS bespoke software page has a fuller version of this checklist, and it shows what CBOS would build in five common situations.
How does a bespoke software project work?
A bespoke software project at CBOS starts with a discovery call and then a consultancy session. The session finds where a new system is needed and where a bought product will do. A proposal follows, and only then does the build begin.
The build itself runs in six stages:
- Understand. CBOS maps who does what, where information comes from and which rules apply.
- Design. CBOS designs the screens, workflows, architecture and security.
- Build. Development happens in short cycles, and you review working software as it grows, so a wrong turn shows up while it's still cheap to change.
- Integrate. The system is connected to your ERP, CRM, accounting and other systems.
- Deploy. It goes live with its hosting, access, monitoring and backups in place.
- Evolve. The platform keeps being developed after go-live, so it doesn't become the legacy system someone has to replace in ten years' time.
Where an old application is still running the business, CBOS rebuilds it in phases around the live system, so operations carry on during the move.
If some part of your business is held together by people retyping information between systems, that's the first place to look for software of your own, and a discovery call with CBOS is a good place to work out whether a product already covers it.
Frequently asked questions
Is bespoke software the same as custom software?
Yes. "Bespoke" is the British and South African term and "custom" is the American one, and both mean software built for one organisation's own processes and systems. "Tailor-made software" means the same thing.
What is a bespoke solution?
A bespoke solution is a system designed for one company's problem, as opposed to a standard product that the company adapts to. In software it usually means a bespoke platform, portal, app or integration, often working alongside products the company has bought.
What is bespoke application software?
Bespoke application software is a single application built for one organisation, such as a field app for technicians, a customer portal or an internal workflow tool. Supa Quick's franchise management system and I&J's crew app are both examples.
Who owns bespoke software once it's built?
That depends on the contract, so agree it in writing before the build starts. Ask who owns the source code, the data and any intellectual property, what documentation you'll receive, and what happens if you later move the system to another supplier.
How long does it take to build bespoke software?
It depends on how much of the business the system runs and how many systems it connects to, so any timeline given before the process has been looked at is a guess. Building in phases means part of the system can be in use well before the whole of it is finished.
Is bespoke software only for large companies?
No. Industry and size matter less than complexity. Bespoke software suits companies whose operations have outgrown spreadsheets, disconnected systems or ageing software, and whose process is specific enough that a standard product would make them work around it.
Can bespoke software connect to Sage or our ERP?
Yes. Connecting to a company's ERP, accounting and other systems is a large part of most bespoke projects. CBOS has built integrations with Sage for point-of-sale, sales invoices and inventory, and builds connections to ERP, CRM, payment and Microsoft 365 systems.