How IT Companies Should Structure Their Sales Pipeline Stages

Open any CRM and you will find the same default pipeline: Prospecting, Qualification, Proposal, Negotiation, Closed Won or Lost. Five stages. Clean, simple, and built for a sales process that IT companies almost never run.

The generic pipeline model assumes a relatively linear buyer journey with a single decision-maker, a clear evaluation window, and a defined close event. IT sales — whether you are selling managed services, software licences, implementation projects, or a combination of all three — rarely works that way.

The consequence is a pipeline where deals appear to be in "Proposal" for eleven weeks, where three different deals are simultaneously in "Negotiation" with radically different close probabilities, and where nobody can look at the pipeline and say with any confidence what is actually closing this quarter.

Here is how to build a pipeline stage structure that reflects the reality of how IT companies actually sell.

Why the Generic Model Fails IT Sales

IT buying decisions typically involve multiple stakeholders: a technical evaluator, a budget holder, a procurement team, and often a management board for larger contracts. The decision moves through these stakeholders in sequence — and stalls at a different point for a different reason with each one.

A standard 5-stage pipeline treats all of this as a single "Negotiation" stage. The deal sits there for weeks while procurement reviews the contract, the board schedules a sign-off meeting, and the technical team completes their security assessment. None of that is visible in the pipeline. The forecast assumes the deal is close to closing because it is in the "Negotiation" stage. It may be nowhere near closing.

Multi-stakeholder complexity requires more stages — not to add bureaucracy, but to give each major decision gate its own visible milestone. That way a deal in stage 6 and a deal in stage 3 are not both called "Proposal" and weighted at the same probability.

A Pipeline Stage Structure Built for IT Companies

Stage 1: Identified

A potential opportunity has been identified — an inbound lead, an outbound prospect, or a referral. No qualification has happened yet. This stage is a holding area, not a forecast stage. Nothing in Stage 1 belongs in the forecast.

Close probability: 0%

Stage 2: Qualified

The opportunity has been qualified against defined criteria: budget authority is confirmed or has a clear path to confirmation, the problem is real and urgent enough to act on, a technical decision-maker is engaged, and a timeline exists. No deal without all four of these belongs in Stage 2.

Close probability: 10 to 15%

Stage 3: Technical Fit Confirmed

A discovery process or technical assessment has been completed. Your solution has been validated as technically capable of solving the identified problem. This stage is particularly important for IT services and MSPs — it gates the pipeline on actual technical suitability, not just commercial interest.

Close probability: 25%

Stage 4: Proposal Submitted

A formal proposal or Statement of Work has been submitted to the client. The deal is now in the buyer’s hands. Stage 4 is not a passive waiting stage — it should have a defined follow-up cadence and a maximum time limit before the deal is moved back to Stage 3 or disqualified.

Close probability: 40%

Stage 5: Commercial Stakeholder Engaged

The budget holder or economic decision-maker has reviewed the proposal and is actively engaged in the process. In IT sales this is often a distinct step from the technical evaluation — the person who can sign the contract may not have been involved in stages 2 through 4. Confirming their engagement is a meaningful milestone that warrants its own stage.

Close probability: 60%

Stage 6: Contract or Procurement Stage

The deal has entered a formal procurement or legal review process. A verbal agreement may exist. The remaining steps are administrative rather than evaluative. This stage should have a defined maximum duration — deals that sit in procurement for more than 30 days need active intervention, not passive waiting.

Close probability: 80%

Stage 7: Closed Won / Closed Lost

The deal is signed or formally lost. Every Closed Lost deal should have a reason code attached — this data becomes the single most valuable input for improving forecast accuracy in future quarters.

Close probability: 100% / 0%

Setting the Right Close Probabilities

The probabilities above are starting points — not fixed rules. Your actual probabilities should be derived from your own historical data: of every deal that reached Stage 4 in the last four quarters, what percentage closed? That number is your Stage 4 probability, not the CRM default. Tracking this by stage for 2 to 3 quarters produces a probability model that reflects your actual sales motion — and makes your revenue forecast significantly more reliable than one built on industry averages.

How MSPs Should Adapt This Structure

For Managed Service Providers and IT service businesses, Stage 3 (Technical Fit) may split into two sub-stages: one for the technical assessment and one for the scope-of-work definition. Scope definition in MSP sales is not a minor administrative step — it determines the implementation cost, the ongoing service load, and the margin on the contract. Treating it as part of the proposal stage underweights its importance in the pipeline. See how MSPs and IT companies use structured pipeline stages in practice →

The Connection to Forecast Accuracy

A pipeline with well-defined stages does two things for forecast accuracy that a generic pipeline cannot.

First, it forces honest classification. A deal cannot be labelled Stage 5 if the commercial stakeholder has not been engaged — because the stage definition requires it. This removes the optimism bias that inflates most pipelines.

Second, it makes stalled deals visible. If a deal has been in Stage 4 for six weeks, something has stopped moving. In a generic pipeline, that deal just sits in "Proposal" indefinitely and keeps contributing its weighted value to the forecast. In a structured pipeline, the time-in-stage triggers a review.

The Bottom Line

A pipeline stage structure built for the way IT companies actually sell gives you a forecast you can trust — because every deal in it has been classified against defined, consistent criteria. Sales Planner is built to support this kind of structured pipeline management, with planning and forecasting tools designed specifically for IT businesses, MSPs, and software companies. Speak with Andreas Dorsch to review your current pipeline structure and identify where the definition gaps are creating forecast inaccuracies.