By Siddharth GangalKeep opportunity-level deal management distinct from pipeline, review, metric, and strategy jobs
This page owns the complete opportunity-level operating discipline. Sales pipeline management owns the portfolio across opportunities; deal review owns the manager meeting; deal-management KPIs owns metric definitions; and AE deal strategy owns the rep’s strategic plan.
Do not treat a deal as a close date, amount, and stage. The record represents a changing decision process. Its purpose is coordination and truth: distinguish buyer-confirmed facts from seller inference, preserve contradictory evidence, show authority and restrictions, and make stage movement reversible when the underlying evidence changes.
A team can use this control with any suitable qualification methodology. It does not require a universal stage count, contact count, score, contract value, review cadence, or win-rate promise.
Define one stable deal record with explicit states, clocks, relationships, and authority
Give the opportunity a stable ID and define the account, product or service scope, currency, quantity, expected contract structure, owner, source, opened-at date, current state, target decision date, and authoritative system. Connect it to contacts, activities, requirements, artifacts, quotes, agreements, risks, approvals, and handoff records through explicit relationships.
Use states that describe business reality rather than seller optimism. Every state needs entry evidence, allowed actions, exit evidence, exception authority, rollback rules, and terminal outcomes. HubSpot’s documentation for object pipelines demonstrates configurable pipelines and stages; that product capability does not define the correct stages for a buyer.
Maintain separate clocks for state entered, evidence observed, target decision, commitment due, last verified, and record updated. One “last activity” timestamp cannot explain whether the decision process is current.
Write down field authority before connecting tools. The CRM may own opportunity identity and current state; a quote system may own priced configuration; a contract repository may own executed terms; a project system may own accepted implementation work. Derived summaries can propose updates, but they should not silently replace an authoritative artifact. Store stable source IDs and versions so a reviewer can trace and reverse a write.
Turn material assertions into sourced, dated, reviewable evidence
Each material assertion should have an evidence state: confirmed, inferred, proposed, disputed, missing, expired, waived, or not applicable. Record the statement, decision affected, source artifact, source person or system, observed-at, as-of date, owner, confidence basis, reviewer, restriction, and expiry or revalidation trigger.
W3C’s PROV-O supplies general Entity, Activity, and Agent concepts for provenance. The deal evidence register is an editorial application: the business case is not “confirmed” because a seller wrote it; a technical requirement is not current because it appeared in an old call; and a verbal intent is not an executed commitment.
Use sales discovery to collect and test early evidence. Preserve counterevidence and corrections. If two participants disagree about need, authority, scope, process, or timing, open a conflict instead of selecting the statement that supports the forecast.
Govern stage entry, allowed work, exit, rollback, and terminal outcomes
| Stage contract field | Question | Failure response |
|---|---|---|
| Entry | What evidence makes the state true? | Reject the move or mark an approved exception. |
| Allowed work | Which actions are appropriate here? | Block premature proposal, evaluation, or approval work. |
| Exit | What buyer or internal decision completes the state? | Keep the state open and assign the missing evidence. |
| Rollback | Which change invalidates the state? | Return to the prior valid state and preserve history. |
| Terminal | What closes, pauses, disqualifies, or transfers the deal? | Require reason, evidence, owner, and follow-up status. |
Test the workflow with normal and hostile cases: skipped stages, reopened opportunities, product-scope changes, split deals, mergers, owner transfer, duplicate accounts, multiple currencies, expired quotes, withdrawn approval, and late evidence. The pipeline-stage data-quality test owns the deeper measurement protocol.
Represent decision owners and relationships without inferring authority from titles
Map decisions before contacts: business priority, user workflow, technical fit, risk, finance, procurement, legal or policy, implementation, and final authorization as applicable. Then associate the appropriate participant, actual authority evidence, relationship, communication owner, restriction, and current status.
Salesforce documents opportunity teams for internal collaborators. That representation does not prove an external buyer role. The multi-threading guide owns permission-centered engagement; this page only requires the deal record to preserve the relationship and decision history.
Test aliases, changed employers, account merges, one person on multiple opportunities, several open opportunities at one account, departed champions, delegated authority, and access restrictions. Never store speculative personal or sensitive information merely because it might influence a sale.
Separate the internal plan from buyer-accepted mutual commitments
Maintain an internal plan for the seller’s work and, when the buyer agrees, a separate mutual action plan. Each shared commitment needs an outcome, owner, counterparty, dependency, evidence of acceptance, due window, status, change reason, and completion artifact. Dates proposed only by the seller remain proposals.
Do not call silence acceptance. A missed commitment should trigger clarification: still required, re-owned, rescheduled, blocked, withdrawn, or complete with evidence. Version material changes so both parties can see what moved and why. Keep private coaching, forecast probability, negotiation limits, and internal risk assessments out of the buyer-facing artifact.
Control risks, conflicts, exceptions, and qualified-owner escalation
Separate risks from facts. A risk has a condition, possible consequence, evidence, likelihood rationale if used, owner, mitigation, trigger, review date, and closure rule. Examples include missing decision authority, unresolved data boundary, unapproved claim, implementation dependency, quote expiry, or incompatible contract term.
Exceptions require an owner, approver, rationale, affected control, compensating action, expiry, and reapproval after material change. Never turn an exception into a permanent hidden process. A critical privacy, security, legal, financial, product, or claim issue goes to the qualified owner; the sales team should not interpret professional obligations to keep a deal moving.
Review a frozen packet and reconcile evidence, decisions, commitments, and state
Run review from a frozen evidence packet rather than memory. Inspect identity, current state, evidence freshness, required-decision coverage, unresolved conflicts, accepted commitments, commercial version, critical risks, next action, and change history. Reconcile the opportunity record against source artifacts and connected systems.
Calibrate reviewers on the same sample before using the review for coaching, forecast, or resource decisions. Compare their stage-validity and evidence-state judgments, inspect disagreement by field, adjudicate critical cases, and revise ambiguous definitions. A high-level score can hide a dangerous mismatch on approval, scope, price, or authority, so preserve item-level results and the evidence cited by each reviewer.
Useful controls include valid stage rate = opportunities whose required stage evidence passes ÷ opportunities reviewed, decision coverage = required decisions with a confirmed appropriate owner ÷ required decisions, and commitment reconciliation = matched current commitments ÷ commitments expected from the frozen plan. Report denominators, missingness, exceptions, and critical errors; do not convert these descriptive measures into a causal revenue claim.
The UK Government Analysis Function’s guidance on quality, uncertainty, and change is not a sales standard, but its emphasis on communicating limitations and revisions is a useful design reference.
Use a printable deal control record and close with an accepted handoff
| Block | Minimum fields |
|---|---|
| Identity | stable opportunity, account, scope, currency, owner, authority |
| State | stage, entered-at, evidence, exit gap, exception, rollback |
| Decision | decision, participant, authority, requirement, status, date |
| Evidence | assertion, state, source, provenance, restriction, expiry |
| Commitment | outcome, owner, acceptance, dependency, due, completion |
| Risk | condition, consequence, owner, mitigation, trigger, review |
| Control | version, approval, reconciliation, incident, correction, handoff |
At close, loss, pause, or transfer, freeze the final evidence packet, record the governing outcome and reason, reconcile commercial and operational artifacts, remove obsolete access, and obtain explicit handoff acceptance. Gangly may support workflow work, but no first-party feature claim substitutes for this buyer-specific record, qualified approvals, or hands-on validation.
Test the operating design in a bounded pilot before applying it to every opportunity. Use representative new, active, reopened, transferred, won, lost, and paused records; seed duplicate, stale, contradictory, missing, and late evidence; rehearse rollback; and predeclare hard failures. Expand only when the record remains correct under those cases and the people responsible for review and handoff can operate it without hidden spreadsheets or oral exceptions.