Individual educator plans
Best when one educator wants self-serve access and is not asking the school to review a broader implementation path yet.
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.
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.
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.
Scoped case by case. A 6-teacher departmental pilot and a district review with multiple stakeholders are not the same job.
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.
Most pilots should be framed as a short, structured evaluation, not an endless “let's just try it” situation.
TeachSmartHQ™ is built as an educator-facing workflow platform, not a student information system. That distinction is important for district review.
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.
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.
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.
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.
The current public posture supports this plain-language summary:
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.
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.
Best when one educator wants self-serve access and is not asking the school to review a broader implementation path yet.
Best for a small working group that wants shared access with one bill and a shared generation pool.
Best when the organization needs privacy review, stakeholder alignment, onboarding and training, and a cleaner path from evaluation to broader adoption.
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.
| 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.
Structured present-level drafting for educator workflow that is already live and central to the platform.
Differentiated, teacher-quality worksheets designed for real classroom use rather than generic one-shot AI output. Included in current paid-ladder framing.
Full lesson-structure support positioned as part of the Premiere™ path on the individual and team ladders.
Family-facing update support positioned for higher tiers as the broader integrated workflow expands.
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.
District value is not just “one good generator.” It is the connected workflow logic:
TeachSmartHQ™ is publicly positioned to work alongside the tools schools and support teams already use, including:
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.
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:
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 →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 →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 →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 →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 →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.
First response within 2 business days. Required fields marked with *.