Choose Between Renewing the Current Service and Offering a Smaller Scope
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A customer says they no longer need most of the service. The account team prepares a full renewal anyway, hoping to defend the relationship before the customer decides to leave. That approach skips the real decision: which arrangement, if any, can cover the customer's remaining needs without creating an unworkable service commitment?
Compare continuation, a smaller scope, and a pause where one is actually available. Start with current needs, test whether each option can be delivered, and state what the customer would lose. A reduced scope is worth proposing only when it remains useful on its own and someone has authority to approve it. A pause is appropriate only when the customer can manage without active service and the stop-and-restart conditions are understood.
The decision should produce a clear recommendation, not a menu of speculative offers. The filled hypothetical option table below shows how to make that comparison before discussing commercial terms.
1. Replace the renewal question with a service-fit question
“Will they renew?” is a forecast question. “What work still needs doing, and who will do it?” is a service-fit question. Answer the second before committing to the first.
Separate three things that often get bundled together:
- Required outcomes: work the customer still needs completed.
- Delivery activities: tasks currently used to produce those outcomes.
- Access and support: permissions, assistance, and continuity needed to keep the work functioning.
A customer may no longer need frequent planning meetings but still need exception handling. Removing meetings could be sensible; removing the specialist who resolves exceptions could undermine the remaining service. Equally, a familiar activity should not survive simply because it appeared in the previous agreement.
Ask the customer what has stopped, what continues, and what is uncertain. Record the evidence and its source. A sponsor saying “we need less” is a starting point, not a usable service definition. Confirm the change with whoever owns the remaining work.
2. Build a current-needs baseline before comparing options
Use a short needs record rather than editing the old scope line by line. For every continuing need, capture its owner, timing, consequence if uncovered, and whether the customer can handle it internally.
Fictional worked example: A customer previously used a managed service for routine request handling, weekly planning, and periodic improvement work. The customer has moved routine handling in-house. It still wants help with difficult exceptions and a monthly review of unresolved issues.
For this hypothetical customer, the baseline is:
- Routine requests: handled by the customer's operations team, with a named internal owner.
- Difficult exceptions: still need specialist input; the customer does not yet have an internal substitute.
- Monthly unresolved-issue review: still needed to decide ownership and next steps.
- Weekly planning: no longer needed because the customer now manages scheduling.
- Improvement projects: deferred, with no agreed restart date.
This baseline changes the renewal discussion. Full continuation would cover work the customer no longer needs. A smaller service might fit, but only if specialist support can operate without the removed activities. A pause would leave a known exception-handling gap unless the customer finds another owner.
Do not treat low recent usage as proof that a need has disappeared. Ask whether usage was low because the work stopped, access was difficult, the service was unsuitable, or the customer was waiting for a project to resume. Those explanations lead to different decisions.
3. Use a filled option table to expose the trade-offs
The following is a hypothetical comparison table, displayed as option rows so the detailed cells remain readable. These are fictional service arrangements, not claims that a provider offers them. The reduced scope and pause remain candidates until availability and authority are confirmed.
OPTION CURRENT SERVICE REDUCED SCOPE PAUSE, IF AVAILABLE
Needs covered Exceptions; monthly Exceptions; monthly No active service
review; planning; review needs covered
improvement work
Needs left uncovered None of the stated Improvement projects; Exceptions; monthly
continuing needs future needs outside review; any new work
the defined scope
Operating requirements Existing delivery Named customer owner; Customer takes over;
team and cadence intake criteria; stop/restart process;
specialist capacity access decisions
Approval needs Normal renewal Service owner and Policy owner and
authority; customer authorised commercial authorised commercial
acceptance approver; customer approver; customer
acceptance acceptance
Reasons to reject Unneeded work has Exceptions cannot be No replacement for
no credible purpose; separated safely; specialist work;
customer rejects fit capacity unavailable restart unclearContinuation: retain the existing delivery model
In this fictional case, continuation preserves specialist availability and the established working rhythm. It also retains planning and improvement activities that the customer has explicitly deprioritised.
That does not automatically make continuation wrong. It might be justified if the apparently optional activities are necessary inputs to reliable exception handling. The delivery owner must explain that dependency in concrete terms. “This is how we have always delivered it” is not enough.
Reduced scope: keep exceptions and the monthly review
The proposed smaller scope removes weekly planning and improvement projects. The customer owns routine requests, supplies relevant case information, and appoints someone to accept actions from the monthly review.
This option leaves deferred improvement work uncovered. It also cannot quietly retain all the responsiveness and flexibility of the larger service unless those commitments are explicitly feasible. Reject it if the remaining work depends on resources or activities that have been removed.
Pause: stop active service with a defined handoff
A pause covers none of the active needs during the paused period. It becomes credible only if the customer can own exception handling and unresolved-issue review without the provider.
For this example, that substitute does not yet exist, so a pause is not the recommended option. Even if the provider permits pauses, the team still needs to establish what happens to access, open work, retained information, and restart requests. Do not imply that paused service includes standby support.
4. Test the smaller scope for operational feasibility
A smaller scope should be a coherent service, not the old service with several lines deleted. Ask the delivery owner to walk through a realistic request from arrival to closure.
- Entry: How does the customer submit work, and what information must accompany it?
- Qualification: Who decides whether the request falls within the smaller scope?
- Delivery: Who performs the work, and which dependencies remain?
- Exceptions: What happens when the request exceeds the agreed boundary?
- Closure: Who confirms completion and owns follow-up actions?
In the hypothetical case, “specialist exceptions only” is too vague. The teams need a shared description of an exception, examples of excluded routine work, and an owner for disputed requests. Otherwise, the customer may send the same workload through a narrower label.
Capacity also needs checking. Removing recurring activities may not remove the need to keep specialist time available. If the delivery team cannot support the remaining commitment, revise the proposed service or reject it. Do not assume that reducing scope automatically makes delivery easier.
Record feasibility separately from customer preference. “The customer wants this” and “we can reliably deliver this” are different findings.
5. Distinguish an available option from an approved offer
Before presenting a candidate as something the customer can choose, verify whether the arrangement exists and who may approve it. A useful internal status sequence is:
- Candidate: worth investigating, with availability unconfirmed.
- Feasible: delivery requirements have been checked.
- Approved to offer: the authorised owner has accepted the proposed boundaries and conditions.
- Accepted: the customer has agreed through the required process.
These are recommended operating labels, not assumed software features. Use whatever shared record your team can maintain consistently.
Check the relevant service terms, workspace, and current plan where product availability is involved. A technical ability to disable an activity does not establish permission to offer a different service arrangement. Similarly, an account manager's support for a pause does not establish that a pause is available.
Keep the customer informed without overpromising: “We are checking whether exception support can be separated from the broader service. We will confirm the boundary and availability before asking you to choose.” That is more useful than presenting an unapproved arrangement and withdrawing it later.
6. Recommend an option by explaining the consequences
Do not ask the customer to interpret the comparison unaided. Give a recommendation tied to the needs baseline, then make its limitations equally visible.
For the fictional case, the provisional recommendation is reduced scope, subject to feasibility and approval. It preserves the two continuing needs while removing work the customer now owns or has deferred. Full continuation is the fallback only if the removed activities prove necessary to support those needs and the customer accepts that rationale.
A concise recommendation could read:
Based on the work you still need, we recommend retaining exception support and the monthly unresolved-issue review, if that arrangement is approved. Your team would own routine requests and scheduling. Improvement projects would not be included. A pause would leave exception handling with your team, so we would not recommend it until you have a workable substitute.
Then ask the customer to confirm the uncovered work and transferred responsibilities, not just the preferred option. Agreement that a smaller service sounds attractive is not confirmation that someone will perform the removed tasks.
If every available option fails the fit test, say so. Retaining an account through an arrangement neither side can operate is not a sound renewal decision.
7. Set recovery triggers before the new scope starts
Even a well-reasoned decision can fail when real work arrives. Define observable triggers for review rather than waiting for general dissatisfaction.
- Repeated out-of-scope requests: check whether the boundary is unclear or the customer's needs were understated. Clarify intake first; reconsider scope if the work genuinely persists.
- Unowned customer tasks: return to the named customer owner and agree a workable handoff. Do not silently absorb the tasks into the smaller service.
- Delivery dependencies reappear: have the service owner reassess feasibility and seek approval for any change before promising expanded support.
- A paused customer requests urgent help: explain the current service state and check available restart or separate-service routes. Do not assume immediate reactivation.
For a hypothetical initial review period, the teams might examine the first month of work. Record which requests were accepted, redirected, or disputed; whether required customer inputs arrived; and which unresolved issues lacked an owner. These observations show whether the boundary works. Renewal acceptance alone does not.
8. Make the next decision review measurable
Before the next renewal discussion, complete the comparison for one account whose needs have narrowed. Every continuing need should have an owner under each candidate option, or be explicitly marked uncovered.
Assign a person to resolve each feasibility and approval question, with an agreed response date. Keep candidates visibly separate from approved offers. Bring the customer a recommendation only after the relevant checks are complete.
The immediate output is a decision record containing the confirmed needs, the filled option comparison, the reason for the recommendation, customer-owned work, and a review trigger. The test is simple: can the customer and delivery team independently describe the same remaining service, its exclusions, and who owns the gaps? If not, the renewal decision is not ready.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications