Vibe coding for CPOs in education.
An education CPO is building for three audiences at once, teachers, students and parents, none of whom will read a manual, and a procurement office that reads every page of the privacy policy. The tension is that your prototype has to be tested with real classrooms to learn anything, and real classrooms mean data about children.
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.
What a CPO in education builds first.
01The practice tool for one classroom
The activity the learning platform does not support, built for a single teacher's class with student accounts created by the teacher, no email addresses, and no data leaving the class until you know it works.
02The view teachers actually want
Progress from the LMS grade book and the student information system joined to show which students have not submitted anything in two weeks, on one screen, without a report the teacher has to build.
03The parent communication prototype
Weekly summaries of what a child did, generated from activity data and reviewed by the teacher before sending, so you can test whether parents open it before engineering builds the real notification system.
CPOs in every industry tend to build the same four things. The CPO page has that list.
A classroom pilot that collects children's data without consent
You pilot with two schools and the sign-up form asks students for an email and a birthday. Some of them are under thirteen, no parent consented, and the data went to an analytics vendor with no agreement in place. The cost is a COPPA problem in the United States, a data protection problem in Europe, and a district that will not sign the contract you were piloting for.
The pattern underneath is the one every CPO hits: sales saw the demo. A customer signed. Now the exploratory build with no error handling and no tests has a contract attached, and 'we will rebuild it properly' has no date.
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.
What changes for a CPO in education.
A CTO in your corner draws the line between discovery and production, and helps you cross it on purpose. Prototypes stay cheap and disposable. The ones that are going to live get the ten things production needs before a customer touches them. When engineering takes over, it comes with a written account of what was decided and why. Discovery stays fast. The handover stops hurting.
What CPOs 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.
In your corner.