The average school district ran nearly 3,000 distinct edtech tools last year, a 9% jump over the year before, and right now, in the quiet weeks of summer, IT and curriculum leaders are cutting that list down. Denver Public Schools pared its stack from more than 1,000 tools to 346 and saved about $1 million doing it. If you sell into K-12, how to sell to school districts in 2026 is less about winning net-new business and more about not getting quietly dropped in a review you never see.
Summer tool audits decide renewals before fall budgets are even set. A vendor that can’t be re-justified to the person running the cull gets deleted from the approved-app list, and the first sign you’ll get is a login that stops working in August.
Why this costs you more than one lost renewal
When a district drops your product, you lose more than the contract. You lose the usage data, the reference, and the internal champion who now has to explain to the cabinet why they kept paying for something with thin adoption. Districts waste an estimated 43% of their software licenses, so audits hunt for exactly that: seats nobody logs into and subscriptions nobody can defend. “No one flagged it as essential” is the whole reason a tool gets cut. Getting re-justified before the review closes protects revenue you already earned, and it applies to any recurring contract, not just software: assessment platforms, PD subscriptions, data services, and security tools all land on the same spreadsheet.
Find out who actually runs the review
The person deciding your fate usually isn’t the teacher who loves your product. It’s a technology director, a chief academic officer, or a data-privacy lead running every tool against three questions: does it integrate, is it used, and is it safe? Oklahoma City narrowed its inventory to about 250 approved apps, each screened for interoperability, privacy, and instructional alignment. If you don’t know which title owns that process in your accounts, you’re invisible to the decision. Mapping it is the same discipline as understanding the full K-12 buying process from teacher request to board approval: the champion opens the door, but a different desk decides whether you stay.
Make your tool easy to keep, not easy to cut
Three things get a product kept through an audit: proof of use, proof of integration, and proof of impact. Send the review owner a one-page account summary before they ask for it, active users, adoption trend, and one measured result tied to a district goal. Confirm you roster cleanly through Clever or ClassLink and meet the district’s privacy agreement, because a tool that breaks single sign-on is the easiest line to delete. A vendor who hands the auditor the evidence saves them work; a vendor who goes quiet over summer hands them a reason to cut.
Email the review, not the calendar
Most vendors go dark in June and July and reappear in August to a stack that’s already been rebuilt without them. That timing is backwards. The consolidation window is also the buying window, which is a big part of why summer is the best time to close school deals, not fall. Reach the technology and curriculum offices while the audit is open, when a single well-timed email with your impact data can move you from “under review” to “renewed.” To land there, you have to reach the school and district decision-makers directly, not route everything through one teacher who may not survive the reshuffle either.
Get in front of the desk that signs off
Surviving the cull comes down to one thing: reaching the IT director, curriculum leader, or business official running the audit before the approved-app list is final. That means knowing how to sell to school districts at the title level, with verified district decision-maker contact data rather than a generic info@ address that dies in a filter. The vendors who keep their spots through summer aren’t the flashiest. They’re the ones who found the auditor, proved they were used, and made “keep” the easy call, while their quieter competitors got a login-disabled email in August.
