Buying is the right answer more often than vendors like us admit
If your sales process is a pipeline with stages, contacts, activities and reminders, an off-the-shelf CRM will do it well, today, for a monthly fee that is cheaper than any build. Most organisations should start there, and a supplier who tells you otherwise before understanding your process is selling rather than advising.
The reason to consider anything else is not features. It is fit: the specific, awkward part of how your organisation works that the product cannot represent without everyone pretending.
Test one: where does your process stop looking like everyone else's?
Write down the path from first contact to signed, as it actually happens rather than as the handbook describes it. Then mark every step that a generic CRM would not have a field for.
Common examples we see in India: an approval that depends on a distributor's credit position held in the ERP; a quotation that has to be recalculated when a component price moves; an admissions counsellor whose follow-up rules change by programme and by cycle; a service contract whose renewal depends on how many tickets the customer raised last year.
If that list is empty, buy the product. If it has one item, configure a product around it. If it has three or more and they are the parts that decide whether you win, a built system starts to pay.
Test two: what happens to the data you cannot put in?
Everything a CRM cannot hold ends up in a spreadsheet next to it, and that spreadsheet becomes the real system. Ask where those spreadsheets already live in your organisation. They are an accurate map of the gap between the product you bought and the work you do.
This matters beyond tidiness. The moment the decisive data lives outside the system, forecasting, reporting and any AI you later want to apply all inherit the split, and someone reconciles by hand every month.
Test three: how many systems must it see?
A CRM that stands alone is easy to buy. A CRM that must read stock, credit terms, service history or campus records to be useful is an integration problem wearing a CRM's clothes, and integration is where the cost actually sits.
Before choosing, count the systems the salesperson currently opens in a day. If the answer is one, buy. If it is four, the decision is not about the CRM at all: it is about what joins those four together.
Test four: what does leaving cost?
Ask any vendor, including us, three questions. Can you export everything, in open formats, without asking permission? Who owns the data and anything derived from it? What happens if the supplier disappears?
A product you can leave cheaply is a safer purchase than a product with more features. This is the question buyers forget until the renewal, and the answer should be in the agreement before work starts rather than discovered during it.
The three honest options
In practice the choice is not binary. It is one of three.
- Buy: your process is ordinary, the product covers it, the integration list is short. Cheapest, fastest, and right most of the time.
- Adapt: the product covers most of it and you configure the rest — your approval chain, your fields, your reports. Costs more than buying and far less than building.
- Build: the decisive part of your process cannot be represented in any product you have seen, or the systems it must join are the real work. Most expensive, and occasionally the only thing that works.
How to find out in an afternoon rather than a quarter
Whichever direction you lean, test it against your real workflow before committing. Take the awkward part — the approval that depends on the ERP, the programme-specific follow-up rule — and see it on a screen with your own terminology and a plausible sample of your data.
If a product can be configured to do it, you have your answer and you should buy. If it cannot, you have learned that cheaply, and you know precisely which part has to be built rather than guessing at a whole system.
That is the entire argument for prototyping before purchase: not that custom is better, but that the decision is much easier to make with something in front of you.