How to Sell Online Courses to Schools and Universities
Selling online courses to schools and universities is not a bigger version of selling to individuals — it is a different transaction entirely. You are not persuading a buyer; you are entering a procurement process where a committee decides, the money moves on a fiscal calendar, and the deal is won or lost on compliance and integration long before anyone watches your first lesson. This guide maps how institutions actually buy, what they screen for, and who should pursue this channel — and who should walk away from it.
The institutional buyer is not the corporate buyer
Three very different customers can all “buy your course,” and treating them the same is the most expensive mistake creators make. A consumer buys one seat, on impulse, with a card. A company buys workforce training on its own timeline and budget, often quickly, to close a skills gap — that is the B2B motion covered in our corporate licensing playbook. A school district or university buys through procurement: public or grant money, spending rules, a committee, and an academic calendar that dictates when anything can be signed.
The tell is your own instinct. If your plan is a landing page, an email sequence and a fast close, you are describing the consumer or corporate motion, not this one. Institutions rarely move on marketing. They move on evidence, compliance sign-off and a purchase order — and they move slowly. Everything below assumes you are comfortable with that trade: longer cycles and heavier requirements in exchange for larger, stickier, multi-year contracts.
How schools and universities actually buy: POs, RFPs and the academic calendar
Institutions almost never pay by card. They issue a purchase order and pay against an invoice on net terms, typically net-30 or net-60. If you cannot invoice and wait, you cannot sell here. Above a spending threshold — which varies by district and state — the purchase must go out to bid as a Request for Proposal (RFP), a formal reverse-auction process in which you submit an original proposal, not just a price. Federal and many state buyers run this under strict acquisition rules, so the RFP typically precedes any purchase order.
The calendar is just as decisive as the paperwork. Academic budgets are usually set in the spring for the following academic year, and unspent departmental money often has to be committed before the fiscal year closes. That creates real buying windows and real dead zones; a brilliant pitch delivered the week after budgets lock will wait nine months regardless of merit. Expect a committee, too: a department chair or program director champions the purchase, an instructional designer evaluates fit, procurement runs the paperwork, and IT or legal clears security and privacy. Your job is to make every one of those people’s review easy.
The compliance gate: FERPA, accessibility and student data
This is where most independent creators are quietly filtered out, usually without ever hearing why. Under the Family Educational Rights and Privacy Act (FERPA), a federal law codified at 20 U.S.C. § 1232g, students and parents have rights over education records and personally identifiable information. Those rights transfer from the parent to the student once the student turns 18 or enrolls in a postsecondary institution — which means selling into K-12 schools, where the learners are minors and parents hold the rights, carries a higher bar than selling to a university. If your platform touches student records as a vendor, you inherit obligations for how that data is stored, shared and deleted.
Accessibility is the second gate, and it is not optional for public institutions. Section 508 requires that electronic content agencies develop, procure or use be accessible, and its 2017 refresh harmonized those requirements with the W3C’s WCAG standard. In practice a course that lacks captions, transcripts, keyboard navigation or sufficient color contrast can fail a procurement accessibility review and be rejected before content is ever evaluated on quality. Build accessibility in from the start — our guide to online course accessibility covers the concrete checklist — and treat it as a purchasing requirement, not a nice-to-have.
Packaging for institutions: seat licensing, integration and pilots
Institutions do not buy a seat; they buy a cohort, a classroom, a department or a whole campus. Price and package accordingly: per-seat volume tiers or a flat site license, with a clear mechanism to provision and reclaim seats each term. Consumer pricing logic does not transfer — anchor your model on the value of the deal, not a single learner (our note on how to price an online course is a useful starting point before you build institutional tiers).
Integration is the other differentiator. Universities want content that plugs into their learning-management and student-information systems — single sign-on, roster sync and, ideally, grade or completion pass-back — so faculty are not managing a second login. Where relevant, map your course to credit hours or continuing-education units so it fits an existing catalog. And almost every institutional deal starts with a paid pilot: one department, one term, one measured cohort. Nail the pilot, document the outcomes, and expansion becomes an internal decision rather than another sale.
A realistic timeline from first contact to signed deal
The single most useful thing you can internalize is how long this takes and who controls each stage. The table below sketches a typical single-department deal; a district-wide or campus-wide agreement stretches every row.
| Stage | Who is involved | Typical duration | What moves it forward |
|---|---|---|---|
| First contact & interest | Department chair / instructional designer | 2–6 weeks | A pilot proposal, not a sales pitch |
| Pilot & evaluation | Faculty plus a small cohort | One term (8–16 weeks) | Documented learning outcomes |
| Compliance & security review | Procurement, IT, legal | 3–8 weeks | FERPA and accessibility (WCAG/508) sign-off |
| Procurement / RFP / PO | Procurement office | 4–12 weeks | An open budget window and a purchase order |
| Rollout & renewal | Department plus your support | Ongoing | Seat usage and completion data |
Who should sell to schools and universities — and who should not
This channel is for you if your content can survive an accreditation-grade and accessibility review, you have the patience for one-to-two-term cycles, and you are willing to handle purchase orders, security questionnaires and system integration. It rewards durable, curriculum-shaped subjects — the things a department will teach for years — far more than fast-moving trend topics. If you can support an institution after the sale and grow one pilot into a renewable license, the economics are excellent.
It is not for you if you want a fast, self-serve, marketing-led close; that is the consumer or corporate route, and the B2B licensing playbook will return more per hour. Walk away, too, if your course cannot pass accessibility or privacy scrutiny, if you have no capacity to support a client through onboarding and renewal, or if your content is low-ticket and ephemeral. Selling to institutions is a deliberate business model, not a way to move a few more units — choose it on purpose.
Win the review before you pitch the course
The institutions that say yes are rarely the ones you sold hardest. They are the ones whose procurement officer, IT reviewer and accessibility checker found nothing to object to. So build for that reviewer first: accessible content, clean data handling, a pilot you can measure, and pricing that scales by seat. Do that, and the academic calendar — not your funnel — will close the deal for you.
Frequently asked questions
Is selling to a university the same as selling to a company?
No. Companies buy workforce training on their own budget and timeline and can move quickly; schools and universities buy through procurement, on the academic and fiscal calendar, under FERPA and accessibility rules, usually via a purchase order. The buyers, the paperwork and the pace are different — see the corporate B2B route if speed matters more to you than institutional scale.
Do I need to be FERPA compliant to sell to a school or university?
If you handle student education records or personally identifiable information as a vendor, you take on obligations under FERPA. The bar is higher for K-12 schools, where learners are minors and parents hold the rights until the student turns 18 or enrolls in a postsecondary institution. Clarify early what student data your platform stores and how it is protected.
How do institutions pay — can I just take a card?
Usually not. Institutions pay against a purchase order on net terms after you invoice, and larger deals often follow a formal RFP. You need to be set up to issue invoices and wait for payment; a card-only checkout is a common reason a deal stalls in procurement.
