Most signal infrastructure is built for enterprise SaaS. In EdTech, the signals that actually predict revenue outcomes are structural and external - budget cycles, procurement timelines, champion turnover in district roles, and policy changes that reshape demand. If your signal model does not account for how districts make decisions, you are detecting risk after the decision has already been made.
The six thematic categories below sit on top of PILLAR's underlying signal taxonomy - 30+ discrete signal types across 8 families (renewal, expansion, pipeline, account, coverage, workflow, external intelligence, economics).
Generic B2B signal models track internal activity: product usage, NPS, support tickets, CRM engagement. Those signals matter. But in EdTech, the signals that determine whether an account renews, expands, or churns are primarily external. They live outside your CRM, outside your CS platform, and outside the tools your team checks every day.
A usage decline at an account where the budget is already approved and the champion is stable is a product problem. A usage decline at an account where the budget window is closing and the champion just changed roles is a churn event. Same internal signal. Completely different meaning. The external context is what makes the signal actionable.
A district's fiscal year starts July 1 in most states. Budget decisions are finalized between March and May. If your renewal is in September, the decision about whether to renew was made four months earlier during budget planning.
The district budget calendar:
If your renewal process starts at contract expiration, you are starting after the budget is locked. The signal window is March through May, not 90 days before the contract date.
In enterprise SaaS, champion turnover means your main contact changed jobs. In EdTech, it means the curriculum director who championed your adoption got promoted to assistant superintendent, or the superintendent who signed the contract lost a school board election, or the tech director retired and the replacement has a different vendor relationship.
District leadership turnover follows predictable patterns:
If your system is not tracking role changes against these patterns, you are reacting to stakeholder turnover instead of anticipating it.
Usage drops every summer. That is expected. The signal is not "usage declined in June." The signal is "usage declined 35% more than the seasonal baseline, and the decline started in April, two months before summer break."
Seasonal patterns your signal model needs to know:
Back-to-school adoption surge (Aug-Sep). Testing season spike (Feb-Apr). Curriculum adoption windows (fall). Professional development weeks (varies by district). Winter break dip (expected). Summer break dip (expected). Your signal infrastructure needs seasonal baselines, not absolute thresholds, or every summer looks like a churn event.
Districts do not buy software the way enterprises do. Procurement signals include:
These signals are all public data. Most revenue teams are not systematically monitoring them.
Federal funding changes reshape the entire market. State mandates create sudden demand. Legislative sessions produce bills that change procurement rules. These signals do not live in your CRM.
The teams that systematically track external signals have a 6-to-12-month lead time on the teams that do not.
What districts say in meetings, calls, and emails contains signal that no dashboard captures. Conversational intelligence surfaces patterns that predict outcomes months before they show up in usage data or CRM fields.
District-specific language signals: budget language ("we need to justify the spend"), evaluation language ("the board wants to see options"), timing language ("we will revisit this after the fiscal year"), and champion language ("the new director wants to do a review"). These linguistic patterns are early warning signals that precede CRM stage changes by weeks or months.
The gap most EdTech revenue teams have: Internal signals (CRM activity, support tickets, usage data) are tracked reasonably well. External signals (budget cycles, procurement activity, stakeholder turnover, policy changes, conversational intelligence) are almost never tracked systematically. The external signals are the ones that determine whether the internal signals matter.
Twelve questions to pressure-test your EdTech signal coverage.
Count the no's by signal category. The category with the most no's is where your team is most exposed to the signals competitors are already acting on.
Want to know which signals your organization is missing and what it is costing you?
Take the Free Blueprint Assessment
The benchmark figures here are PILLAR operator estimates. They come from our own work with EdTech and public sector revenue teams, not from a published study and not from a survey. They are a practitioner's calibration, offered so the argument has something concrete to push against, and they should be read that way rather than cited as measurements.
Where a figure on this site does come from a public record, it is sourced at the point it appears. Anything drawn from a state disclosure file, a federal dataset or an independent outcome measure carries its source, its vintage and a way to re-derive it.
Every figure PILLAR publishes, on this page and everywhere else, is covered by our standing correction offer. If one of these estimates does not match what you see in your own book, we want to hear it.