Track multiple decision-makers per account: Record each contact’s role in every opportunity separately; Use CRM fields to assign roles like 'evaluates delivery approach' or 'approval role to confirm'; Keep role updates visible—don’t change a person’s identity even if their role changes
Image: CRM Stack

Pipeline Design

Part of CRM contacts and account structure

Modelling several decision-makers in one account

Record each person's role in a particular CRM opportunity, distinguish confirmed decision-makers from assumptions and handle role changes.

Keep a person’s contact details on their contact record and record their part in each opportunity separately. An account-wide label such as “decision-maker” can mislead when the same customer has several purchases under discussion. Someone may approve one purchase, advise on another and have no role in a third.

Map the particular decision

For a proposed service contract, ask who requests the work, evaluates the proposal, approves expenditure and will use or receive the service. Do not infer authority from a job title. One person may fill several roles, and some roles may remain unconfirmed.

PersonPart in this opportunityWhat is known now
Operations managerEvaluates delivery approachHas asked for a revised scope.
Finance managerApproval role to confirmHas not joined the discussion.
Site leadIntended service contactNeeds to review the start date.

This is a hypothetical example. “Approval role to confirm” does not claim that the finance manager has approval authority.

Confirmed Roles vs. Assumptions in Opportunity Decision-Making

Confirmed Role
Finance manager – Approval role to confirm (not yet confirmed)
Assumed Authority
Operations manager – Evaluates delivery approach (no formal approval authority stated)
Unconfirmed Role
Site lead – Intended service contact (needs to review start date)

Put the role on the opportunity relationship

Link each relevant contact to the opportunity and record a role if the CRM supports it. Update the role as the decision develops without changing the person’s identity.

HubSpot supports several contacts on a deal, but descriptive association labels require a Professional or Enterprise subscription. Check whether the team’s edition and configuration can show the distinctions it intends to record.

Keep uncertainty visible

A primary contact is a route for a particular discussion; that designation alone does not prove purchasing authority. If it matters, record who supplied a role description and when it was confirmed. Keep inferred influence separate from what the customer has said.

If someone leaves, changes employer or delegates a decision, keep the opportunity and its relevant history. Update current relationships and the next person to contact. A person’s role in one opportunity can end while an earlier relationship remains part of the record.

Compare two opportunities under the same account. A colleague should be able to see who is involved in each, which roles are confirmed and which decision still needs clarification.

More from Pipeline Design

Contact Data

Choosing a unique identifier for customer records

Choose CRM identifiers for contacts, accounts and opportunities, and set matching rules for imports and other systems.

Contact Data

Separating contacts, companies and opportunities

Decide whether CRM information belongs to a person, customer account or separate sales opportunity, using a practical example.