Custom software or off-the-shelf?
Most small businesses should buy first. A few should build. This page sets out how to tell which you are, what each route really costs, and where each one lets you down, from someone who builds the custom kind and says so when it isn’t needed.
If one off-the-shelf product covers most of what you do and the rest is a few workarounds, buy it. Build when your process is part of your edge, when you are paying for several tools that don’t talk to each other, or when per-seat licences grow faster than the business. The best answer is often in the middle: keep the product that fits and build or connect the missing piece.
Custom vs off-the-shelf software, factor by factor.
| Factor | A custom system | off-the-shelf software |
|---|---|---|
| Cost model | Effort up front, paid in phases, then hosting and an optional support plan. No licence per user, so a new hire doesn’t add a bill. | A subscription, usually per user per month in tiers. Cheap to start, and it grows with seats, plan tier and add-ons. |
| Fit to your process | Built around your steps, documents and rules, so nobody works around the software. | Configurable within what the product allows. Fits well when your process is close to the standard one. |
| Time to start | A first version takes weeks of build, phased so the must-haves go live first. | Sign up today. Setup and importing your data still take time, but you can be running within days. |
| Integrations | Connected to the tools you actually use, including WhatsApp and your website, in both directions. | Popular tools are covered by marketplaces and public APIs. Gaps need a connector or a middleware tool. |
| Data ownership and export | Your data in the system’s own database, in a documented structure you can export. Agree what you receive at handover in writing. | Your data in principle. Export formats and what they include vary by vendor, so check before you commit. |
| Scaling with team size | Cost follows effort and hosting, not headcount. | Cost follows seats and plan tier: kind to a team of two, steeper for a team of twenty. |
| Updates and security | Changes when you ask for them. Dependency updates and fixes are covered by a support plan or done pay as you go. | The vendor ships improvements and security patches continuously, without you doing anything, on its own schedule. |
| Vendor dependence | You depend on whoever maintains the code. With one developer that is a real risk, so ask for the source and documentation. | You depend on the vendor’s roadmap, pricing and terms, which can change. |
- You need to be running this week, not in a month.
- Your process is close to the standard one: basic invoicing, a simple pipeline, email campaigns.
- The job is a commodity: payroll, accounting, email, document signing. Nobody wins by building these.
- You are one to three people and a free or low tier covers what you do.
- You want a vendor with a large team to keep improving the product and patching it for you.
- Your process is part of your edge and you don’t want to bend it to a template.
- You run four or more tools and people re-type the same data between them every day.
- Per-seat pricing grows with the team while the value to you doesn’t.
- You need quotes, bookings, invoices, a client portal and WhatsApp on one set of data.
What it really costs over three years
The monthly price on a pricing page is not the cost. Work it out as a sum. For a product: licence per user, multiplied by the number of users, multiplied by the months, plus the add-ons you will need (a marketplace connector, a higher tier for the feature you actually want), plus the setup and the hours your team spends working around gaps.
For a custom system: the build, which depends on how many modules you need and how many tools it must connect to, plus hosting, plus whatever you pay for support. The quote builder shows the build in hours and weeks so you can see what is driving it.
Then compare the two lines over three years rather than one. A product is cheaper in month one. A custom system tends to catch up when the team grows, when you would otherwise buy three products, or when the workarounds cost more in staff time than the licences do. If none of those is true for you, buying is the cheaper route and I will tell you so.
Where each one breaks
Off-the-shelf software breaks at the edges of its configuration. You ask for something the product does almost, and the answer is a workaround: a spare field, a spreadsheet next to it, a person who knows the trick. It also breaks on price when seats multiply, and quietly when a vendor changes a plan or retires a feature you depended on.
Custom software breaks in different places. A badly scoped build runs late. A system nobody documents becomes hostage to its author. And a custom system doesn’t improve by itself: new features are work that somebody has to be paid to do. That is why I build in phases and write the structure down.
Commodity or edge: a quick test
Ask of each part of your operation: if a competitor used the same standard software for this, would it matter? For accounting, payroll and email the answer is no, so buy. For how you quote a job, schedule a crew, qualify an enquiry or onboard a client, the answer is often yes, and that is where custom software earns its place.
Storex is a good example of the second kind. It began as a small client and invoice tracker synced with the company’s Wix site and grew into the platform the office and crew run on every day. The Storex case study shows what it does today.
The hybrid: keep what fits, build or connect the rest
This is not an either-or. Keep the accounting package your accountant already knows and connect it. Keep the website platform and have its forms feed a proper client record. Keep the email tool and build the part that doesn’t exist: a quoting engine from your own rate card, a client portal or a booking flow with your rules.
That is most of what I do under integrations: the bridge between products you like, rather than a replacement for them. A hybrid is also the lowest-risk way to try custom, because the product stays in place until the new piece has proved itself.
How a switch works
Before buying anything, ask how you get your data out: which formats, whether history, attachments and settings come with it, and what it costs. Before building, ask the same of any developer, me included: what you receive at handover, and how you get your data out at any time.
A move from a product to a custom system is a data migration: export, clean, import, then check against the source before anyone switches over. The data migration guide covers the steps. Done in phases, the old tool runs alongside the new one until the numbers match. If you are still on spreadsheets, start with spreadsheets versus a system.
Questions, answered.
Is custom software always more expensive than SaaS?
No, but it is paid differently. SaaS is a smaller monthly cost that grows with users and plan tier. Custom is a build cost up front and then hosting and support. Over a few years, with a growing team or several tools replaced by one, custom can come out level or cheaper. For a team of two with simple needs, SaaS almost always wins.
What if the developer disappears?
That is the right question. With any single developer, ask for the full source code, the database structure and written documentation at handover, and keep your hosting accounts in your own name. Then another developer can pick it up.
Can I start with a product and move to custom later?
Yes, and for most businesses that is the sensible order. Your data moves across in a migration, and the product keeps running until the new system matches it.
Do I need custom software to get a Digitalise Your SME grant?
No, but custom software is an eligible cost under the scheme. Eligibility, quotations and timing rules apply, and work can only count once the grant is approved, so check the Malta page before you spend anything.
Read next, then decide.
Quotes, stock, staff, jobs and invoicing on one shared set of data.
ServiceCustom CRMEnquiries, clients, pipeline and follow-ups in one place, shaped to how you sell.
ComparisonSpreadsheets vs a systemWhen Excel or Google Sheets is enough, and the signs it’s time for a system.
ComparisonCustom integrations vs ZapierZapier and Make for simple automations, custom integrations for critical, two-way, high-volume jobs.
GuideData migration checklistA checklist for moving data to a new system: mapping, cleaning, duplicates, test imports and cut-over.
GuideWhat a custom CRM costsA custom CRM explained in build hours and weeks, with three worked examples.
Case studyStorexA storage and logistics company’s whole operation in one custom system: quotes, clients, invoicing, the warehouse and the crew in the field.
PagePricingHow a custom system is priced: what moves the number and typical build times.
PageComparisonsCustom software against HubSpot, Salesforce, Zoho, Odoo, booking apps, Zapier and spreadsheets.
Get a fixed quote.
Not sure which way to go? Scope it in the quote builder and I’ll tell you honestly whether custom is worth it for you.