Cohort purchasing through consolidated edtech procurement produced savings of nearly $200,000 and roughly 50 percent per-license discounts in Denver Public Schools¶
Claim · All claims
Evidence · 1 study · qualitativer2·q2
Currency · newest study 2025 · checked against its sources 2026-10-15 (automated, 1 of 1 entry) · not reviewed by a person · recheck by 2028: local conditions change quickly
Subclaims¶
Reading the evidence codes
q is the design tier, i the impact, n the sample, and the kind with its r
the rigour judged within that kind: what each code means.
This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.
q2 i? By limiting the number of available tools and pre-negotiating district contracts, DPS achieved significant savings per license through cohort purchasing. → Noakes 2025
Evidence¶
Noakes 2025¶
Noakes, S., Shell, A., & Karim, S. (2025). Driving Edtech Coherence and Intentionality: Denver Public Schools' Innovative Procurement Process. https://doi.org/10.51388/20.500.12265/267
q2 · i? · qualitative · r2
A Digital Promise case study of DPS's first-year rollout (interviews and focus groups with 23 district leaders, school leaders, teachers and community members, plus classroom observations in three schools) reports the district's own figures for cohort purchasing savings. The report states "significant savings of nearly $200,000" and that "for most of these agreements, the district is finding a 50 percent user discount"; no effect size is printed.
"Cohort purchasing has already made significant savings of nearly $200,000, and enables teachers to continue using the same tools that already have high user engagement."
Discussion¶
Related Claims¶
- Bulk negotiation with the Kahoot! provider reduced the per-teacher price from $149.99 to $44.60, saving the district over $25,000 on licenses — a narrower finding that bears on this claim
- Students, teachers, and principals are perceived to have limited involvement in ed-tech procurement decisions, and providers are far less satisfied with end-user involvement than district stakeholders — related
- Ed-tech providers are overwhelmingly dissatisfied with procurement: only 4 percent say today's processes meet contemporary needs, and nearly two-thirds report the processes directly influence their product development — related
- Edtech tool access per district grew more than 350% between 2019 and 2025, yet most tools are unused or used at low intensity — related
- Consolidating edtech tools enabled DPS to pursue vendor partnerships that systematically compare app usage with student data to evaluate tool effectiveness — related
- Funding is a top procurement challenge for districts, and many districts treat learning technology as a supplemental purchase rather than part of core curriculum budgets — related
- DPS's evaluation process led schools to use safer edtech products by prioritizing student data privacy and accessibility review — related
- Denver Public Schools' cross-functional AI-edtech review cut its edtech portfolio from over 1,000 tools to fewer than 350 while saving millions of dollars — a broader claim this one bears on
- The OBC model enabled districts to better establish instructional coherence, support increased student engagement, and assess associated outcomes. — a broader claim this one bears on
Page metadata
| Field | Value |
|---|---|
type |
claim |
id |
dps-cohort-purchasing-savings-200000 |
title |
Cohort purchasing through consolidated edtech procurement produced savings of nearly $200,000 and roughly 50 percent per-license discounts in Denver Public Schools |
description |
Cohort purchasing through consolidated edtech procurement produced savings of nearly $200,000 and roughly 50 percent per-license discounts in Denver Public Schools |
status |
review |
evidence_strength |
moderate |
newest_evidence |
2025 |
source_checked |
2026-10-15 |
recheck_by |
2028 |
generated |
by process:wiki-ingest on 2026-10-09 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — noakes-2025 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.