A full list of conversations can feel reassuring until you try to plan next month’s work. One person is exploring, another is waiting for an internal decision, and a third has accepted the scope but not paid. Calling all three “promising” leaves you with very little to act on.
Your Birmingham consultancy needs a pipeline that shows what has changed for the buyer and what you should do next. It should help you protect delivery time as well as win work. Start with a few meaningful stages and a dated action, rather than making every email another stage.
Gbeya’s workspace pipeline starts with New, Qualified, Proposal, Won and Lost stages, with opportunities attached to contacts. Use those labels with written definitions. A manual move to Won records the opportunity’s status; it does not by itself establish a received payment, a signed agreement or a successful client outcome.
Can you explain your next three opportunities?
Choose three active conversations and answer these questions from the saved record.
- What specific work is being considered, and what decision does the buyer need to make?
- What evidence places it in its current stage?
- Who owns the next action, and what date or event prompts the review?
- Is the amount a proposal, an agreed commitment or a confirmed payment?
- What would cause you to pause, revise or close the opportunity?
If two opportunities share a label but require different explanations, tighten the stage definition or the record before relying on the totals.
This diagnostic improves review discipline. It does not measure demand, predict an individual sale or establish payment.
Step 1
New
A specific enquiry exists; fit still needs checking.
Step 2
Qualified
The need and decision process are sufficiently understood to progress.
Step 3
Proposal
A defined scope is with the buyer for a decision.
Step 4
Won
Your written acceptance rule is met; verify the agreement separately.
Step 5
Lost
Close the opportunity with a factual reason and appropriate next action.
Step 6
Payment evidence
Check the paid-order record rather than treating a stage move as money received.
If the scope changes, reassess the stage. In the worked example below, £6,000 face value and £2,500 assumed weighted value are planning views, not collected revenue.
1. Decide when an enquiry becomes an opportunity
An enquiry says somebody contacted you. An opportunity says there is a particular piece of work worth evaluating. Write down the problem, the person involved and the next decision before assigning a value. A general networking conversation may remain useful without entering a revenue forecast.
For a defined workshop, qualification might mean that you understand the intended audience, the decision owner and the timing well enough to decide whether to scope it. These are your working criteria, not a universal checklist or a claim that budget must always be fixed before a conversation begins.
- Why this matters
- A clear entry rule prevents the pipeline from mixing ordinary relationships with commercially scoped work. It also stops a low-information lead from acquiring false precision through an estimated value.
- Work through the example
- Suppose a people director asks about a leadership workshop. Record the requested outcome and agree a discovery call. After that call, decide whether a defined workshop is appropriate, who will approve it and what information is still missing.
- When the approach changes
- A returning client may already have an agreed procurement route. Do not force them through irrelevant discovery questions merely to satisfy a stage template.
- Your decision
- Create an opportunity for a specific decision you can describe. Leave broad interest as relationship context until the next commercial step is clear.
2. Make each stage represent evidence, not optimism
Keep a short definition beside each stage. Qualified can mean that the project is suitable for scoping and the open questions are known. Proposal can mean that the agreed scope has been sent to the right person for a decision. Won needs your explicit commercial rule; write it down rather than letting the label decide for you.
Stage order should describe a useful process, but an opportunity can legitimately move backwards when facts change. If the buyer changes the scope, return to the relevant work. Do not keep an old proposal in a later stage simply because you have already invested time in it.
- Why this matters
- A stage is a summary of evidence. When people use different entry rules, the same column contains different realities and the summary becomes unreliable.
- Work through the example
- Two workshop enquiries reach Proposal. One has an agreed scope and a scheduled decision discussion; the other received an unsolicited document. Under your definition, only the first belongs there until the second has a meaningful decision route.
- When the approach changes
- A simple repeat workshop may go from a clear request to agreement quickly. The process should preserve evidence without manufacturing intermediate meetings.
- Your decision
- Write one or two observable conditions per stage and review the underlying record before moving it. If you need the software to prevent a move until those conditions are met, ask for that rule to be demonstrated.
3. Give uncertainty a next action and a review date
“Waiting to hear back” describes your position, not the buyer’s plan. When appropriate, agree what happens next and when you will review it. A task might be to clarify the delivery dates, provide a requested scope option or check whether the internal decision has moved.
Respect the person’s communication preferences and the basis for contacting them. A silent prospect is not an instruction to increase message volume indefinitely. Record a pause or a clear decline accurately; preserve the relationship without pretending the opportunity is active.
- Why this matters
- A dated task turns a vague open loop into a reviewable commitment. The date is a prompt to reassess the evidence, not permission to contact someone regardless of their preference.
- Work through the example
- Your contact expects an internal decision next Thursday. Agree a suitable check-in, assign the task and record the dependency. If the meeting moves, update the evidence and timing instead of keeping an obsolete close date.
- When the approach changes
- Some public-sector or large-organisation processes have a defined communication route. Use that route rather than inserting your preferred cadence.
- Your decision
- Every active opportunity needs a known next decision or a stated reason for the pause. Close or pause stale work deliberately rather than leaving it permanently warm.
4. Keep pipeline value separate from money received
A proposal amount describes possible business. A signed commitment describes an agreement. A paid order describes money recorded through a payment process. Those distinctions matter when you decide whether you can reserve delivery time or spend against expected income.
If you use weighted values, state how the probabilities were chosen. A default stage percentage is a modelling assumption, not evidence that your particular deal will close. Keep currencies separate and avoid treating a weighted total as a bank balance.
- Why this matters
- Multiplying value by a probability produces a scenario estimate. It does not convert uncertain work into an entitlement to revenue. The estimate becomes more informative only when the assumptions fit the opportunities and are tested against outcomes.
- Work through the example
- For one £4,000 proposal with an assumed 50% likelihood and one £2,000 proposal with an assumed 25% likelihood, the weighted scenario is £2,500. Either, both or neither can close; the £2,500 is not a receivable or a prediction of a particular payment.
- When the approach changes
- With only a few bespoke engagements, percentages may create more apparent accuracy than useful information. A clear range of possible delivery commitments may support the decision better.
- Your decision
- Label assumed probabilities, use one currency per calculation and reconcile actual payments separately. Use historical outcomes only when their scope is comparable.
5. Review renewal as a new decision, not an automatic victory
Finishing a successful engagement can open a useful conversation about what happens next. It does not establish that the client wants another programme. Review what was agreed, what was delivered and what the client says they need before turning a renewal into a new opportunity.
Keep the original engagement history intact. A new opportunity should describe the next scope and decision, so that a declined renewal does not rewrite the outcome of the earlier work. Before relying on automatic renewal reminders or stage changes, verify the trigger, recipient, timing and stop conditions.
- Why this matters
- A separate renewal decision preserves the meaning of the first engagement and makes the next commitment explicit. It also reveals when delivery capacity or a changed client need makes a different offer more appropriate.
- Work through the example
- At the final workshop review, the client identifies a different management problem. Record that need, agree whether a scoping discussion would help and create the new opportunity only when there is a concrete next step.
- When the approach changes
- If a contract already contains a renewal mechanism, follow its actual terms and applicable requirements. A CRM convention does not override the agreement.
- Your decision
- Treat renewal as evidence-led work with its own scope, owner and decision. Do not count it as won or paid because the earlier engagement went well.
A smaller, clearer pipeline can be more useful
Practitioner guidance argues for stages tied to buyer milestones and explicit exit conditions. That is useful for a consulting practice because the work depends on decisions about scope, timing and authority. It does not justify copying a vendor’s default stages or contact cadence without considering your clients.
The opposite risk is bureaucracy. A stage system can become so detailed that you update the board instead of understanding the opportunity. Our recommendation is to keep only distinctions that change your next action, and to preserve the supporting context in the record.
Research on CRM adoption and strategic alignment provides a reason to examine fit between technology and the way a business operates. The available abstract concerns Taiwanese IT-service firms; it does not establish a conversion uplift for your UK consultancy. Your own comparable outcomes remain the relevant check.
Start by reviewing whether your definitions make the next decision easier. Later, compare stage transitions and closed outcomes using the same period and scope. Avoid claiming improvement simply because more cards were added or a larger total appeared on the board.
High confidence in keeping evidence, next actions and payments distinct. The best number of stages and any probability model depend on your own work and observed outcomes.
This guide describes a way to run your pipeline. Before relying on automatic stage rules or renewal reminders, demonstrate the exact behaviour you need. The examples do not establish which activity caused a sale.
Work through a scenario without calling it revenue
£6,000 of proposed work is not £6,000 collected
Suppose you have two proposals in GBP: £4,000 and £2,000. For planning only, you assign probabilities of 50% and 25%. The combined face value is £6,000, while the weighted scenario is £2,500.
£4,000 × 0.50 + £2,000 × 0.25 = £2,500. Face value: £4,000 + £2,000 = £6,000.
The probabilities are stated assumptions, not Gbeya conversion data. With a small number of bespoke opportunities, a delivery-capacity range may be more useful than a weighted total.
Show face value, assumed weighted value and confirmed payments as separate measures. Never add different currencies without a documented conversion method.
Assumptions worth checking
A larger pipeline means the business is healthier.
It may contain more opportunities, more stale work or simply more low-information records. Review what is active and what evidence supports the next decision.
An experienced consultant can assign an accurate probability by feel.
Judgement can inform a scenario, but it is not calibrated evidence. Label the assumption and compare it with sufficiently similar closed outcomes before relying on it.
Won means paid, and a happy client means renewed.
A sales status, a payment and a new engagement are separate events. Each needs its own evidence.
Your next 30 days
Days 1–7
Write the stage rules
Define what enters the pipeline and the evidence for each stage. Use three existing conversations to expose ambiguity.
Ready for the next step: Two people would place the same opportunity in the same stage for the same reason.
Days 8–14
Give active work a next step
Review each active opportunity, assign an owner and record the decision or event being awaited. Pause stale work explicitly.
Ready for the next step: Every active item has a meaningful next action or a documented pause.
Days 15–21
Separate value and delivery commitments
Review proposal amounts by currency, payment evidence and likely delivery demands. Treat probabilities as assumptions unless calibrated.
Ready for the next step: Pipeline totals cannot be mistaken for collected revenue or available capacity.
Days 22–30
Run a short evidence review
Review changes, overdue decisions and closed outcomes. Adjust definitions that create confusion; preserve previous evidence when a scope changes.
Ready for the next step: The review produces deliberate actions, not just a refreshed board.
Questions before you proceed
How many stages should a consulting pipeline have?
Use the fewest stages that distinguish decisions in your actual process. Start with clear definitions, then remove a stage if it does not change what you do next.
Should every enquiry become an opportunity?
No. Create an opportunity when there is specific work and a commercial next decision to evaluate. Keep broader interest in the contact relationship until that boundary is met.
Can an opportunity move backwards?
Yes, when the evidence changes. A revised scope may need renewed qualification. Keep the reason visible rather than protecting an optimistic label.
Are stage probabilities a forecast?
They are inputs to a model. Default percentages are not measured likelihoods for your practice. State the assumptions and review comparable outcomes before relying on them.
Does Won prove that the client paid?
No. Confirm the relevant payment separately. An agreement, a manually selected stage and a paid order do not mean the same thing.
Can renewals be automated?
A reminder or transition can be automated only after its rules, timing and stop conditions are implemented and tested. A completed engagement does not itself prove permission, intent or payment for another one.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026.