☀️ Summer Offer List price starts at $19/month. With code SUMMER2026: July + August free on eligible monthly plans. Existing members get the summer discount automatically. See plans & pricing →
For schools & districts

Procurement-ready. Privacy-review friendly.
Built for real educator workflow.

If your school or district is evaluating TeachSmartHQ™ for teacher workflow, documentation, differentiated materials, or broader implementation planning, this is the right place to start.

TeachSmartHQ™ is not a student information system and it is not a student-account platform. It is an educator-facing workflow system built to help teachers and support teams generate stronger drafts, differentiated materials, and more usable instructional tools without rebuilding everything by hand.

This page is for
  • district and school leadership evaluating fit
  • procurement reviewers running first-pass diligence
  • IT and privacy teams reviewing technical and contractual posture
  • special services, instructional, and implementation leads scoping rollout options
Educator-facing, not student-account-first Generic student references by design DPA / NDPA review available Pilots typically $2,500–$7,500 2-business-day first-response target

First response target: within 2 business days.

TeachSmartHQ™ has multiple entry points, but this page is specifically for teams that need more than an individual teacher checkout path.

You are probably in the right place if

  • you need privacy language before approving teacher use
  • you are evaluating a pilot instead of individual self-serve signups
  • you need onboarding, training, or implementation planning included
  • you want to understand the difference between Team plans and school-level adoption
  • you need a realistic picture of what TeachSmartHQ™ is now versus what is still on the roadmap

If you are one educator deciding whether PRO or Premiere™ fits your personal workflow, the better path is Plans & Pricing. If you are evaluating use across a department, school, or district, stay here.

TeachSmartHQ™ school and district pilots are built for teams that want a real evaluation path: privacy review early, implementation scope defined up front, and clear expectations about what the pilot is actually for.

Pilot pricing
$2,500$7,500

Scoped case by case. A 6-teacher departmental pilot and a district review with multiple stakeholders are not the same job.

Public range · first response within 2 business days

Scope depends on
  • number of educators involved
  • implementation depth
  • training and onboarding needs
  • school-level vs district-level evaluation
  • access to the deeper Adaptive Lesson Generator™ (ALG) implementation lane

What a pilot typically includes

  • implementation scoping conversation
  • fit review against your actual educator workflow
  • privacy / DPA / NDPA discussion path
  • onboarding for the participating cohort
  • training for the educators included in the pilot
  • defined evaluation period and intended use case
  • access structure aligned to the pilot scope
  • broader implementation discussion if the pilot proves value
2026–2027 cohort

The 2026–2027 pilot cohort is application-based. Up to 3 pilots accepted per quarter — 12 maximum across the school year.

The cap is capacity-driven, not artificial scarcity: each pilot receives full onboarding and implementation support, which means a deliberate cohort cap rather than open enrollment.

First-cohort pricing locked through October 31, 2026

Realistic pilot timeline

Most pilots should be framed as a short, structured evaluation, not an endless “let's just try it” situation.

  1. initial inquiry and fit review
  2. privacy / procurement questions surfaced early
  3. scope and cohort defined
  4. onboarding and training scheduled
  5. pilot runs against a specific use case
  6. decision conversation on next-step adoption

What is not included by default

  • a district-wide unlimited rollout
  • a custom integration project
  • a promise that every roadmap feature is already live
  • a replacement for your SIS, LMS, IEP platform, or district AI stack
  • an unscoped consulting engagement with no boundary around support
  • a defined cohort and use case
  • a named implementation path instead of ad hoc access
  • onboarding for the educators involved
  • training on how TeachSmartHQ™ fits real workflow
  • early privacy / procurement handling instead of late-stage scrambling
  • a clearer decision about whether the platform should stay small, expand, or stop there

TeachSmartHQ™ is built as an educator-facing workflow platform, not a student information system. That distinction is important for district review.

What that means in practice

  • educators are instructed to use generic learner references such as “Student A” or “the student” rather than names or identifiers
  • TeachSmartHQ™ is publicly positioned to avoid collecting, storing, or processing student names, IDs, birth dates, and other identifying student information as part of normal use
  • AI processing happens server-side, not directly from the user's browser to the AI provider
  • TeachSmartHQ™ states that customer inputs and outputs are not used to train AI models
  • district privacy review can proceed through a DPA / NDPA pathway on request
Defense-in-depth safeguard

Server-side PII scrubbing

TeachSmartHQ™ does not rely only on “please be careful” language.

The public privacy posture also describes a server-side safety layer: if a real student name, initials, or identifier is typed into a generator input, the backend applies scrubbing logic so the output uses a generic reference rather than passing named student language through as the final draft.

That is not a license to enter PII. It is a defense-in-depth safeguard designed to support compliant use.

FERPA posture

Aligned, not overclaimed

TeachSmartHQ™ is built to support FERPA-aware, privacy-conscious educator use. It is not sold as a student records database or system of record. That matters because districts evaluating the platform are not being asked to approve a replacement for their SIS or IEP platform.

Contractual trust anchor

No AI training on customer content

TeachSmartHQ™ is powered by Anthropic AI. Anthropic's Commercial Terms of Service prohibit using customer inputs and outputs to train Anthropic's models. That is an important contractual trust anchor, not just marketing copy trying to look responsible.

Administrative visibility

Audit logging at the district level

For district and school programs, TeachSmartHQ™'s public privacy posture already supports the idea of audit-log access for administrative activity under a district license. This should be part of the pilot / district review conversation early, not buried after contract review starts.

Retention & deletion

Defined window, not indefinite storage

The current public posture supports this plain-language summary:

  • active account content is retained to deliver the service
  • saved content can be deleted by the user
  • deleted items can move through a soft-delete / trash-style process before permanent removal
  • canceled or closed accounts are supported by a removal-from-active-storage window, typically within about 30 days, rather than indefinite permanent retention
DPA / NDPA pathway

Case-by-case, not one-size-fits-all

If your district requires a DPA or NDPA, bring that into the first inquiry. TeachSmartHQ™ is publicly positioned to handle that review case by case, rather than pretending a one-size-fits-all district packet solves every state and district requirement.

Accessibility posture

WCAG 2.1 AA as the target

TeachSmartHQ™'s public direction already points toward WCAG 2.1 AA as the accessibility target. That matters for procurement review because it signals accessibility is being treated as part of platform architecture, not as a post-launch apology tour.

TeachSmartHQ™ does not force every organization into the same adoption path.

01Individual

Individual educator plans

Best when one educator wants self-serve access and is not asking the school to review a broader implementation path yet.

02Team

Team plans

Best for a small working group that wants shared access with one bill and a shared generation pool.

03Pilot

School or district pilot

Best when the organization needs privacy review, stakeholder alignment, onboarding and training, and a cleaner path from evaluation to broader adoption.

04Broader implementation

The post-pilot conversation

What scaled use should look like, which educator groups should be included next, and whether the platform is being used for one workflow problem or as a broader connected system.

Current Team-plan structure

Tier Seats Shared generations Monthly
Team PRO 3 educator seats 75 shared / month $45 /mo
Team Premiere 3 educator seats 180 shared / month $99 /mo
Team Premiere Plus 3 educator seats 300 shared / month $169 /mo
Team Premiere Elite 3 educator seats 450 shared / month $239 /mo
Team Premiere Max 3 educator seats · bundles ALG 750 shared / month $429 /mo

Annual billing is available on the live Team page and framed as save 45%. Team plans are the right fit when a department chair, SPED coordinator, grade-level team, or small school-based cohort wants to adopt together without jumping immediately into formal district implementation.

A district reviewer should not have to guess what TeachSmartHQ™ is actually offering. Here is the cleanest current public picture.

Live now

PLAAFP Generator™

Structured present-level drafting for educator workflow that is already live and central to the platform.

In active build

Worksheet Generator™

Differentiated, teacher-quality worksheets designed for real classroom use rather than generic one-shot AI output. Included in current paid-ladder framing.

Premiere™ path

Lesson Delivery System

Full lesson-structure support positioned as part of the Premiere™ path on the individual and team ladders.

Coming soon

Parent Update Generator™

Family-facing update support positioned for higher tiers as the broader integrated workflow expands.

Flagship · deeper implementation lane

Adaptive Lesson Generator™ (ALG)

ALG is the most ambitious part of TeachSmartHQ™'s district-facing story — designed as a more adaptive, student-specific lesson system with broader accessibility and interaction ambitions than a standard lesson generator. Public site positioning already treats ALG as the deeper implementation lane for schools, teams, and advanced users who need more than a generic planning tool.

Why this matters at the district level

District value is not just “one good generator.” It is the connected workflow logic:

  • documentation support
  • differentiated material creation
  • lesson support
  • family-facing communication direction
  • broader adaptive/inclusive lesson architecture through ALG

TeachSmartHQ™ is publicly positioned to work alongside the tools schools and support teams already use, including:

Infinite Campus PowerSchool Skyward Goalbook Google Classroom Microsoft Copilot Kami IEP systems LMS platforms

That means the platform is not asking to become your SIS, your LMS, your IEP platform, or your district productivity suite. It is meant to improve the educator-facing workflow that happens around those systems.

The strongest implementation posture is the honest one: a successful pilot or rollout depends on clear scope, the right stakeholders, and training that respects how educators actually work.

Typical stakeholders in the first serious conversation

  • school or district instructional lead
  • special services or SPED leadership, if that is a core use case
  • privacy / IT reviewer, if district review is required
  • implementation lead or operations owner
  • procurement reviewer when formal vendor review is already underway

What onboarding should cover

  • what TeachSmartHQ™ is and is not
  • which workflows the pilot is actually evaluating
  • how generic student references and privacy rules work
  • how participating educators should use the platform in practice
  • what success looks like during the pilot window

What training should cover

  • how to use the relevant generators well
  • what to review manually before using outputs
  • where TeachSmartHQ™ fits beside district systems
  • what not to do, especially around student PII and scope creep

What the scoping conversation should settle

  • pilot cohort size
  • target educator roles
  • priority workflows
  • privacy / contract path
  • success criteria
  • evaluation timeline
  • whether the district is exploring a narrow workflow solution or a broader implementation path

TeachSmartHQ™ was built by people working inside real K-12 workflow, not by a team guessing from the outside.

That matters because procurement teams are not just evaluating software. They are evaluating whether the product reflects how classrooms, special services teams, and school systems actually function.

The public credibility story is simple and strong:

  • shaped by working educators and classroom professionals
  • informed by curriculum and instructional-design expertise
  • supported by enterprise-grade IT and privacy discipline
  • Is this an educator-facing platform or a student-data system?
  • Can our district review DPA / NDPA terms before adoption?
  • Does this replace our existing systems?
  • What is live now versus still on the roadmap?
  • What does a pilot actually include?
  • Can we start with a small group before a broader rollout?
  • How is student privacy handled in practice, not just in marketing language?
01 Do you offer a DPA or NDPA pathway for schools and districts?

Yes. TeachSmartHQ™ is publicly positioned to support district DPA / NDPA review on request, handled case by case rather than through a fake one-size-fits-all packet.

Read the full answer on the FAQ →
02 Is TeachSmartHQ™ FERPA-compliant?

The careful public answer is that TeachSmartHQ™ is built for FERPA-aware, privacy-conscious educator use. It is not marketed as a student information system, and it is designed around generic student references rather than named student records.

Read the full answer on the FAQ →
03 What's the difference between Team plans and school pilots?

Team plans are self-serve small-group plans for up to 3 educators with shared generations and one bill. School pilots are separate, scoped implementation paths built for privacy review, onboarding, training, and broader evaluation.

Read the full answer on the FAQ →
04 Does TeachSmartHQ™ use educator inputs or outputs to train AI models?

No. TeachSmartHQ™ states that customer inputs and outputs are not used to train AI models, and the Anthropic Commercial Terms of Service provide the strongest public contractual anchor for that claim.

Read the full answer on the FAQ →
05 Is my student data safe?

TeachSmartHQ™ is built around generic student references, server-side PII scrubbing safeguards, server-side AI processing, and a workflow model that is educator-facing rather than student-record-first.

Read the full answer on the FAQ →
12Start an inquiry

Start with the real questions.

If your team is evaluating TeachSmartHQ™ for a school, department, or district use case, the best next step is a structured inquiry. That gives us the context needed to route well and respond with something useful instead of a generic sales reply.

The 2026–2027 cohort is application-based — first-cohort pricing locked through October 31, 2026.

Schools & Districts inquiry

Tell us about your school or district.

First response within 2 business days. Required fields marked with *.

Workflows you are evaluating*
Select at least one.
Up to 500 characters.

Submitting opens your email client with a pre-filled message to our routing inbox.