Start with the job that gets stuck
Your CRM may handle contacts, sales opportunities and follow-ups perfectly well. Then a renewal comes along, someone needs approval for a discount, and the work escapes into email.
That is a reason to investigate the renewal task. It does not yet tell you whether to change a setting, add a supported feature, connect another tool or replace the CRM.
Start by watching one person complete that task, including the awkward bits. Record what they enter, where they look for information, who decides, and how everyone knows the work is finished. Keep a separate list of what the CRM already does well. Those are things a proposed change needs to preserve.
A renewal that needs approval
Consider this hypothetical example: a sales representative prepares a renewal, a manager approves any discount, and the representative sends the agreed offer to the customer. Today, the representative copies the renewal into an email and later types the decision back into the CRM.
The complaint is simple: “We keep chasing approvals.” The cause needs a closer look.
- Can the CRM already assign an approval task, but people cannot find it or have never been shown how to use it?
- Can it store the renewal and enforce the right access, but needs a supported addition for approval steps?
- Does the decision depend on information held in another system that should remain responsible for it?
- Can the CRM represent a customer’s contracts and separate renewals accurately at all?
These answers lead to different changes. Adding another screen will not fix a task people cannot find. Connecting systems will not fix a renewal that is stored as the wrong kind of record.
Check what your actual CRM can do
Ask the administrator or supplier to demonstrate the complete task in your edition of the product, with the permissions your staff actually have. A demonstration from a more expensive edition does not establish what your current subscription includes.
Check configuration and training first. Perhaps an existing field, view, task or permission setting covers the gap. Have the representative and manager try the documented steps. If they can complete the job correctly, the next step may be a clearer screen or training rather than development.
If something is genuinely missing, investigate supported ways to extend the current product. Establish which extension points the provider supports, what your edition allows, who will maintain the addition, and how it will be tested after updates. “Customizable” on a sales page is a starting point for questions.
Microsoft’s model-driven app guidance gives a useful, bounded example: modeling the data, defining processes, composing the app and configuring security roles are separate parts of the work. It describes that platform; it is not evidence that every CRM offers the same controls.
Write down three credible options
For our hypothetical renewal, the decision note could contain the following three options. Each describes a possible fit and the evidence needed before choosing it.
1. Keep the work in the CRM
First test existing configuration and training. If they cannot cover the task, assess a supported extension that adds renewal approval inside the CRM.
Evidence needed: a demonstration using representative records and staff permissions; confirmation of edition and licensing limits; and a named owner for the extension, support and update testing.
2. Connect another tool
Keep the CRM for customer and sales work. Use a separate approval tool if it better fits the decision and has a clear reason to exist.
Evidence needed: which system owns the renewal and decision, what information crosses the connection, who may see it, and how a missing or conflicting update is noticed and corrected.
3. Replace the CRM
Consider replacement when essential records or rules cannot fit the current product through an acceptable configuration or supported extension.
Evidence needed: examples of the mismatch, a demonstration that the proposed replacement handles them, and a plan to preserve useful history, permissions and the work that already succeeds.
For this hypothetical case, the provisional choice could be: “Test the CRM’s existing approval facilities first. We have not yet established whether this edition supports the required permissions and renewal history. Continue if the trial proves both; assess an extension or connection if a specific capability is missing. Investigate replacement if the essential contract and renewal records cannot fit.”
When a connection earns its place
A connection is worth considering when each system has a clear job. In the renewal example, perhaps a separate service already holds the contract terms needed for approval. Bringing the relevant information to the decision may be more sensible than copying that service’s entire job into the CRM.
But agree what the information means. Does “approved” mean the manager approved a proposed discount, or that the customer accepted the renewal? Who can change it? What happens if the renewal changes after approval?
Microsoft’s guidance on translating between systems explains how different systems can interpret the same business concepts differently. It also identifies the extra work of maintaining that translation. You do not need to choose its particular architecture to ask the useful question: who will keep these meanings aligned?
Before selecting a separate tool, prove that the necessary connection is supported in the actual products and editions involved. Then decide who will deal with failed updates. A second subscription and a connector still need someone responsible for them.
When the CRM’s basic structure is the problem
By a core mismatch, we mean that the product cannot adequately represent the things your business needs to manage or the rules they must follow.
For example, suppose a customer can have several contracts, each with its own renewal, approval and history. If the proposed solution keeps overwriting one “renewal date” on the customer record, ask how it will preserve the other renewals. Check whether the product supports the necessary related records before concluding that replacement is needed.
If it can, a supported extension may be sensible. If it cannot, a succession of workarounds may leave the essential problem unresolved. That is stronger evidence for replacement than general frustration with a screen.
Replacement also has work attached: moving records and attachments, preserving useful history, setting permissions, rebuilding necessary connections and helping people do their jobs in the new system. Demonstrate the difficult renewal there before treating a polished sales demo as proof of fit.
For every option, ask who controls the records, who can export them, and what an export actually contains. Check the agreement and a sample export. Access to a screen does not by itself answer what happens to history, attachments or custom additions when you leave.
Compare the work after launch too
Put the same questions against all three options: who can request and approve a renewal, who maintains the solution, what happens after a provider update, and what continuing costs remain?
Include subscriptions and required editions, configuration or development, staff training, support, connection maintenance and eventual exit work where relevant. Use actual terms and estimates for this task. A small extension can have ongoing responsibilities; a replacement can introduce work well beyond the feature that prompted it.
The UK government’s technology purchasing guidance considers adapting existing products and building software alongside needs, capability and continuing supplier management. It offers a useful comparison framework, not a universal winner for a commercial CRM decision.
Test the smallest credible change
Choose the smallest option that could genuinely solve the identified gap. Use invented representative records in a supported test environment. Keep the trial away from live renewals, customer messages and production updates, and keep the existing process available until the trial has earned a wider rollout.
For the renewal example, test an ordinary approval, a rejection, a changed offer that needs fresh approval, and an attempt by someone without approval rights. If another system is involved, also test a missing update and its recovery. Decide beforehand how to stop the trial, remove its test records and settings, and retain its findings. A trial should not depend on undoing a real customer decision.
A useful result is concrete: the representative can see what needs action, the correct manager can decide, and the renewal retains the decision and its context. Record any remaining manual steps and give each one an owner. Then update the decision note with what the trial showed.
We provide custom software and API integration services. If you want help assessing a CRM gap, bring the troublesome task, an example record and the parts of the current system you want to keep. Scope, licensing, handover and ongoing care are agreed for the particular work.
Questions before you change your CRM
Could configuration or training solve the problem?
Yes, if the current edition already supports the complete task and the right people can use it with their actual permissions. Ask for a demonstration and let staff try it. If a capability is missing, assess a supported extension separately from configuration and training.
When is a connection better than replacing the CRM?
Consider a connection when the CRM still handles its main work well and another tool has a clear job. Confirm the products support the connection, agree which system owns each record and decision, and assign responsibility for failed or conflicting updates.
What happens to customizations after CRM updates?
That depends on the product, edition and kind of customization. Before approving the work, confirm supported extension points, provider support terms, who tests updates and who fixes incompatibilities. Do not assume an addition will keep working without care.
