K-12 sales pipeline stages usually come straight out of the box: Prospecting, Qualification, Proposal, Negotiation, whatever Salesforce or HubSpot shipped with, accepted once during setup and never revisited. That’s a problem, because a K-12 deal never moves through any of that.
A district deal moves when a budget line gets identified, when a real champion is willing to spend political capital defending the purchase, when the procurement path becomes visible, and when a board actually signs off. None of that maps onto a generic SaaS pipeline, so reps do what people always do with a form that doesn’t fit: they guess. A deal stuck waiting on a board vote gets logged as “Negotiation” because that’s the closest box. A deal with no funding identified sits in “Proposal” because a deck was shared in a meeting.
This piece breaks down what K-12 sales pipeline stages actually look like when they’re built as a stage-gate model, borrowed from product development, where nothing advances until it clears a specific, checkable test.
Where Generic CRM Stages Break Down in K-12
The break often starts with a small, easy-to-miss conflation: treating a proposal as the deck a rep shows in a discovery meeting.
That deck, the case study walkthrough, the problem-solution conversation, happens while a deal is still being qualified. It’s how a rep earns the right to a real proposal, not the proposal itself. The actual proposal in K-12 is a narrative document, typically three to five pages, written as a specific response to the problem a district has already named. For RFP-driven deals, that same stage produces a formal response instead, built from research done earlier into whether the RFP language is already wired toward a competitor.
Collapse those two things into one CRM stage, and the pipeline stops telling you anything true. A rep who showed a great deck looks like they’re deep in a deal that hasn’t actually started. A rep sitting on a real proposal that’s already been reviewed and endorsed by a champion looks identical to one who sent a cold PDF nobody read.
The same blur shows up at the other end of the pipeline. Most CRMs default to a binary close: Won or Lost. K-12 doesn’t work that way. In my years running K-12 pipelines, the largest of the three eventual outcomes was never Closed-Lost, a district that evaluated us and picked someone else. It was Closed-Stalled: a district that simply never followed through, no vendor selected, no decision made, the opportunity just going quiet. Folding that into “Lost” erases the single most common way a K-12 deal actually ends, and a sales leader forecasting off that number is working from a pipeline that’s lying to them by omission.
None of this is a rep problem. It’s a template problem. The stage names in most CRMs describe a company that doesn’t sell into K-12, and every rep who has ever guessed at which box to check has just been doing the best they can with a form that was never built for the deals they’re actually running.
Why Does a K-12 Deal Need Its Own Pipeline?
A K-12 deal needs its own pipeline because the events that actually move it forward, budget identification, champion commitment, a known procurement path, board approval, don’t correspond to any stage in a generic B2B template. A pipeline built around demo-to-close motion measures actions a district buyer doesn’t take, on a calendar the district doesn’t follow.
K-12 purchasing runs through a fiscal-year budget cycle that most districts finalize months before a contract gets signed, often in spring for a purchase that won’t close until the following school year. It also runs through a buying committee where no single person has full authority, and a board approval step that has little to do with how convinced any individual buyer already is. A generic pipeline assumes one decision-maker moving through a linear, sales-team-driven sequence. K-12 has a coalition working through its own process, on its own clock, largely out of a vendor’s view. You can read more about how that buying process actually unfolds in How K-12 Districts Actually Buy.
That’s the structural reason the guessing happens. A rep working a real K-12 deal is watching for signals inside a process they don’t control and don’t fully see, and a pipeline stage is supposed to represent the best read of where that process actually stands. When the available stages don’t match any real checkpoint in that process, the rep isn’t failing. The form is.
What Do K-12 Sales Pipeline Stages Actually Look Like?
A K-12 pipeline works best as eight stages, from Targeting through Closed, each with a specific gate that has to clear before a deal can move forward, plus a percentage weight for forecasting. This is the K-12 Stage-Gate Pipeline that Scott Noon developed at Midday Advisors, refined across years of running these exact deals, and the weights aren’t evenly spaced. They cluster hardest right before a signature, matching how uncertain a K-12 deal actually stays until very late.
Here’s the full model.
Targeting (0%)
Research confirms the account is a real ICP fit, and three to five possible buying-committee names are identified and logged. Nothing has happened with the district yet. Gate: ICP fit confirmed, names in the CRM.
Prospecting (10%)
A rep has had a substantive conversation with someone who actually has stake in the decision, not an email reply. Gate: real contact confirmed.
Qualifying (20%)
The rep confirms the real problem, maps the buying committee, and gets a first read on whether funding is plausible. This is also where the deck and case study walkthrough happen, and where RFP-track deals get researched for competitive wiring and split into writing assignments. Gate: a champion is identified, the problem is confirmed in the district’s own words, and a funding path looks credible.
Proposing (30%)
The narrative proposal goes out, or, for RFP deals, the response gets drafted using the work done in Qualifying. Gate: the champion has reviewed or endorsed it, and three or more district people are engaged and warm.
Considering (50%)
The district’s internal evaluation window, where a proposal or an RFP response is formally submitted. The rep stays visible while the district works a process it often can’t fully explain from the outside. Gate: the procurement path is known and funding is identified, meaning you can name which board or committee process the deal is routed through, and roughly when it resolves.
In Purchasing (70%)
The decision is effectively made and internal evaluation is positive. Funding is locked, and questions about whose contract paper gets used are worked out. Gate: contract is submitted.
Contract Pending (95%)
Legal has reviewed, the board has signed off, and signatures are being solicited. Gate: executed contract in hand.
Closed
A three-way split, not a binary. Closed-Won. Closed-Lost, when the district picked a different vendor. Closed-Stalled, when the district never followed through at all, no decision was made either way. Keeping Stalled separate from Lost is what keeps the forecast honest, since it’s typically the largest of the three.
If your team is still tracking wins and losses without separating out the stalled deals, it’s worth reading how that same blind spot shows up in Why K-12 Sales Pipeline Reviews Produce False Confidence, and What to Track Instead. And since so much of this model runs on a real champion, not just an enthusiastic contact, The Five Stakeholders Every K-12 Deal Has to Win Over is the companion piece on who else has to say yes.
The Close
None of this requires new software. It requires deciding, once, what has to be true before a deal is allowed to move, and holding every rep to the same test. A pipeline that measures real gates instead of a rep’s optimism will look less full for a while. It will also, for the first time, tell leadership something true.
A pipeline is not supposed to describe hope. It’s supposed to describe evidence.
If your organization is dealing with a version of this, let’s talk.
Scott Noon is the founder of Midday Advisors, a K-12 go-to-market advisory firm.
Frequently Asked Questions
Eight works well for most K-12-focused teams: Targeting, Prospecting, Qualifying, Proposing, Considering, In Purchasing, Contract Pending, and Closed. The number matters less than each stage having a specific, checkable gate rather than a rep’s best guess.
A sales deck or case-study walkthrough happens during Qualifying, while a rep is still earning the right to propose. The actual proposal is a narrative document, typically three to five pages, written as a specific response to a district’s stated problem, and it belongs to its own later stage.
Three, not two. Closed-Won means the district signed with you. Closed-Lost means the district evaluated vendors and chose someone else. Closed-Stalled means the district never made a decision at all, no vendor selected, the opportunity just went quiet. In most K-12 pipelines, Stalled is the largest of the three, and folding it into Lost hides the real reason forecasts miss.
RFP research and a competitive read happen during Qualifying, the response gets drafted during Proposing, and the formal submission happens at the start of Considering. Treating RFP submission as a separate, weighted event, distinct from a standard proposal, keeps forecasting accurate.
Because they were built around a single buyer moving through a short, linear, sales-team-driven sequence. K-12 purchases move through a buying committee, a fiscal-year budget cycle, and a board approval step that a generic template has no stage for, so reps end up guessing which default box fits.
