A middle school principal takes a demo call in October. A district curriculum director takes another call in January. Neither one mentions the other, and neither has to, because your CRM already treats them as two unrelated contacts. Nothing in the system knows they work for the same buyer.
I call this the Account Rollup Gap, and it’s the quiet reason a lot of K-12 account-based selling stalls before it ever really starts. Everything in the Next 50 model depends on seeing an account, not a contact. A working list is only as useful as the system’s ability to show a rep that the principal, the curriculum director, and the business office contact are three people building one relationship, not three separate leads that happen to share a zip code.
Scott Noon, founder of the K-12 go-to-market advisory firm Midday Advisors, has watched more account-based strategies quietly fail here than anywhere else, not because the strategy was wrong, but because the system underneath it couldn’t represent the thing the strategy was asking it to track.
What is the Account Rollup Gap?
The Account Rollup Gap is the mismatch between how most CRMs model accounts and how K-12 buying actually works. A CRM built for generic B2B assumes an account is one clean entity, a company, with contacts underneath it. In K-12, the real account is a district, and the people you actually talk to are spread across individual schools, the district office, and sometimes shared regional services, none of which a standard CRM connects to the district automatically. Engagement at the school level and engagement at the district level end up looking like two unrelated relationships instead of one account building momentum.
Why doesn’t a normal CRM handle this out of the box?
Because the underlying data problem is genuinely messy, not because CRM vendors overlooked something simple. There are roughly 13,300 regular public school districts in the United States and around 91,000 traditional public schools, an average of about seven schools per district, but that average hides enormous variation. Some districts have exactly one school. New York City Public Schools has well over a thousand. Charter schools sometimes function as their own single-school district for purchasing purposes. Some services are delivered through regional co-ops that span multiple districts at once. There’s no clean, uniform rule a CRM could apply automatically, because the real structure isn’t uniform.
Public data sources exist that map this relationship, most notably the National Center for Education Statistics’ Common Core of Data, but that data isn’t perfectly current, isn’t formatted for a plug-and-play CRM import, and doesn’t include the private and parochial schools that show up in some sales motions. Building a complete, always-current national hierarchy from public sources alone is a real data engineering project. It is not a checkbox in a CRM settings menu, and any framing that treats it as one is setting a small team up to be frustrated by a problem that was never actually simple.
Some CRMs try to shortcut the problem by grouping contacts into accounts based on email domain, assuming everyone at the same domain belongs to the same organization. That works reasonably well in generic B2B, where a company usually has one domain. It breaks in K-12 more often than teams expect, because plenty of individual schools run their own vanity email domain separate from the district’s. A principal at a school with its own domain gets auto-grouped into an account that has nothing to do with the district record the rest of the relationship lives in, and the rollup silently fails exactly where it matters most. Domain matching isn’t a reliable spine for this problem. It’s a heuristic that happens to work until it doesn’t, and K-12 is one of the places it doesn’t.
This is worth saying plainly because it’s the part most ABM advice skips. A two- or three-person team cannot build and maintain a perfect national school-to-district hierarchy, and trying to is a good way to spend a quarter on infrastructure instead of pipeline. The honest starting point is smaller than that, and it’s still enough to make account-based selling actually work.
Where does the actual buying authority sit?
The rollup problem gets more complicated in districts that use school-based budgeting, where individual schools, not the district office, control a real share of the budget, including staffing dollars. New York City is the clearest current example. Its Fair Student Funding formula is flexible funding spent at the principal’s discretion, and it made up 57 percent of a school’s total budget on average in the 2023–24 school year, used mostly for hiring but also for materials and other resources. Chicago ran a similar Student-Based Budgeting model for over a decade, though it’s worth noting CPS began moving away from full SBB in 2024 toward a different formula-based staffing approach, so it’s a well-known historical example more than a current one.
In a district like this, the economic buyer for some purchases genuinely is the principal, not the curriculum director or the business office at the district level. A CRM model that automatically treats the district office as the account’s decision-maker will misroute exactly the deals most likely to close in these districts. This doesn’t undercut the case for building the account rollup. It’s the reason the rollup has to be built carefully rather than assumed: the goal isn’t just connecting a school to its district for context, it’s correctly identifying which node in that hierarchy actually controls the money for a given purchase, and that answer changes district to district.
What to do instead
Map budget authority per account instead of assuming it. For each account on the working list, note whether the district or the individual school controls spend for what you sell, and flag school-based budgeting districts explicitly rather than defaulting every account to a district-office buyer.
Build the hierarchy for the working list, not the whole market. This is where the Next 50 model earns its keep beyond just focus. Fifty accounts is a hierarchy a lean team can build by hand in a reasonable amount of time, verifying the specifics account by account. Two thousand accounts is not.
Use NCES data as the spine, not domain matching. The safest, most common way to get school-to-district rollups right is to build the hierarchy from NCES’s Common Core of Data and confirm it against state department of education directories, then hard-code that mapping into the CRM rather than relying on the system to infer it from email domains. It’s more manual up front, but it doesn’t quietly fail the moment a school’s own vanity domain doesn’t match its district’s.
Give the CRM a real parent-account structure, even if it takes some manual setup. Most CRMs support some version of a parent-child account relationship or a custom rollup field, even if it isn’t configured that way by default. Every school-level contact on the working list should point up to its district as the actual account, so a rep opening the district record sees every relationship underneath it in one place.
Treat the hierarchy as a living dataset, not a one-time import. Schools close, merge, and get reassigned. New charter schools open. A hierarchy built once during onboarding and never revisited will be wrong within a year. Since the working list is only fifty accounts, keeping it current is a maintenance task, not a project.
Don’t wait for the data to be perfect before using it. A hierarchy that’s ninety percent right for fifty accounts is far more useful than a perfect hierarchy that never gets built because the goal was set at national scale. Start with what’s confirmed, flag what isn’t, and correct it as reps encounter the real structure in the field.
The gap doesn’t close nationally. It closes fifty accounts at a time.
No small team is going to solve this problem for the entire K-12 market, and trying to is the wrong ambition in the first place. The realistic version is smaller and still valuable: a working list where every contact rolls up to the right account, built by hand, maintained on purpose, and good enough to make the strategy underneath it actually work.
If your organization is dealing with a version of this, let’s talk.
This post is part of the guide Account-Based Sales and Marketing for K-12 Education Providers. Related reading: The Address Book Problem and The Shared Clock.
Scott Noon is the founder of Midday Advisors, a K-12 go-to-market advisory firm.
Frequently Asked Questions
The Account Rollup Gap is the mismatch between how most CRMs model accounts, as one clean entity with contacts underneath it, and how K-12 buying actually works, where real relationships are spread across individual schools, a district office, and sometimes regional service co-ops that a standard CRM doesn’t connect automatically.
Because the underlying structure isn’t uniform enough to automate. District size varies from one school to well over a thousand, some schools function as their own purchasing entity, and services are sometimes delivered through multi-district co-ops. No standard rule captures all of that, which is why it takes deliberate, partly manual data work rather than a settings change.
No, and trying to is usually a mistake for a small team. Build the hierarchy only for your working account list, fifty accounts is realistic to map and maintain by hand using public data sources as a starting point, where a national hierarchy across thousands of accounts is not.
The National Center for Education Statistics’ Common Core of Data, confirmed against individual state department of education directories, is the safest, most common spine to build the hierarchy from. Neither source is perfectly current or formatted for direct CRM import, so treat them as the foundation to verify and correct per account, not a finished dataset.
Because plenty of individual schools run their own vanity email domain separate from their district’s. A CRM that auto-groups contacts by domain will miss the connection entirely in those cases, silently placing a school-level contact in the wrong account or no account at all. Building the hierarchy from NCES data instead of inferring it from email domains avoids this failure.
No. In districts that use school-based budgeting, most notably New York City, individual schools control a real share of the budget, including staffing dollars, and the principal is the one with discretion over how it’s spent. Assuming the district office is always the buyer will misroute deals in these districts. Budget authority should be mapped per account rather than assumed.
Regularly. Schools close, merge, and get reassigned, and new charter schools open every year. Because the working list is only around fifty accounts, this is a manageable ongoing maintenance task rather than a large project, but it does need to be revisited each fiscal cycle.
