AI for education providers
Instructors teach, the admin runs itself, every learner gets a tutor's attention. 5x ROI in 30 days, or we work free.
- Private colleges
- Tutoring networks
- Corporate training
- Continuing education
- Language schools
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
Proof, honestly
No published education case study yet, and we say so. Founding clients get priority scheduling, direct founder involvement, and a co-published case study once the numbers are real. The 5x ROI guarantee applies from day one.
We guarantee 5x ROI inside 30 days of deployment, in writing, measured against a baseline you sign before we build. If the system misses the bar, we keep working for free until it clears.
Instructors burn out on everything but teaching.
The paid hour is the classroom. The unpaid ones are marking, lesson prep, differentiation and the parent inbox, stacked on top of it. The people quitting are not tired of students. They are tired of everything else.
Enrollment inquiries go cold.
Prospective students ask at 9pm. The reply comes Monday. They enrolled somewhere else Friday.
Course content costs too much to keep current.
Every cohort, client and delivery format forks the materials, and the master copy stops being the master by week three. Updating one module means finding every place it was ever pasted.
Feedback returns after the next assignment is due.
Marking at scale means feedback lands two assignments late, when it can no longer change how the student works. The instructor is not slow. The pile is just bigger than the evening.
The withdrawal was visible in week two.
The student who stopped logging in after the second module withdrew six weeks later. The LMS held the signal the whole time. Watching it was nobody's job.
Applications stall half-complete.
The transcript is in, the English score is not, the deposit is a maybe. A seat is only real when the file is complete, and the chase belongs to whoever remembers. Nobody remembers in intake season.
A lead instructor's Thursday
The 8am block is just teaching.
humanShe teaches. No dashboard, no queue, no tabs. The system's whole job before noon is to make the classroom the only place her morning goes.
Draft feedback is waiting at the break.
Last night's submissions carry first-pass marks against her rubric, every comment pointing at the line in the student's work it refers to. Nothing has a grade yet. Drafts are proposals, and the gradebook does not know they exist.
Grades leave under her name.
humanOver lunch she reviews the drafts, overrides two marks where the reasoning was better than the rubric anticipated, and releases the rest. The gradebook writes on her click and never otherwise.
The course tutor holds the afternoon.
Students in the practice lab ask it questions. It scaffolds from her own materials, refuses to hand over finished answers, and flags the one question that fell outside the syllabus for her Friday session. Every exchange is logged to the integrity file beside the Turnitin reports.
The quiet students get loud.
Three students stalled on the same module surface on her list with their attempts and their last login. The signal sat in the LMS all term. Now it arrives before the withdrawal deadline instead of in the withdrawal form.
She picks the interventions.
humanTwo get a seat in tomorrow's lab hour. One gets a call from the program head. The system flags, she decides. Nothing about a student's standing moves without her.
Friday's materials fork from the master.
The updated lab manual drafts itself out of the master course with this cohort's schedule and the new software version, and parks for her morning look. She will read it with coffee, not build it at midnight.
Built around your rules
| Regime | What it demands here | How the system complies |
|---|---|---|
| PIPEDA and BC PIPA | Learner and family personal information collected with consent, used for the stated purpose, and protected wherever it flows. | Minimal collection by design, consent tracked in the data layer, and records stay on your own instance under no-training API terms. What the workflow needs is documented, and nothing beyond it is collected. |
| FIPPA | Where the provider is a BC public body. Public-sector privacy and residency duties attach to the institution, and the privacy office signs before systems touch student data. | Builds for public bodies are designed around FIPPA from the start, data flows are mapped in writing before anything is built, and your privacy office is in the loop from the first session. |
| Minors' data | Where learners are under 18, explicit consent flows and minimal collection are duties, not preferences. | Consent flows are explicit, collection is minimal, access is scoped per cohort and per role at the database layer, and nothing about a minor leaves your own instance. |
| CASL | Enrollment marketing is sent with consent, identifies the sender, and can be left with one click. | The enrolment agent works a consent-tracked list, every message identifies the school, and unsubscribes propagate to every sequence the same day. |
| Private Training Act, BC | Where the college offers regulated career training. Certification with the Private Training Institutions Regulatory Unit, student records kept and producible, enrolment contracts and tuition refunds handled to the standard. | Enrolment steps are logged in the SIS where the regulated records already live, refund-relevant dates are tracked rather than remembered, and nothing in the enrolment path is invisible to an auditor. |
| IRCC compliance reporting | Where the school hosts study-permit students as a designated learning institution. Enrolment status reported accurately and on the regulator's schedule. | The report assembles from SIS enrolment and attendance records into a draft the registrar reviews and files. Nothing is submitted to IRCC by an agent. |
The regimes that govern education providers, what each demands, and how the system complies
Regime
- PIPEDA and BC PIPA
What it demands here
Learner and family personal information collected with consent, used for the stated purpose, and protected wherever it flows.
How the system complies
Minimal collection by design, consent tracked in the data layer, and records stay on your own instance under no-training API terms. What the workflow needs is documented, and nothing beyond it is collected.
- FIPPA
What it demands here
Where the provider is a BC public body. Public-sector privacy and residency duties attach to the institution, and the privacy office signs before systems touch student data.
How the system complies
Builds for public bodies are designed around FIPPA from the start, data flows are mapped in writing before anything is built, and your privacy office is in the loop from the first session.
- Minors' data
What it demands here
Where learners are under 18, explicit consent flows and minimal collection are duties, not preferences.
How the system complies
Consent flows are explicit, collection is minimal, access is scoped per cohort and per role at the database layer, and nothing about a minor leaves your own instance.
- CASL
What it demands here
Enrollment marketing is sent with consent, identifies the sender, and can be left with one click.
How the system complies
The enrolment agent works a consent-tracked list, every message identifies the school, and unsubscribes propagate to every sequence the same day.
- Private Training Act, BC
What it demands here
Where the college offers regulated career training. Certification with the Private Training Institutions Regulatory Unit, student records kept and producible, enrolment contracts and tuition refunds handled to the standard.
How the system complies
Enrolment steps are logged in the SIS where the regulated records already live, refund-relevant dates are tracked rather than remembered, and nothing in the enrolment path is invisible to an auditor.
- IRCC compliance reporting
What it demands here
Where the school hosts study-permit students as a designated learning institution. Enrolment status reported accurately and on the regulator's schedule.
How the system complies
The report assembles from SIS enrolment and attendance records into a draft the registrar reviews and files. Nothing is submitted to IRCC by an agent.
Learner data is handled to respect PIPEDA, BC PIPA and public-sector rules where they apply, with minors' data held to minimal-collection design.
How we build it for education providers
Ground everything in your curriculum.
Tutoring and feedback are indexed on your own materials and marking standards. Outside the syllabus, the system says so rather than guessing.
Grade the grader against your instructors.
Feedback quality is measured as agreement with the standard your markers already apply, not against a generic rubric. Drift here shows up as unfair marking.
Automate the chase, never the assessment.
Enrolment steps and routine questions are automated first. Anything reaching a learner's record stays a proposal an instructor releases.
What we will not automate
Grades and assessment decisions. Learner records are personal information, often for minors, so nothing is written without an instructor releasing it.
The hard questions
Free · 3-5 days
Know your number in five days.
We map your operations, find the highest-ROI automations, and hand you a ranked plan with the payback math attached. Yours to keep, whoever builds it.
Prefer to talk first? Book 15 minutes with our team. No pitch deck.