01 · THE SITUATIONEvery enrollment went through a person.
GERTC is a civil engineering board-exam review center with two intakes a year, face-to-face in Cebu and Manila, plus hybrid and online. Demand was never the problem. The back end was.
Here's how a student enrolled before we started: they messaged the Facebook page, staff sent payment details, the student paid and sent a screenshot, staff checked it, found the order and flipped it to "Completed", and only then did the student get access to their course.
- Proof of payment was checked one screenshot at a time, which caused delays and drop-offs.
- Students picked their own sections with no seat limit, so overbooking was always a risk.
- Student IDs and exam numbers were assigned by hand through a mail merge.
- The LMS was controlled by an outside developer, with no admin access and no backup.
Growing meant hiring more admin. That's the exact wall a Maestro hits: the program can only grow as fast as the team can process it.
02 · WHAT WE BUILTOne source of truth, built around the intake calendar.
We built everything away from the live site first, so nothing broke for students enrolling mid-intake. Every step was approved by Ken, GERTC's operations lead, before we coded it.
Proposal and kickoff
A public proposal with a live demo of the sectioning form. Payment providers were registered, and we copied the live books form instead of editing it, so students filling it out weren't disrupted.
Master database + sectioning form
One Google Sheet became the master database. The new sectioning form only accepts emails already in it, so shared links and non-students are blocked. Picking a section takes a seat away live, and a full section (say 220 out of 220) disappears from the form on its own.
A checkout that doesn't need a person
In a sandbox copy of the site, we built a minimalist checkout so students could pay without logging in. Orders started syncing to the master database on their own.
Books, payments and a server decision
The books form tags every sign-up as new, refresher or duplicate, so inventory is never deducted twice. When a developer quoted $600 to $1,800 a month for a bigger server, we traced the lag to configuration instead and recommended a platform GERTC could own.
The Student Database app
HitPay and JotForm feed Zapier, Zapier writes to the sheet, and a custom app reads it live. Each student sees their section, schedule, payments and balance per program, with discounts applied. It's hosted inside Thinkific, so GERTC owns it outright.
2,000 past students brought in
169 current students got IDs, then 1,963 past registrants were imported. A published Zap now gives every new payer a student ID and exam number automatically.
03 · WHAT HAPPENEDThe team stopped counting seats.
Payment validation came off the owner's plate. Sections fill and close on their own. IDs, exam numbers, balances and discounts live in one place the whole team can trust.
And GERTC owns all of it. No outside host, no $199-a-month sync tool, no developer holding the keys.
If every new student adds to your workload, you're a Maestro.
Your marketing works. Your back end is what caps you. The Maestro container takes enrollment, onboarding and student admin off your plate, so you can say yes to more students without hiring more people.
Work with us