Agenteach

Built with teachers, for schools

Take the busy out of busywork.

Agenteach helps teachers save time on documentation, tracking, parent communication, and paperwork — so they can focus on the students in front of them.

Book time with us Try demo coming soon

Today’s follow-through

Thursday afternoon

4 tasks saved

Documented accommodations

Captured notes once, organized for review, logs, and follow-up.

Parent update drafted

Warm, specific language ready for teacher review before anything is sent.

Repeated issue flagged

The same student pattern appeared across notes, emails, and prior logs.

Building with educators

Building with current and former educators from

Insights from classrooms, schools, and district contexts are shaping what Agenteach becomes.

Detroit Public Schools

Ann Arbor Public Schools

Spring ISD

Edison Township Public Schools

Freire Schools

Keystone School

District of Columbia Public Schools

DC Prep

Harris County Schools

Teacher voices

Teachers, what would you do with an extra hour each day?

A living whiteboard for the time teachers want back. Add a response and watch it join the board by theme.

The extra-hour board

What we heard

The work is not one big task. It is dozens of tiny follow-ups.

Documentation lives everywhere.

Teachers are asked to record the same facts across SIS, LMS, folders, reports, and emails.

Repetition steals reach.

Manual follow-up means fewer families contacted and more students slipping through.

Context gets scattered.

Notes, contacts, behavior records, accommodations, and next steps rarely live in one actionable place.

Teachers do not need more tools.

They need less duplication, fewer logins, and practical help with the work after the teaching.

How Agenteach works

Capture once. Route everywhere it needs to go.

Document

Drop in notes, screenshots, forms, CSVs, emails, or quick voice memos.

Organize

Agenteach links the evidence to students, tasks, communication, and required records.

Follow through

Draft updates, flag repeated patterns, remind teachers what is open, and keep humans in control.

Student data privacy & security

Designed so schools stay in control of student data.

Agenteach is being built for sensitive K–12 workflows: student notes, parent communication, accommodations, evidence, and auditability. Our architecture starts from data minimization, school-controlled storage, and human approval.

Plain English promise

Agenteach should help teachers organize and draft. It should not silently scan school accounts, sell student data, target ads, or send messages without the educator choosing to act.

School-controlled storage

Google Workspace is the default source of record. Student evidence is designed to live in the school-controlled Google tenant, not in an Agenteach student-content database.

Data minimization by default

Where possible, Agenteach stores references, task state, policy metadata, and audit events rather than raw student files, screenshots, transcripts, or message bodies.

Teacher-invoked only

No background Gmail or Drive scanning. Agenteach analyzes material only when a teacher chooses a file, note, email, or workflow and asks for help.

Human approval before action

No auto-sending parent emails. Drafts, exports, and sharing flows stay under teacher review, with sensitive-evidence checks before anything leaves the workspace.

No ads. No selling data.

Agenteach will not sell or rent student, teacher, school, or family data, and will not use student data for behavioral advertising, retargeting, or unrelated commercial profiling.

Least-privilege Google access

Google integrations are designed around narrow scopes, consent, domain controls, and revocable access — with Microsoft OneDrive planned for a later roadmap phase.

What Agenteach may store

• File IDs or links pointing back to school-controlled Google Drive
• Workflow state, task status, and teacher preferences
• Policy labels such as evidence sensitivity or sharing restrictions
• Audit events needed for security, support, and district review

Not stored by default

• Raw student files, screenshots, PDFs, spreadsheets, or videos
• Voice-note recordings, transcripts, or extracted student evidence
• Parent email bodies unless a school explicitly enables that storage
• Student records used for unrelated product training or advertising

District procurement path

• DPA-ready commitments for deletion, return, retention, and subprocessors
• Breach-response process, access controls, logging, and vendor review support
• FERPA, COPPA, PPRA, state student privacy, and accessibility-aware workflows
• Roadmap: SOC 2 readiness, ISO 27001 readiness, NIST CSF alignment, penetration testing, and responsible disclosure

Built for review, not hand-waving

We are aligning the product to the privacy commitments schools already expect from edtech vendors.

That means clear DPAs, limited collection, purpose limitation, deletion and export support, subprocessors transparency, role-based access, secure development practices, and auditability. Some certifications and audits are roadmap items, so we describe them as design targets until formally completed.

For teachers

More time for the human work.

Less retyping, less searching, fewer open loops after school.

For principals

Cleaner follow-through.

Better documentation, parent communication, and visibility without adding another burden.

For districts

A practical AI wedge.

Start with everyday workflows while building toward secure, compliant automation across school tools.

Demo coming soon

We are building with design partners now.

If you are a teacher, principal, or district leader who wants to reduce documentation and follow-through burden, we would love to learn from you.

Book time with us Add to the teacher board