“We’re not ready to switch.” What to do next.
Respect the incumbent relationship and the prospect’s timing. Establish what is known, what must be confirmed, and a useful reason to reconnect—without urging early cancellation or guessing at notice dates.
Clarify what “not ready” means
Ask whether the barrier is satisfaction with the incumbent, a contract commitment, internal priorities, transition risk, missing evidence, budget review or another constraint. Acknowledge what works with the current provider instead of inventing dissatisfaction.
Confirm whether the prospect wants any follow-up. If not, respect that preference and do not keep contacting them.
Separate known facts from assumed dates
Ask whether the client can locate the agreement, renewal date, notice period and any required notice method. Record the source and who confirmed each detail. If the document has not been checked or the client is unsure, mark the status unknown.
Do not calculate a cancellation deadline from a guessed renewal date, tell someone to terminate early, or imply a prospect has missed a deadline. Encourage them to confirm contractual terms with the appropriate internal or professional resource.
Understand the transition constraints
Ask what must be true before a change could be considered: technical inventory, access and ownership, service expectations, backup and restore evidence, security requirements, specialist applications, internal approvals, and a feasible onboarding window.
Discuss a transition only at a high level until responsibilities and prerequisites are verified. Do not promise zero downtime, effortless migration or a specific timeline without evidence.
Offer a small, useful next step
Choose something the prospect has agreed is useful: document questions to take to the incumbent, map who needs to review a future option, or gather a missing technology or service expectation. Keep the task neutral and useful even if they remain with their provider.
Ask permission for a specific check-in tied to a confirmed event or prospect-selected date. If no reliable date exists, agree on a gentle interval only if they want it, and record the purpose—not a manufactured countdown.
Keep follow-up factual and proportionate
Summarize the incumbent strengths the prospect named, open evidence items, the status of contract timing, and agreed next steps. Use a short note with clear ownership. Update or stop follow-up when the prospect’s preference changes.
Before preparing a proposal, recheck service fit and identify the people who evaluate, approve and sign. If there is no fit or no permission to continue, close the loop respectfully.
Respectful renewal conversation plan
- Open without an ultimatum: “It sounds like you are not looking to make a change right now. Is it useful to map what would need to be true before you revisit it?”
- Recognize the incumbent: Ask what the current provider does well and what the prospect would want to preserve.
- Confirm, don’t infer: “Have you checked the agreement for its renewal date, notice period and notice method? If not, we’ll leave timing as unknown.”
- Surface readiness conditions: Ask about evidence, stakeholders, security, backup/restore, transition prerequisites and capacity for internal change.
- Agree on permission and next contact: Set a practical follow-up only with consent, tied to the prospect’s stated conditions. Make it easy to decline or pause.
This is a conversation structure, not legal advice or a recommendation to cancel a contract.
A hypothetical operations lead likes the current provider’s onsite support but says a recent service handoff has raised questions. Their agreement is in a shared drive, but no one has confirmed the renewal or notice terms. The MSP records renewal timing as unknown, asks permission to reconnect after the operations lead reviews the document internally, and offers a checklist of backup, service-expectation and transition questions. No one suggests sending notice or switching before those facts are understood.
Next action
Use the browser-local worksheet to track incumbent context, unknown dates, decision roles, transition prerequisites and evidence gaps. Recheck the service boundary before proposing a change and map the buying roles before preparing an approval path.