Pipeline Design
Part of CRM for relationship-led businesses
Tracking several opportunities within one customer account
Decide when one customer needs separate opportunities and keep each deal’s scope, people and outcome distinct.
Keep the agreed customer account as the relationship view and use a separate opportunity for each purchase decision that can have its own outcome. Link each opportunity to the appropriate account or buying unit. Give it a distinct scope, owner, relevant people and next decision so several possible sales do not become one ambiguous deal.
Test whether the decisions are separate
A new conversation is not automatically a new opportunity. Ask whether the proposed work can be won or lost independently of an open proposal. Different budgets, sites, scopes or approval routes can help reveal separate decisions, but none is decisive on its own. A request to revise the current proposal usually belongs on that opportunity.
For example, an established customer may consider an equipment upgrade at one site and a service extension across several sites. Record two opportunities if each proposal has a separate decision and outcome. A routine fault in the current service remains service work, even if it prompts discussion of an upgrade.
Account or buying-unit view / Individual opportunity
- Agreed customer identity and relationship owner
- Particular scope and purchase decision
- People connected to the wider relationship
- People involved in this decision
- Context useful across work items
- Current position, open question and deal owner
- Related work under that customer
- Amount, expected date and outcome when known
These are placement rules to agree locally, not universal required fields. Leave a date or role uncertain when the customer has not supplied it.
Make each opportunity recognisable
Use a name that distinguishes the proposed work, such as the site or scope, without exposing sensitive details in a widely visible title. Check the account and contact links when the opportunity is created. An account contact list does not prove that every person participates in every purchase.
In HubSpot, a deal can be associated with a company and several contacts. Descriptive association labels require a Professional or Enterprise subscription.
Pipedrive's default deal link permits one person or organisation; additional related people or organisations can be added through custom fields, with one additional contact per field. Creating those fields requires global-admin access or the relevant field-setup permission.
Confirm that each opportunity shows the people involved in that decision.
Keep each interaction with the right decision
When one person discusses both opportunities, identify which decision a call or email concerns. Record the meaningful update against that opportunity. Add account context only when the information affects the wider relationship; copying every note into both deals makes their histories harder to interpret.
Pipedrive activities can be linked to people, organisations, leads, deals or projects, and users need visibility into all linked items to see an activity. HubSpot's automatic associations depend on activity type, logging location and existing links. Inspect the resulting timelines before relying on a conversation appearing on the intended opportunity.
Review the account as several decisions
List each open opportunity once and ask for its separate next decision. Look for duplicated proposals, a deal with no current purchase path or one amount that combines unrelated work. Treat opportunity amounts as potential work, not certain sales. Closing one deal should leave the account and other decisions intact.
A colleague should be able to open the account, select the right opportunity and identify who acts next without reading every other deal. If that is difficult, correct the scope, name or links before adding reporting fields.
