Dievio
Key points
- Begin with the existing customer relationship and a specific supported need
- Separate first-party usage and CRM context from discovered contact records
- Review responsibilities and coordinate every next action with the account owner
A SaaS account-expansion list should begin with the existing customer relationship. Identify the customer's actual need, the team responsible for the account and the people whose work would change.
The list supports a coordinated customer conversation. Product usage, a company-size change or a newly discovered executive is a research input, not automatic evidence that the account wants an upgrade.
Agree the expansion question with the account owner
Review the current customer scope, known objectives, active projects and unresolved service issues. Ask whether the proposed change helps an observed need and who should discuss it first.
- Which team or workspace uses the product today?
- What specific additional workflow or operating need is being considered?
- What has the customer actually said or requested?
- Which promises, preferences and relationship constraints already apply?
- Who owns the next customer-facing action?
An open support issue may require service work before an expansion conversation. Do not treat renewal risk, heavy usage and buying intent as interchangeable labels.
Separate customer evidence from contact discovery
| Input | Possible use | Limit |
|---|---|---|
| Customer conversation | Understand the stated need and next step | One person's answer may not describe every team |
| First-party product activity | Investigate observed use within the available scope | An event does not by itself establish willingness to pay |
| CRM relationship record | Coordinate ownership, commitments and history | Old titles or notes may need review |
| Contact-discovery record | Find additional candidate responsibilities | It does not contain your private customer usage or complete approval process |
Dievio supports documented contact discovery and known-profile lookup. It does not natively observe your customer's seats, workspaces, contract, adoption or live expansion intent.
Map responsibilities for the proposed change
Identify the person who can explain the need, the operating users, relevant evaluators and any approval responsibilities. The appropriate group depends on the customer's actual workflow.
There is no mandatory Product–RevOps–Engineering trio for every SaaS expansion. A new operating team, customer-success contact or procurement function may matter more in a particular case.
The buying-group worksheet can help document responsibilities and unresolved questions.
Work through an illustrative expansion
Scenario: an existing customer asks whether a second regional team can use a workflow already operating in another region.
- Confirm the request and current account owner.
- Clarify what the second team needs and which parts of the current workflow apply.
- Identify a suitable operating contact for that team.
- Investigate relevant implementation, data-handling and purchasing requirements.
- Agree the next discussion and record who will coordinate it.
A regional operations leader might be the useful new contact. A CTO is relevant only if the proposed work calls for that responsibility; executive seniority alone is insufficient.
DievioYour next customer starts here.
Find decision-makers by role, company and location. Build your next prospect list in Dievio.
Find my leadsFree audience preview · No credit card
Find missing contacts with appropriate criteria
Use the known company domain and documented role criteria to discover candidates for a specific missing responsibility. Distinguish a parent company, subsidiary, regional entity and similarly named organisation.
Decision-maker search can support this research. If supported profile URLs are already known, lookup can return the fields available for those profiles.
Free count preview reports matching contacts, not expansion-qualified customers. Retrieve a bounded set using applicable credits and review the actual person-company relationship before using new records.
Reconcile new evidence with the customer record
Compare discovered candidates with existing CRM contacts. Preserve the original title, relevant source and unresolved identity questions instead of silently replacing a known relationship.
A matching name or shared company phone is insufficient for an automatic merge. A newly returned work email does not independently prove current responsibility or fresh mailbox verification.
Use the CRM data-hygiene guide when identity and field conflicts need an explicit review process.
Keep customer communication coordinated
Give the account owner the reason for including each new contact and the question they can help answer. Use the customer's actual context without inventing usage details in a message.
Review preferences, access to customer information and applicable communication requirements. An existing commercial relationship does not settle every future channel or data-use decision.
Use a customer-owned process for CRM writes, scheduling and notifications. An API retrieval is not a native automatic expansion workflow or a guarantee that a changed role has been detected.
Measure useful customer outcomes
Track supported needs, resolved responsibilities, agreed evaluations and customer decisions. Keep these separate from retrieved records, messages sent and raw product activity.
Include research and coordination effort, implementation implications and any effect on the existing relationship. Use the general account-expansion guide for broader account contexts.
Refresh the list when a new customer decision, observed role change or planned action warrants review. The objective is a relevant customer conversation with clear ownership.
