Buy a standard CRM if your sales process looks like most sales processes and the job ends when the deal is won. Build one around the business when your process is unusual enough that the product would change how you work, when the cost of adapting and connecting it keeps growing, or when the work that matters most happens after the sale. For most businesses with a standard sales process, an off-the-shelf product is the right answer.
We are writing this for the owner or operations lead of an established Irish business whose sales, quotes and jobs live across spreadsheets, email and sometimes a CRM that half the team uses. We build custom CRMs, so we have an interest here. That is exactly why we start every conversation by asking whether a standard product would do the job.
When a standard product is the right answer
Products such as HubSpot, Salesforce, Zoho and Pipedrive are built around a sales pipeline. A lead comes in, someone qualifies it, it moves through stages, and it is won or lost. Contacts, companies, emails, tasks and reports hang off that pipeline.
If that describes your business, buy one. You get a mature product and a large pool of people who know how to set it up. Updates arrive without you paying to develop them, and it connects to most of the tools you already use. A sales team selling a defined service on a monthly fee, or a distributor selling from a price list, will usually fit well.
When a CRM goes unused, the usual cause is that nobody decided who enters what, when, and what happens when they do not. A system built from scratch fails for the same reason. Fix that before you change software.
Where the fit starts to strain
The case for building gets stronger as the following pressures add up. One on its own rarely justifies it.
How standard your process really is
Write down what happens from first contact to paid invoice, in the order it actually happens. If it reads like a pipeline with a few stages, you are in standard territory. Some processes branch by product, need technical detail before anyone can price the work, or loop back through revisions with the customer. Those will need the product adapted to hold them.
How much the business would have to bend
Every product makes assumptions about how a business works. Some bending is healthy, because a good product often reflects a better way of doing things. The warning sign is when the team keeps a spreadsheet beside the CRM because the CRM cannot hold something they need. That spreadsheet is where the real process lives, and the CRM becomes a second job.
What it costs to adapt and connect over years
The subscription is the visible cost. The larger one tends to arrive later. It comes as custom fields, workflow rules, paid add-ons and integration tools that pass data between systems. It also needs someone who understands how it was all put together. Each change is reasonable on its own. Over several years they can add up to a heavily customised system that you rent, and that only one person or one consultant fully understands. Ask what the setup will look like in year three, as well as on day one.
Who owns the data and how it leaves
With any product, check how you export your full record, including history, notes and attachments, and in what format. With a system built for you, check that you own the code and the database outright and can move them to another supplier. In both cases the question is the same. If the relationship ends, does your record come with you in a form you can use?
What happens after the sale
This is usually the deciding question. A sales CRM is built to get a deal to won. Many businesses do most of their work after that point, in quoting with versions, production, scheduling, delivery and invoicing. If those steps sit in other tools, the record breaks at the handover, and people rekey the same details into each system. We cover that handover in more detail in order to cash on one record.
How to make the decision
This is a short exercise, and it is worth doing before you speak to any supplier, us included.
- Map the process as it runs today. Follow three or four recent jobs from enquiry to paid invoice. Note every tool, every rekeyed detail and every point where someone chases someone else for information.
- Mark where the sale ends. Draw a line at the point a standard sales pipeline would call the deal won. Look at how much of the map sits after that line.
- Test one or two products against the map. Use a trial and enter a real job end to end, including the awkward parts. Note what needs a custom field, a workaround or another tool.
- Cost both routes over several years. For a product, include licences per user, add-ons, integration tools and the setup and changes you will pay someone for. For a build, include the build itself, hosting and the ongoing care any system needs.
- Decide what you must own. Settle where the record lives, who can change the system and how you would leave.
If the product holds the real job with light adaptation, buy it. If the map shows most of the work after the sale and the trial needed workarounds at every step, a system built around the business deserves a proper look.
A system built around one print business
Our enquiry to production study describes a system we built for a B2B print manufacturer. It shows why a sales CRM would have covered only the start of the job.
Work arrived by email, through website forms and through an online storefront. A print enquiry is only useful once its specification is captured, because nobody can price the job without it. So the system triages the inbox and pulls the print specification into a lead record.
From there, quotes are versioned. Revisions are kept alongside the earlier versions, so the commercial history of the job stays intact. The agreed quote then carries its terms into a production project, which holds the working files in permanent folders and connects to the accounting system. Artwork is checked against defined rules through a queue.
Almost none of that is a sales pipeline. Specification capture, quote versions, production files, artwork checks and the link to invoicing are the business itself. A standard CRM could have tracked the enquiry. Everything that made the job profitable would have lived somewhere else.
The study records 300% revenue growth within 12 months, measured as the client's total revenue in the 12 months after launch against the 12 months before. The system was one of several commercial changes in that period, so we do not claim the growth for it alone. What it did was give the business one record from enquiry to invoice while that growth happened.
That is the kind of work our custom CRM practice takes on. Where a standard product fits, we will say so.
What to ask before you choose
Whether you are talking to a CRM vendor, a consultant who configures one, or a team that builds systems, these questions will show quickly whether the fit has been thought through.
- Can you walk a real job of ours through the system, from first contact to paid invoice?
- Which parts of our process need custom fields, workarounds or a separate tool?
- What will this cost to run and change over several years, including add-ons and integrations?
- How do we export our complete record, with history and files, and in what format?
- Who will understand how this was set up in three years, and what happens if they leave?
- What happens to quoting, production and delivery after the deal is marked as won?
If your process has outgrown the tools around it and you want an honest view on whether to buy or build, you can start a project with us.
