Decide when parallel purchase paths should be separate opportunities
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
One department has approved its purchase. Another is still looking for budget. An optional addition has not reached a decision-maker. If all three sit in one opportunity, moving that record forward can make the entire amount look closer to purchase than the evidence supports.
Split an opportunity when the buyer can make separate purchase commitments and those commitments need independently meaningful outcomes, stages, or close dates. Keep one opportunity with workstreams when several activities support a single purchase decision, especially when the components cannot be bought independently.
The test is not how many departments, budget codes, sellers, or implementation tasks are involved. It is whether one purchase can proceed while another is declined or delayed. The worksheet below uses independent authority, commitment, timing, and purchase dependency to make that distinction visible.
1. Define the decision your opportunity represents
An opportunity should describe a purchase decision clearly enough that its stage, amount, and expected close date mean something together. If the stage refers to one part, the amount includes several parts, and the date belongs to whichever part is moving fastest, the record is no longer describing one coherent decision.
Start by writing a sentence in this form: This buyer is deciding whether to commit to this scope, through this approval path, by this expected decision date. If the sentence needs several unrelated approval paths or incompatible dates, investigate a split.
Separate opportunities are useful when they preserve independent outcomes. Workstreams are useful when they expose parallel effort without pretending that each activity is a separate sale. For example, security review, operational evaluation, and purchasing review may all belong to one opportunity if they lead to one commitment.
This is a choice about the unit of pipeline tracking. It does not require redesigning quote line items, changing account identity, or deciding who receives revenue credit.
2. Apply four tests before creating another record
Use these tests as a structured discussion, not a score that automatically produces an answer. Purchase dependency can outweigh differences in timing or ownership.
- Independent decision authority: Who can approve, reject, or defer each scope? Different contacts do not necessarily mean different authority. Two department leaders may recommend purchases while one central committee makes the only binding decision.
- Independent commitment: What evidence would establish that each scope is won? Could the buyer commit to one without committing to the other? Identify the observable commitment under your organisation’s closing rules rather than relying on enthusiasm.
- Independent timing: Can the decisions happen on different dates without changing what is being purchased? Different evaluation schedules are not enough if both must converge on one final approval.
- Purchase dependency: Can either scope actually be purchased if the other is rejected? Distinguish a genuine condition of purchase from a preference to buy together or a shared implementation task.
A useful counterfactual is: If purchase A were declined tomorrow, would purchase B still have a valid route to commitment? Ask the reverse question too. If both answers are yes, separate opportunities are often appropriate. If both are no, one opportunity with workstreams is usually clearer.
If only one answer is yes, the relationship is asymmetric. A base purchase may proceed alone while an addition depends on it. That can justify a linked addition opportunity, but only when the addition has a real buying process of its own.
3. Filled hypothetical decision worksheet
Fictional worked example: The following purchases, amounts, dates, and buyer roles are hypothetical. They illustrate a recommended tracking design, not customer results. A fictional supplier is reviewing parallel requests from a fictional buyer, Northstar Services.
Each entry records the same fields: scope, authority, commitment, timing, dependency, tracking choice, and evidence needed next. Copy these fields into a review note if your system does not offer suitable structured fields.
Entry A: Two departmental purchases
- Scope: Operations is considering a $24,000 purchase; Support is considering an $18,000 purchase.
- Authority: Each department head controls a separate approved budget. Central purchasing processes both purchases but does not require a combined decision.
- Commitment: Each department can issue its own purchase authorisation. Operations has completed its evaluation; Support has not.
- Timing: Operations expects a decision in September; Support expects one in November.
- Dependency: Either department can buy if the other declines.
- Tracking choice: Create two linked opportunities. Give each its own scope amount, evidence-based stage, expected close date, and next buyer action.
- Evidence needed next: Confirm the separate authorisation routes with each budget owner. Record explicitly that neither purchase requires the other.
The shared account and central purchasing contact do not turn these into one decision. Operations progressing should not advance Support’s stage.
Entry B: An optional addition
- Scope: A $30,000 core purchase and a possible $7,000 reporting addition.
- Authority: The core sponsor can approve the base scope. A finance manager must approve the addition.
- Commitment: The buyer is actively evaluating the core purchase. The addition has been mentioned, but no approver has agreed to evaluate it.
- Timing: The core decision is expected in October. There is no buyer-supported decision date for the addition.
- Dependency: The core can proceed without the addition. The addition requires the core purchase.
- Tracking choice: Track the core as an opportunity. Record the addition as a potential follow-up, outside the active opportunity amount. Do not create a forecastable addition merely because it has a price.
- Evidence needed next: Establish whether the finance manager wants to evaluate the addition, what decision is required, and when. If a distinct buying process develops, create a linked opportunity with the core dependency stated.
Independently sellable scope is not automatically an active opportunity. There must also be a purchase process worth tracking.
Entry C: Phased commitments
- Scope: A $12,000 pilot followed by a possible $48,000 expansion.
- Authority: A team lead can approve the pilot. An executive committee must approve expansion.
- Commitment: The pilot authorisation covers only the pilot. Expansion requires a new decision after a results review.
- Timing: The pilot decision is expected in August. The expansion review is planned for December.
- Dependency: Expansion depends on the pilot proceeding and meeting buyer-defined review criteria. Buying the pilot does not commit the buyer to expansion.
- Tracking choice: Keep the pilot separate. Create a linked expansion opportunity only if the buyer has established an active expansion decision process; otherwise retain it as future potential.
- Evidence needed next: Confirm who owns the expansion review, the agreed review criteria, and whether the review is a genuine purchase decision or only a discussion.
The pilot’s progress must not make the expansion look committed. Conversely, a single already-authorised purchase delivered in phases would normally remain one opportunity; delivery dates alone are not separate buying decisions.
Entry D: Mutually dependent components
- Scope: A $20,000 operational component and a $10,000 administrative component.
- Authority: Different department heads sponsor the components, but one committee approves the complete package.
- Commitment: The buyer will authorise only the combined scope.
- Timing: The operational evaluation finishes in September; the administrative review finishes in October. The combined decision follows both.
- Dependency: The buyer will purchase neither component alone.
- Tracking choice: Keep one $30,000 opportunity with separate evaluation workstreams. Advance its stage only when the evidence supports the combined purchase.
- Evidence needed next: Confirm the remaining committee conditions and the owner of each unfinished workstream.
Separate sponsors and review schedules create coordination work, not necessarily separate opportunities.
4. Make stages and amounts match the chosen unit
After a split, every opportunity needs its own reason for being at its current stage. Do not copy the original stage and close date to all new records just to finish the administrative change.
For the hypothetical departmental purchases, Operations might have completed evaluation while Support is still defining requirements. Their relationship does not justify equal stages. Likewise, the later purchase should not inherit the earlier close date simply because the seller wants one account-level milestone.
Allocate the original scope deliberately. The amount on each record should describe that record’s purchase decision. Do not leave the original combined opportunity open alongside its replacements with the same amounts still counted.
For a retained opportunity with workstreams, use workstream progress to explain what remains—not to substitute for the overall stage requirements. One review finishing is evidence about that review. It is not evidence that the buyer has approved the whole purchase.
5. Preserve dependencies without duplicating the pipeline
Splitting should not erase the relationship between purchases. Use whatever relationship mechanism your workspace supports, or maintain a clear cross-reference in the records. This is a recommended operating design, not a claim about any particular CRM feature.
For each linked opportunity, record:
- The related purchase and the nature of the relationship.
- Whether the dependency blocks evaluation, commitment, or only later implementation.
- The event that satisfies the dependency and the person responsible for confirming it.
- What happens to this opportunity if the related purchase is delayed or declined.
A shared implementation resource does not automatically require a combined opportunity. Two independent purchases can compete for the same delivery slot. Conversely, separate budgets do not establish independence when the buyer will authorise only a combined package.
Also distinguish parallel purchases from alternatives. If a buyer is choosing between two mutually exclusive packages, treating both as independent additive opportunities overstates the possible purchase. Preserve the alternatives within one decision unless your reporting design can explicitly prevent double counting.
6. Recognise the failure cases on both sides
Too little separation hides uncertainty. A combined record may repeatedly move its close date because different purchases take turns becoming the blocker. A small approved scope may carry a much larger unapproved amount into a late stage. Sellers may say a deal is partly won without being able to name what remains independently undecided.
Too much separation creates false precision. Records can multiply for every stakeholder, evaluation task, or proposed feature even though there is only one commitment. The result is duplicated activity, fragmented buyer context, and several forecasts that all depend on the same approval.
The practical trade-off is administrative effort versus decision clarity. Separate records are worth the effort when they let a reviewer understand genuinely different outcomes. They are not useful merely because the seller has different internal owners for different tasks.
Do not resolve ambiguous evidence by inventing certainty. Record the unanswered question and assign someone to verify it with the buyer. Until then, avoid advancing the combined scope on evidence that applies only to one part.
7. Recover when an opportunity is already structured incorrectly
A mid-cycle correction should preserve the sales history while making the current decision structure understandable.
- Write the scope map first. List the purchase decisions currently bundled together, their amounts, their authorities, and their dependencies.
- Choose the surviving structure. Decide whether the original record will retain one scope, become the single combined purchase, or be removed from active totals under your team’s established process.
- Reassess each decision. Set stages and dates from its own evidence. Assign a next buyer action and an accountable seller.
- Reconcile the totals. Explain every change in active pipeline as scope reassignment, removal of unqualified potential, or newly established buying scope. A structural edit should not silently create more potential revenue.
- Leave a dated explanation. State why the structure changed and how the old and new records relate. Follow your organisation’s reporting conventions rather than recording an administrative change as a buyer rejection.
If records were split unnecessarily, consolidate their decision context and preserve the workstreams. Ensure the redundant records no longer contribute duplicate amounts to active reporting. Check how your workspace handles record changes before editing historical outcomes.
8. Run a bounded review and measure clarity
Start with a small batch of opportunities where a seller reports partial approval, multiple budget owners, or repeated date changes. For example, a hypothetical review could cover five records at the next pipeline meeting.
Complete the worksheet for each purchase path. Require an answer to four questions: Who can decide? What establishes commitment? When can that decision occur? What other purchase must happen first?
At the end of the review, count how many active records still combine independently decidable purchases, how many separate records merely represent tasks, and how many decisions have no buyer-supported next step. Reconcile the amount before and after restructuring so duplicate scope is visible.
At the following review, check whether a buyer’s approval or delay can now be reflected without misrepresenting unrelated scope. That is the observable outcome to seek: not more opportunities, but records whose stage, amount, and date all describe the same purchase decision.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications