What is your goal?
I’m currently building automation systems for clinics (appointment reminders, no-show handling, messaging flows) using Make.com + Supabase + Google Calendar.
What is the problem & what have you tried?
Right now I got my first client, but I’m trying to design this properly before scaling to 20–50+ clinics, even if will take long ofc
Main question is about architecture at scale:
Do you run:
A) One multi-tenant system
- Single Make scenario
- Single database (clinic_id separation)
OR
B) Isolated systems per client
- Separate Make scenarios
- Separate databases / projects
My concerns:
• Multi-tenant:
- Easier to manage centrally
- Lower cost
- But risk of breaking all clients if something fails
- More complex logic (filters, routing, clinic separation)
• Isolated:
- Safer per client
- Easier debugging
- But becomes a nightmare to maintain at 30+ clients
For those actually running 20+ clients:
- What architecture are you using today?
- At what point did things start breaking / getting messy?
- Biggest scaling bottleneck in Make (operations, routers, maintainability)?
- How do you handle updates across all clients?
- If you had to restart, what would you do differently?