The Signals That Actually Matter in EdTech

Last week I introduced the four layers of a revenue operating system. Layer I is signal infrastructure — the detection layer that identifies events worth paying attention to before they become crises.

Most signal models are built for enterprise SaaS. Usage trends. NPS scores. Support ticket volume. Those signals matter. But if you are selling into school districts or government agencies, the signals that actually predict revenue outcomes are structural and external. And most teams are not tracking them.

Here is what I mean.

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. If your signal model only tracks contract expiration date, you are detecting risk after the decision has already been made.

The signal that matters is not "renewal is in 90 days." The signal that matters is "budget finalization window opens in 30 days and we have not confirmed line-item inclusion."

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: board elections in odd years, superintendent contracts on 3-year cycles, and a wave of retirements every June. 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." That distinguishes a normal seasonal pattern from an adoption problem that will become a renewal problem.

Back-to-school in August, testing season in March, and curriculum adoption windows in the fall all create usage patterns that generic SaaS signal models interpret as anomalies. In EdTech, they are the baseline. Your signal infrastructure needs to know the difference.

Districts do not buy software the way enterprises do. Procurement signals include: RFP issuance on public procurement portals, cooperative purchasing activity (TIPS, PEPPM, E-Rate), board agenda items mentioning technology evaluation, and sole-source threshold changes at the state level.

If a district that has been buying your product through a cooperative purchasing contract is suddenly listed on a public RFP portal evaluating your category, that is not a pipeline signal. That is a churn signal. Your competitor is already in the building.

Federal funding changes reshape the entire market. The ESSER cliff eliminated billions in EdTech spending. State mandates create sudden demand in specific categories. Legislative sessions in January produce bills that change procurement rules by July.

These signals do not live in your CRM. They do not live in your CS platform. They live in public data sources that most revenue teams are not systematically monitoring. The teams that track them have a 6-to-12-month lead time on the teams that do not.

Most EdTech revenue teams track internal signals reasonably well — CRM activity, support tickets, usage data. Almost none systematically track the external signals — budget cycles, procurement activity, stakeholder turnover patterns, and policy changes — that actually determine whether the internal signals matter.

I wrote the full framework with the complete signal taxonomy for EdTech revenue teams — budget cycles, champion turnover, procurement intelligence, and external market signals. Each one with detection patterns, lead times, and the data sources you need to track.

Next week: why territory design breaks at $15M, and what to do about it.