Back to all articlesSales pipeline design

Track parallel buyer approvals without turning them into a false sequence

Alactic Editorial10 min read

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

A buyer’s technical team is testing the proposed solution while security reviews supporting information, procurement sets up the supplier, and the commercial sponsor negotiates scope. Moving the opportunity from Technical review to Security review to Procurement makes that concurrent work look sequential. It also hides unfinished work whenever the stage changes.

Keep the main opportunity stage tied to the buyer’s overall progress toward a purchase. Track each review as a separate workstream with its own state, owner, blocker, evidence, and next action. Then define which workstream outcomes are required for the next overall stage—not which team supposedly goes first.

The practical result is one opportunity with several live reviews, rather than several competing versions of where the deal stands. The fictional worked example below shows how to represent that distinction and make a defensible stage decision.

1. Give the main stage one job

A main stage should answer: What purchase milestone has the buyer reached? A workstream state should answer: What is happening in this particular review? Mixing those questions creates ambiguous reporting.

For example, a stage called Security review could mean the buyer has just requested documents, the reviewer is evaluating them, or every other review is complete except security. Those situations need different actions, even though the stage label is identical.

A recommended stage design might distinguish these overall milestones:

  • Evaluation agreed: the buyer has agreed the proposed scope, review participants, and evaluation approach.
  • Evaluation underway: required reviews have owners and active work is taking place.
  • Decision ready: the buyer has the required review outcomes and can make the purchase decision without unresolved prerequisites.
  • Purchase authorized: the designated buyer authority has confirmed the decision, with any remaining execution steps tracked separately.

These are suggested labels, not a universal pipeline. Use milestones that fit your sales motion and define their entry conditions. Keep your organization’s closed-won definition separate and explicit; a positive review is not itself a completed sale.

If you need to see opportunities waiting on security, filter the security workstream. Do not make the main stage carry every possible bottleneck.

2. Build a small workstream record, not another pipeline

Each review needs enough structure to support a decision, but not an elaborate sub-pipeline that nobody maintains. Start with the same fields for every workstream:

  • Workstream: the distinct review or decision being tracked.
  • Required for: the overall milestone that depends on its outcome.
  • State: the current review condition.
  • Buyer owner: the person responsible for coordinating or confirming the buyer’s outcome.
  • Internal coordinator: the person responsible for keeping the record and next action current.
  • Blocker or condition: what prevents the required outcome.
  • Evidence: a dated confirmation or reference supporting the recorded state.
  • Next action and review date: who will do what, and when the record will be checked again.

Use a short state vocabulary: Not started, In progress, Blocked, Accepted with conditions, Accepted, and Not required. Keep the blocker in a separate field so that an ongoing review can retain its specific obstacle rather than disappearing into a generic red status.

Not required needs a reason and an appropriate buyer confirmation. Otherwise, it becomes a convenient way to remove uncomfortable work from the view. Accepted with conditions also needs the actual condition, including whether it must be resolved before the next milestone.

Where responsibility is still unknown, record Owner unconfirmed and assign an internal discovery action. An empty owner field should not look like an absence of work.

3. Use a filled parallel-review matrix to make the stage decision

Fictional worked example: All names, dates, scope details, and outcomes below are hypothetical. A seller is discussing a limited deployment with a buyer. The opportunity is currently at Evaluation underway. Technical, security, procurement, and commercial work are happening concurrently.

The agreed entry rule for Decision ready is: the buyer has confirmed the proposed scope; technical and security reviews have accepted that scope; procurement has confirmed a viable purchase route with no unresolved prerequisite to the decision; and the commercial sponsor has confirmed the proposed spend and decision authority. Any unresolved condition must be classified as either required before this milestone or explicitly allowed afterward.

The following filled matrix is presented as workstream cards so that blockers and evidence remain readable. Each card is one row of the same operating record.

Technical review

  • Required for: Decision ready.
  • State: Accepted with conditions.
  • Buyer owner: Maya, technical lead.
  • Internal coordinator: Eli, solutions lead.
  • Blocker or condition: Acceptance covers the limited deployment only. A proposed expansion needs a separate evaluation and is excluded from the current scope.
  • Evidence: Maya’s hypothetical 12 June evaluation summary confirms the limited scope meets the agreed technical criteria.
  • Next action: Eli to attach the confirmed scope to the opportunity and check that the commercial proposal matches it on 13 June.
  • Milestone effect: Satisfied for the current scope, provided the proposal does not include the expansion.

Security review

  • Required for: Decision ready.
  • State: Blocked.
  • Buyer owner: Noor, security reviewer.
  • Internal coordinator: Eli, solutions lead.
  • Blocker or condition: Noor is waiting for a response about one access-management question before recording an outcome.
  • Evidence: Noor’s hypothetical 12 June review note identifies the open question; no acceptance has been recorded.
  • Next action: Eli to coordinate a response by 14 June and ask Noor to confirm whether it resolves the question.
  • Milestone effect: Not satisfied. A response being prepared is not a review outcome.

Procurement review

  • Required for: Decision ready.
  • State: In progress.
  • Buyer owner: Jules, procurement coordinator.
  • Internal coordinator: Rowan, account owner.
  • Blocker or condition: The supplier record is being prepared, but the available purchase route has not yet been confirmed.
  • Evidence: Jules’s hypothetical 11 June message acknowledges receipt of the supplier information and says route confirmation remains open.
  • Next action: Rowan to ask Jules on 13 June which steps are prerequisites to the purchase decision and which can follow it.
  • Milestone effect: Not satisfied. Receipt of information does not establish a viable purchase route.

Commercial review

  • Required for: Decision ready.
  • State: Accepted with conditions.
  • Buyer owner: Sam, business sponsor.
  • Internal coordinator: Rowan, account owner.
  • Blocker or condition: Sam supports the proposed spend, but the designated budget approver has not confirmed authorization for the decision.
  • Evidence: Sam’s hypothetical 12 June meeting recap supports the scope and spend while identifying the outstanding approver confirmation.
  • Next action: Rowan to request an introduction to the budget approver on 13 June.
  • Milestone effect: Not satisfied. Sponsor support does not replace the required authority confirmation.

Resulting overall stage decision: Keep the opportunity at Evaluation underway. Technical acceptance supports the current scope, but security, procurement, and commercial prerequisites remain unresolved. Continue all three actions in parallel; do not wait for security to finish before clarifying the purchase route or decision authority.

The opportunity summary should name those unresolved conditions, not simply say Awaiting approvals. That gives the next reviewer a usable explanation of both the current stage and the route forward.

4. Separate evidence from activity and optimism

A workstream should change state because its evidence changed, not because the seller completed a task. Sending a questionnaire response demonstrates an outbound action. It does not demonstrate buyer acceptance. Scheduling a decision meeting demonstrates a planned event, not a decision.

Use evidence that identifies the source, date, scope, and outcome. A concise record could read: Buyer technical lead confirmed acceptance for the limited scope in the evaluation summary; expansion excluded. That is more useful than Technical looks good.

Where confirmation is verbal, record who said it, when, and what they confirmed. If authority or meaning is unclear, retain that uncertainty and request clarification. An internal interpretation should not silently become a buyer decision.

Evidence also has a boundary. Acceptance for one scope should not be carried over automatically when deployment size, commercial terms, or the proposed use changes. Record what was accepted so the team can recognize when a review needs to reopen.

5. Define gates without recreating a sequence

A milestone gate is a set of conditions, not an order of departments. Technical and security acceptance can both be required for Decision ready without either needing to happen first.

Write each gate in plain language and test it against the matrix. Avoid a rule such as All reviews complete unless complete has a shared meaning. It can otherwise include a finished seller task, a submitted document, or a confirmed buyer outcome.

Some dependencies are real. Procurement might need an agreed scope before it can confirm the relevant purchase route. Record that dependency on the affected action rather than forcing the entire opportunity into a sequential pipeline. Other procurement preparation may still proceed.

Distinguish three kinds of outstanding work:

  • Milestone prerequisite: must be resolved before advancing.
  • Permitted follow-up: may remain open after advancing, with an owner and explicit rationale.
  • Future-scope work: excluded from the current decision and reconsidered if scope changes.

This distinction prevents both premature advancement and unnecessary waiting. The technical condition in the fictional matrix concerns excluded future scope; the missing commercial authority confirmation concerns the current decision. They should not have the same effect.

6. Handle reversals, silence, and conflicting signals

The matrix is useful only if it can show deterioration as well as progress. If scope changes after acceptance, identify which workstreams are affected, mark their outcomes for reconfirmation, and reassess the overall gate. Do not erase the earlier evidence; retain it with its original scope.

If a reviewer stops responding, do not change In progress to Accepted because an expected date passed. Keep the unresolved outcome visible, note the last substantive confirmation, and assign an escalation or ownership-discovery action. A planned review date is a prompt to inspect the record, not an automatic acceptance date.

Conflicting signals also need explicit treatment. If a sponsor says procurement is finished but the procurement owner reports an unresolved prerequisite, record the discrepancy and seek clarification from the responsible buyer owner. Avoid choosing the more optimistic interpretation merely to preserve stage movement.

If a newly discovered prerequisite means the current milestone is no longer supported, correct the stage and explain why. Preserve the stage history where your recordkeeping allows it. A visible correction is more informative than keeping an advanced stage while hiding an unresolved prerequisite in notes.

7. Keep the record maintainable and reporting honest

The trade-off is additional recordkeeping. Too little structure hides risk; too much creates a second administrative system. Start with workstreams that can independently affect the purchase milestone. Keep routine tasks inside those workstreams rather than creating a separate approval lane for every document or conversation.

Maintain one authoritative record per opportunity. Whether you use related records, a structured note, or a linked worksheet depends on the tools available. Confirm workspace and current-plan availability before choosing a CRM implementation; this design does not assume any particular product control exists.

Keep overall stage reporting and workstream reporting distinct. Stage reporting shows buyer milestone progress. Workstream reporting shows unresolved prerequisites, missing owners, and overdue next actions. An opportunity can appear in several workstream views without being counted as several opportunities.

Avoid averaging review states into a completion score. Several accepted reviews cannot cancel out one mandatory unresolved prerequisite. If the team wants a compact summary, list the remaining gate conditions alongside the overall stage rather than presenting a percentage that suggests every review has equal weight.

8. Test the design on live records before expanding it

Run a small record-review exercise before redesigning the entire pipeline. The following is a hypothetical trial plan, not a benchmark: select five active opportunities with concurrent reviews and map each into the workstream structure.

  1. Write the next overall milestone and its entry conditions.
  2. Fill in each required workstream, including buyer owner, evidence, unresolved condition, and next action.
  3. Ask another team member to determine the stage using only that record.
  4. Compare their decision with the recorded stage and resolve disagreements by clarifying the evidence or gate.

Count missing buyer owners, unsupported acceptance states, unresolved conditions without next actions, and stage decisions that reviewers cannot reproduce. Recheck those counts at the next opportunity review. Fewer unexplained states and more reproducible stage decisions are observable signs that the representation is improving.

For the first record you update, end with one sentence: The opportunity remains at this stage because these buyer conditions are still unresolved. If the matrix supports that sentence—and gives each unresolved condition an owner and next action—you have a usable model of parallel buying work without pretending it happens in a line.

Sales pipelineBuyer approvalsCRM designOpportunity management

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