Verity for EdTech
EdTech spends heavily to produce content and is judged on whether learners finish it. Verity records the production cost and the completion it produced.
Verity runs the company. Your learning platform stays where it is.
Verity / Company
LiveActive learners
18,400
Completion rate
31%
Content in production
14 courses
Institutional contracts
22
Needs attention
Illustrative figures. Verity shows your own company in this shape.
How the business runs
An EdTech business spends heavily up front to produce a course and then earns from learners who enrol in it. Enrolment is the number that gets reported and completion is the number that determines renewal, referral and institutional confidence — and the gap between them is enormous. A completion rate spanning eight to seventy-four percent across courses on the same platform is a content problem, not a platform one.
That makes course-level economics the central question: what a course cost to produce, how many learners it attracted, how many finished, and what support burden it generated. Most EdTech companies measure the first two.
The second characteristic is content production, which behaves like any other project business — briefs, subject experts, production, review and release dates that slip against marketing commitments already made.
The third is support load, which concentrates on specific courses and is almost always a symptom of the content rather than of the learners.
The fourth is institutional contracts, where the buyer is an organisation with completion expectations and renewal dates, and evidence is required.
Verity records production cost and progress, completion by course and cohort, support load by course and institutional delivery.
What Verity calls these things
What gets in the way
EdTech difficulties come from production cost committed ahead of demand and completion nobody attributes.
Completion varies enormously and is not attributed
One course completes at eight percent and another at seventy-four on the same platform, and the difference is treated as learner behaviour.
In Verity Completion is measured per course and cohort against production cost and content structure.
Production slips against marketing commitments
A course release date is committed publicly and the production runs late.
In Verity Production is work with stages, owners and a release date, so slippage is visible before the commitment is broken.
Support load reveals content problems
Tickets concentrate on specific courses and are handled as support rather than as content feedback.
In Verity Support is recorded against the course and module, so concentration becomes a content decision.
Course economics are never assembled
Production cost, enrolment, completion and support burden exist in four places.
In Verity All four attach to the course, so contribution per course is calculable.
Institutional renewals need evidence
An organisation renews on completion and outcome evidence that is assembled by hand each time.
In Verity Cohort completion and progress are records, so renewal evidence is an extract.
Content ages without review
Courses remain live long after their material has dated, and nobody owns the review.
In Verity Courses carry review dates and performance, so refresh decisions are prompted.
The complete system
One system across production, completion, support and contracts.
Records
Each course carries its modules, production cost, release date, version, review date and performance.
Why it matters here The course is the unit of investment and of completion.
In practice Completion from eight to seventy-four percent across courses on the same platform.
Work
Production is work with stages, subject experts, producers, reviewers, cost and a release date.
Why it matters here Content production is a project business inside the company.
In practice Five courses past their release date with enrolment commitments made.
Relationships
Learners and institutional accounts carry enrolment, progress, completion, support history and contract terms.
Why it matters here Institutional buyers renew on completion evidence rather than on enrolment.
In practice Cohort completion evidence assembled for a renewal.
Workflows
Support tickets carry the course and module, and concentration raises content review.
Why it matters here Support load is content feedback arriving through the wrong channel.
In practice Support concentrated on four courses, raised as content review.
People
Contributors are modelled once with effort recorded against production.
Why it matters here Production cost is mostly people, including external subject experts.
In practice Production cost per course including external contributor effort.
Control
One permission model and one audit trail, with institutional contracts, licence terms and renewals recorded.
Why it matters here Institutional terms differ and renewals need evidence.
In practice Six contracts up for renewal with completion evidence attached.
Reports and analytics
Completion by course and cohort, production cost against enrolment and completion, support load by course, and contract renewal evidence come from the records.
Why it matters here Course contribution requires all four together and is usually assembled from none of them.
In practice Contribution per course after production and support cost.
Verity AI
Verity AI answers from your own course, production, learner and support records, respects permissions, and can create assigned follow-ups.
Why it matters here The valuable questions cross content, learners and support.
In practice "Which courses have the worst completion and the highest support load?" returns the overlap.
Communication
Reporting, feedback and escalations attach to the institution or course they concern.
Why it matters here Institutional relationships run on periodic evidence.
In practice Cohort progress reporting issued and recorded against the contract.
Orders
Enrolments, licence allocations and invoices are recorded against learners and institutions.
Why it matters here Institutional licensing and individual enrolment behave differently.
In practice Licences allocated against a contract with utilisation tracked.
Locations
Production teams and content units roll into the company with reporting following the same structure.
Why it matters here Production quality and completion vary by team.
In practice Completion by producing team and subject area.
Suppliers
External contributors carry engagements, cost, delivery reliability and rights granted.
Why it matters here Much EdTech content is produced with external subject experts under licence.
In practice Content rights and their scope recorded against the course.
Work in motion
These already happen. Recorded against the course, contribution becomes calculable.
Recording production cost against the course is what makes contribution calculable later.
Drop points within a course are content feedback of the most direct kind.
A module generating support is usually a module that needs rewriting.
Renewal evidence should be an extract rather than a construction.
Courses age and nobody owns the review unless it has a date.
Verity AI
Verity AI reads the same course, production, learner and support records the company creates as it operates. It answers from your own catalogue, respects permissions, and can turn an answer into content reviews.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the company’s own records at the point the condition is met.
When
A production stage passes its date
When
Support concentrates on a module
When
A cohort stalls at a module
When
An institutional contract approaches renewal
When
A course passes its review date
What you can understand
Course-level economics rather than platform-level totals.
Verity records the company around the product. Your learning platform and content delivery continue as they are.
One system, different ways of seeing it
Everyone works from the same records.
Founder
Which courses actually work?
Contribution per course after production and support, completion by course, institutional renewals.
Content lead
What needs producing or fixing?
Production stages against release dates, support concentration by module, courses past review date.
Learning or success lead
Where are cohorts stalling?
Drop points within courses, cohort completion, intervention outcomes, institutional progress.
Support lead
Where is the load coming from?
Tickets by course and module, reasons, effect of revisions, cost to serve.
Where it is used
Production cost, enrolment, completion and support load assembled per course, which is the only honest measure of whether a course works.
Content production as staged work, so slippage is visible before a public commitment is broken.
Tickets recorded against course and module, so concentration becomes a content decision rather than a support burden.
Progress recorded through modules, so where learners stop is a specific module rather than a general completion rate.
Cohort completion and progress as records, so renewal evidence is an extract rather than a construction.
Review dates and performance on the course, so ageing content is refreshed rather than left live.
Plain-language questions spanning production, completion and support, with reviews raised in the same step.
Getting there
Your learning platform and content delivery continue and are mapped during implementation. Courses with production cost, cohorts and completion history, institutional contracts and support history are brought across.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
No. The platform, content delivery and learner experience continue and are mapped during implementation. Verity records the company around them — production cost, course economics, completion, support load and institutional contracts.
Verity AI answers questions from your own course, production, learner and support records: which courses have the worst completion and the highest support load, which are past their release date, what contribution looks like per course, where learners drop out. Each answer can become a content review.
Because enrolment is the number that gets reported and completion is the number that renews, refers and satisfies institutional buyers. A completion range from eight to seventy-four percent across courses on one platform is a content signal, not a learner one.
Production is work with stages, subject experts, producers, cost and a release date, so slippage is visible before a marketing commitment is broken and cost is recorded against the course it produced.
Because it concentrates on specific modules. A module generating disproportionate support is usually a module that needs rewriting, and treating the tickets as a support burden fixes nothing.
Cohort completion and progress are records, so the evidence an institutional buyer wants at renewal is an extract rather than something assembled by hand each time.
Courses carry review dates and performance, so declining completion on ageing content prompts a refresh decision rather than remaining live indefinitely.
About four weeks: discovery and mapping of course structures, production process and contract terms, configuration, migration of courses, cohorts and contracts, then an ongoing operations partnership.
It usually reorders which courses look successful. Tell us how production cost is tracked today.