Build or buy? Every business that outgrows its spreadsheets hits the custom CRM vs off-the-shelf question sooner or later, and most of the advice out there is written by someone selling one side of it. We build custom systems, so take this with that in mind. I'll still tell you where off-the-shelf is the better call, because for plenty of businesses it is.
The honest answer depends on three things: how standard your way of working is, how many people need access, and how much the gaps in a packaged product are costing you in time and workarounds. Get those clear and the decision mostly makes itself.
When off-the-shelf genuinely wins
Packaged CRMs exist for good reasons. The business.gov.au page on using AI in your business sums up the general case well: off-the-shelf tools tend to be cheaper, quicker and easier to put in place, and reliable because many users have already tested them. That applies to CRMs as much as AI tools.
Off-the-shelf is usually the right choice when:
- Your process looks like most businesses in your industry. Enquiry, quote, job, invoice, done.
- You have a small team and expect it to stay that way, so per-user pricing stays modest.
- You need something running next week, not next month.
- Nobody in the business has time to think about how the system should work. A packaged product makes those decisions for you, which is a feature as well as a limit.
- The tools you already use (accounting, email, calendar) have ready-made connectors that do what you need.
Here's something a custom builder probably shouldn't say out loud: if a mainstream product fits about nine-tenths of what you do and the last tenth is a minor annoyance, buy it. Spending money to fix a minor annoyance is how software budgets go sideways.
Take a hypothetical two-person bookkeeping practice in Geelong. Clients come in by referral, the work follows the same monthly rhythm, and the main need is a tidy contact list, reminders and a record of who asked for what. A mainstream CRM covers that on its cheapest sensible plan. Building something custom for them would be solving a problem they don't have.
When a custom CRM wins
The same business.gov.au guidance notes that custom solutions can be tailored to specific problems and are usually more flexible as a business grows, while costing more and carrying ongoing support costs. That's a fair summary. The question is when the flexibility is worth paying for.
Custom tends to win when the way you work is part of your edge. Take a hypothetical pest control business that runs recurring service contracts, compliance paperwork for commercial sites and one-off residential jobs, all with different pricing and follow-up rules. A packaged CRM can hold that information. Whether it can run the business that way without three extra tools and a lot of copy-and-paste is another question. In practice the recurring contracts end up in one place, the compliance documents in a shared drive and the residential follow-ups in somebody's head, and the owner spends Sunday night stitching it back together.
Other signs custom is worth a look:
- You're paying for several subscriptions that each do one slice of the job, and staff re-enter the same details in more than one place.
- You want AI working inside your records, not as an add-on. Our guide to what an AI-first CRM actually does explains the difference.
- Your headcount is growing and per-seat fees are starting to sting.
- You've been told "that's on the roadmap" about the same feature for a long time.
The hidden costs of off-the-shelf
The sticker price on a pricing page is rarely what you end up paying. The business.gov.au page on choosing digital tools for your business recommends working out the total cost of ownership: the upfront cost plus running costs over the tool's life span. With subscription CRMs, a few costs tend to hide.
Add-ons and tiers
The base plan gets you in the door. Automation, reporting, extra pipelines, phone integration or AI features often sit in a higher tier or a paid add-on. Price the plan that does what you need, not the one on the banner.
Per-seat creep
Per-user pricing looks small for three people. Add an office manager, two apprentices who need the job list and a casual bookkeeper, and you're paying for seats that use a fraction of the product. Some teams end up sharing logins to dodge the cost, which creates a security problem to save a few dollars.
Workarounds
Every gap gets filled somehow: a spreadsheet on the side, a form tool, a shared inbox rule, a person who remembers to do the thing. None of those show up on an invoice. They show up as hours, errors and the one staff member who is the only one who knows how it all hangs together.
You don't own the changes
When the vendor changes a screen, retires a feature or raises prices, you adapt. You can request features, but you can't make them happen. For a business with standard needs that's fine. For one that depends on a particular workflow, it's a real risk worth pricing in.
Connectors that only go one way
A listed integration with your accounting package or calendar sounds reassuring. Check what it actually syncs, which direction, and how often. A connector that pushes new contacts across but never brings paid invoices back means someone still checks two systems every morning.
The hidden costs of custom
Custom has its own traps, and you should hear about them from a builder before you sign with one.
The build is only as good as the scoping. If nobody writes down how the business actually works, you'll get software that matches the builder's guess. Insist on a written scope and a fixed quote before work starts.
Support and changes cost money. Software needs updates, security fixes and the odd change as the business moves. Ask what ongoing support costs and how fast changes are turned around.
Key-person risk moves to the builder. If one freelancer built it and then disappears, you're stuck. Ask who owns the code and the data, where it's hosted, what documentation you get and what happens if the relationship ends.
Your data has to be in decent shape. Custom systems, and AI features especially, work best on clean, well-organised records. Budget time for the cleanup. Our guide to migrating from spreadsheets to a CRM covers that step.
Your team's time during the build. A good builder will want to sit with the people who do the work, test early versions and hear what's wrong with them. That's time away from paying jobs, and it's worth planning for rather than squeezing in.
You become the product owner. Someone in the business has to decide what the system should do. If that's nobody, custom will drift.
Custom CRM vs off-the-shelf at a glance
This table is a generalisation. Individual products and builders vary a lot, so use it to frame questions, not to make the decision for you.
| Factor | Off-the-shelf CRM | Custom CRM |
|---|---|---|
| Upfront cost | Low; mostly setup and data import | Higher; a scoped build |
| Time to start | Days to weeks | Weeks to months, depending on scope |
| Ongoing cost | Subscription per user, plus tiers and add-ons | Hosting, support and changes |
| Fit to your process | You adapt to the product | The product adapts to you |
| Changes | On the vendor's roadmap and timetable | Your call, at the builder's turnaround |
| Integrations | Whatever connectors exist | Built to what you use |
| Main risk | Workarounds and price rises | Poor scoping or an unreliable builder |
A decision checklist
Run through these with whoever handles the day-to-day admin, not just the owner. They usually know where the bodies are buried.
- List every tool you pay for that touches customers, quotes, jobs or invoices. Note the monthly cost and who uses it. Our guide to auditing your business software subscriptions has a method for this.
- Write down the five tasks staff repeat most often each week. Can a packaged product do them without a workaround?
- Count the people who need access now and in two years. Price the off-the-shelf option at that headcount, on the tier you'd actually need.
- List the systems it must connect to: accounting, email, calendar, phone, website, payments. Check whether the connectors do what you need, in both directions.
- Ask each option who owns your data, how you'd export it and what it costs to leave.
- For custom, get a written scope and fixed quote, and ask how changes are handled after launch.
- Compare the total cost over three to five years, including staff time spent on workarounds.
If off-the-shelf comes out ahead on most of these, buy it and don't look back. If it keeps losing on items two, four and seven, that's the pattern where custom tends to pay for itself.
A middle path worth knowing about
It isn't always one or the other. Some businesses keep their accounting package and build a custom CRM that talks to it, so the books stay where the accountant wants them and the customer side works the way the team does. That's often the most sensible split. Our article on connecting Xero or MYOB to your CRM explains what to sync, and our system integrations service covers how we connect the pieces.
The reverse also works. Plenty of businesses start on a packaged CRM, learn what they really need over a year or two, and move to a custom system once the workarounds pile up. That isn't wasted money. You arrive at the build with a clear list of what matters, which makes the scope sharper and the quote more accurate.
At Imagine AI we build custom AI-first CRM systems with a fixed quote before work starts, and changes after launch are done within days rather than queued for a roadmap. If you'd like a straight read on which side of this decision your business sits, book a 30-minute call with our team. If off-the-shelf is the better fit, we'll say so.
— Craig Winder, Founder
