An existing customer may be easier to reach than a new prospect, but access is not evidence that an expansion is appropriate. Before proposing another service or business unit, check whether the first engagement is producing the agreed usable outcome. Expansion should address a distinct need the customer recognizes, with enough operational capacity to support both the current work and the next commitment.
Separate Satisfaction From Actual Use
A positive review meeting can coexist with low adoption. Ask what the customer now does differently, who uses the deliverable and which tasks still require the original project team. If a workflow was implemented, inspect whether its intended users can complete it. If the engagement produced advice, ask which decision it informed and what remains unresolved.
Keep commercial sentiment and operational evidence in separate fields. A supportive sponsor may want a broader relationship while the team still struggles with the first implementation. That does not make the sponsor’s interest invalid. It means the account plan needs a repair or adoption step before it adds another dependency.
Identify A New Problem With A Real Owner
Describe the proposed expansion in the customer’s terms. Identify the person accountable for the new problem, the affected team and the reason it matters now. A seller’s desire to increase account revenue is not a customer requirement. Neither is a list of adjacent services that happen to be available.
Check whether the new owner agrees with the current sponsor’s interpretation. An executive may support rolling a process into another department, while that department has different inputs or constraints. A short discovery conversation can reveal whether the expansion is a repetition of proven work, a modification or a separate project that requires its own assessment.
Use A Readiness Ledger
Record five items before preparing a proposal: the original acceptance evidence, unresolved commitments, the proposed new outcome, its accountable owner and the delivery capacity needed. Label each item established, uncertain or blocked. Attach a concrete record or conversation note rather than relying on a general account health color.
Illustrative scenario: a supplier has introduced a customer service workflow at one branch. Leadership wants it at two more branches. The first branch has documented ownership and uses the queue daily, but one reporting defect remains. The account team can consider expansion if the defect is bounded and owned. If staff still bypass the workflow for ordinary requests, further rollout would multiply an unresolved adoption problem.
Protect The Original Engagement
List the people and resources the expansion would share with current work. Check whether a new start would interrupt support, delay a promised correction or pull the only experienced operator away from the first team. A proposal should make these dependencies visible before the buyer commits.
Where readiness is incomplete, offer a sequencing decision rather than a disguised upsell. Finish the outstanding work, run a small transfer test or gather missing evidence first. Do not charge for correcting an agreed deliverable by relabeling the correction as expansion. Distinguish a defect in existing work from a genuinely new requirement.
Choose A Customer Review Point
Agree on the evidence that will support the next decision. A transfer test might show that a second team can use the workflow with ordinary training and a defined local owner. A separate service might require proof that its inputs are available and its output will be used. Use a review tied to that evidence, not simply the next billing date.
After expansion, evaluate both the new work and the original account. If the initial outcome weakens, investigate shared capacity and ownership before pursuing another sale. Healthy account growth requires maintaining what was already promised. Keep the account plan useful to the delivery team as well as the sales team.
Common Questions
Can We Discuss Expansion Before The First Project Ends?
Yes. Early planning can reveal dependencies and scheduling needs. Treat it as planning until the customer and delivery team have evidence that the next commitment is appropriate.
What If A Customer Requests More Work Despite Open Issues?
Document the issues and distinguish urgent new needs from unresolved obligations. Agree on resources and sequencing explicitly so the new work does not silently displace existing commitments.