Opportunity management process flowchart (stage exit criteria)

What the opportunity management process flowchart (stage exit criteria) process is

Opportunity management is what happens to a single deal between the moment sales accepts it and the moment it is closed on the record. It is not selling technique and it is not reporting: it is the set of rules that decide when an opportunity may change stage, what number it contributes to the forecast, when somebody senior looks at it, and what has to be written down when it ends. The chart below follows one opportunity end to end. It is accepted from a qualified lead with an amount, a close date and a source; tested against the exit criteria at the qualification gate; taken through discovery, a confirmed decision process, a priced solution and a versioned proposal; given a forecast category the sales manager either accepts or downgrades; put through a deal review if it is large enough; checked for activity so a quiet deal is worked rather than carried; negotiated to signature; and closed as won or lost with a reason that is still usable a quarter later.

This is deal governance, not the selling motion. A sibling template, the sales pipeline process, draws what the seller does inside each stage: the discovery call, the tailored demo, the technical validation, the discount approval. This chart deliberately draws the layer above that and repeats none of it. Its subject is the exit criteria that let a deal move, the forecast category it is carried at, the threshold that pulls a large deal into review, the activity rule that catches a stalled one, and the evidence the win/loss review works from. Two boundaries are worth marking on your own version. Upstream, lead capture, scoring and the marketing-to-sales handoff belong to lead management, so this chart starts at an opportunity that has already been accepted. Downstream, it stops when the outcome is recorded: order fulfilment, invoicing, collections and the onboarding handover each have their own process, and pulling them into one diagram is what makes an opportunity chart unreadable. Every threshold drawn here is a placeholder for a number your own commercial policy sets.

Four decisions carry the chart, and they sit where they do for a reason. 'Qualification criteria met?' is in the account executive's lane because the person who owns the deal has to be the person who admits it does not qualify, and its no-fit branch ends the opportunity on the record rather than leaving it to age quietly in an early stage. 'Manager accepts the category?' sits in the sales manager's lane, because a forecast category the seller sets alone is a hope; its downgrade branch loops back through a step that re-dates the deal and evidences the next step before it can be carried again. 'Above the deal review threshold?' is the only place seniority is spent deliberately, so the deals that get an hour of scrutiny are chosen by a written rule rather than by whoever asks loudest. And 'Activity in the last 30 days?' sits with sales operations rather than with sales, because hygiene enforced by the person whose commission depends on the answer is not enforced at all.

What this flowchart covers

In this template

• Five swimlanes (Account executive, Sales manager, Sales ops / RevOps, Customer and Finance) across six phases: create and stage, qualification gate, solution and proposal, forecast and deal review, negotiation and signature, and outcome and review
• A qualification gate with three real exits: a "Qualification criteria met?" decision that promotes the deal, sends it back through a step to name the economic buyer and the budget, or ends it at "Disqualify with a recorded no-fit reason" so no-fit deals leave the board instead of ageing
• Forecast discipline drawn as a loop rather than a field: "Set the forecast category for the deal" is followed by a "Manager accepts the category?" decision whose downgrade branch returns the deal for re-dating and an evidenced next step before it can be carried again
• A written threshold for scrutiny: "Above the deal review threshold?" routes large or non-standard deals through a finance review of margin, terms and delivery risk, while smaller deals pass straight on, so senior time is spent by rule rather than by volume of noise
• Stalled-deal hygiene owned by sales operations: an "Activity in the last 30 days?" check sends quiet deals into a re-engagement play and a "Buyer re-engages?" decision, which either returns the deal to negotiation or takes it out of the forecast with a reason
• Three closing routes and one learning loop: "Customer accepts the terms?" ends in signature, a competitive loss, or a no-decision branch that re-enters the re-engagement play, and both outcomes reach "Run the win/loss review on the deal" before the findings update the stage criteria

When to use this template

• You are defining or rewriting opportunity stages in a CRM and need the exit criteria, the forecast rules and the review points agreed before anyone configures a picklist
• The forecast keeps missing and nobody can say why, so you need to see where a category is set, who is allowed to challenge it, and what evidence a commit is supposed to rest on
• Deals sit untouched for weeks and are still carried in the number, and you want the stalled-deal rule written down and owned by someone other than the seller
• Closed-lost data is unusable because the reasons are free text, and you need one route out of the pipeline that captures the reason and the competitor separately
• You are onboarding account executives or a new sales manager and want the governance around a deal on one page rather than spread across a playbook and a spreadsheet

How it works

1. Rename the lanes to your roles

   Replace Account executive, Sales manager, Sales ops / RevOps, Customer and Finance with the functions you really have. Smaller teams have no revenue operations lane at all: give the hygiene steps to whoever administers the CRM rather than drawing a role that does not exist. If a deal desk or legal genuinely owns the large-deal review, rename the Finance lane instead of adding a sixth.

2. Write the exit criteria into every stage

   The chart is only worth drawing if each stage has a written test for leaving it. Decide whether you qualify on MEDDICC, on BANT, or on a list of your own, and record the specific evidence a deal needs: a named economic buyer, an agreed metric, a confirmed decision process. Put those tests in the step comments, so a stage change is a fact somebody can check rather than an opinion.

3. Define your forecast categories and their evidence

   Salesforce ships Pipeline, Best Case, Commit, Closed and Omitted, and most CRMs offer something similar. Whatever the names, write down what has to be true for a deal to be carried at each one, who may change it, and when the category is frozen for the period. A category anyone can set at any time, for any reason, forecasts nothing.

4. Set the deal review threshold from your own book

   The threshold on the chart is a placeholder. Replace it with a rule that matches your average deal size and your real risks: value, contract length, non-standard terms, a first deal in a new segment, or a strategic account. Say who chairs the review, who has to attend, and what the review is allowed to decide, because a review that can only encourage is a status meeting.

5. Choose the stalled-deal rule and who enforces it

   Thirty days is a starting point, not a standard. Take a number from your own median sales cycle and state what counts as activity, because a logged email is not the same as a meeting with the buyer. Then decide what the rule does: whether a stalled deal is flagged, dropped out of its forecast category, or closed after a second silent period.

6. Fix the close-lost reasons before you need them

   Replace free text with a short pick-list everyone applies the same way, keep the competitor in its own field, and give no decision a value of its own rather than folding it into a competitive loss. Then decide which deals earn a win/loss review: many teams review every loss above a value, plus a sample of the wins, so the process learns from both.

7. Walk it against three real opportunities

   Take a deal you won, a deal you lost to a competitor and a deal that simply went quiet, and trace each one through the chart with the people who worked it. Any decision described in the room that is not drawn, and any box everyone admits is skipped in practice, is the finding worth acting on before this is published to the team.

Frequently asked questions

What are the steps in an opportunity management process?

A qualified lead is accepted as an opportunity and sales operations stamps the amount, close date and lead source. The account executive tests the deal against the stage exit criteria, and it either moves on, goes back so the economic buyer and the budget can be named, or is disqualified with a recorded reason. Discovery and agreed success criteria follow, the buyer confirms the decision process and paper trail, the solution is built and priced, and a versioned proposal is issued. The deal is then given a forecast category, which the sales manager accepts or downgrades, and anything above the review threshold gets a finance review of margin, terms and delivery risk. An activity check sends quiet deals into a re-engagement play. Negotiation ends in signature, a competitive loss or no decision, and both outcomes are recorded before a win/loss review feeds the findings back into the stage criteria.

What is the difference between opportunity management and pipeline management?

Opportunity management is the governance of one deal: the criteria that let it change stage, the category it is forecast at, the reviews it attracts, and the record it leaves behind when it closes. Pipeline management is the aggregate view of all the open deals: coverage against target, stage distribution, ageing and conversion between stages. The two read the same data and answer different questions. A manager doing opportunity management asks whether this deal has earned the right to be called commit. A manager doing pipeline management asks whether there is enough of it, early enough, to make the quarter. A chart of this kind is drawn for the first question, because the second is a report rather than a process.

Who owns the forecast category, the seller or the manager?

Both, in sequence, which is what the chart draws. The account executive sets the category because they hold the evidence, and the sales manager either accepts it or downgrades it at the forecast call. Splitting it that way avoids the two usual failures: a category nobody ever challenges, which turns the forecast into a mood, and a category set only by management, which teaches sellers that their own read of a deal does not matter. Sales operations normally owns the definitions, the freeze date and the audit trail rather than any individual deal. Whatever you decide, write it down, because the argument is never really about the number. It is about who was allowed to move it, and when.

When should a deal be marked closed lost rather than left open?

When it fails a rule you wrote in advance, not when the quarter needs tidying up. Most teams use two triggers: the buyer has said no, or the deal has been silent past the stalled threshold and a documented re-engagement attempt has failed. This chart draws the second as an explicit path so that closing it is a decision somebody made rather than a slow disappearance. Leaving dead deals open inflates coverage, hides the real conversion rate and makes the close date field meaningless for planning. The counterpart discipline is that a closed-lost opportunity can be reopened or recreated if the buyer returns, so nobody is penalised for closing one honestly.

What should a win/loss review actually record?

Enough that somebody who was not on the deal can learn from it. At minimum: the reason from the fixed pick-list, the competitor where there was one, the stage at which the deal was really decided rather than the stage it happened to be sitting in, what the buyer said about price against value, and anything promised during negotiation that delivery now has to honour. Reviews are most useful run on a schedule against a sample of wins as well as losses, because a win examined only when it is being celebrated teaches nothing. Keep the output wherever the stage criteria live, so the next revision of the process is written from evidence rather than from the loudest recent deal.