Zatrovo

Independent fitness, Pilates, and yoga studios are stuck between Mindbody-class enterprise software and spreadsheets. The tools that exist are bloated, expensive, and built for chains, not the single-location operators who actually run most studios. Booking, packs, payments, and member comms live in three different tools.

Treat it as a real product, not a side-project: pick one painful workflow (booking + packs + payments) and ship it production-grade for one design partner first. Use AI as a force multiplier: Claude Code in the loop for boilerplate, Supabase for auth and Postgres, Stripe Connect for per-tenant payouts. Prove the multi-tenant architecture before adding surface area.

1. 01

   Per-tenant subdomain + Stripe Connect from day one

   Studios want their own brand. Building cross-subdomain auth and per-tenant Stripe accounts up front avoided a painful retrofit later, and made the product credible to design partners who were already running their own websites.

2. 02

   AI assistant as a first-class surface, not a bolt-on

   Studio owners do admin between classes. An assistant that can answer "who is in tonight's 18:00?" or "draft a no-show email to Sarah" is more useful than another menu. Built it on top of the same data layer so it can read and act, not just chat.

3. 03

   Solo build with agentic AI workflows (Claude Code + Cursor)

   The point of Zatrovo is that one PM-builder using agentic AI can ship what used to take a small team. Sub-agents on specs, schemas, reviews, and ops let one person own the full stack without the quality drop-off that usually comes with that scope.

4. 04

   Ship to one paying studio before adding more features

   Avoided the SaaS trap of building 80% of ten features. Got the booking + packs + payments loop watertight with a real studio running real classes through it before opening up to a second tenant.

• Next.js
• React
• Supabase
• Postgres
• Stripe Connect
• Claude
• Vercel
• Tailwind