CRM & sales / GUIDE + WORKSHEET
Fix your CRM or replace it?
Separate process problems from product limits, then compare a focused repair with the real work of a CRM migration.
THE STARTING POINT
First separate poor configuration and unclear processes from limits the product genuinely cannot meet. Try a bounded repair when the core workflow is supported. Replace the CRM when essential requirements remain unmet and the benefit justifies migration, training, integration, and ongoing administration.
Turn complaints into observable requirements
'Nobody likes the CRM' is a symptom, not a replacement requirement. Watch someone assign a lead, update a deal, and find the last customer conversation. Record the specific obstacle and whether it comes from missing information, permissions, layout, training, or an unsupported capability. Ask the team which change would make tomorrow's work easier.
Run a small repair trial
Choose one team and one workflow. Simplify its fields, define stages, establish ownership, and measure whether people can complete the task with fewer workarounds. Agree on the evaluation period and success criteria before making changes. A repair trial should answer a decision, not become an indefinite project that delays a necessary migration.
Compare the work on both sides
List the cost of maintaining the current setup alongside the work of moving: data mapping, historical relationships, integrations, reports, access, training, and support. Ask a replacement vendor to demonstrate your actual difficult cases. A clean demo with ideal data does not establish that your operating constraints will disappear.
WORKED EXAMPLE / ILLUSTRATIVE
Two fictional companies, different choices
The first company can perform its essential workflow but has accumulated confusing configuration. The second needs a capability it has verified the current product cannot support. The decision changes with the constraint, not the age of the software.
| Situation | Useful test | Possible direction |
|---|---|---|
| Forty required fields, unclear ownership | Simplify one sales workflow | Repair configuration |
| Essential access model unsupported | Demonstrate permissions in both products | Evaluate replacement |
| Reports disagree across tools | Trace definitions and source records | Investigate data flow before migrating |
MAKE IT USEFUL
Repair or replace decision
Use specific evidence rather than a software satisfaction score.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Include the people entering the data.
- Test your real edge cases in the replacement.
- Compare ongoing administration as well as setup.
- Assign an owner to the decision.
A replacement cannot resolve an undefined process by itself. Equally, do not force an unsupported critical requirement into endless workarounds.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.