Back to all articlesSales pipeline design

Prevent duplicate opportunities from representing the same purchase

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

Two sellers each have an opportunity for the same account. One came from an inbound enquiry; the other followed a conversation with a different stakeholder. Both have a value, a close date and a next step. Before counting both, ask whether the customer can actually make two purchases—or whether both records describe competing paths to one purchase.

Keep one active opportunity for each independently decidable purchase. Treat records as duplicates when their scope, buying decision, budget and commitment evidence point to the same purchase. Keep them separate when the buyer can approve and proceed with each independently. When evidence is missing, record the uncertainty and resolve it rather than assuming either duplication or additional demand.

The review below is a recommended operating practice, not an automated deletion process. It covers opportunity records only—not duplicate people, contact merging or changes to contact identity.

1. Define the purchase before comparing the records

An enquiry is evidence of interest, not necessarily a separate purchase. A new seller, channel, quote version or stakeholder does not by itself create another buying decision.

Write a purchase statement for each suspected duplicate:

The buyer is considering purchasing [scope] for [business purpose or location], through [decision process], using [funding source], with [current evidence of commitment].

Compare those statements before comparing record names. Similar titles can hide separate purchases, while different titles can describe the same one.

Use four tests:

  • Scope: Are the records for the same deliverables, users, sites, quantities or period? Could both scopes be fulfilled without supplying the same thing twice?
  • Buyer decision: Does one approval determine the outcome of both records? Can one purchase proceed if the other is rejected?
  • Budget: Is the funding additive or shared? Does spending on one reduce or replace the money available for the other?
  • Commitment evidence: What buyer action supports each purchase as distinct—such as an independently requested proposal, a separate approval path or a confirmed order?

No single field settles the question. One budget can support multiple purchases, and different departments can participate in one shared decision. Look for a coherent explanation across all four tests.

2. Use a filled review checklist, not a similarity score

Fictional worked example: All organisations, records, amounts, dates and evidence in the examples below are hypothetical. They illustrate a review method, not customer results.

A sales manager is reviewing several opportunities for fictional Northbank Services. The following filled checklist can be copied into a review note. Its purpose is to make the decision inspectable, not to produce a mathematical duplicate score.

Case A: Duplicate records for one purchase

  • Records reviewed: OPP-A, “Northbank central rollout,” owned by Maya; OPP-B, “Northbank operations enquiry,” owned by Leo.
  • Scope check: Both cover the same central operations rollout, the same users and the same implementation period. The latest proposals describe alternative packages, not additional purchases.
  • Buyer-decision check: Both stakeholders report into the same purchasing sponsor. The sponsor confirms that only one package will be selected.
  • Budget check: Both proposals draw on the same hypothetical £24,000 allocation. The amounts are alternatives, not additive.
  • Commitment check: OPP-A contains the sponsor-confirmed requirements and an agreed proposal review. OPP-B contains an earlier enquiry and a draft quote.
  • Classification: Duplicate opportunity records.
  • Disposition: Keep OPP-A active. Retain OPP-B as a duplicate record with a clear reference to OPP-A, using an available non-active status or documented equivalent.
  • Reason: One scope, one selection decision and one funding allocation; no evidence of a second purchase.

Case B: Separate purchases within the same account

  • Records reviewed: OPP-C, “Northbank training centre setup”; OPP-D, “Northbank depot setup.”
  • Scope check: Distinct sites and deliverables, with no overlapping quantities.
  • Buyer-decision check: The training director can approve the training-centre purchase; the depot director can approve the depot purchase. Either can proceed without the other.
  • Budget check: Separate confirmed allocations: a hypothetical £12,000 for training and £18,000 for the depot.
  • Commitment check: Each director has requested a site-specific proposal and confirmed a separate review meeting.
  • Classification: Legitimate parallel purchases.
  • Disposition: Keep both active, with distinct scope descriptions, next steps and decision owners.
  • Reason: The account is shared, but the purchase decisions and deliverables are independently supported.

Case C: Uncertain relationship between records

  • Records reviewed: OPP-E, “Northbank regional pilot”; OPP-F, “Northbank regional expansion.”
  • Scope check: The expansion may include the pilot sites, but neither proposal defines the overlap.
  • Buyer-decision check: It is unclear whether the pilot requires approval before expansion or is merely an alternative offer.
  • Budget check: Both sellers reference a hypothetical £40,000 programme budget. Neither has confirmed whether funding is shared or additional.
  • Commitment check: There are exploratory conversations but no buyer-confirmed relationship between the proposals.
  • Classification: Uncertain; do not consolidate yet.
  • Disposition: Preserve both records, identify the potential overlap and flag the values as non-additive in the management forecast until clarified. Assign one owner to obtain confirmation.
  • Resolution task: Ask whether expansion replaces, includes or follows the pilot, and whether either can be approved independently. Review after the next buyer conversation.

The uncertain case matters as much as the duplicate case. A forced answer can either erase a real purchase or leave unsupported value in the forecast.

3. Ask questions that distinguish alternatives from additions

A seller's assertion that “this is my deal” is not purchase evidence. Nor is the existence of two quotes. Ask questions that reveal how the customer intends to decide.

  • “If you choose this proposal, would you still consider purchasing the other scope?”
  • “Are these two offers alternatives, or do you expect to buy both?”
  • “Does this allocation cover both purchases, or would each require its own funding?”
  • “Who can approve each purchase, and can either proceed without the other?”
  • “Which deliverables, if any, appear in both proposals?”

Use existing evidence first so the buyer does not have to repeat information already provided. If clarification is still needed, coordinate one conversation rather than having several sellers ask contradictory questions.

Record the answer, who provided it and where the supporting note or document can be found. Distinguish a buyer-confirmed fact from a seller interpretation. “Probably the same budget” should remain an assumption, not become the basis for closing a record.

4. Choose the surviving record by evidence, not ownership politics

The oldest record is not automatically the right survivor. Neither is the record with the largest value or the most senior owner.

Prefer the record that best represents the current purchase: accurate scope, the clearest decision process, reliable commitment evidence and a next step agreed with the buyer. If another record contains important information, preserve that information or a usable reference before changing its status.

Separate record selection from seller credit. Decide who owns the next buyer action, then handle contribution or credit questions through the team's existing management process. Keeping duplicate pipeline open to postpone an ownership disagreement makes the pipeline less trustworthy without resolving the disagreement.

Do not add duplicate values together. For alternative packages, keep the currently supported amount under your normal valuation rules and retain the alternatives as context. If only part of the scope overlaps, identify that overlap before adjusting either record; do not close an entire opportunity merely because one line item is duplicated.

5. Leave a consolidation record that explains what changed

A duplicate status without an explanation invites someone to reopen the record later. Use a consolidation note that another manager can understand without reconstructing the entire conversation.

Filled hypothetical consolidation record for Case A:

  • Decision: OPP-A remains the active representation of the central operations purchase. OPP-B is retained as a duplicate, not counted as an additional purchase.
  • Evidence: The purchasing sponsor confirmed that the two proposals are alternatives for the same rollout and the same hypothetical £24,000 allocation.
  • Survivor rationale: OPP-A contains the current requirements and buyer-agreed proposal review.
  • Information preserved: OPP-B's initial enquiry, stakeholder requirements and earlier quote remain accessible through the retained record or an authorised reference. Its additional requirement has been added to OPP-A's scope notes.
  • Amount treatment: OPP-A retains the hypothetical £24,000 supported scope value. OPP-B's hypothetical £21,000 alternative quote is not added to it.
  • Stage treatment: Keep OPP-A at the stage justified by its evidence. Consolidation does not itself advance the purchase.
  • Ownership: Maya owns the next buyer action. Leo contributes the requirements he collected. Any credit decision is handled separately.
  • Next action: Maya confirms the consolidated scope at the already agreed proposal review.
  • Reporting treatment: OPP-B is excluded from active pipeline and sales-loss calculations through the team's supported duplicate disposition or documented reporting adjustment.
  • Authorisation: The sales manager approves the disposition; an authorised record owner makes the changes.
  • Reversal condition: Reassess if the buyer confirms an additional, independently approved scope.

Check which statuses, references and reporting options your workspace and current plan support before implementing this design. If no dedicated duplicate disposition exists, use a clearly documented convention and verify its reporting effect. Do not assume that marking a record inactive automatically removes it from every forecast or dashboard.

6. Handle partial overlap and recovery without rewriting history

The most difficult cases are not exact copies. A pilot may be included in a later rollout, a renewal may sit beside an expansion, or two sellers may have priced overlapping bundles.

For partial overlap, describe the shared component and the distinct component separately. Retain separate opportunities only where the remaining scopes represent separately supportable purchases. Avoid arbitrary value reductions that make the total look reasonable but cannot be explained from the proposals.

A later phase is not automatically a second current opportunity. Check whether it has its own decision and commitment evidence, or is simply an aspiration attached to the first purchase. Conversely, do not collapse a confirmed second purchase merely because it depends on successful completion of the first.

If a consolidation proves wrong, restore the separate purchase representation through your authorised process. Reference the original review, document the new evidence and check for duplicated tasks or outdated proposals. Correct the current forecast, while keeping the earlier decision explainable. Do not silently rewrite past reporting snapshots to make the mistake disappear.

Also distinguish duplicates from genuine losses. If the buyer rejected one real purchase and proceeded with another independent one, that is not duplication. Using a duplicate label to hide a lost decision damages the meaning of both pipeline and loss reporting.

7. Prevent recurrence at the moment an opportunity is created

Before opening another opportunity, require a short explanation of what makes the purchase distinct. This is more useful than relying only on matching account names.

A practical creation note includes scope, decision owner or process, funding relationship to existing opportunities and the buyer action supporting the new record. If any of these are unknown, say so. Unknown information is a reason to investigate, not to invent independence.

When an enquiry appears related to an existing purchase, route it to the purchase owner for review while preserving the new stakeholder's requirements. Do not suppress the enquiry simply because an active opportunity already exists.

Keep the review proportionate. Requiring extensive proof for every early conversation can discourage useful recordkeeping. Apply closer review when scopes overlap, proposals are alternatives, or several sellers are counting the same funding. Use a brief distinct-purchase statement for clearer cases.

8. Make the next review measurable

At the next pipeline review, select a manageable batch of same-account opportunities with overlapping scope. Record the number reviewed, the number classified as duplicates, separate purchases and uncertain cases, and the supported pipeline value before and after the review.

Track unresolved cases separately, with an owner and a next evidence-gathering action. Also check whether duplicate dispositions have accidentally entered loss reporting or remained in active totals.

The immediate success measure is not the largest reduction in pipeline. It is that every reviewed purchase has a defensible active representation, every separate purchase has evidence of independence, and every uncertain overlap has a visible resolution task. That gives the next forecast conversation a clearer starting point than a list of competing records.

Pipeline managementSales operationsOpportunity reviewsForecast quality

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