Off-the-shelf software is the better choice when your process is common and a mature product already covers most of it. Custom software is the better choice when the process is what makes your business different, when no product fits without costly workarounds, or when you need control over data, integrations and the roadmap. Many companies end up with a mix of both.
The decision is rarely about technology. It is about how much of your way of working is genuinely unusual, how fast you need results and what you are prepared to maintain over the years. This article sets out the differences, the real costs on each side, a decision checklist and the hybrid options in between.
What each option means
Off-the-shelf software, also called packaged or commercial software, is a product built for many customers. You configure it, pay a subscription or licence, and the vendor maintains it. Examples range from accounting packages to e-commerce platforms to full ERP systems.
Custom software is built for your specific requirements by an internal team or an external partner. You own, or at least control, the design and the code. Between the two sit configurable platforms and low-code tools, where you assemble much of your application from existing parts and write only the differing bits.
Side-by-side comparison
| Factor | Off-the-shelf | Custom |
|---|---|---|
| Fit to your process | Good for standard processes; you adapt to the product | Built around how you work |
| Time to start | Days to weeks | Weeks to months before first release |
| Upfront cost | Lower; setup and subscription | Higher; design and build |
| Ongoing cost | Subscription per user or per module | Hosting, maintenance and further development |
| Control of roadmap | Vendor decides | You decide |
| Integration | Standard connectors, limits at the edges | Designed to your systems |
| Risk | Vendor changes pricing or features; lock-in | Delivery risk, key-person and maintenance risk |
| Competitive advantage | Competitors can buy the same tool | Process can become a differentiator |
When off-the-shelf is the right choice
Buy when the problem is solved well and your needs are ordinary. Accounting, payroll, email, basic CRM and standard e-commerce are mature categories where a mature product, refined by many customers, often beats what a small team can build for a similar budget.
- The process is similar to other companies in your industry.
- You need to be live quickly, and a few compromises are acceptable.
- You lack the budget or appetite to maintain software.
- Regulation matters and the vendor handles updates, such as tax rule changes.
- The software supports the business but does not define how you win.
When custom software earns its cost
Build when the software itself is part of how you compete, or when buying forces compromises that cost more than building. Typical signs follow.
- Your team keeps a spreadsheet or manual process alongside the product because it cannot do something essential.
- You pay for many modules but use a small part of each, and still lack one critical function.
- Your pricing, scheduling or production logic is specific and changes how you quote or deliver.
- You need several systems to act as one and no standard connector exists.
- Customers or partners use a portal with your own rules and brand.
- Data ownership, hosting location or security requirements exclude standard products.
The hybrid route: buy the core, build the edge
The most common outcome for mid-size companies is a hybrid. Run finance, payroll and standard operations on proven products, and build the parts that carry your advantage on top: a quoting tool, a customer portal, a planning module, an integration layer or a reporting platform.
This limits risk and cost. You avoid rebuilding commodity functions, and your custom work stays small enough to maintain. Make sure the packaged product offers a reliable way to connect, such as documented interfaces and exports, before you commit. Our guide to ERP for small business covers how to judge that side of the decision.
A structured way to decide
- Write down the process in plain steps, including the unusual ones, and mark which steps differ from standard practice in your industry.
- Score each requirement as essential, useful or optional.
- Test two or three products against the essential items using your real cases. Record every workaround you would need.
- Estimate the annual cost of the workarounds in hours, and compare it with the cost of building the missing part.
- Estimate the five-year cost of each route: licences or subscriptions, setup, development, hosting, support and internal time.
- Check who would own the result: who can change it, who holds the data and what happens if the vendor or partner disappears.
An example comparison
This example uses assumed figures. A firm needs a quoting tool. A packaged product costs £900 a month in subscriptions for the users needed, and the team loses 15 hours a month to workarounds at £35 an hour, which is £525. Over five years that is £54,000 in subscriptions and £31,500 in workaround time, a total of £85,500. A custom tool costs £60,000 to build, £1,000 a month for hosting and support (£60,000 over five years) and 3 hours of workaround time a month (£6,300). The total is £126,300. On these assumptions, buying wins. Raise the workaround time to 60 hours a month and the packaged route becomes £54,000 plus £126,000, a total of £180,000, so building wins. The result depends on your numbers, which is why you should do the arithmetic with your own.
Hidden costs on both sides
Packaged software hides costs in customisation, extra modules, per-user growth, data migration, training and price rises. Custom software hides costs in requirements that change, testing, security updates, hosting, documentation and the person who understands how it works. Plan for maintenance either way. A rough planning habit is to budget a share of the original build cost for each year of upkeep and agree it up front. Read more about the cost side in custom software development cost.
Where we fit
We do both ends of this decision. We built Dika Ops as an AI-native ERP for companies that make, move and sell things, so that sales, purchasing, stock, finance and HR run on one record; it is in closed beta and you can look at its inventory module. For what a product cannot cover, our custom software and enterprise applications service builds portals, internal tools, integrations and data platforms. We will tell you if a product you can buy fits better than anything we would build.
Frequently asked questions
Is custom software better than off-the-shelf?
Neither is better in general. Off-the-shelf wins for standard needs, speed and low upfront cost. Custom wins when your process is distinctive, when workarounds are expensive or when you need control. Decide with your own requirements and numbers.
Is custom software more expensive?
Upfront, usually yes. Over several years the difference narrows or reverses if the packaged option needs many subscriptions and workarounds. Compare five-year total cost, including internal time.
How long does custom software take to build?
It depends on scope. A focused internal tool can reach a first release in weeks, while a broad application takes months. Releasing the most valuable part first reduces risk.
Can I start with off-the-shelf and move to custom later?
Yes, and it is a sound approach. Keep your data exportable and use documented interfaces so you can replace the parts that outgrow the product.
What are the risks of custom software?
Scope growth, unclear requirements, dependence on one developer or supplier, and ongoing maintenance. Reduce them with a written scope, code ownership terms, documentation and a plan for support.
Who owns custom software?
That depends on your contract. Agree ownership of the code, the data and any third-party components in writing before work starts, and make sure you can maintain the system if the supplier stops.
What is low-code and where does it fit?
Low-code platforms let you assemble applications from ready-made components with limited coding. They suit internal tools and simple workflows, but check limits on performance, integration and exporting your data.
Next step
List the five requirements your current tools cannot meet and put a yearly cost on the workarounds. That number tells you whether building is worth discussing. If it is, our team can review the scope with you.
