From the K–12 edition of October 19, 2026
Peninsula School District (Wash.) builds its own agentic AI assistant for teachers, claims nearly $300,000 saved versus buying
Peninsula School District, reported by District Administration (DA Changemakers podcast) · K-12 district-built AI agent for teacher administrative work · Washington State, United States
- Publisher
- District Administration
- Original publication
- October 19, 2026 (District Administration)
- Source retrieved
- 2026-10-20
What happened
Peninsula built an in-house agentic AI assistant for educators so it could embed district student and teacher data and its own educational frameworks, and rolled it out this school year. According to Kris Hagel, most teachers use it to offload administrative work (one built a QR-code classroom checkout), and the district saved nearly $300,000 by building rather than buying. He credits years of work on foundational data systems and advises leaders to get their 'data house' in order first.
Why it matters
A rare district build-versus-buy example for agentic AI, with the data-readiness prerequisite stated plainly.
Evidence and measured results
Operator claims relayed by trade press from a podcast; no usage metrics, cost basis for the savings figure, security review or evaluation.
Limitations and uncertainty
Single-source operator claims; savings figure has no stated baseline; details deferred to a January conference talk.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Districts want AI agents tailored to their data and frameworks but must judge whether building beats buying.
- Stakeholders
- Chief technology officer
- Data governance lead
- Chief academic officer
- Finance
- Teachers
- Discovery questions
- How integrated are your student, staff and curriculum data today?
- Do you have in-house engineers to maintain an agent?
- What would a commercial license cost for the same workflows?
- Which administrative tasks take the most teacher time?
- Value hypothesis
- A district with mature data systems might lower costs by building narrow agents; the source's savings are unverified.
- Potential engagement
- A six-week data-readiness and build-versus-buy assessment for one teacher workflow.
- Unsupported claims
- Savings figure lacks a cost basis.
- No measured time savings.
- No security review reported.
Pre-sales engineering
Role takeaway
- Fit
- Fits districts with integrated data systems and in-house development staff.
- Architecture and integration
- Connect an agent to district data through governed APIs with role-based permissions.
- Prerequisites
- Integrated SIS, HR and curriculum data
- Identity and access management
- Engineering capacity
- Constraints
- FERPA and Washington privacy requirements
- Maintenance burden
- Model provider terms
- Security
- Enforce least-privilege access to student records and log every agent action.
- Proof of value
- Pilot workflow with audit logs
- Measured time baseline vs after
- Security review completed
Delivery
Role takeaway
- Work
- Operate a district-built AI agent as a supported product with security and change control.
- Dependencies
- Data integration
- Security review
- Teacher pilot group
- Ownership
- District technology department with the data governance lead.
- Skills and adoption
- Teacher training on safe task delegation; engineer upskilling on agent tooling.
- Governance checkpoints
- Data access review
- Pilot go/no-go
- Annual cost and maintenance review
- Acceptance criteria
- Proposed: one workflow live with logged access
- Proposed: measured time saved vs baseline
- Proposed: documented total cost of ownership
- Risks
- Key-person dependency
- Unreviewed data access
- Hidden maintenance cost
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
District-built agent connected to internal student and teacher data; interpretation: build viability depends on mature data integration and in-house engineering staff.
Governance
Who approves, reviews and stays accountable for outcomes?
Embedding student data in a district-built agent puts security, access control and audit duties on the district rather than a vendor.
Security and privacy
What data, permissions and controls need testing?
Not described. Interpretation: agentic access to student records needs role-based permissions, logging and FERPA review.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Teachers build their own uses, such as a classroom checkout; capacity depends on district engineering staff.
Procurement
What should contracts, pricing and exit terms secure?
Build-versus-buy is a real option for data-mature districts; claimed savings should be verified against total cost of ownership.
Operating model
Which teams own the service once it runs?
District becomes the developer and operator of its own AI agent.
Publication history
- 2026-10-19K–12 · Issue 435 resources
Stable resource ID: peninsula-sd-in-house-agentic-ai-teacher-assistant-20261019