The demo tells you about the content. The licence tells you about the business.
Most teams evaluating white-label K-12 content spend ninety percent of their time watching sample videos and ten percent reading the licence. The samples tell you whether the content is good; the licence tells you whether the deal is good — and a strong library on weak terms can quietly become the most expensive line item in your business two years from now.
This checklist is written for anyone evaluating any provider, not just us. Every point is a question you can put to a vendor in writing before you sign. Clear answers to all ten suggest a serious licensor; dodging more than two or three is information in itself.
1–2. Rights scope: what exactly are you allowed to do with it?
"White-label licence" is not a standard legal term — it means whatever the agreement says it means. The first thing to pin down is the scope of rights, and there are four distinct levels: the right to host the content on your own platform, the right to integrate it into your app or LMS, the right to distribute it to your customers (schools, students, franchisees), and the right to resell it — that is, to charge your customers money for access under your brand.
These are not the same thing, and agreements frequently grant the first two while staying silent on the last two. If your business model involves selling subscriptions, selling to schools, or supplying dealers, the word "resell" or "commercial distribution" needs to appear explicitly in the grant clause — and you should ask the vendor to point to where.
The second scope question is territory and segment. Some licences are limited to one country, one state board, or one delivery channel (app only, no smart-class hardware). If you plan to expand, make sure the licence does not quietly expire at the border of your first market.
3–4. Perpetuity vs renewal — and the per-student fee trap
The single biggest structural difference between licences is whether the grant is perpetual (a one-time fee, rights that survive forever) or term-based (an annual licence that must be renewed). Neither is inherently wrong, but they suit different businesses. A term licence means the vendor can reprice you at every renewal — and once your platform, your marketing, and your customer base are built on their content, your negotiating position at renewal is weak. If you accept a term licence, cap renewal pricing in writing now.
The related trap is per-student or per-seat pricing. It looks cheap on day one — a few rupees per learner sounds trivial next to a lakh-scale one-time fee. But per-student pricing means your content cost scales exactly as fast as your success does, and it converts your best growth months into the vendor’s best invoicing months. Model the fee at your target scale, not your current scale, before comparing offers. A one-time perpetual licence (the model we use at Edupotion — see edupotion.com/pricing) trades a larger upfront number for a marginal content cost of zero; run both numbers at your target scale before deciding.
Also check what happens to already-delivered content if either side terminates. In a well-drafted perpetual licence, delivered content stays yours. In some term licences, termination requires you to delete everything — including from customers you have already sold to. That clause deserves a lawyer’s attention.
5–6. Rebranding depth, and formats that actually work in your product
Vendors use "white-label" to describe everything from "we will put your logo in the corner" to "your brand appears everywhere and ours appears nowhere." Ask precisely what gets rebranded: the video intro and outro, the watermark, the PDFs and notes, the MCQ interfaces, the thumbnails, the file names. Then ask the sharper question: does the vendor’s name appear anywhere in the delivered assets — credits, metadata, embedded URLs? For a genuine white-label business, the answer needs to be no. Ask for one fully rebranded sample video and one rebranded PDF as part of the evaluation; a vendor with a real rebranding pipeline can produce these quickly.
On formats, get specific about resolution (1080p should be the floor for new licensing), codecs and containers (MP4/H.264 remains the safest default for web and app delivery), and — easy to forget — captions. Time-synced caption files (SRT or VTT) matter for accessibility, for sound-off viewing on phones, and for search indexing inside your platform. If the library is bilingual, confirm captions exist for both audio tracks, not just one. Also confirm how the library is delivered and organised: a clean folder structure mapped to class, subject, and chapter saves your team weeks of tagging work.
7–8. Source files and curriculum mapping
Rendered MP4s are enough if you only intend to play the content as-is. The moment you want to translate it into another language, adapt it to a state board, re-edit segments, or change the on-screen text, you need the editable source projects — animation files, voice-over stems, graphics assets. Most vendors either do not offer source files at all or offer them as a separate, higher tier. Neither is a problem in itself — the problem is discovering that after you have committed. Ask now: are source files available, at what price, in what software format, and with what rights attached (can you create and sell derivative versions)?
Curriculum mapping is the other unglamorous item that determines whether the library is usable. "Aligned to CBSE" can mean mapped chapter-by-chapter to the current NCERT textbooks, or it can mean loosely organised by topic in an order that matches no actual textbook. Ask for the mapping document itself — a spreadsheet listing every asset against class, subject, and chapter — and spot-check one class-subject combination against the current NCERT book. Ten minutes with the Class 8 Science contents page will tell you more than any brochure.
9–10. Updates, support, and the red flags worth walking away from
Syllabi change. NCERT rationalises chapters, boards reshuffle topics, textbooks get revised. Your licence should say what happens then: are updates included for some period, offered at a discount, or sold as a fresh licence? There is no single right answer — a one-time perpetual licence cannot reasonably promise free updates forever — but the policy should be written down before you sign, not improvised after the next syllabus revision.
Support is the quieter clause. Agree in writing on a named contact, a response-time expectation for defective files (a corrupted video, a missing caption file, a wrong answer key), and a replacement commitment. You are not asking for a call centre; you are asking for a promise that broken deliverables get fixed.
Finally, the red flags. Walk away, or at least slow down, when you see: a vendor who will not put resale rights in writing; pricing that only exists verbally; refusal to show a full asset list or mapping document before payment; "unlimited everything" promises with a two-page agreement; no sample deliverables in final rebranded form; and pressure to close before you have had the agreement reviewed. None of these guarantees a bad vendor — but each one shifts the burden of proof onto them.
How to use this checklist
Turn the ten points into an email and send the same email to every vendor on your shortlist: rights scope, territory, perpetuity or term, per-student fees, rebranding depth, formats and captions, source files, curriculum mapping, update policy, and support terms. Written answers make providers directly comparable — and become part of the record if a dispute ever arises.
Then weight the answers by your business model. A school running its own smart classes cares most about mapping, formats, and support. A publisher planning translations cares most about source files. An EdTech company selling subscriptions cares most about resale rights and fee structure. The best licence is not the longest or the cheapest — it is the one whose terms match what you are actually going to do with the content. If you want to see how we answer these ten questions ourselves, the details are at edupotion.com/white-label-k12-content.