Two Sales Opportunities at One Company: Keep the Decisions Separate
A client asks for a training workshop while another department discusses a process review. Both conversations belong to the same company. Should they share one opportunity?
Decide from the work and the buying decision. A single company record can provide shared context, while separate opportunity records keep different decisions visible. The right arrangement should let the team answer what is being considered, who is considering it and what happens if only one piece goes ahead.
Use the independent-decision test
Ask whether the client could accept one piece of work and decline the other. Could the timing, people approving it or next action differ? If so, keeping separate opportunities may make the work easier to follow.
If the discussion concerns two options for the same assignment, separate opportunities can create a misleading picture. The client may choose a workshop or a written review, rather than buying both. Keep that relationship explicit in whatever structure you use.
Creating another record should solve an operational problem. A new email thread, colleague or proposal revision does not automatically create another sale.
Draw the boundary in a short note
Consider this fictional example. A consultancy is speaking with Northbank about two assignments.
| Question | Workshop | Process review |
|---|---|---|
| Work under discussion | Train six team leaders | Examine the dispatch planning process |
| Main contact | Learning coordinator | Operations manager |
| Decision needed | Confirm attendees and dates | Agree which process to examine |
| Could proceed alone? | Yes | Yes |
| Shared dependency | Availability of the same consultant | Availability of the same consultant |
| Relationship | Separate work at the same company | Separate work at the same company |
The team keeps two opportunities because either assignment can proceed independently. Both link back to the same company context. A note identifies the shared consultant dependency so that two salespeople cannot promise the same time without checking.
Give each opportunity a specific name. “Northbank — team-leader workshop” is more useful than two records both called “Northbank project.”
Agree what belongs in the shared account
Shared information might include the company's current relationship with your firm and the person coordinating it. Opportunity-specific information includes the task, proposal, decision and next action for that assignment.
Avoid copying every note into both opportunities. Copies can drift. Instead, establish where the shared fact is kept and where colleagues should look. Confirm how your CRM represents those relationships; a link, a note or an agreed naming convention may be appropriate in your setup.
Name a coordinator when several people work on the account. They do not need to run every opportunity, but they should be able to spot conflicting promises and disconnected approaches.
Handle options and bundled work explicitly
Suppose Northbank later asks for a combined proposal. Record what changed: the two decisions may now be linked, or the proposal may simply package independent assignments for convenience.
Before altering the records, ask which decision the client is actually making. Mark older proposals and tasks clearly so a colleague does not continue to follow up on an option the client has replaced. If a combined opportunity becomes the team's working record, explain what happened to the earlier ones.
In a pipeline review, check for amounts appearing in both a combined proposal and its component opportunities. Whether your team counts the combined value or the independent parts, the view should make the chosen treatment clear. Do not assume that different record names prevent double counting.
Finish with a colleague test
Ask someone outside the two conversations to read the records and explain whether the client can buy one assignment without the other. They should also identify the next action for each and the person coordinating shared dependencies.
When evaluating Konekt CRM, use this fictional two-opportunity case. Check how your intended setup keeps the decisions separate and makes shared information available. Verify the actual relationship and reporting behaviour before adopting the structure for live work.