Multi-Tenant Scheduling Microservice
Dynamic slot logic + CRM sync reduced ops load and accelerated lead→meeting.
Overview
Manual scheduling slowed growth teams. I wrote the PRD, set success metrics, and led delivery across teams.
Context & Role
Internal product for sales & academic teams; cross-functional leadership.
Problem
Spreadsheet slots; inconsistent rules; no auditability.
Objectives
Self-serve booking; consistent rules; unified audit trail.
Product Decisions
Declarative slot logic with test cases; auditability as a first-class requirement. CRM as source of truth for people/state; scheduler as orchestration layer.
Solution
Next.js + Supabase (RBAC, calendars, conflict checks); n8n triggers (reminders, reschedules, tagging); CRM sync + API fallback; webhooks; audit logs.
Architecture
Scheduler service ↔ CRM ↔ n8n ↔ Notification providers.
Metrics & Impact
70% ops reduction · 1,000+ meetings/mo · 25% faster lead→meeting.
Evidence
Ops time studies; CRM event logs; scheduler audits.
Challenges
Multi-team priorities; timezones; overlap edge cases.
Lessons
Testable slot logic and audit trails prevent regressions at scale.