Revenue CRM School Edition, in beta

The state of every student,
without going to look.

The roster is a spreadsheet. The lesson records are on each coach's own device. Payments are in a third tool. The school edition is one screen layout that puts status, records, and billing around the student.

See the demo See the screens
  • Students, lessons, and billing in one place
  • Mobile-first UI for coaches
  • In closed beta
A walkthrough of the Revenue CRM school edition, moving through the home screen, student list, student detail, billing, the weekly schedule, and the monthly report.
The screens: home, student list, student detail, billing, weekly schedule

What you follow is not "can we close this."
It is "will they still be coming next month."

So the three things at the center are students, lessons, and coaches. Not just whether someone is enrolled, but who took what and when, and how far they got.

The screens are built for the phone first. What mattered was a coach opening it between the classroom and the train, recording what just happened, and checking who is next, right there.

The same foundation works for any business built on recurring payments, subscriptions and repeat orders included. Take the student, lesson, and coach parts out and it watches contracts and retention instead. Ask us.

Read about this approach →

The problem

What drives retention is scattered around the school.

01

You find out after they leave

Absences, unanswered messages, a failed payment, a change in how they reply. You notice once they have already quit.

02

Handover lives in one person

When the coach changes, what happened last time, what the guardian said, and what to watch next all go with them.

03

Enrollment and billing become month-end work

Enrolled, on hold, withdrawn, paid. Counted again in a spreadsheet at the end of every month.

A student detail page, showing the assigned coach, lesson history, intake notes, and billing status on one screen.
One screen per student. Who is responsible, what was done and when, and how it went on a single page. When the coach changes, this screen tells the story.

The screens

Everything you open daily, organized around the student.

The student list, filtered by enrolled, trialing, near graduation, on hold, and graduated, with a status badge on each student.

Students

Trialing, paying, on hold, withdrawn. Where each student stands, at a glance.

The weekly schedule: lessons this week, coaches working, and a day-by-day list of times, students, and assigned coaches.

Weekly schedule

Lessons managed by the week, tied to the closure-day calendar.

Lesson history listing student name, assigned coach, course, and date in chronological order.

Lesson records

What was taught, kept per student. The history survives a change of coach.

The home screen: enrolled students, items needing attention, calls today, and retention rate, with a list of what needs handling now.

Call tracking

Who to contact, who is still waiting, and who has been handled, kept apart.

The intake form, with a transcript paste box and a fill-with-AI button above fields for how they found us, basic details, current level, and goals, each already filled in.

Intake notes

Paste the trial transcript and AI sorts it into fields. A coach corrects it before it is saved.

The monthly report screen, showing an AI-drafted progress comment with regenerate and confirm buttons.

Monthly report

Drafted from that month’s lesson records and calls. Check it, fix it, send it.

The knowledge base, listing articles for common questions, operating rules, and manuals.

Knowledge base

Teaching policy and operating rules written down, so running the school stops depending on one person.

The billing screen showing MRR, paying, and failed counts, with paying, cancelled, and failed badges on each contract.

Billing

Paying and failed payments in one place, so a stalled payment gets noticed early.

Running the school

Month-end reporting and the daily checks, done on the screen.

The month-end report, who has not been contacted, and this week's schedule all run straight off the student data. The point is not to produce a document. It is to leave something the next person can act on.

The monthly progress report is drafted by AI from that month's lesson records and call history. Counts come from the data as they stand. In a month with too little recorded, it does not invent anything; it lists the records. A coach checks it, corrects it, and submits it.

What you check most

  • AttentionStudents to contact today
  • EnrollmentEnrolled, on hold, and withdrawn this month
  • ScheduleThis week's lessons
  • ReportingThe monthly report draft

AI

Ask in plain language,
get the answer back.

You do not have to build a report to find something out. Ask it the way you would say it, and it searches the student data and answers.

Paste a trial-lesson transcript and it sorts what was said into fields: how they found you, their level, what they are after, and what the trial exposed. The writing-up afterwards goes away.

Anything AI writes stops at a draft. Nothing reaches a student or a guardian until a coach has checked it and confirmed it.

  • Which students need attention today?
  • What is this month's retention rate?
  • What lessons are scheduled this week?
  • List the students we haven't called

Permissions

Coaches see their own students. No one else's.

In schools that work with a lot of contract coaches, how far each person can see is a practical problem. Scope is set per role.

Owner
Every school, every student, billing, and permissions
School admin
Day-to-day operations and permissions
Manager
View and edit student data for their school or team
Coach
Only their own students and lesson records

Actions are logged, so you can trace who changed what, and when.

Closed beta

We are looking for schools
to build this with.

A closed beta is not where a finished product gets sold. It is where you run it in real operations, tell us what is missing, and we finish it together. The demo opens with just an email address.

See the demo See the B2B edition

What we show you

  • The student list and how enrollment status reads
  • The weekly schedule and closure-day management
  • How lesson records and intake notes accumulate
  • The AI-drafted monthly report
  • Coach permissions and the audit log