The wrong question, and the right one
Software selection meetings usually open with the same question: "Which one is cheaper?" The answer is almost always off-the-shelf. It is billed monthly, it activates quickly, and the demo is polished.
A more useful question: how much of our operation has to change to fit this software, and what will it cost after three years?
Off-the-shelf products are built for their average customer. While your way of working sits near that average, they work well. The trouble starts when your business has rules of its own that are exactly where your advantage comes from: how you price, how approvals flow, how stock moves, how branches relate to each other.
When off-the-shelf clearly wins
Do not rush to build. Buy when:
- The process is standard and does not set you apart from competitors, such as basic accounting, attendance, or email.
- You need to be live in weeks, not months.
- There is no deep integration need with systems you already run.
- User count is small and stable, so per-seat cost stays flat.
If all four hold, buy it. Building custom for needs like these is waste.
Five signs it is time for custom
1. Your team works around the system. Patchwork spreadsheets, notes in chat groups, month-end reports rebuilt by hand. Each workaround is a hidden cost that never appears on the license invoice.
2. License fees grow faster than the business. Per-user or per-transaction pricing feels light at 10 people. At 80 people and more branches, the annual bill can match the cost of building your own system, and you still do not own it.
3. Your data is trapped. Ask your vendor today: can we export all of our data in an open format, and how long does it take? A vague answer is a warning. Your data is your most important asset, and you should not rent it forever.
4. Your business rules do not fit a settings menu. Tiered pricing per branch, commissions that depend on several conditions, layered approval chains. If the answer is "yes, with paid customization and a queue," you are already in custom territory, only on worse terms.
5. The system must run where the vendor never planned for. Locations without stable internet, sync across many branches, or integration with legacy systems that have no API.
Two examples from the field
A cash register that cannot stop. A motorcycle accessories workshop with several branches in Yogyakarta needed point-of-sale and payroll that match how they actually work, including one location with no permanent internet. Off-the-shelf POS usually assumes connectivity. We built an offline mode that keeps serving transactions and syncs to headquarters periodically. The register keeps running when the network drops, and the owner still sees every branch in one place.
From custom project to reusable asset. A multi-branch restaurant platform we built for one client was modular from day one. That is why its foundation can now grow into a product for other restaurants. Custom software that is designed well is not only a cost, it is an asset that can appreciate.
How to calculate: three-year total cost
Compare both options with the same formula. The table is an illustration of structure only, fill in your own numbers.
- Upfront cost (implementation/build). Off-the-shelf: Low. Custom: Higher.
- License or subscription, 36 months. Off-the-shelf: Continuous, grows with users. Custom: None or very small.
- Customization and integration. Off-the-shelf: Per request, often paid. Custom: Part of the design.
- Cost of workarounds outside the system (team hours). Off-the-shelf: Often uncounted. Custom: Near zero.
- Maintenance. Off-the-shelf: Included in license. Custom: Annual maintenance plan.
- Ownership of code and data. Off-the-shelf: Vendor. Custom: You.
The two most forgotten items: team hours spent patching system gaps, and the cost of switching vendors in year five. They rarely appear in any proposal, yet they are real in your financial statements.
The risks of custom software, and how to manage them
- Dependence on the builder. Mitigation: require source code, documentation, and a clear maintenance plan in the contract.
- Scope creep. Mitigation: build in stages, starting with the single most painful process rather than the whole company at once.
- Build time. Mitigation: ship the first module in weeks, then iterate from real usage.
The healthiest decision
For most mid-sized companies the answer is not either-or. Use off-the-shelf for standard functions and build custom only for the processes that differentiate your business. What connects the two is a well-designed integration.
Not sure where to start?
We offer a free 30-minute consultation. Tell us which business process hurts most, and we will help map what off-the-shelf software can cover and what is worth building custom, including an estimated cost and time range. No obligation to continue.