K-12 AI spending is moving from classroom apps to vetting, policy, and proof

School districts are buying AI. They’re also buying time, because the hardest part of AI in K-12 is now the work around the tool: vetting, policy, training, and measurement.

Education Week, citing Grand View Research, pegged the broader U.S. education technology market at almost $48 billion in 2024 revenue, projected to top $90 billion by 2030. In the same Grand View outlook, U.S. AI-in-education revenue was about $2.5 billion last year and is projected to exceed $15 billion by 2033. Those aren’t abstract figures for district CIOs and procurement directors. They translate into a crowded vendor field, fast product cycles, and a growing expectation that districts can explain why a specific AI line item exists.

At the same moment, teen use is already mainstream. A Common Sense Media survey of 1,017 teens ages 13 to 17, conducted in April and May and reported by The 74, found 70% use AI for schoolwork. The same reporting said fewer than one in three teens said a teacher had ever discussed safe AI use, and only one in four had discussed how to evaluate whether AI-generated information is accurate. For operators, that gap is a purchasing requirement: any AI rollout that lacks training, guardrails, and monitoring will create shadow use whether or not an official tool is deployed.

The new K-12 AI “product” is governance, not a chatbot

For years, districts could treat most edtech decisions as an IT deployment problem plus a curriculum alignment problem. Generative AI changes that, because usage bleeds across subjects and devices and because the same tool can be used for drafting, tutoring, and answer generation depending on the prompt.

The Common Sense Media survey data reported by The 74 makes that dual-use reality explicit. Among teens who use AI, 77% said they use it for support functions like brainstorming, checking work, or getting writing feedback. But 63% also said they go straight to a chatbot to get an answer rather than working through it. Those behaviors can be true at the same time, which means policy can’t be written as if there are clean categories of “allowed” and “banned” tools. It has to be written around tasks, contexts, and evidence of learning.

That’s already showing up in how districts talk about buying. Education Week reported that leaders feel overwhelmed by the number of AI learning tools and are still carrying much of the burden of figuring out what is safe and worth buying, even as some states and districts begin to publish vetting guidance. The operational implication is clear: procurement teams will be asked to do more pre-award diligence than they have historically done for instructional software, and to revisit what “pilot” means when a pilot can alter student work patterns immediately.

Policy activity is racing ahead of local definitions of “success”

Districts aren’t writing AI rules in a vacuum. eSchool News reported that 34 states and Puerto Rico have issued some form of AI guidance for schools. It also reported that more than 70 bills related to AI in the classroom were introduced across 27 states in 2026, spanning issues like restrictions, privacy, graduation requirements, and teacher training.

That volume of policy motion matters operationally even when guidance isn’t binding. It changes what boards, parents, and auditors expect: that a district can point to an acceptable-use stance, a process for handling new tools, and a way to show staff have been trained. eSchool News framed the risk as writing rules before defining preparedness and career readiness goals. For operations leaders, that reads as a sequencing problem. Without a district-level definition of what learning outcomes AI should improve, policies tend to default to the most enforceable thing, restrictions, which can still leave the district exposed to unmanaged, off-platform usage.

Procurement is moving toward proof, not promises

One reason the market feels noisy is that it’s growing fast enough to attract new entrants and constant rebranding. Education Week’s Grand View Research figures, almost $48 billion in U.S. edtech revenue in 2024 and a projected $90 billion-plus by 2030, explain why districts see a flood of vendors positioning “AI” as a feature rather than a measurable intervention.

Education Week described one district leader’s approach as starting from a specific performance problem and then testing whether AI can change instruction. The outlet reported that Scott Langford, superintendent of Sumner County Schools in Tennessee, said the district explored AI because middle school reading scores had plateaued and the team wanted real-time visibility into student struggles and faster feedback loops. The procurement lesson is transferable: AI buying works best when it is attached to one instructional bottleneck and one measurement plan, not when it is justified as generalized innovation.

The teen survey data adds a second layer to “proof.” If a tool increases completion speed but shifts cognition away from ideation and practice, districts will face internal pushback from teachers and external scrutiny from families. The 74’s reporting on Common Sense Media found 38% of teen AI users said AI availability leads them to develop fewer original ideas, and 39% said using AI to complete assignments makes them feel they are missing out on learning. Procurement teams are likely to be asked to evaluate not only accuracy and privacy, but also whether a product’s workflows push students toward shortcuts.

What district IT and procurement teams should put in the next RFP

• Define the job before the tool: require bidders to map their AI feature to one measurable instructional objective (for example, reading growth signals, writing revision quality, or time-to-intervention), mirroring the problem-first framing reported by Education Week.
• Treat safe-use training as a deliverable: ask vendors for a district-ready teacher training package and student guidance materials, because Common Sense Media survey findings reported by The 74 show most teens say teachers haven’t discussed safe use.
• Ask for task-level controls and auditability: require role-based access, logging, and the ability to restrict high-risk uses (answer generation for certain assessments) while enabling low-risk uses (brainstorming), reflecting the mixed-use behavior in the Common Sense Media data reported by The 74.
• Align contracts to shifting state guidance: include change-control language that lets districts update acceptable-use requirements as state guidance evolves, given eSchool News reporting that 34 states plus Puerto Rico have issued guidance and legislative activity is heavy in 2026.