Managed IT services: renewal or repeat-engagement conversation
Use this renewal or repeat-engagement conversation exercise to review delivered work and current needs before proposing the next period or engagement. You are discussing a support and device-management service with the owner of a 60-person business. The point of the practice is to make a useful decision together, including recognising when the offer is not a fit.
Agree the next scope and approval process or document a clean, respectful handover.
The situation
In this fictional brief, support requests arrive through personal messages and urgent issues lack a clear owner. The buyer wants a documented escalation path and visible ticket ownership. Your offer is a support and device-management service, but you must first establish whether its scope addresses the actual need.
A relevant delivery constraint is that business-critical systems cannot be changed during working hours. Treat that as a fact in the exercise; do not remove it to make the sale easier.
| Your counterpart | the owner of a 60-person business |
|---|---|
| Offer under discussion | a support and device-management service |
| Evidence available | an example ticket lifecycle with triage, handover and closure evidence |
| Terms to clarify | Define supported devices, service hours, exclusions and escalation contacts. |
How to approach renewal or repeat-engagement conversation
A useful question for this stage: “If we were deciding from scratch today, what would you keep, change or stop?” Ask it when the conversation creates a reason for it, rather than reciting every question in order.
- Compare delivered work with the original scope. Discuss unresolved issues and changed priorities. Propose the next scope on current needs.
- Ground the discussion in the buyer’s work. Ask: “Which incident last interrupted work, and how was responsibility assigned?” Listen for a concrete example before making a claim.
- Use evidence relevant to the decision: an example ticket lifecycle with triage, handover and closure evidence. Explain what it demonstrates and what remains unverified.
- Agree the next scope and approval process or document a clean, respectful handover.
An industry-specific concern
Buyer: “Our existing IT person already handles everything.”
Possible response: “We can map the workload with them and identify gaps in cover; the conversation need not start with replacing anyone.”
Why this response helps: it acknowledges the concern, brings the discussion back to a verifiable requirement and leaves room for a different decision. Adapt the wording to what the buyer actually said.
Run the practice
- Prepare for two minutes. One person takes the seller role and one plays the owner of a 60-person business. Read the offer and constraint separately from your preferred answer.
- Have a five-minute conversation focused on review delivered work and current needs before proposing the next period or engagement. The buyer should answer consistently with the brief and ask for evidence when a claim is vague.
- Add this challenge: The buyer is broadly happy but cannot identify a reason to continue at the same level. Discuss right-sizing or ending the engagement.
- Pause for feedback. Quote one useful question and one missed opportunity. Repeat the difficult exchange using a different response.
- Finish by writing the actual agreement. A sensible option, when it fits, is to review a limited device group and agree escalation responsibilities. A clear decision to pause is also a useful outcome.
What to avoid
| Common mistake | Assuming a satisfied contact has approved another contract. |
|---|---|
| A stronger direction | Let us review the evidence and priorities before deciding whether the same arrangement still fits. |
| Scope and claim boundary | Response time is not resolution time; do not imply they are interchangeable. |
| What to measure in real work | ticket age by priority, with priority definitions agreed first. Establish a baseline and definition before interpreting a change. |
An example conversation
What has been useful so far, and what still needs to change?
Our concern is that support requests arrive through personal messages and urgent issues lack a clear owner. Also, business-critical systems cannot be changed during working hours.
Which incident last interrupted work, and how was responsibility assigned?
Our existing IT person already handles everything.
We can map the workload with them and identify gaps in cover; the conversation need not start with replacing anyone.
If we were deciding from scratch today, what would you keep, change or stop?
Your working sheet.
Make the exercise your own. Notes are saved in this browser when storage is available. Download a copy to keep; avoid confidential information on a shared device.
Example: support requests arrive through personal messages and urgent issues lack a clear owner; business-critical systems cannot be changed during working hours.
Example: If we were deciding from scratch today, what would you keep, change or stop? Industry question: Which incident last interrupted work, and how was responsibility assigned?
Example: an example ticket lifecycle with triage, handover and closure evidence. Response time is not resolution time; do not imply they are interchangeable.
Example: Propose a clear next step, such as: review a limited device group and agree escalation responsibilities. Confirm the owner and date.
Review your work
This is a reflection checklist, not an automated assessment.
Questions
Who is this managed it services exercise for?+
Can I use the example as a script?+
How should I assess the result?+
Fictional training scenario. The dialogue illustrates response choices; it is not a customer testimonial or a record of a real sale.
Explore more sales resourcesTake the conversation further.
Read a practical guide to structuring your sales practice, or explore the current London sales masterclass.
Plan your sales practiceExplore Jordan Belfort in London