Turni — Appointment SaaS Platform
Role: Founder & Fullstack Engineer · 2025

- Status
- Functional MVP
- Type
- Own product / SaaS
- Impact
- Multi-tenant SaaS with plans, payments, notifications and operational dashboard
- Proof
- Public code and usable MVP; not publicly launched due to infrastructure costs.
Overview
Own SaaS product for appointments and booking management. I implemented multi-tenant architecture, plan rules, Mercado Pago subscriptions, notifications and an admin dashboard.
Problem
Many businesses manage appointments manually: messages scattered across WhatsApp; paper agendas or Google Calendar without automation; no-show cancellations; no centralized visibility of clients or metrics. Existing platforms tend to be expensive, complex to configure and poorly adapted to the local market (payments, WhatsApp, custom domains).
Solution
Turni allows businesses to create their online store with their own domain; configure services, schedules and branches; manage clients and bookings from a dashboard; send notifications via email and WhatsApp; sync agendas with Google Calendar; charge through subscriptions (Mercado Pago). Includes Free and Premium plans with functional limits, 30-day free trial and complete automation of the booking flow.
My Role
I was responsible for the product end-to-end: ideation, plan definition and business model; UX/UI design and user flows; multi-tenant SaaS architecture; frontend, backend and payment system development; integration with WhatsApp, email and Google Calendar; infrastructure, deployment and manual testing.
Technical Architecture
Frontend: Astro · React · Tailwind CSS Backend / Infra: Supabase (auth, DB, storage) · Docker · Workers for notifications and jobs Integrations: Mercado Pago (subscriptions) · WhatsApp · Email · Google Calendar Plan logic: Free plan: up to 5 appointments/day, 2 services, no WhatsApp, Google Calendar or custom domain. Premium plan: unlimited appointments, up to 20 services, multiple branches, 30 WhatsApp notifications/week, external integrations, custom domain, full automation.
Major Challenge
Multi-tenant SaaS design with plan-based control: I implemented subscription limit logic directly in the backend, ensuring isolation between accounts, real enforcement of features per plan and dynamic upgrade/downgrade without breaking existing flows. Subscription payment integration: I built complete flows with Mercado Pago for plan signup, state handling (trial, active, expired, cancelled) and automatic feature lock/unlock. Notification automation: I designed independent workers for WhatsApp and email reminders, client and business notifications, and Google Calendar sync.
Current Usage
Complete functional MVP. Operational dashboard. Infrastructure ready for production. Not publicly launched due to hosting costs, but fully usable.
Key Learnings
- Multi-tenant SaaS design from scratch
- Implementation of real monetization (subscriptions)
- Integration with external messaging systems
- Architecture of automation-oriented products
- Infrastructure trade-offs in early-stage products