Book a free call →

Vibe coding for COOs in education.

An education COO runs the year as a machine: enrolment periods, cohort or class scheduling, instructor staffing, facilities and the attendance and completion reporting that funding depends on. The tension from this seat is that your tools feed numbers upward, to a state agency, an accreditor or a funder, and a counting error in a homemade tracker becomes a funding clawback.

Book a free callSee what breaks
ROUND 01Education rules

What is true about software in education before you write a prompt.

Schools, universities, training companies and edtech businesses all have the same shape of problem: a learning platform that does most things and a long tail of tools it does not. Executives are building the tail: an enrolment workflow, a parent portal, an assessment tool, a course marketplace. Most of them hold data about students, and some of those students are children.

  • Student data has its own laws

    FERPA in the United States, GDPR in Europe, and rules about children's data almost everywhere. A tool that stores a student's name, grades or attendance is regulated, and a tool used by under-13s has additional consent requirements.

  • Parents, students and staff see different things

    Role-based access is not optional. A parent must see only their child. A student must not see another's grades. The AI will build a single login unless told otherwise.

  • Accessibility is required

    Education tools are often legally required to be accessible. A page built fast with no attention to screen readers or keyboard navigation can be non-compliant on day one.

  • Term start is your launch day

    Enrolment tools and portals get their year's traffic in one week. Hosting and caching have to be ready for it, and a failure that week costs a term's trust.

ROUND 02What you build

What a COO in education builds first.

  • 01The enrolment pipeline

    Applicants from inquiry through deposit, placement and first day, with the documents still missing and the deadline for each, read from the student information system or the CRM. Built first because the week before term currently runs from a shared inbox.

  • 02The cohort and instructor scheduler

    Sections, rooms, instructors and their maximum load in one grid, with clashes flagged before the timetable goes out. Instructor overload and empty rooms are the two costs no one sees until the term has started.

  • 03The attendance and completion reporter

    Daily attendance and course completion from the student information system or the LMS in the exact shape the state, the accreditor or the funder asks for, with the calculation written down where an auditor can read it.

COOs in every industry tend to build the same four things. The COO page has that list.

ROUND 03What breaks

The attendance report disagrees with the SIS

Your reporter pulls attendance from the LMS because that was the easier connection, and the state counts from the student information system. The two differ by the students who log in but never sit in class. The funding submission is off by four percent, the audit finds it a year later, and the clawback arrives with a corrective action plan that lands on your desk.

The pattern underneath is the one every COO hits: three months in, the app is the only place the real status of anything lives. Then the database is changed by hand, or the hosting bill lapses, and there is no copy.

The full catalogue of what breaks →

ROUND 04The stack

What a safe build in education usually runs on.

Builds run on a standard web stack with Postgres, single sign-on from the institution's identity provider or a properly scoped login for parents and students, integrations with the learning platform and the student information system through read-only keys, and accessibility checked before launch.

The free course builds this stack from scratch →

ROUND 05With a CTO in your corner

What changes for a COO in education.

A CTO in your corner treats your ops tool as what it is: production software that the company runs on. Before the first team uses it, someone has checked how the data is stored and backed up, who can change what, and what happens when an integration fails. Every database change goes through a written migration you have tested on a copy first. You still build it. It just does not fall over when it matters.

How a month in the corner works →

ROUND 06Questions

What COOs in education ask.

A CTO who has read education apps before yours.

Thirty minutes, free, no card. What you built, what is going on with it, whether we can help.

Book a free callSee the price

In your corner.