Expand existing accounts with a verified adjacent need and coordinated ownership

Define the decision

A customer may already have open support issues, contractual boundaries or an agreed roadmap. An unrelated expansion pitch can undermine that context. Review the current engagement before contacting another team and keep the new offer distinct from work already included in the contract.

Work through the procedure

1. Confirm the account owner and current commitments.
2. Identify an adjacent need using authorized relationship evidence rather than speculative account research.
3. Explain what the proposed work adds and what remains outside the existing scope.
4. Agree who should introduce the topic and how the response will be coordinated.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Current engagement: definition review for the sales team
Adjacent possibility: finance uses a related metric with different exclusions
Unknown: whether finance wants a separate review
Next action: account owner asks whether a shared discussion would help
Do not claim the sales contact has endorsed an expansion without their agreement.

Read the result

The approach preserves the existing relationship while testing a specific extension. A referral to another team is useful only within the scope the customer actually agrees to. If an unresolved delivery issue should take priority, address that before asking for additional business.

Check before moving on

1. Avoid duplicate charges for work already included.
2. Keep active support and delivery context visible.
3. Do not enroll existing contacts in generic new-logo sequences.

Limits and next action

This is an account-management method, not a description of native customer-success or contract management in Zintara. Use the actual commercial record and relationship permissions when planning an expansion.

Source: Zintara product context; procedures and examples are editorial guidance