What are the real trade-offs?
Off-the-shelf
- Ready to use quickly
- Vendor handles updates and hosting (for cloud tools)
- Subscription or license fees, often per user
- You adapt your process to the software
- Roadmap decided by the vendor
Custom web app
- Takes time to design and build
- Built around your exact process
- You own the code and decide what comes next
- Needs ongoing maintenance and hosting
- No per-user fees to a vendor
When is off-the-shelf the right call?
- The process is standard: accounting, payroll, email, basic CRM, help desk.
- You need it working this month, not this quarter.
- The gaps are small and you can live with them, or change the process.
- Nobody in-house will own a custom system long-term.
Most businesses should run their accounting and core operations on established software. An ERP such as Odoo covers a lot of ground before anything custom is needed.
When does a custom web app pay off?
- The process is your edge. A quoting engine, a booking flow, a customer portal that competitors don’t have.
- Spreadsheets are holding the business together. Several people copy data between tools every day.
- You are paying for features you don’t use to get the one you do.
- Integration is the real problem. A small app that connects your existing systems can beat replacing them.
What costs do people forget?
| Off-the-shelf | Custom |
|---|---|
| Per-user fees grow with your team | Hosting, monitoring and backups |
| Paid add-ons for missing features | Bug fixes and security updates |
| Workarounds and manual steps | Changes as the business evolves |
| Data export limits if you leave | Documentation so others can maintain it |
How should you make the decision?
- Map the process — Write down each step, who does it and where the data lives.
- Trial the best products — Test two or three real candidates with your own data.
- List the gaps — Mark each one as “can live with”, “can change process” or “must have”.
- Size the custom part — Only the must-haves. Keep it as small as possible.
- Decide and own it — Name who owns the system, whichever way you go.
Can you combine both approaches?
Often this is the best route. Run accounting, stock and sales on a proven system, then build a small custom web app for the one process that makes you different — a customer portal, a quoting tool, a field-team checklist — and connect it to the core system through its API.
This keeps the custom part small, so it is quicker to build and cheaper to maintain, while the standard parts get updates from their vendor. It also avoids the riskiest outcome: rebuilding generic features such as invoicing from scratch.
- Keep the source of truth in one system.
- Let the custom app read and write through documented connections, not copied spreadsheets.
- Write down who maintains each piece.
Before building anything, check whether your core system already offers an add-on or setting that covers the gap. A small configuration change is always cheaper than new code.
Questions we get asked
Is custom software more expensive?
Upfront, usually yes. Over several years it depends on per-user fees, add-ons and the cost of workarounds on the other side. Compare total cost, not the first invoice.
Who owns the code of a custom app?
You should. Make sure your contract says the code, data and hosting accounts belong to your business.
Can we start off-the-shelf and go custom later?
Yes, and it is often wise. Using a product first shows you exactly which gaps matter.
Can a custom app connect to our existing software?
Usually, if those systems offer an API or data export. Checking that early is part of scoping.
Something else on your mind? Ask us directly →
