How to Review a Sales Pipeline and Keep Follow-Ups Moving

At Monday’s sales meeting, the team starts with a list of 42 prospects. Two people say they are “following up,” but no one can say when a buyer was last contacted or who should send the proposal. The owner sees Rp780 million in the spreadsheet and asks how much could realistically arrive this month. That large total does not answer the question.

A sales pipeline is a list of opportunities moving through a sales process. Its purpose is not to make a number look reassuring. It should help the team see what is happening with each opportunity, who owns the next action, and where work is getting stuck. Salesforce describes common stages such as prospecting, qualification, meetings, proposals, negotiation, closing and post-purchase follow-up. Your sequence may differ. Read Salesforce’s overview of pipeline stages as one framework, not a rule to copy.

Define stages by observable actions

Create stages that mark events someone can verify. “New prospect” means the team has recorded a contact and its source. “Need confirmed” means someone has asked about the problem, scope, timing and decision-makers. “Proposal sent” applies only after the document has actually been sent, not while a salesperson is drafting it.

Vague stages turn a meeting into guesswork. Words like “warm” or “promising” may feel familiar, but each salesperson can interpret them differently. Write one sentence explaining the entry and exit criteria for each stage. If an opportunity does not meet the criteria, do not move it just to make a column look more advanced.

A short process might run from incoming prospect to need confirmed, meeting, proposal, negotiation, won or lost. Add a stage only when it represents a distinct decision or piece of work that needs tracking. A service requiring a site survey, for example, may need a technical review stage because it has a clear owner and completion evidence.

Record the minimum facts for each opportunity

Each pipeline row should answer: who the buyer is, what need is under discussion, where the contact came from, who owns the opportunity, its current stage, the estimated value and its basis, the last interaction date, the next action, its owner and due date. Add the decision-maker’s contact and location or division when relevant. Avoid fields that never help anyone choose an action.

Opportunity	Need	Stage	Estimated value	Owner	Last interaction	Next action	Due
Bintang Clinic	Care schedules across branches	Need confirmed	Rp24m	Sales A	2 Nov	Confirm branch count	4 Nov
Pangan Utama Ltd.	Stock and order records	Proposal	Rp36m	Sales B	31 Oct	Send revised scope	3 Nov
Reka Studio	Project management	Meeting	Not estimated	Sales A	1 Nov	Schedule workflow demo	5 Nov

This is a synthetic example, not a record of real prospects. The names and values illustrate a possible format. Replace them with information your team has verified. “Not estimated” is more honest than guessing a value to make the total look complete.

For an estimated value, record what it covers: one-time or recurring charges, quantities, duration and unresolved assumptions. Do not combine agreed revenue with an opportunity still under discussion. If your team uses probabilities, explain how it calculates them and test them against available historical outcomes. Without enough past records, a percentage is not evidence; use stages and documented progress instead of invented odds.

Set rules for when an opportunity can advance

Do not rely on personal intuition as the only reason to move a deal. To move from prospect to confirmed need, for example, record the problem the buyer described, who will use the solution, who makes the decision and when they want to address it. Before a proposal, check the scope, recipient, timing and information needed to prepare it.

This does not require a long form after every conversation. A short note might read: “Needs stock records for three warehouses; operations manager is collecting requirements from other branches; requests a draft before 6 Nov.” That gives a colleague the reason for the stage and the next action. “Interested” does not.

When a buyer delays, do not leave the opportunity in the same stage indefinitely. Record an agreed follow-up date, or move it to a waiting status with a reason and review date. A stalled deal is not necessarily a lost deal; track the statuses separately so the team can distinguish them during reviews.

End pipeline meetings with an owner and a date

Start with opportunities that have overdue actions, high values but weak evidence, changed dates, or long gaps since the last interaction. For each row, answer three things: what is the latest fact, what is the specific obstacle, and who will do what by when. The meeting does not need to read every row from top to bottom.

Managers can group the pipeline by stage, owner, lead source, action date and value. Microsoft’s documentation on the sales pipeline chart explains visualizing opportunities by phase to spot concentrations. That view shows the distribution of recorded opportunities, not certainty that they will close. Check that stage definitions and records are consistent before drawing conclusions.

If a proposal needs an operations or finance review, make that work visible. Record the document to check, its owner, the date it was requested and the expected response date. Update a changed scope or schedule in the opportunity record instead of leaving it only in a disconnected chat. The manager can then distinguish an internal delay from a decision still pending with the buyer.

Read bottlenecks without blaming people

An opportunity that stays in one stage may point to several things: the need is unclear, an authorized decision-maker is not involved, a document is unfinished, the buyer’s timing has changed, or no next action was agreed. Check the record before concluding that a salesperson is inactive. Look at stage age across several opportunities, not one late row.

Separate activity measures from outcomes. Calls or meetings show work performed, not sales won. Pipeline value is the value recorded for open opportunities, not money received. Keep won, lost, waiting and active opportunities distinct so a report does not count all of them as certain results.

When an opportunity is lost, record a reason the team actually knows, such as a changed need or timing. Do not mark “price” unless the buyer said so. A short list of reason categories can help the team learn, but categories that are too broad hide the cause; leave room for a note when none fits.

When a spreadsheet becomes hard to follow

If several people update stages and notes without a clear change history, review whether the current record system is enough. Sora’s business app page says owners can describe a workflow or upload a spreadsheet to create a team application with roles, branches, approvals and reports. Its homepage describes AI-assisted work-app creation. Those capabilities may be considered for recording owners and work steps; they are not evidence that sales will automatically increase.

Before changing tools, clarify stage definitions and data ownership. See how teams record daily cash flow for an example of separating operational records from conclusions, and how purchase approvals can be tracked for linking decisions to an owner. Use only patterns that fit your sales process.

Test one cycle this week

Today, choose ten active opportunities. Check whether each has evidence for its stage, an owner, the last interaction and one dated next action. Flag those that do not qualify, correct the stage with its owner, then use the next meeting to assign actions and due dates. After several cycles, review which stages are most often delayed and look for causes in the records before changing the process.