Sound familiar?
What yoga studios tell us before a project starts.
- Class passes, memberships and drop-ins are tracked in different places.
- Waitlists are managed by hand and spots go empty.
- Workshop sign-ups arrive by email and we chase payments.
- New students try a class and we never follow up.
- Teacher pay depends on attendance and takes hours to calculate.
What we build
Each one is a working piece you can open and check when it's done.
Waitlist that fills itself
When someone cancels, the next person on the waitlist is offered the spot by text or email, with a short window to accept.
Booking and scheduling systems n8n, Make and Zapier automationNew student follow-up
A thank-you after a first class, a note a few days later about a next step, and a nudge to anyone who hasn't returned in a month.
GoHighLevel setup n8n, Make and Zapier automationWorkshops and teacher trainings
A sign-up page with deposits, payment plans, confirmation emails and a roster for the teacher.
Stripe integration and billing Web apps and MVPsMember lapse and renewal
Memberships that are about to end or have failed payments flagged, with a friendly message and a record of the reply.
n8n, Make and Zapier automation API integrations and data syncTeacher pay
Attendance and rates turned into a pay sheet per teacher per period, ready to check and pay.
Google Sheets and Apps Script automation Python scripts and utilitiesStudio numbers
Attendance by class and teacher, member count and revenue by offering on one page the owner reads weekly.
Dashboards and reportingYoga studios software we work with: Mindbody, Vagaro, Acuity Scheduling, Square.
And the general tools around it: Stripe, Mailchimp, Google Sheets, QuickBooks, Calendly, Twilio, Zapier, Make.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Waitlist offers by text
Example: a studio with full evening classes wants a canceled spot texted to the first person on the waitlist, with the next person offered it if there is no reply in fifteen minutes.
Booking system, Twilio, ZapierExample project
First-class follow-up
Example: a studio sends new students a thank-you the same day and an offer to book a second class three days later, stopping once they book.
Booking system, email, CRMExample project
Teacher pay sheet
Example: a studio pays per head with a minimum per class. Each period's attendance is read from the booking export and a pay sheet is built per teacher.
Booking export, Google SheetsQuestions people ask first
We use Mindbody or a similar system. Do we replace it?
No. We build around it, through the integrations and exports it supports, and tell you in the scope where its limits are.
Who owns what you build?
You do. It is built in your own accounts, and you get notes on how it works so your team can change it without us.
Can members get texts?
Yes, if they have agreed to receive them. We set up the opt-in and the stop option properly.
How do we start?
Tell us which tools you use and the one thing that wastes the most time each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com