· revenue engine
Contract renewal can create a useful review point for an MSP buyer. Renewal dates are rarely public, and a guessed date can make an otherwise relevant approach feel careless.
A respectful renewal workflow uses three timing states: verified, reported and unknown. The state controls the next research action and the language a salesperson can safely use.
Define the timing states
Verified
The organisation or an authorised source has confirmed the renewal or review window. Record who confirmed it, when, which service it covers and how long the information remains useful.
Reported
A credible source refers to the timing, but the buyer has not confirmed it. Record the source and the uncertainty. The next action checks the timing without presenting it as fact.
Unknown
No reliable source confirms timing. The account may still fit the MSP’s service model. Research should focus on service relevance and responsibility. Leave renewal out of the premise.
Never calculate a renewal date from an announcement unless the contract term and start date are explicit and current.
Build the account around service fit
Renewal timing cannot rescue a weak account. Check:
- user, site and support fit;
- location and travel coverage;
- service scope;
- technical and security requirements;
- transition capacity;
- likely service owner;
- exclusions and conflicts.
Public changes can supply context. Companies House offers free company and filing information and states that the register is not comprehensive. A change of address or officer may prompt research. The filing alone does not prove an IT review or supplier renewal.
Prepare for a supplier review
The NCSC’s supply chain principles provide useful questions for an IT supplier review. The guidance covers understanding risk, establishing control, checking arrangements and continuous improvement.
Translate the principles into discovery topics:
- services and data that depend on suppliers;
- minimum security and support requirements;
- subcontractors and third-party access;
- incident roles;
- assurance evidence;
- exit, transition and continuity.
These topics help an MSP show what a considered review looks like. They do not imply that the incumbent has failed.
Fictional example
A fictional example involves a multi-site business that publicly announced a managed service appointment several years ago. The announcement contains no term, start date or renewal clause. The timing state is reported history with current renewal unknown.
The MSP records strong geographic fit and a plausible multi-site support requirement. The account enters a monitoring queue. The conversation, if approved, can ask how supplier review works and whether a review is planned. The conversation cannot state that renewal is due.
If a responsible person later confirms a review window, the record moves to verified with the source, date and scope.
Set the review rhythm
Use the timing state to set the next action:
| Timing state | Allowed premise | Next action | Review rule |
|---|---|---|---|
| Verified | Confirmed review window and service | Prepare relevant review material | Reconfirm before contact |
| Reported | Sourced timing with uncertainty | Verify with the responsible area | Expire when source becomes stale |
| Unknown | Service fit only | Research ownership or monitor | Keep renewal out of the claim |
A monitoring date is an internal research prompt. A monitoring date is not a predicted renewal date.
Apply privacy and channel controls
ICO guidance says UK GDPR can apply when personal data is processed for B2B marketing. The rules vary by channel and subscriber type, and businesses or contacts can object. The current guidance is under review. Check the live position, lawful basis, transparency, suppression and objections before outreach.
Keep monitoring separate from contact
A review date tells the research team when to check the evidence again. A review date does not authorise contact. Keep monitoring, marketing approval and sales action as separate fields. This allows an MSP to maintain useful timing records without treating every internal reminder as a prospect claim.
When a source changes, preserve the old source and add the new one. The evidence trail should explain why the timing state moved.
Renewal-timing record
| Field | Entry | Source | Review date |
|---|---|---|---|
| Service-fit summary | |||
| Timing state | |||
| Service covered | |||
| Timing evidence | |||
| Responsible area | |||
| Supplier-review questions | |||
| Transition capacity | |||
| Stop condition | |||
| Next research action |
Before sales sees the record:
- [ ] Renewal timing is verified, reported or unknown.
- [ ] The source, date and service scope are visible.
- [ ] No date is calculated from incomplete contract information.
- [ ] Service fit stands without the renewal premise.
- [ ] Supplier-review questions do not attack the incumbent.
- [ ] Transition capacity has been checked.
- [ ] Stale timing has an expiry rule.
- [ ] Privacy, channel, suppression and approval checks are complete.
The MSP lead generation guide covers broader switching signals. To compare this timing workflow with Hyper’s MSP approach, visit the MSP growth page.
Sources and further reading
- Searching the Companies House register · Companies House
- Business-to-business marketing · Information Commissioner’s Office
- Supply chain security guidance: The principles of supply chain security · National Cyber Security Centre