Even in districts like New York City Public Schools and Chicago Public Schools, demand is not the problem, execution is. Vendors including zSpace, Legend Power Systems, and Blue Bird Corp are all seeing the same pattern: deals don’t disappear, they stall. This piece breaks down what’s actually happening between demand and revenue and why most teams are misreading it.
This week’s Deep Dive covers:
Why isn’t “guaranteed demand” turning into revenue?
How much of your pipeline is actually executable and when?
How should you sell into a system that cannot execute on demand timelines?
I. Why isn’t “guaranteed demand” turning into revenue?
In K–12, “demand” refers to policy-driven need (e.g., class size mandates), but revenue only materializes after funding, procurement, and execution align. In New York City, a class-size law implies up to $1.7B annually in operating costs and $18B–$27B in facilities, yet timelines are slipping. The implication: most visible demand is real, but not time-executable, and therefore not revenue.
For most vendors, the signal looked clear. New York City passed a class-size law. The requirement was explicit: reduce classrooms to 20–25 students and scale toward full compliance. The implied demand was massive: more teachers, more classrooms, more infrastructure.
From a market perspective, it looked like a guaranteed expansion cycle. It wasn’t.
Continue reading with a paid subscription to K-12 Executive Intelligence
Get access to this post and other subscriber-only content.
UpgradeA paid subscription gives you access to:
- The full edition of The Curve, our flagship weekly signal briefs - what happened, why it matters, and the commercial implications for vendors.
- Rapid intelligence on policy, funding, accountability, curriculum and assessment shifts, and district demand patterns that affect product strategy, GTM, and pricing.
- Deeper analysis on procurement cycles, budget signals, category adoption curves, AI disruption, and early indicators that shape vendor opportunity.