How to Start an Edtech Startup Without VC (2026 Playbook)

Short answer: To start an edtech startup without VC, build a narrow tool for one buyer who can pay quickly (an individual teacher, tutor, parent or adult learner), charge from the first term, and only then sell school or district licences to the places where teachers already use you. Learn FERPA, COPPA and the UK Children's code before your first school customer, build to WCAG 2.1 AA from day one, and plan your year around the school calendar rather than a fundraising calendar.

Edtech has a reputation as a venture game: big district contracts, long sales cycles, free products subsidised for years until they "monetise." Some of that is real. But a large part of education software is small, useful tools that teachers, tutors and learners pay for themselves, and those can be built and run on revenue. Below are the product shapes that work, who pays for each, what the privacy and accessibility rules actually say today, the distribution channels that cost little or nothing, three verified bootstrapped examples, a stage table with pass/fail gates, a 12-month plan built around the school year, a labelled worked example, common mistakes and a checklist.

Every price, rule, date and quote below was checked on the source's own page on 11 Nov 2026. The analysis in between is ours and is marked as such.

TL;DR#

• Decide who pays before you build. The user (a student) is rarely the payer. Teachers, parents and adult learners can buy with a card today; schools and districts buy through budgets, data agreements and procurement.
• Start teacher-paid, then go bottom-up into schools. Gimkit, for example, sells Pro to individual teachers at $14.99 a month or $59.88 a year, and Groups at "$650 per year for up to 20 teachers" or "$1000 per year for your entire school" (Gimkit Pro FAQ).
• Bootstrapped edtech is real. FeedbackPanda's co-founder writes: "We never raised any money either. We bootstrapped the whole business." (The Bootstrapped Founder). ClassHook's co-founder told EdWeek Market Brief its costs were "less than $1,000 a month to run the whole website" (EdWeek Market Brief).
• Privacy rules are a sales gate, not paperwork for later. FERPA's school official exception requires that a vendor "Is under the direct control of the agency or institution with respect to the use and maintenance of education records" (34 CFR 99.31). The amended COPPA Rule's compliance date was April 22, 2026 (Federal Register).
• Accessibility is now a public school requirement in the US. The DOJ rule sets WCAG 2.1 AA as the standard, with compliance dates extended to April 26, 2027 and April 26, 2028 (ADA.gov).
• Cheap distribution exists. Google Classroom add-ons go through Google Workspace Marketplace, ClassLink says "Partners pay nothing to integrate", and Moodle Marketplace lists "free or paid" plugins.

Disclosure: ZeroRaised publishes this guide and runs a launch site for bootstrapped products. ZeroRaised has no commercial relationship with any company, vendor or platform named here, and no links in this post are affiliate links. This is general information, not legal advice. Student privacy law depends on your product, your customers and where they are, so have a lawyer who works with education data review your terms and data agreements before you sign your first school.

Why edtech looks like a VC-only game (and when it is not)#

Founders usually give three reasons why edtech needs venture money: schools buy slowly, students do not pay, and the privacy rules are heavy. All three are true for some products. They are much less true for others.

It helps to split education software into two families:

1. Institution-first products. Platforms sold to districts, multi-academy trusts or universities from day one: a new learning management system, a student information system, an assessment platform for a whole state. These need procurement wins, many integrations and long pilots before revenue. They are capital-heavy because the sales cycle is long, not because the software is hard.
2. Individual-first products. Tools a single teacher, tutor, parent or learner can find, try and pay for this week: a quiz game, a feedback writer, a flashcard app, a lesson-clip library, a tutoring scheduler, a homeschool planner, a micro-course tool for a niche skill. Revenue starts with the first card payment. Schools can come later, pulled in by teachers who already use you.

Every bootstrapped edtech company we could verify for this guide started in the second family. That fits with the general pattern in our guide to funding a product without venture capital: customer revenue is the cheapest money there is, and it arrives fastest when the person using the product can also pay for it.

Our read: the trap is not choosing family one, it is drifting into it. "We will just add a district dashboard" sounds small, but it brings rostering, data agreements, admin roles, procurement and a sales cycle measured in terms instead of days. Keep the institution layer as something you add once teachers are asking for it.

Who pays vs who uses#

In most software, the user and the buyer are the same person or sit on the same team. In edtech they are often three different people: a student uses it, a teacher chooses it, and a school or parent pays. Your price, your sales motion and your privacy obligations all follow from which of these pays.

Our read: a bootstrapped edtech company usually needs one row where money moves in days. Pick your first payer from the top half of the table. Move to the bottom half once you have usage you can point to.

Product shapes that work without investors#

Here is how common edtech ideas line up against capital needs. The privacy column is a rough guide to what tends to come up, not a legal determination for your product.

If you are weighing an idea in this table, run it through the same niche tests we use in how to build a vertical SaaS without VC: a reachable community, a painful weekly task, and a buyer who already spends money on that task.

Three paths to revenue: teacher-paid, bottom-up, district#

Most bootstrapped edtech businesses use one or two of these in order.

1. Teacher-paid (B2C to educators)#

The teacher finds you through a colleague, a search, a social post or a marketplace, signs up free, hits a limit, and pays with their own card or a small classroom budget. This is the fastest route to revenue. Its weaknesses are price sensitivity and summer churn, because many teachers cancel when term ends.

Public examples of teacher-level pricing, checked on the vendors' own pages:

Note the shape: a cheap annual plan for a single teacher, then a flat department or school price that is easy for a head of department to approve. We could not load public pricing for Blooket, Wayground (formerly Quizizz) or Edpuzzle from this box today, so we have left them out rather than quote secondhand numbers.

2. Bottom-up into schools#

Once a few teachers in one school pay, you offer that school a site licence: everyone gets the paid plan, the school gets one invoice and an admin view. This is the move from the top half of the payer table to the bottom half without cold-calling districts. Your usage data is the sales pitch: "Eleven of your staff already use this, four of them pay personally."

What schools usually ask for at this point (our read, from the rules below): a data processing or privacy agreement, a list of sub-processors, single sign-on or rostering, an accessibility statement, and the ability to pay by invoice or purchase order. Brainscape's pricing page, for instance, lists "Request signed Digital Privacy Agreement" and "Enable Single Sign-On (SSO)" as features of its group licence (Brainscape pricing).

3. District or trust sales#

District and multi-school sales look much more like selling to government, because public school districts are public bodies with public money. Formal procurement, RFPs, security questionnaires and insurance requirements can all appear. We cover the mechanics in how to sell software to the government; the short version for edtech is to treat it as a stage-three channel that your teacher revenue pays for, not your first market.

Selling resources instead of software#

Many teacher-founders start by selling lesson resources before writing any code. Teachers Pay Teachers (owned by IXL Learning, per its page footer) currently offers two seller tiers (TPT Become a Seller):

Exclusive requires you to "Sell eligible digital products exclusively on TPT", and the page says "Premium features are now included with Exclusive membership." It also advertises an introductory offer to "Earn 80% on all sales made until January 1." Our read: resources are a cheap way to learn what teachers will pay for and to build an audience you can later sell software to. Think hard before choosing Exclusive if you plan to sell the same materials on your own site.

The school-year calendar#

Edtech has seasons, and a bootstrapped company feels them in cash flow. This calendar is our read for schools in the US and UK; confirm budget timing with the specific schools, districts or trusts you target.

Two practical rules follow. First, sell annual teacher plans, not just monthly, so summer churn does not wipe out your revenue. Second, release large changes in summer and keep the product stable during term: a teacher whose lesson breaks at 9am on a Tuesday does not renew.

Privacy rules you need to know#

This section covers the rules that most often come up when selling to schools and families. It is a starting map, not legal advice.

FERPA (US): the school official exception#

FERPA is the US federal law that protects students' education records held by schools. The part that matters to vendors is the "school official" exception, which lets a school disclose education records to an outside provider without parental consent in specific conditions. The regulation says a contractor "may be considered a school official" provided that the outside party (34 CFR 99.31(a)(1)(i)(B)):

1. "Performs an institutional service or function for which the agency or institution would otherwise use employees;"
2. "Is under the direct control of the agency or institution with respect to the use and maintenance of education records; and"
3. "Is subject to the requirements of § 99.33(a) governing the use and redisclosure of personally identifiable information from education records."

Our read: "direct control" is why schools ask you to sign their data agreement rather than accept your terms of service. In practice it means you use student data only to provide the service to that school, do not reuse it for your own purposes such as advertising, and delete or return it when the school asks. The US Department of Education's Student Privacy Policy Office hosts the official FERPA material.

COPPA (US): children under 13#

COPPA covers online services directed to children under 13, or that knowingly collect personal information from them. The FTC published amendments to the COPPA Rule in the Federal Register on April 22, 2025. The notice says: "Effective date: The amended Rule is effective June 23, 2025." and "Compliance date: Except with respect to Sec. 312.11(d)(1), (d)(4), and (g), regulated entities have until April 22, 2026 to comply." (Federal Register, 90 FR 16918). That compliance date has passed, so the amended rule applies now.

The notice describes the FTC as modifying operators' obligations around notices and "information security, deletion, and retention protocols." On edtech specifically, it says "the Commission is not finalizing the proposed amendments to the Rule related to ed tech" and "The Commission will continue to enforce COPPA in the ed tech context consistent with its existing guidance." The 2024 proposal it set aside would have meant "codifying a school authorization exception to obtaining verifiable parental consent."

Our read: if your product is used by under-13s in schools, do not assume a new codified school exception exists; there is not one in the amended rule. Read the full amended rule (or have counsel read it) before you collect any data from children, and design so you collect as little as possible: no student emails if a class code works, no free-text profile fields, no third-party ad or tracking scripts.

State student privacy laws and data agreements#

Many US states have their own student privacy laws, and many districts ask vendors to sign a standard data privacy agreement before any student data is shared. We could not load the official text of the state statutes from this box today, so we are not quoting them. Our read: expect to sign district or state templates rather than your own, keep a clean list of sub-processors, and never use student data for targeted advertising or sell it. Those are the commitments we would expect any school or district to ask for.

UK: the ICO Children's code and DfE guidance#

The ICO's Children's code (the Age Appropriate Design Code) "details fifteen standards" for online services likely to be accessed by children (ICO). It applies to "information society services likely to be accessed by children" in the UK, and "also covers not-for-profit apps, games and educational sites" (ICO: services covered).

The ICO has a page specifically on edtech (ICO: the Children's code and edtech). Key lines:

• "Edtech products and services that process children's personal information may be in scope of the Children's code."
• Schools themselves "are not Information Society Services (ISS) and are not in scope of the Children's code", but "The code also applies to edtech services provided to children through a school," "where the edtech provider influences the nature and purpose of the processing".
• The code falls away only where all of the page's listed criteria are met, including that "the edtech service is not accessed on a direct-to-consumer basis" and that the provider "acts solely on the instruction of the school".

The Department for Education's guidance on data protection in schools has a section on procuring edtech. It tells schools: "Make sure responsibilities are clearly assigned in a contract or data processing agreement." and "You should also consider if they use any other organisations as sub-processors to perform any element of the processing." It also notes "Schools are usually data controllers for the personal data they process." and "You must complete a DPIA when the processing of personal data is likely to result in a high risk".

Our read: the teacher-paid route has a privacy consequence in the UK. If teachers sign up directly and you decide how the data is used, you are likely acting as a controller offering a service children access, so the Children's code is likely to apply. If you sell only to schools and act strictly on their instructions, you may fall outside it. Many bootstrapped tools do both, so design for the code from the start: high privacy by default, no nudges, minimal data.

App stores: kids category rules#

If you ship a mobile app aimed at children, Apple's App Review Guidelines section 1.3 applies to the Kids Category. It says apps "must not include links out of the app, purchasing opportunities, or other distractions to kids", that they "should not include third-party analytics or third-party advertising", and that "Kids Category apps may not send personally identifiable information or device information to third parties." (Apple App Review Guidelines). Our read: this rules out a lot of standard indie analytics and growth tooling. Plan your measurement around first-party, aggregate data.

Accessibility: WCAG 2.1 AA is a sales requirement#

The US Department of Justice's rule under Title II of the ADA sets "Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA" as the technical standard for state and local governments' web content and mobile apps, and the fact sheet lists "Public schools, community colleges, and public universities" as examples of covered entities (ADA.gov fact sheet).

The compliance dates have moved. The page says: "On April 20, 2026, the Federal Register published the Department's Interim Final Rule (IFR) extending the compliance date for State and local government entities with a total population of 50,000 or more to April 26, 2027." For entities under 50,000 and special district governments, the date is "extended to April 26, 2028." It also notes "A school district is not a special district government."

The rule applies to public entities, not directly to vendors. But public schools are responsible for the content and apps they provide, so they will increasingly ask vendors for WCAG 2.1 AA conformance. If you sell in the EU too, read our guide to the European Accessibility Act for SaaS.

Our read: accessibility is far cheaper to build in than to retrofit. Use semantic HTML, keyboard navigation, visible focus, captions on any video, sufficient contrast and labelled form fields from your first version, and test with a screen reader before you pitch your first school.

Distribution and integrations that cost little#

You do not need a sales team to reach teachers. These are the channels and integrations worth knowing, with what each official source says today.

Google Classroom add-ons#

Google's developer docs say "Developers create add-on applications distributed through Google Workspace Marketplace." Teachers "can install applications to their own Google Workspace for Education account", and "Google Workspace administrators can install applications for their teacher users." The licence catch: "Classroom add-ons are available to all teachers with Teaching & Learning or Plus Google Workspace for Education licenses." (Google for Developers). Google Workspace for Education Fundamentals "is available for no charge for qualifying institutions" (Google for Education), but add-ons need the paid tiers.

Our read: an add-on is a strong channel in schools that already pay for those tiers, but do not make it your only door. A simple "share to Classroom" link or an assignment URL reaches every Classroom teacher, whatever their licence.

LTI 1.3 for learning management systems#

1EdTech describes LTI as "a technical standard (not a product) used to connect learning tools" with an institution's learning environment, and says "The current version, LTI 1.3, addresses education security requirements and provides a structure for additional services." (1EdTech LTI). Its TrustEd Apps Directory "is the official listing of products that have achieved 1EdTech interoperability certification." Moodle's directory has moved: "Moodle Marketplace is the new home for Moodle plugins and integrations, replacing the Plugins Directory." (Moodle Marketplace). Instructure says its partner programme lets you "Reach over 30 million educators and learners" (Instructure partners).

Our read: build LTI 1.3 once a paying school asks for it, not before. For higher education and corporate training it is often required; for a teacher tool in its first term it is usually a distraction.

Rostering: Clever and ClassLink#

Rostering means a school's class lists flow into your app automatically, and students sign in with school single sign-on. US districts often expect it for school-wide licences. The two programmes are priced very differently:

• Clever: "Application partners pay to roster their apps through Clever using Secure Sync," with a custom quote, and a starter pack where "you pay a one-time integration fee, build your integration, and your first five schools are included." Clever also says "It is against our terms of service for application partners to levy fees on schools" for rostering through Clever (Clever pricing, Clever partners).
• ClassLink: "Partners pay nothing to integrate with our single sign-on and rostering platforms." (ClassLink partners).

Our read: add rostering when your first school licence depends on it, and price your school plan so the integration cost is covered.

Real bootstrapped edtech examples#

We looked for edtech companies whose funding story is confirmed by the founders themselves. Several popular names did not make the list because we could not verify their funding on a primary source today. These three we could.

FeedbackPanda: sold directly to teachers#

FeedbackPanda helped online English teachers write student feedback. Co-founder Arvid Kahl describes how it started: his partner Danielle wrote feedback for kids she taught, and "we started talking about building a little software tool that would do that work for her." He writes: "We never raised any money either. We bootstrapped the whole business." and "We never hired a single employee." The company had "over five thousand customers and still require no employees," and they "managed to run, grow, and sell the company within two years after building that little software tool," selling to SureSwift Capital (The Bootstrapped Founder).

On the Startups For the Rest of Us podcast, the founders explained the go-to-market: "We sold to the teachers directly." The episode introduces it as a business "they bootstrapped to $55k MRR with no outside funding and no employees" (Startups For the Rest of Us, episode 492).

Lesson: a teacher-paid tool that saves hours of weekly drudgery can grow without any school sales at all, especially when the founders are part of the community they sell to.

ClassHook: a lean, bootstrapped content library#

ClassHook gives teachers short clips from TV shows and films to open lessons. In a November 2024 interview with EdWeek Market Brief, co-founder and CEO Alex Deeb said: "We were bootstrapped, so we didn't grow quite as fast as one of those venture-backed companies." Asked how much outside money they took, he said "Very little", explaining it was "only $10,000 that we received from [Impact Ventures'] accelerator." On costs: "Our costs were less than $1,000 a month to run the whole website, just for its operations". ClickView acquired ClassHook in August 2024, and by then it had "more than 7,400 videos." (EdWeek Market Brief).

Lesson: low fixed costs buy you time. A small team with sub-$1,000 operating costs can keep going through slow school sales cycles that would sink a company burning investor money.

Anki: free desktop app, paid mobile app#

Anki is a spaced-repetition flashcard app used heavily by language learners and medical students. Its site says "The free computer version is available for all major platforms." and "AnkiMobile is the official iOS app and all purchases help fund Anki's development." (Anki). The Anki FAQ explains the logic in the developer's own words: "AnkiMobile is my way of putting food on the table and supporting future development." (Anki FAQ). AnkiMobile is listed at $24.99 on the US App Store, and its listing says "Your purchase directly supports the open-source project that keeps Anki desktop free for everyone." (App Store).

Lesson: for adult learners, a generous free product plus one well-chosen paid surface (here, the iOS app) can fund development for years, without ads or investors.

Validate before you build#

Edtech ideas are easy to love and hard to sell, because teachers are polite. They will tell you an idea is great and then never sign up. Use the validation steps in how to validate a SaaS idea before building, with three edtech-specific changes (our read):

1. Ask about last week, not about the idea. "Show me how you wrote your last batch of report comments" beats "Would you use an AI report comment tool?"
2. Test willingness to pay with the teacher's own money. Offer a paid pilot or a pre-sold annual plan. If teachers will only use it if the school pays, you have learned your real buyer, and your sales cycle just got longer.
3. Check the data path. Before building, write down what student data the product needs. If the answer is "names, emails and work samples of 11-year-olds", your legal work starts before your first line of code.

Pilots with a pass/fail line#

Schools love pilots, and bootstrappers can lose a whole year to them. A pilot is only useful if both sides agree up front what success means and what happens next.

A pilot agreement we would use (our template, not legal language):

• Length: one half-term or six to eight weeks, not "the rest of the year."
• Scope: named teachers and classes, a named school contact.
• Success line: written down, measurable, decided before you start. For example: "At least 8 of 12 teachers use it in at least 3 lessons each, and the teachers' average rating is 4 out of 5 or higher."
• Next step if it passes: the price and the decision date for a paid school licence.
• Next step if it fails: you both stop, and you get a 20-minute debrief.
• Paid or free: a small paid pilot (even a token amount) filters out schools with no budget.
• Data: the data agreement is signed before any student data enters the product.

Our read: a pilot with no success line and no price is a free trial that can last forever. Never run one.

Stage table with gates#

This is our stage model for a bootstrapped edtech company. Do not move to the next stage until you pass the gate.

A 12-month plan aligned to the school year#

This plan assumes you start in January and target K-12 teachers in the US or UK. Shift it if you serve adult learners or corporate training, who do not follow the school calendar.

If you sell in the US K-12 market and want non-dilutive money for research-heavy products, the Department of Education's IES SBIR programme "provides up to $1.25M in funding in 2 phases": "Phase I for $250,000 for 9 months" for prototypes and "Phase II for $1,000,000 for 2 years" for full development, with solicitations "released annually" (IES SBIR). Our guide to startup grants for bootstrapped founders covers SBIR more broadly.

Worked example: a report-comment tool for teachers#

This is an illustrative example with our own assumptions, not data from any real company.

Product: a tool that helps secondary teachers write end-of-term report comments from a rubric. No student names are needed: teachers paste or type their own notes and get suggested comments.

Pricing (our assumptions): $7 a month or $60 a year per teacher, and a school licence at $1,200 a year for up to 40 teachers.

Costs (our assumptions): $250 a month for hosting, email, AI usage, payments overhead and tools; $1,500 one-off for a lawyer to review the privacy notice and data processing terms; $1,000 one-off for an accessibility review.

What this shows (our read): a year-one edtech tool will not replace a salary on its own, but it can pay for itself and fund the second year. The important lines are the annual teacher plans and the school licences, because they survive the summer. If every teacher were monthly and half cancelled for July and August, monthly revenue would dip hard just as you need to invest in back-to-school.

Common mistakes#

1. Building for the district on day one. You spend a year on rostering, admin dashboards and RFPs before anyone pays.
2. Free for teachers forever, "schools will pay later." Without a paid teacher tier, you have no revenue and no proof that anyone values the product enough to pay.
3. Collecting student data you do not need. Every student email, name and free-text field adds privacy obligations. Class codes and teacher-entered nicknames often do the job.
4. Pilots with no success line. See above. Write it down before you start.
5. Ignoring the calendar. Launching in June, pushing a big redesign in October, or sending school sales emails during exam season.
6. Third-party trackers in a kids' product. Ad pixels and session-replay scripts can conflict with COPPA, the Children's code and Apple's Kids Category rules.
7. Accessibility as an afterthought. Public schools now have WCAG 2.1 AA deadlines, and an inaccessible tool can fail a school review late in the sale.
8. Selling only monthly plans. Summer churn quietly halves your revenue.
9. Promising outcomes you cannot prove. "Raises test scores by 20%" invites questions you cannot answer. Describe what the tool does and what teachers say.

Checklist before your first school customer#

• One named first payer (teacher, tutor, parent, learner or school) and a price for them
• Annual plan offered alongside monthly
• A written list of every piece of student data you collect and why
• Privacy notice and data processing terms reviewed by a lawyer
• Sub-processor list (hosting, email, analytics, AI provider, payments)
• No third-party ad or tracking scripts in student-facing pages
• COPPA review if under-13s may use the product
• Children's code review if you serve UK children directly
• WCAG 2.1 AA check and a short accessibility statement
• Data deletion process when a school leaves
• School licence price, invoice and purchase order support
• Pilot template with a written success line
• Launch plan for the start of the school year

Frequently asked questions#

Can you start an edtech startup without VC funding?#

Yes, if you sell to a buyer who can pay quickly. FeedbackPanda sold a feedback tool directly to online English teachers, never raised money, never hired an employee and was sold to SureSwift Capital within two years. ClassHook, a library of TV and film clips for lessons, was bootstrapped with only $10,000 from an accelerator and ran on under $1,000 a month before ClickView acquired it in 2024. Anki funds its free, open source desktop app through sales of its paid iOS app.

Who should an edtech startup sell to first: teachers, schools or parents?#

Our read: start with whoever can pay with a card this month. That is usually individual teachers, tutors, parents or adult learners. Schools and districts pay more per deal but need budgets, data privacy agreements, rostering and sometimes procurement. Teacher-paid revenue funds the product while you collect the usage and champions that make a school licence an easy yes later.

Do I need to comply with FERPA and COPPA?#

If you serve US schools, assume both will come up. FERPA governs schools, but a school can share education records with you as a school official only if you perform a service it would otherwise use employees for, are under its direct control for use and maintenance of the records, and follow FERPA's re-disclosure limits. COPPA applies to online services directed to children under 13 or with actual knowledge they collect from them; the amended rule's compliance date was April 22, 2026. This is not legal advice.

How much does it cost to start an edtech startup?#

A software-only teacher tool can start for well under $1,000 a month; ClassHook's founder said costs were under $1,000 a month to run the whole website. Distribution can be cheap too: ClassLink says partners pay nothing to integrate, Moodle Marketplace lists free or paid plugins, and selling resources on Teachers Pay Teachers starts with a $29 one-time Basic fee. Clever charges application partners for rostering on a custom quote. Budget extra for legal review of your privacy terms and an accessibility audit.

When do schools buy edtech?#

Our read: schools commit money once or twice a year and use the summer to set up for the new school year. Teachers try new tools during the school year, budgets for the next year are usually discussed in spring, and contracts and rostering are set up before term starts. Plan teacher acquisition for term time and school sales for spring and summer, and confirm the budget calendar with each target district or trust.

Launch your edtech product#

ZeroRaised is a launch directory for products built without institutional VC. When your teacher tool is ready for the back-to-school rush, run through our product launch checklist for bootstrapped makers, then submit your product for free. For more playbooks on building and funding without investors, join the ZeroRaised newsletter.

Sources#

• 34 CFR 99.31, FERPA disclosure conditions (Cornell LII), last checked 11 Nov 2026
• US Department of Education, Student Privacy Policy Office: FERPA, last checked 11 Nov 2026
• Federal Register, Children's Online Privacy Protection Rule, 90 FR 16918 (April 22, 2025), last checked 11 Nov 2026
• ICO, Children's code guidance and resources, last checked 11 Nov 2026
• ICO, Services covered by this code, last checked 11 Nov 2026
• ICO, The Children's code and education technologies (edtech), last checked 11 Nov 2026
• DfE, Data protection in schools, last checked 11 Nov 2026
• DfE, Data protection in schools: procuring educational technology, last checked 11 Nov 2026
• ADA.gov, Fact sheet: ADA Title II web and mobile accessibility rule, last checked 11 Nov 2026
• Apple App Review Guidelines, 1.3 Kids Category, last checked 11 Nov 2026
• IES SBIR, last checked 11 Nov 2026
• 1EdTech, Learning Tools Interoperability, last checked 11 Nov 2026
• Moodle Marketplace, last checked 11 Nov 2026
• Instructure Partner Program, last checked 11 Nov 2026
• Google for Developers, Classroom add-ons, last checked 11 Nov 2026
• Google for Education, compare Workspace for Education editions, last checked 11 Nov 2026
• Clever pricing, last checked 11 Nov 2026
• Clever partners, last checked 11 Nov 2026
• ClassLink partners, last checked 11 Nov 2026
• Teachers Pay Teachers, Become a Seller, last checked 11 Nov 2026
• Gimkit Pro FAQ, last checked 11 Nov 2026
• Brainscape pricing, last checked 11 Nov 2026
• Arvid Kahl, From founding to exit in two years: the FeedbackPanda story, last checked 11 Nov 2026
• Startups For the Rest of Us, episode 492, last checked 11 Nov 2026
• EdWeek Market Brief, Why an Ed-Tech Company Founder Chose Bootstrapping Over Venture Capital (Nov 15, 2024), last checked 11 Nov 2026
• Anki, last checked 11 Nov 2026
• Anki FAQ: Why does AnkiMobile cost more than a typical mobile app?, last checked 11 Nov 2026
• AnkiMobile Flashcards on the App Store, last checked 11 Nov 2026