When it does not fit
Nobody in your business has ever said “forecast category” out loud.
Every CRM and business system arrives with a vocabulary attached. Deal. Opportunity. Account. Pipeline stage. None of those are your words, and every person you hire has to learn the translation before they can do anything useful.
That is the visible half. The invisible half is that the software is asking questions your business does not have answers to, and not asking the ones it does.
How misfit shows up
Three symptoms, and they are all the same disease.
A spreadsheet beside the system. The most reliable diagnostic in business software. Nobody keeps a spreadsheet beside a system that fits. It exists because something the business genuinely needs has nowhere to live.
Required fields filled with nonsense. When a field is mandatory and irrelevant, people type a full stop. Now every report that touches that field is quietly wrong, and everyone has agreed not to mention it.
Reports nobody quite trusts. The number comes out, somebody says it does not look right, and a person is dispatched to check it against reality. At that point the reporting is decorative.
Why configuration does not fix it
You can rename the label. You cannot rename the model.
Most products let you rename fields, and it helps a little. What you cannot change is the shape underneath: what a record is, what can belong to what, which things can happen in which order.
If your business has jobs that belong to sites rather than to customers, and the product believes every job belongs to a customer, no amount of renaming fixes it. You will be entering the address as a customer for the next five years and explaining it to every new starter.
What fitting actually looks like
The new starter is useful on day two.
The measurable version of fit is onboarding. In a system built around how your business works, a new employee learns your business, and the software is just where your business is written down. In a system that does not fit, they learn your business, then the product’s model, then the workarounds that bridge the two.
That third thing is the expensive one, because it is undocumented and it is different in every team. See the custom CRM page for the same argument with a working example on it.
Common questions
Answered plainly.
Can we not just customise our existing CRM?
Up to a point, and it is worth trying first. You can usually rename fields and reorder stages. What you cannot change is the underlying model: what a record is and what can belong to what. When the mismatch is structural, configuration only hides it.
How do I know if our software actually fits?
Look for the spreadsheet beside it. That single diagnostic catches most cases. After that, look for required fields filled with junk, and reports somebody checks by hand before trusting.
Is a custom system harder to learn?
Usually the opposite. It uses the words your business already uses, so a new starter learns your business rather than your business plus a vendor's model plus the workarounds between them.
What if our process changes?
Then the software changes, because you own it. That is the difference between a system that has to accommodate your business and one that has to be accommodated.
What does it cost to fix?
From $5,000, fixed before we start. Whether it is worth it depends on what the misfit costs you now, and the free cost check is where we work that out with you rather than assert it.
Where to next
Name the field nobody fills in properly.
And the spreadsheet next to the system. Those two things describe the misfit better than any requirements document, and twenty minutes on them tells us whether a build is worth your money.