{"resourceId":"peninsula-sd-in-house-agentic-ai-teacher-assistant-20261019","versions":[{"version":"external-1c4ce0fd849594df0ab773df6f492538c7ede168e8601c214680ff8144b7f0ed","resource":{"id":"peninsula-sd-in-house-agentic-ai-teacher-assistant-20261019","title":"Peninsula School District (Wash.) builds its own agentic AI assistant for teachers, claims nearly $300,000 saved versus buying","organization":"Peninsula School District, reported by District Administration (DA Changemakers podcast)","sector":"K-12 district-built AI agent for teacher administrative work","geography":"Washington State, United States","publishedAt":"October 19, 2026 (District Administration)","publicationDate":"2026-10-19","eventDate":null,"sourceName":"District Administration","sourceLabel":"Trade press summary of a podcast interview with district leader Kris Hagel","sourceUrl":"https://districtadministration.com/why-this-washington-district-built-its-own-agentic-ai/","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["developers-agents","infrastructure","knowledge-work"],"finding":"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.","sledRelevance":"A rare district build-versus-buy example for agentic AI, with the data-readiness prerequisite stated plainly.","evidence":"Operator claims relayed by trade press from a podcast; no usage metrics, cost basis for the savings figure, security review or evaluation.","architectureImplications":"District-built agent connected to internal student and teacher data; interpretation: build viability depends on mature data integration and in-house engineering staff.","governanceImplications":"Embedding student data in a district-built agent puts security, access control and audit duties on the district rather than a vendor.","securityPrivacyImplications":"Not described. Interpretation: agentic access to student records needs role-based permissions, logging and FERPA review.","caveats":"Single-source operator claims; savings figure has no stated baseline; details deferred to a January conference talk.","streamIds":["k12"],"roles":{"sales":"Sales framing: some districts will build rather than buy AI agents if their data foundations are mature. Peninsula says it saved nearly $300,000, but gives no cost basis. A bounded data-readiness and build-versus-buy assessment fits districts weighing that choice. Do not repeat the savings figure as a benchmark or promise efficiency gains; the source reports no measured usage or outcomes.","engineering":"Engineering framing: the enabling factor was integrated district data, not the model. Pre-sales should assess data integration, identity and access controls, and logging before scoping any agent that reads student records. Proof of value: a limited agent pilot with role-based permissions and audit logs on one administrative workflow, measured for time saved against a baseline.","delivery":"Delivery framing: an in-house agent becomes a district-run product. Assign product ownership, a security review, a change process and support. The technology department owns it with the data governance lead. Acceptance means one workflow running with logged access and a measured time baseline. Risks include key-person dependency, unreviewed data access and maintenance cost hidden in the savings claim."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"A district with mature data systems might lower costs by building narrow agents; the source's savings are unverified.","potentialEngagement":"A six-week data-readiness and build-versus-buy assessment for one teacher workflow.","unsupportedClaims":["Savings figure lacks a cost basis.","No measured time savings.","No security review reported."]},"engineering":{"fit":"Fits districts with integrated data systems and in-house development staff.","architectureIntegration":"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.","proofOfValue":["Pilot workflow with audit logs","Measured time baseline vs after","Security review completed"]},"delivery":{"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.","skillsAdoption":"Teacher training on safe task delegation; engineer upskilling on agent tooling.","governanceCheckpoints":["Data access review","Pilot go/no-go","Annual cost and maintenance review"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-19T22:10:31-05:00","enrichedAt":"2026-10-19T22:18:02-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Teachers build their own uses, such as a classroom checkout; capacity depends on district engineering staff.","procurementImplications":"Build-versus-buy is a real option for data-mature districts; claimed savings should be verified against total cost of ownership.","operatingModelImplications":"District becomes the developer and operator of its own AI agent.","sourceVerification":{"openedUrl":"https://districtadministration.com/why-this-washington-district-built-its-own-agentic-ai/","referenceExcerpt":"Peninsula schools rolled out the agent this school year.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}