The problem
His students take one class and, ideally, come back for the next one. The follow-up is what brings them back. In his words: "I would have to send you a text message with an invoice after getting all the info from you. And then I would have to manually add you to an Excel document. And it was a pain in the butt."
He also had no way of knowing whether his emails landed. "Maybe half the students receive it, and the other people don't. And so maybe it's in a spam or a junk folder. I have no idea."
What we built
One Google Form he fills in once per class, with the class name, the last day of class, and the roster pasted straight out of his booking tool. It takes about two minutes. Two Make.com scenarios do the rest: the first splits the roster into students and queues their emails, and the second prepares each one in his Gmail on the morning it's due.
- The next-steps email goes out the morning after class.
- The 10-week check-up goes out ten weeks later and points students to the continuing classes.
- Nothing goes out on a Sunday, a couple who booked together gets one email addressed to both of them, and a roster submitted twice is ignored.
- Every email is logged in a sheet he can open anytime, so he knows exactly who got what and when.
Built for an owner who isn't a tech person
The owner put it plainly: "make things simplistic because I'm not the smartest when it comes to technology." So there's nothing new for him to learn. Everything runs in his own Google and Make accounts, and he got a written guide with screenshots for the rare day he needs to look under the hood.
The result
For now each email waits in his Gmail as a draft he can glance at before it goes, which is how we prove a new system on a real class. After his November class runs through it, it sends on its own.


