Decision guide
Repair or replace your marketing and CRM tools?
An enquiry arrives, but the salesperson cannot see what the person asked. Marketing keeps sending a general sequence after a useful conversation has started. Your team copies information between tools because nobody trusts the connection.
These are good reasons to investigate. Start by following the work through the tools you already have. Find the specific gap, then compare keeping the setup, repairing it, extending it or replacing the part that limits you.
Your website, marketing tools, CRM and inbox may be separate products or parts of one platform. Either arrangement can need attention. An imperfect setup can still be a sensible fit if it helps your team do the necessary work reliably, at a cost they can support.
Start with one useful result
Choose a workflow that matters today. For a quote enquiry, the result might be: the right person can understand the request, find the relevant history and take the agreed next action without asking the customer to repeat themselves.
Trace one recent enquiry using records your team is authorised to access. If you need to share the example outside the team, describe it without customer details or use an invented test record.
- Enquiry
What was asked, when and through which route?
- Marketing context
Which offer or relevant interaction helps explain the request? Where is the source?
- Sales action
Who owns it, what can they see and what should happen next?
- Follow-up update
What changed, and which follow-up or marketing activity should continue, pause or stop?
These are jobs in the workflow. Several may happen in one tool. Mark any manual handoff, missing detail or delay between them.
Ask a sales rep to try the route. Can they answer a useful question or move the conversation forward? Watch where they search, copy information or work around the system. A CRM earns its place in daily selling when it makes that work easier. Include that benefit in the decision alongside reporting needs.
Keep stated needs and timing separate from guesses. A campaign response can provide context; it does not establish that someone has budget or is ready to buy. The next action may be an answer, a clarification, a later follow-up or relevant, permitted marketing.
Locate the gap before choosing a tool
Write down the last point where the information and action were correct. Then check what changes at the next step. More than one kind of problem may be involved.
- Process and ownership
- Does everyone agree what happens next and who does it? If the owner or next action is unclear, define it and try the workflow with the people doing the work. Include absence cover, training and a way to raise exceptions.
- Configuration
- Is the information available but hidden, or is an existing rule sending it to the wrong place? Inspect the actual view, field mapping, routing rule and user permissions. Test an appropriate correction within the team's access controls.
- Data
- Is the message missing, the status out of date or the same person represented by conflicting records? Identify where each fact comes from and which source should govern updates. Repair the cause as well as the records. Keep genuine new enquiries distinct from repeated delivery of the same request.
- Connection
- Does the right information exist in one place but arrive late, incomplete or not at all elsewhere? Check the transfer, matching rules, failures and recovery. This can happen between separate products or between parts of a combined platform.
- Platform limit
- Can the current setup meet the requirement at all, with an approach the team can maintain? Verify the actual edition, supported configuration, integration and relevant limits in current vendor documentation and a representative test. A frustrating screen or a failed first attempt is a reason to investigate further.
Write the requirement in business terms: “The rep needs the original request and relevant offer beside the next action.” That gives you something specific to test in both the current setup and a proposed replacement.
Compare four workable choices
Keep and simplify
Choose this when the existing setup meets the important needs, or a small amount of manual work is manageable. Clarify ownership, remove unnecessary steps and document the limits you accept.
- Test
- the team can complete the workflow reliably as agreed.
- Effort and risk
- internal time still counts; manual work may become harder as volume changes.
- Ongoing owner
- the person responsible for the workflow and its exceptions.
Repair
Choose this when a supported capability exists but configuration, data or working practices make it unreliable. Correct the specific defect and retest the affected route.
- Test
- the corrected record, rule or view produces the intended result without breaking another workflow.
- Effort and risk
- allow for investigation, cleanup, regression tests and training.
- Ongoing owner
- someone who can maintain the rules, data and documentation.
Extend or connect
Choose this when the core tools still fit and one bounded gap needs an additional connection or capability. Check supported options before adding custom work.
- Test
- the missing information or action arrives correctly, and failure and recovery are visible.
- Effort and risk
- include subscriptions, usage limits, dependencies and maintenance; another component needs care.
- Ongoing owner
- someone who can monitor the connection and resolve failures.
Replace the constrained part
Choose this when an essential requirement cannot be met reliably, or the cost and burden of maintaining the current approach make another option more sensible. Decide which component needs changing; the rest may still fit.
- Test
- a representative trial meets the essential requirements with acceptable daily effort.
- Effort and risk
- include data migration, history, permissions, connected workflows, training and disruption.
- Ongoing owner
- a named lead for the change and a named owner after launch.
Compare the same scope
For each viable option, write down one-time costs, recurring costs and internal hours. Include cleanup, testing, temporary workarounds, training and ongoing care. If replacing a tool, include contract commitments, any overlap while both systems run and a way to recover or pause if the change fails. Use the same comparison period and state any unknowns.
A useful comparison shows what each option will cost to run as well as to start. Ask the people using and maintaining it whether the proposed effort is realistic.
Test a small change before a large commitment
Choose one enquiry route and agree what a successful test looks like before changing it. Start with synthetic records in an appropriate test environment, with sending disabled or restricted to approved test recipients. Avoid triggering live customer activity.
Include these checks:
- A new enquiry reaches the right owner with the original question, source and useful marketing context
- An existing contact's new request keeps its own history and next action
- Repeated delivery does not create repeated work; a failed or delayed update is visible and recoverable
- An absent owner has cover and unanswered work remains visible
- A human reply or changed status has the agreed effect on pending follow-up
- Communication preferences stay intact and an enquiry is not treated as an automatic marketing signup
- A rep can find the context and take the next step without unnecessary searching or repeated entry
Keep the expected result, actual result and any remaining manual step beside each test. Compare the current and proposed workflow using the same tasks. Record handling time, corrections and failed or unassigned requests over a stated period. With a small sample, keep the counts and circumstances visible.
These checks show whether the workflow improved. Any claim about sales impact needs its own evidence.
When keeping the imperfect setup makes sense
Keeping it can be reasonable when essential tasks work, the manual effort is acceptable and someone owns the exceptions. You might also postpone a change while the requirement is unclear or nobody has capacity to test and maintain it.
Make that an explicit decision. Record the limit you are accepting, the person watching it and a review trigger, such as an agreed workload threshold, repeated missed handoffs or a contract renewal. Waiting still needs a safe way to handle the work today. An active security, privacy or data-loss problem needs prompt attention even if a wider replacement decision takes longer.
Use the decision worksheet
Use the worksheet to record the workflow, the requirement and the evidence for each viable option. Compare costs and internal effort over the same period, then agree who will test the proposed change.
View the worksheet prompts
Use one workflow and the same comparison period for each option. Fill this in locally in your own document. Record unknowns and how you will check them.
The work
Workflow and useful result: ____________________ Tools or modules involved: ____________________ Current failure and evidence: ____________________ Useful change for the rep or other person doing the work: ____________________ Essential requirement, shared acceptance test and acceptable manual steps: ____________________ Decision owner, workflow owner and review date: ____________________
Comparison period and currency: ____________________
The options
Keep and simplify
- Required change and evidence it meets the requirement: ____________________
- One-time cost and internal hours: ____________________
- Recurring cost and care over our chosen period: ____________________
- Main risk or unknown, and how we will check it: ____________________
- Who will maintain it: ____________________
Repair
- Required change and evidence it meets the requirement: ____________________
- One-time cost and internal hours: ____________________
- Recurring cost and care over our chosen period: ____________________
- Main risk or unknown, and how we will check it: ____________________
- Who will maintain it: ____________________
Extend or connect
- Required change and evidence it meets the requirement: ____________________
- One-time cost and internal hours: ____________________
- Recurring cost and care over our chosen period: ____________________
- Main risk or unknown, and how we will check it: ____________________
- Who will maintain it: ____________________
Replace the constrained part
- Required change and evidence it meets the requirement: ____________________
- One-time cost and internal hours: ____________________
- Recurring cost and care over our chosen period: ____________________
- Main risk or unknown, and how we will check it: ____________________
- Who will maintain it: ____________________
The decision
Preferred option and evidence for it: ____________________ Smallest trial and the result it must demonstrate: ____________________ Who will test it, including a daily user: ____________________ Conditions for proceeding, pausing or returning to the previous workflow: ____________________ If keeping or waiting, the accepted limit and review trigger: ____________________
You can rule an option out when it fails an essential requirement. Record why. There is no need to turn every option into a full project proposal.
This worksheet does not collect or submit your answers.
You can rule out an option that fails an essential requirement; record why. If you keep the current setup, name the accepted limit and the trigger for reviewing it.
Choose the change you can support
Start with the part of the workflow that makes the next action difficult. Keep what works, test the smallest worthwhile change and compare replacement when there is a clear reason for it.
ExactWork can help investigate the gap across marketing automation, CRM and the data between them, implement the agreed change and test the result.
Tell me what’s stuck.
Where does the work become difficult: the marketing context, the CRM record or the next sales action? Tell me the tools you use and one example of the gap. You can describe it without sending customer records.