The custom-versus-platform debate is usually framed as a budget question. It's actually a fit question: how far is your real workflow from the assumptions a generic platform makes?
Most CRMs assume a linear sales pipeline, one kind of customer record, and follow-up that lives in email. If that's roughly your business, configuration beats construction every time. The trouble starts when your process has structure the platform can't represent — referral partners who need their own view, a regulated communication step, an object that isn't a contact, company, or deal.
Three honest questions
- Where does your team currently work around the tool? Every workaround is a place the software's model and your business's model disagree.
- Which of those disagreements are cosmetic, and which are structural? Renaming a stage is cosmetic. Needing a 'property' or 'policy' object with its own lifecycle is structural.
- What would it cost to keep living with the workaround? Count re-entry time, dropped handoffs, and reporting you can't produce.
The hybrid answer is common
In practice, many teams need a configured foundation for the 80% of CRM work that is genuinely standard — contacts, pipeline, tasks, dashboards — plus custom components where their business is actually different. Insisting on all-custom multiplies cost; insisting on all-platform multiplies workarounds.
A useful rule: configure what is common to your industry, customize what is unique to your firm, and refuse to build anything you can't describe as a workflow someone runs today or has committed to run.