From market signal to pursuit: an operating model

Every professional services firm runs some version of the same pipeline, whether or not it is written down: notice something, decide whether to care, work out the way in, decide whether to bid, resource the bid, and learn from the result. Written as an explicit operating model, it has ten steps.

The ten steps

• 1. A relevant signal appears, a tender, a planning approval, a framework notice, a hire, a rumour with substance.
• 2. The signal is attributed to the organisation behind it, joining whatever the firm already knows.
• 3. The decision-makers are identified, with influence marked honestly.
• 4. The firm's routes in are mapped, who knows whom, at what strength, last active when.
• 5. The opportunity is created with an estimated value and a stage, visible to everyone who needs it.
• 6. It is qualified: strategic fit, capability evidence, relationship strength, probability, and a bid/no-bid decision recorded with reasons.
• 7. An owner and a pursuit team are named. Ownership is singular; help is plural.
• 8. Next actions are agreed with dates. A pursuit without a next action is treated as stalled, whatever the stage says.
• 9. Leadership sees it in the weighted pipeline, with risk flagged and explained.
• 10. The outcome and its lessons are recorded, so win/loss analysis reads back against what was argued at the time.

Where it usually breaks

Almost never at step 1, firms see plenty. The common fractures are steps 2 and 4 (the signal never meets the firm's own knowledge of the organisation and its relationships), step 6 (bid decisions are made in a corridor and remembered differently later), and step 8 (opportunities drift for weeks with no named next move). Each fracture has the same root cause: the information needed lives in different places owned by different people.

Making it real without making it bureaucratic

The model fails if it becomes an admin tax on fee earners. The workable version asks partners only for what they uniquely know, the relationship, the meeting, the judgement, and derives the rest: signals arrive from public feeds already scored, organisations enrich themselves from public registers, weighted values compute from stage, and the priority list assembles itself from whatever is missing an owner or an action. The discipline lives in the system so it does not have to live in anyone's calendar.

A pipeline review should be an argument about judgement, not an audit of whose spreadsheet is current.