EdTech Marketing Playbook: How to Market to Schools, Colleges and Parents

Questions EdTech founders ask. Fifteen questions on pricing, pilots, evidence, buyers, budgets and classroom use, each answered on its own.

Should EdTech pricing be per student, teacher, school or district?

For an EdTech product sold to schools, price in the unit that matches the budget that pays and the way your value grows. Whatever unit you choose, also show the cost per student, because that is how a district finance office compares quotes.

How each unit maps to who pays

• Per student. Fits a product every student uses, paid from a district's core curriculum or technology budget. Easy to compare; the risk is that revenue falls when enrollment does.
• Per teacher. Fits teacher tools, such as planning or grading, where value grows with the number of teachers. It suits smaller purchases from a school or professional-learning budget.
• Per school (site licence). Fits when a principal or a school-level fund pays. Some federal money is school-level: districts "target the Title I funds they receive to schools with the highest percentages of children from low-income families" (US Department of Education). A flat site price is simple, but it undercharges large schools unless you band it by enrollment.
• Per district. Fits systems the whole district runs on. One contract, a larger number, a longer approval chain and often a board vote.

Site versus district licence. In my view, start with site licences so one school can say yes. Once several schools in the same district are paying, offer a district licence that brings them under one contract and one budget line, priced so the district saves something by consolidating.

Minimums. Set a minimum annual fee per account. No reliable universal figure exists; set yours from what it costs you to onboard, train and support one account for a year, so the smallest customer does not lose you money.

By stage. At seed, pick one unit and one starting scope (one grade, one subject) and keep the quote to one line. At Series A–B, add a district licence and multi-year terms once renewals show what districts will keep paying for.

The common mistake is copying a competitor's unit when your value grows differently. If your product saves teacher time, a per-student price makes a small school with many teachers look cheap and a large school with few teachers look expensive.

Example Co. (fictional) quotes its illustrative district price both as a total and per student, so finance can compare it with what it already pays.

How should you price an EdTech product for schools versus parents?

Price an EdTech product for schools and for parents as two different products, because they are two different buyers. A school pays by invoice from a budget line set once a year; a parent pays by card from household money and can cancel in any month. AAJ publishes no price benchmarks for either; you need to research and test your own.

How the two buyers differ

• Payment. Districts often pay a year at a time. PowerSchool, which sells mainly to K-12 schools and districts, says in its annual report for 2021 that "Customers are billed annually in advance, with a small number of customers billed semiannually, quarterly or monthly" (PowerSchool 10-K for 2021). Parents expect a card checkout and a monthly or annual plan.
• What they compare you with. A district compares your per-student cost with what the product replaces. A parent compares you with a tutor, a workbook or another app.
• What proof they need. A district wants evidence of learning and privacy paperwork. A parent wants visible progress in the first week.

How to research price levels yourself

1. Find published prices for each buyer's alternatives: competitors' pricing pages and app store listings for parents; board meeting agendas and cooperative contract price lists for districts, where public.
2. In discovery calls, ask what the buyer pays today for the problem you solve.
3. Treat stated willingness to pay as a starting range only.

How to test. For parents, run real price tests at checkout and compare trial starts, paid conversion and cancellations at each price. For schools, put two scopes at two prices in each proposal and record which one is approved.

Whether to serve both, and in what order. In my view, pick one first. Choose schools first if the product needs a classroom routine and evidence; choose parents first if a parent can see the value alone within a week. If you later sell to families of students who use your school product, build that list from parents who opt in separately. In its 2022 policy statement on education technology under COPPA, which protects children under 13, the FTC says EdTech companies are "prohibited from using such information for any commercial purpose, including marketing, advertising, or other commercial purposes unrelated to the provision of the school-requested online service" when it was collected with a school's authorization (FTC, 2022). This is orientation, not legal advice.

The common mistake is deriving one price from the other, such as charging parents a district's per-student price.

Should family subscriptions be monthly or tied to the school year?

For a family EdTech subscription, no reliable public study compares monthly billing with school-year billing for K-12 products, so decide by testing. In my view, offer both: a monthly plan for families who want to try, and a school-year or annual plan at a discount, with a clear plan for the summer.

The trade-offs

• Monthly. Lower commitment, so more families start paying. But each month is a chance to cancel, and in my view the summer break is the riskiest stretch.
• School-year or annual. Cash up front and no summer cancellations inside the term. But the price is larger, refund requests are bigger, and the renewal a year later needs a plan of its own.

Plan for summer. Choose one: a pause option, a lower-priced summer plan, or summer content worth paying for.

Rules on automatic renewal. An FTC staff report summarises the federal Restore Online Shoppers' Confidence Act as requiring sellers to clearly disclose "all material terms of the transaction", obtain "a consumer's express informed consent before charging the consumer's account" and provide "simple mechanisms for a consumer to stop recurring charges" (FTC, 2022). In September 2025 the FTC said EdTech provider Chegg would pay $7.5 million to settle allegations that it "made it extremely difficult for consumers to cancel recurring subscriptions" (FTC, 2025). States add rules: California requires "an annual reminder" about auto-renewal plans and online cancellation for plans bought online (California Attorney General, 2025). Write and publish your refund policy, and get legal advice for the states you sell in. This is orientation, not legal advice.

How to decide. Compare plans on revenue per family over 12 months, not on first-month conversion.

How should you price and structure a school pilot?

In my view, a school pilot should carry a fee, a fixed scope, a length set by the school calendar, success measures agreed in writing, and the contract price written in before it starts. No reliable public data shows whether paid pilots convert better than free ones, so treat this as judgement, not a rule.

Paid or free. A free pilot gets a faster yes but often becomes free use. A paid pilot proves a budget exists and someone with spending authority is involved. A middle path: charge a pilot fee and credit it against the first contract year.

Scope. Small enough to approve quickly: one grade, one subject or a few classrooms in one school. Include training.

Length. No universal right length exists. Set it from two dates: how long your success measure needs before it can move, and when the district drafts next year's budget. For most states the school fiscal year "begins on July 1 and ends on June 30" (NCES, 2025), so a pilot that starts in autumn and reaches a decision in winter can still make the spring budget.

Success criteria, agreed up front. Pick one learning measure the school already uses (its own screener or benchmark test), one teacher measure (a short survey) and one usage measure. Agree what result counts as success before any classroom starts, and write it down.

Conversion. Put the next step in the pilot agreement: the full-contract scope, its price and the decision date. A district can then budget for it without a new negotiation.

Who signs. The person who holds the budget line signs. A small pilot may be within a principal's or department director's own authority; the full contract may need the business office, procurement and, above local limits, a board vote. Those limits are set by each state and district, so ask your champion who signs at each size.

By stage. At seed, standardise one pilot package: fee, length and report template. At Series A–B, run pilots on the same template so you can compare conversion.

The common mistake is an open-ended pilot with no measures, no decision date and no price.

Example Co. (fictional) plans an illustrative eight-week pilot in six classrooms, with its pilot fee credited against the first year.

What evidence do schools expect before they will pilot a product?

Before a pilot, expect a district to ask for privacy and security documents and for a short evidence summary. For a young product, the realistic evidence is ESSA Tier 4: a logic model based on research, plus a study that is planned or under way. In my view, higher tiers matter more at the full purchase than at the pilot.

The four ESSA tiers, precisely. The US Department of Education's 2023 guidance sets out ESSA's four tiers alongside the matching definitions the Department uses for its own grants (EDGAR, 34 CFR 77.1) (US Department of Education, 2023):

• Tier 1, strong: at least one well-designed and well-implemented experimental study (random assignment).
• Tier 2, moderate: at least one well-designed and well-implemented quasi-experimental study (a non-random comparison group).
• Tier 3, promising: at least one well-designed and well-implemented correlational study "with statistical controls for selection bias", for example "a study using regression methods to account for differences between a treatment group and a comparison group".
• Tier 4, demonstrates a rationale: a logic model informed by research, with "ongoing efforts to examine the effects".

For Tiers 1 and 2, the Department's grant definitions (EDGAR), summarised in the same guidance, add "A large sample (n = 350+) and a multisite sample" and "no overriding statistically significant and negative effects on relevant outcomes"; ESSA's own statutory wording sets no sample size.

What a Tier 4 logic model involves. The guidance defines a logic model as "a framework that identifies key project components" and "describes the theoretical and operational relationships among the key project components and relevant outcomes". In practice: the problem, what the product does, what should change for students, and how you will measure it, each linked to published research. A Regional Educational Laboratory handout adds that "an effort to study the effects of the program must already be planned or under way" (REL Midwest, 2019).

What a Tier 3 study involves. Data from students who used the product, compared with similar students who did not, with statistical controls for prior achievement and other differences.

What you can show at seed. A one-page logic model with its research citations, usage data from early pilots, and a written plan for a Tier 3 study with a named partner. At a March 2020 webinar, the What Works Clearinghouse said "IES currently does not plan to add ESSA ratings for Tier 4 to the WWC website" (What Works Clearinghouse, 2020). So you document it yourself.

The common mistake is calling a product "research-based" without naming the tier or the research.

How do you show your product improves learning outcomes?

To show an EdTech product improves learning, compare users with similar non-users on a measure the school already trusts, and have someone independent check the work. Users' before-and-after scores show change, not cause.

Study designs, simplest to strongest

1. Pre/post, users only. Cheap, but cannot separate your effect from normal growth.
2. Correlational with controls. Users versus non-users, adjusted for prior scores and other differences (ESSA Tier 3).
3. Quasi-experimental. A matched, non-random comparison group (can support Tier 2 if well run with a significant positive effect).
4. Randomised. Classes or schools assigned to the product by lottery (can support Tier 1 on the same conditions).

Three What Works Clearinghouse (WWC) credibility checks:

• Baseline match. Without random assignment, show the groups matched at baseline. "If baseline equivalence is not established, the study Does Not Meet WWC Group Design Standards" (WWC).
• Several units per group. A study is confounded if "either the intervention group or the comparison group contains only one student, classroom, teacher, or school" (WWC).
• Few drop-outs. If drop-outs leave the two groups different, "the observed effect of the intervention is biased" (WWC).

Sample size. No universal number exists; it depends on the expected effect, score variation and whether you assign whole classes or individuals. Ask an evaluator for a power calculation first. For Tiers 1 and 2, the Department's grant definitions (EDGAR), in its 2023 guidance, require a sample that "includes at least 350 students or other individuals across sites" (US Department of Education, 2023); ESSA's statute sets none.

Third-party evaluators. A university researcher or evaluation firm adds credibility and often an ethics (IRB) review. Agree to publish whatever the results show.

Privacy and consent. FERPA's studies exception lets a school share student records without parental consent only with an organisation studying for, or on behalf of, the school, for purposes such as "improving instruction"; "A written agreement with the organization is required, specifying the purposes of the study and the use and destruction of the information" (US Department of Education). Student surveys touching protected areas, such as "mental or psychological problems of the student or the student's family", fall under the Protection of Pupil Rights Amendment, which applies to schools and other recipients "of funds under any program funded by the U.S. Department of Education" (US Department of Education). Ask each district about research approval. This is orientation, not legal advice.

Timing and stage. Agree the design before term; take baseline scores at the start. At seed, a correlational study is realistic; at Series A–B, commission an independent quasi-experimental or randomised one.

How do you report learning outcomes without overclaiming?

To report EdTech learning outcomes without overclaiming, say exactly what your study showed, name the study and its limits, and have the evidence on file before the claim goes out. US law expects that order: the FTC requires "a reasonable basis for advertising claims before they are disseminated" (FTC, 1984).

Wording rules

1. Match the verb to the design. Without a comparison group, say "students who used it scored higher", not "it raised scores". "Improves", "boosts" and "causes" claim causation; only a well-run comparison study supports them.
2. Name the study in the claim. Who ran it, when, where, how many students, which measure, and for how long.
3. State the limits. One district, no random assignment, your own staff ran the analysis: say so next to the result.
4. "Studies show" is itself a claim. If you say "studies show" or "tests prove", the FTC expects "at least the advertised level of substantiation" (FTC, 1984).
5. Name the ESSA tier. Say "ESSA Tier 4: logic model, study under way", not just "evidence-based".
6. Testimonials are claims too. If a teacher's quote describes results, the FTC says an advertiser without proof the experience "represents what people will generally achieve" must make "clear to the audience what the generally expected results" are (FTC).

Two FTC cases show the risk. In 2016 the FTC charged that Lumosity's maker deceived consumers with "unfounded claims that Lumosity games can help users perform better at work and in school"; the settlement requires "competent and reliable scientific evidence before making future claims" (FTC, 2016). In 2025 its final order against Workado, over accuracy claims for an AI content detector, requires "competent and reliable evidence" for future effectiveness claims (FTC, 2025). AI features get no exemption.

A weak and a strong claim (illustrative, Example Co. is fictional)

• Weak: "Example Co. boosts reading scores."
• Stronger (illustrative): "In an eight-week 2026 pilot in six classrooms in one district, students who used Example Co. gained more on the district's reading screener than students in the same grades who did not. Classes were not randomly assigned, so this shows an association, not proof the coach caused the gain. An independent study is under way."

In my view, the stronger version sells better to a curriculum leader, because it is the claim they can repeat to their board. This is general information, not legal advice.

Should EdTech startups sell to administrators or teachers first?

For an EdTech startup selling to schools, decide by two facts: who holds the budget line that would pay for your product, and who decides whether it gets used in class. If a teacher can pay and adopt alone, start with teachers. If the money sits in a school or district budget, start with the administrator who owns that line, and treat teachers as the people who make the pilot work.

The two roles depend on each other. Teachers rarely sign, but they decide whether a product is used. Administrators sign, but they decide on evidence that comes from classrooms. RAND's 2026 study of math curriculum adoption found that processes typically gathered input from several groups, but "the final decision was most often made by district-level staff" (RAND, 2026). And districts control what may be used at all: in CoSN's 2026 survey of 607 district technology leaders, 65% of districts require a review by IT and 61% create a list of approved apps before free tools can be used (CoSN, 2026).

How to decide:

1. Name the budget line. A teacher's own money or a small classroom fund supports a bottom-up motion. A curriculum or technology line needs a top-down motion.
2. Name who can stop use. The approved-app list, the IT review and the data-privacy agreement apply in either motion.
3. Pick one motion. Bottom-up: a free or low-cost teacher version that builds usage you can later show a district. Top-down: named districts, one champion, a pilot with agreed measures.
4. Connect it to the other role. Bottom-up needs a path to the approved list, so prepare the privacy paperwork early. Top-down needs teachers to actually use the product in the pilot, because their usage and feedback are your evidence.

District or single school. A single school has fewer approvals, and in some districts the principal controls part of the budget; ask, because it varies. The district's approved-app and privacy rules usually still apply. A district deal is larger and slower, with more people in the buying group.

By stage. At Seed, I would start where the fewest people stand between the user and the budget. Add the second role only once the first motion repeats. At Series A–B, run both: teacher usage feeding a district sales team.

The common mistake is counting teacher sign-ups as pipeline. Free use with no budget owner and no path to the approved list stays free.

How do you write one message for both teachers and administrators?

For an EdTech product sold to schools, write one core promise and three pillars, then give each pillar a teacher line and an administrator line. The pillar stays the same; the lead changes. Teachers judge time and classroom fit; administrators judge standards, evidence and risk. Each line needs its proof beside it, or it is just a slogan.

Example Co. (fictional) makes an AI reading coach for kindergarten to grade 3: children read aloud to it, it flags mistakes, and adults get a weekly report. These illustrative lines are for its future district offer.

Core promise (Example Co.'s district positioning line): "Every K–3 reader practises reading aloud every day, and teachers see who needs help, without extra marking time."

Where each line goes.

• Teacher onboarding email: one teacher line per email, sent when the teacher reaches that step: setup, first report, then control.
• Administrator one-pager: the core promise at the top, the three administrator lines, and the proof documents attached, not promised.
• District demo: open with the administrator line, then show the classroom view so a teacher on the call sees their own line come true.

Test each line. Use words each audience actually says on calls. A district buying group includes both, so each line must survive the other audience hearing it.

The common mistake. In my view, it is writing two promises: "fun AI" for teachers and "higher scores" for administrators. The first undersells; the second overclaims unless the evidence is on file. Keep one promise and the same pillars; change only the lead line and its proof.

How do you budget for school sales that take a full year?

Budget a school sale as cash you spend for most of a year before the first invoice. Fund the work that must happen before districts draft their budgets, and assume new district revenue arrives when their budget year starts. For most states, "The fiscal year begins on July 1 and ends on June 30" (NCES, 2025), so a product that is not in the draft budget by spring usually waits a year.

Cash and payback. Track two things per district: the cash gap (months from first spend to first invoice) and CAC payback (months of gross margin needed to recover acquisition cost). PowerSchool's 10-K for 2022 says "Customers are billed annually in advance, with a small number of customers billed semiannually, quarterly or monthly" (PowerSchool, 2023). Illustrative arithmetic: if winning one district costs $20,000 in sales and marketing between October and April, and the contract is the playbook's assumed $15,000 a year at an assumed 80% gross margin, margin payback is $20,000 ÷ $12,000 a year, about 20 months. With annual billing in advance, the cash comes back only at the second invoice, about 21 months after the first October spend, and only if the district renews. Plan cash for that.

Front-load these (needed before any district talks seriously):

• the privacy page, a data-privacy agreement you will sign and a security summary
• your logic model and a one-page evidence summary
• pilot costs: training, support and reporting

Time these to the buying calendar:

• autumn: outreach, webinars and pilot starts
• winter: pilot reports and champion materials
• spring: conference meetings and budget support
• summer: training and onboarding for new contracts

Pipeline coverage. No reliable public figure gives the right coverage ratio for school sales, so set your own. Work backwards from the number of district contracts you need to start in July. Divide by your own pilot-to-contract rate to get the pilots you need, and start them by the end of autumn. With no history, treat the rate as an assumption and update it after the first budget season.

By stage. At Seed, keep a revenue line that is not tied to district budgets, such as parents or tutoring centers, so cash does not depend on one season. At Series A–B, budget renewals as a second calendar, starting in winter.

The common mistake is launching the big push in May, after most budgets are set.

What must be ready before a back-to-school campaign?

For an EdTech company, back-to-school is a delivery season for schools and a buying season only for teachers and parents. For most states the school fiscal year "begins on July 1 and ends on June 30" (NCES, 2025), so district money for the new school year is usually set before summer, and everything a school customer needs must be ready before teachers return, and anything you pitch to schools in August is mostly next year's pipeline. AAJ's EdTech marketing calendar puts summer (July to September) as the time to close signed deals, train and onboard, and to avoid new pitches to busy teachers once school starts.

Exact start dates vary by state and district, so check each customer's calendar and work backwards from the first teacher day.

For school buyers (signed customers), ready before teachers return:

• data-privacy agreement signed and the product on the district's approved-app list
• rostering and sign-in tested with the district's real class data
• training sessions booked before the first week of school
• a named support contact and a plan for the first two weeks of class
• the report template the administrator will receive, agreed in advance

For teachers, ready before they plan their first weeks:

• a setup guide a teacher can finish in one sitting
• a ready-made first lesson that works on school devices
• onboarding emails triggered by what the teacher has done, not by date
• a short note they can send to families, if families need to know

For parents, ready before late-summer shopping:

• if children under 13 use the product, a parental-consent flow that meets COPPA, reviewed by a lawyer
• a landing page with one offer and a clear first-week result
• tracking set up and tested, so you can judge the campaign

What to decide first. Use AAJ's Campaign Brief: one audience, one business number, one offer, and the metric and stop rule. If you want both new teachers and new parents, that is two campaigns.

By stage. At pre-seed and Seed, run one back-to-school campaign for one audience and make onboarding flawless for existing customers. At Series A–B, run separate tracks for customer onboarding and new-teacher acquisition, with different owners.

The common mistake is treating back-to-school as a district sales push. In the first weeks, teachers are setting up classrooms, and most district budgets for the year are already set.

The Launch Readiness Planner on AAJ helps you plan the dates.

How do you reduce onboarding friction in classrooms?

Classroom onboarding has more friction than ordinary onboarding because one adult must set up many students at once, on school systems, under privacy rules. Reduce it by connecting to the systems schools already use, keeping teacher setup to one sitting, and making the first lesson work.

1. Rostering and sign-in. Rostering means loading class lists automatically instead of typing them. 1EdTech's OneRoster standard "defines information about people (users), courses, enrollments, organizations, and grades", and 1EdTech says "It reduces the manual effort and saves the time of teachers and administrators" (1EdTech). Its LTI standard is "used to connect learning tools with an institution's learning environment without logging into each tool" (1EdTech). Districts check this. In CoSN's 2026 survey of 607 district technology leaders, 43% of districts include interoperability requirements in their RFPs (CoSN, 2026). Support the rostering and sign-in routes your target districts use; ask them which.

2. Teacher setup time. No reliable public benchmark exists, so set your own target. Watch five to ten new teachers set up without help, from first login to a class ready to start, and note each step where they stall. Ask your schools how long a planning period is, and set the target inside it. Then pre-load a sample class, defer optional settings, never ask teachers to retype what rostering can supply, and re-time setup after each release.

3. Student accounts and consent. The FTC's COPPA guidance says that in the educational context "the schools may act as the parent's agent and can consent under COPPA", but only where the operator collects student data "for the use and benefit of the school" and "for no other commercial purpose", and the operator must give the school direct notice of its practices (FTC). In its 2025 rule update, the FTC said it "will continue to enforce COPPA in the ed tech context consistent with its existing guidance" (FTC, 2025). Collect the least student data the lesson needs. This is orientation, not legal advice.

4. First-lesson success. The first lesson is the classroom's first value moment. Give teachers a ready-made first lesson that works on school devices, with a visible result for the teacher at the end.

By stage. At Seed, a clean CSV upload may be enough for a few schools. Before a district pilot, support the standard the district uses.

The common mistake is designing onboarding for one user. In classrooms the teacher onboards, then the whole class does, and either step can stall the other.

How do you keep teachers using your product after month one?

Teachers keep using an EdTech product after the first month when it has become part of their weekly teaching routine and saves them time each week. Get each teacher to an activation milestone early, then build a weekly rhythm around the way they teach.

1. Define a teacher activation milestone. It is a behaviour, not a login: for example, "used the product with a whole class in three lessons and opened the results once". Pick yours from your data: compare teachers who were still active after a term with those who stopped, and find the early behaviour that separates them. No reliable public benchmark exists for teacher activation, so set your own target.

2. Build a weekly rhythm tied to teaching. Most teachers plan, teach, check and regroup each week. Fit the product into that cycle:

• planning: a ready lesson or assignment for next week
• teaching: something that runs in class with little setup
• checking: a short summary of who needs help
• regrouping: a suggested next step for those students

3. Add light retention loops. Each lesson should produce something that sets up the next one. Student work feeds the teacher's summary, the summary suggests the next lesson, and that lesson produces new work. Send a weekly email only when it holds that teacher's own class results.

4. Plan for breaks. Holidays, testing weeks and term ends interrupt habits. Send a short restart note when classes resume, rather than a churn alert during the break.

5. Train, and keep training. RAND's 2026 study found that "Most principals purchased bundled professional learning offered by the curriculum vendor alongside math curriculum adoption" (RAND, 2026). In math curriculum, at least, schools often buy training along with the product. A short session after the first month, on using the results, can matter more than the launch session.

What administrators should see. Class- and school-level usage over time, the share of teachers who reached the milestone, and progress on the outcome in your logic model. Show aggregates, not a tool for watching individual teachers, and keep student data within the school's purposes.

By stage. At Seed, talk to every teacher who stops and find out why. At Series A–B, a customer success team tracks the milestone by school and acts on schools falling behind.

The common mistake is reading the first-month spike as adoption. Judge retention after the first term, against the routine you designed.

How should EdTech startups measure daily active students?

Daily active students (DAS) is the number of unique students who complete at least one meaningful learning action in your product on a given school day. It is easy to calculate and often the wrong measure, because most classroom products are meant to be used on some days, not every day.

How to calculate it.

1. Define the qualifying action: a completed activity or lesson, not a login.
2. Count unique students with that action on each school day; leave out weekends and holidays.
3. Choose the denominator and say which it is: licensed students, rostered students or students whose teacher is active. Each answers a different question.
4. DAS rate = DAS ÷ that denominator.

Why weekly or per-lesson measures often fit better. If the design is three sessions a week, a student who does exactly that looks inactive two days in five. Two alternatives:

• Weekly active students: unique students with a qualifying action in the school week.
• Planned-use completion: sessions completed ÷ sessions the teacher assigned or the logic model expects.

Illustrative example, Example Co. (fictional): if 300 rostered students are meant to read to the coach three times a week, the team tracks the share reaching three sessions each week, not daily logins.

What it tells you. Whether students got the dose your logic model needs, and where use is falling.

What it doesn't tell you. Whether students learned more. Usage is not evidence of learning on its own, and it does not meet any ESSA evidence tier alone. Pair it with the outcome measure the district already trusts.

Benchmarks. No credible public benchmark sets a good DAS rate. Set your target from your own logic model: the use needed for the effect you expect.

How districts use it at renewal. They can see what is actually used. Instructure's 2026 analysis of Canvas LTI launch data for 12,672,611 US K-12 students and educators reported that "While districts maintain access to an average of 3,001 unique digital tools, students and educators interact with only four on average", and that districts are "consolidating around a smaller set of tools that can actually prove their worth" (Instructure, 2026). That is vendor research based on launches from one platform. Send your own usage report before the district drafts its budget, not after.

The common mistake is reporting the best number. Report the definition, denominator and trend.

How should EdTech marketing address AI cheating concerns?

Address AI cheating in EdTech marketing by stating plainly what your product does and does not do, showing the controls teachers have, and making no claim you have not tested. Buyers already worry about it. In Pew Research Center's 2025 survey of 1,458 US teens, 54% had used chatbots to get help with schoolwork, and 59% think using AI to cheat is a regular occurrence at their school (Pew Research Center, 2026). In CoSN's 2026 survey of 607 district technology leaders, the share of districts that have updated academic integrity policies as part of their AI guidelines rose from 32% in 2025 to 46% in 2026 (CoSN, 2026).

What to say:

1. What the product does. One plain sentence about the AI's role.
2. What it does not do. For example, whether it can produce finished work a student could hand in.
3. Teacher controls. What a teacher can switch on or off, and what student activity they can review.
4. Transparency. Whether students, teachers and parents can see when AI was used. The Department of Education's July 2025 guidance stresses "engaging affected stakeholders, especially parents, in decisions about the adoption and deployment of new technologies" (US Department of Education, 2025).

What not to claim. Not "cheat-proof". Not a detection accuracy figure you have not tested on real student work. The FTC alleged that Workado promoted its AI content detector as 98% accurate when "independent testing showed the accuracy rate on general-purpose content was just 53 percent" (FTC, 2025). The final order bars accuracy claims unless the company has "competent and reliable evidence to support the claim at the time it is made" (FTC, 2025). Teachers already rely on detectors: in CDT's survey of 460 grade 6–12 public school teachers, fielded in November–December 2023 and published in March 2024, 68% reported using an AI content detection tool regularly, and CDT notes research showing such tools are not consistently effective (CDT, 2024). CDT warns that "accusations alone can become a catalyst to disciplinary action", so an untested accuracy claim puts students at risk.

Illustrative example, Example Co. (fictional): "The coach listens as a child reads aloud and flags words to practise. It does not write or read for the child. Teachers see every session."

By stage. At Seed, publish the four sentences and offer settings that match district AI policies. At Series A–B, commission an independent test before making any performance claim.

The common mistake is treating integrity as a feature to sell. Treat it as a question to answer honestly.

Frequently asked questions

More in Industry Playbooks

Part of the Industry Playbooks hub - see all 8 resources on this topic.

• Playbook: Marketing AI Products Playbook
• Article: How to Market an AI Product
• Playbook: MedTech Marketing Playbook
• Article: How to Make Security a Selling Point

Also useful in Strategy & Positioning.