The Champion You Don't Know You're Losing

Last week closed the first arc of The Architects. Six issues, one architectural model, four layers. Today opens the second arc with a simpler frame. There are six questions about your customer base that your current revenue stack cannot answer. Each issue of this arc is one of them. We start with the most acute.

It happens like this. You are three months from a flagship $200K district renewal. The CSM is confident. The pipeline review marks the account green. Then the email arrives. It is from the curriculum director who championed your product, ran the implementation, and made the renewal case to her superintendent. “I'll be leaving the district at the end of the school year.”

If you had seen that coming 90 days earlier, you would have run a different play. You would have built a relationship with her replacement. You would have briefed them on the implementation story. You would have protected the renewal narrative. Instead, you are starting from zero in month nine of a twelve-month cycle.

Every EdTech CRO will tell you champion turnover is the leading indicator of churn. Almost none of them can name the twelve districts in their book where it is happening right now.

The signal exists. It is public. It is just not in your CRM.

District board meeting agendas list pending appointments and resignations 60 to 90 days before they take effect. Local press announces departures. LinkedIn shows the new role before the old one ends. State-level superintendent search associations publish formal RFPs. State DOE pages publish CSI, TSI, and ATSI accountability designations (the federal school improvement designations that flag underperforming schools, often a precursor to leadership shakeups). The signal is everywhere except where your team looks.

The reason it is not in your CRM is structural, not configuration. Salesforce and HubSpot are designed to track activity inside an account. Emails, meetings, deals, support tickets. They are not designed to track who the account is. Let alone changes to the human composition of the account in real time. That belongs to a different layer.

Champion turnover is one of six categories of revenue signals specific to EdTech and public sector buyers. The other five are budget cycles (federal allocations, ESSER cliffs, Title I-A, IDEA Part B), adoption telemetry, policy shifts (state DOE designations, assessment proficiency, accountability status), external markets (curriculum adoption windows, procurement RFPs), and conversation signals (call recordings, support tickets, sentiment).

Most revenue teams have native access to two of the six. The two their CRM exposes. The other four are visible only if someone has done the work of canonicalizing them.

A revenue team operating on two of six signal categories will lose accounts they should have saved. The variance gets blamed on execution. It is a data layer problem.

In Issue 006 I argued that an operating cadence is a governance structure with three components. The first is structured inputs. Scored data, not anecdotes. If the renewal triage opens with accounts ranked by risk score, and the risk score does not include champion turnover, the triage is structurally incomplete. The CSM with 53 accounts is not going to manually scan 53 board agendas every week. The signal has to be canonicalized and scored before it is useful at the cadence.

This is the vertical layer. The canonicalization of EdTech-specific signals into structured fields that can be queried, scored, and routed. It is the missing input layer beneath the revenue operating system. It is the answer to all six questions in this arc.

Next week, the funding signal. What happens to your renewal forecast when a Title I-A allocation drops 12 percent for your customer district. And how much of that is sitting in your committed pipeline right now without anyone having computed it.

Eli Jameson

Builds revenue architecture for EdTech and public sector companies. Writes about the structural layer underneath pipeline, renewals, and territory design.