The Architects / Issue 003 Reference
Revenue OS · Layer I · Signals →
The EdTech Signal Map.
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).
Why Generic Signals Fail in EdTech
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.
What most teams track
Contract expiration date. Renewal notice sent 90 days before.
What actually predicts the outcome
Budget finalization window opens in 30 days and line-item inclusion is not confirmed. Board agenda does not list technology renewal on the March docket.
The district budget calendar:
Jan-Feb
Superintendent proposes budget
Mar-May
Board reviews, public hearings, finalization
Jun
Budget locked. Decisions are made.
Jul 1
New fiscal year begins
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.
▲
Champion Turnover Signals
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 - odd years in most states. New board = potential superintendent change within 12 months.
- Superintendent contracts - typically 3-year cycles. Year 3 of a superintendent's contract is a risk signal for leadership change.
- June retirement wave - district administrators retire at end of school year. Your July renewal just lost its champion in June.
- Mid-year departures - curriculum directors and tech directors change roles mid-year more frequently than superintendents. These are your operational champions.
If your system is not tracking role changes against these patterns, you are reacting to stakeholder turnover instead of anticipating it.
▬
Usage Seasonality Signals
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."
Normal seasonal pattern
15-25% usage dip Jun-Aug. Rebounds in September. Teacher engagement drops but admin engagement holds steady.
Anomalous pattern (risk signal)
40%+ usage dip starting in April. Teacher AND admin engagement declining. No back-to-school rebound by October.
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:
- RFP issuance - public procurement portals list active RFPs by category. If your existing customer appears on an RFP for your category, that is a churn signal, not a pipeline signal.
- Cooperative purchasing - TIPS, PEPPM, E-Rate, state cooperative contracts. If a district switches from co-op purchasing to direct RFP, they are evaluating alternatives.
- Board agenda items - public school board meeting agendas are published in advance. "Technology platform evaluation" on a board agenda for an existing customer is an immediate escalation signal.
- Sole-source thresholds - state-level purchasing limits determine whether a district can renew without a competitive process. Threshold changes at the state level can force existing customers into competitive evaluation.
These signals are all public data. Most revenue teams are not systematically monitoring them.
●
External Market Signals
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.
- Federal funding programs. Expiration of major federal programs reshapes billions in EdTech spending. Title I, Title II, IDEA funds each have different eligibility requirements and renewal timelines. A funding cliff is a category-level signal, not an account-level one, and the teams that anticipate it repositioning quarters ahead of time.
- State mandates. When a state mandates a category (college-and-career readiness, SEL assessment, AI literacy, data privacy compliance), it creates a demand spike in specific product categories. Monitor state legislative bills and department-of-education rulemaking activity.
- Legislative sessions - most state legislatures convene in January. Bills introduced in Q1 become law by Q3. Procurement rule changes, funding reallocations, and mandate shifts all originate here.
- Competitive landscape - state adoption lists change annually. A new competitor appearing on a state adoption list for your category changes the competitive dynamics for every district in that state.
The teams that systematically track external signals have a 6-to-12-month lead time on the teams that do not.
✎
Conversational Intelligence Signals
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.
Lagging indicator (CRM field)
Deal stage changed to "At Risk" after CSM manually updated it following a difficult call.
Leading indicator (conversation)
District mentioned "evaluating alternatives" in a QBR three months ago. Call frequency dropped 40%. Competitive vendor name appeared in two separate meetings.
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.
Self-assessment
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.
BUDGETEvery district account carries a fiscal year and a budget-approval window in a structured field.
BUDGETRenewal conversations start against the budget-finalization window, not against contract expiration.
CHAMPIONSuperintendent contract cycles and board election years are tracked against your strategic accounts.
CHAMPIONJune and December retirement-wave windows fire alerts on accounts with champion dependencies.
POLICYState legislative activity relevant to your product category is monitored continuously.
POLICYNew state mandates aligned to your product category fire as acquisition signals against eligible districts.
PROCUREMENTCooperative contract eligibility is validated at opportunity creation, not at close.
PROCUREMENTCompetitor contract expiries at target districts are tracked and surface 90-180 days before the window opens.
FUNDINGFederal funding program changes are tracked for their revenue implications on your installed base.
FUNDINGNew grant announcements aligned to your product catalog fire as expansion signals on eligible accounts.
CONVERSATIONConversational intelligence (call and meeting data) is mined for competitive mentions, timing language, and budget language, not just BDR call volume.
FLYWHEELWon and lost deal outcomes are analyzed for which signal combinations preceded the outcome, and the library gets sharper every quarter.
