I need an experienced SaaS developer who can design, code, and deploy a truly multi-tenant school management platform that runs on a subscription model. Each institution must live in its own secure space while sharing the same core codebase, and the billing engine should handle free trials, tiered plans, upgrades, downgrades, and automated renewals. Core features to be delivered include student information management, attendance tracking, and grade reporting, plus a full set of supporting modules: institution onboarding, secure login, admissions, fees & payments, exams & results, ID-card generation, real-time notifications, consolidated reports, and an internal subscription & billing centre. Role-based access is essential. The system will surface distinct dashboards and permissions for Admin, Teacher, and Student accounts. I’d also like a lightweight “Developer” role so future contributors can safely interact with webhooks, API keys, and staging data without touching production records. Key integrations must be baked in from day one: • Payment gateways for recurring charges. • Email services for system mailers and notifications. • SMS services and WhatsApp services for time-critical alerts. The stack is flexible—as long as it is cloud-ready, scalable, and built with clean API layers. If you favour Laravel + Vue, Django + React, or a Node micro-service approach, let me know how you will keep tenancy isolated, automate CI/CD, and maintain test coverage. Deliverables 1. Source-controlled codebase with README and environment samples. 2. Database schema and migration files supporting multi-tenancy. 3. Fully-functional SaaS billing workflow with test cards and webhooks. 4. Containerised deployment script (Docker/Kubernetes) and a one-click cloud setup guide. 5. Admin, Teacher, and Student dashboards with the listed modules operating end-to-end. 6. Post-launch support window for initial bug fixes and minor tweaks. Acceptance Criteria • A new school can self-register, receive a sub-domain, and enter a trial instantly. • Switching plans updates limits and billing in real-time without downtime. • Data from one school is never visible to another, confirmed via isolation tests. • All outgoing email/SMS/WhatsApp messages hit the correct sandbox or live endpoints. • 90%+ unit test coverage on the most critical services. If you have built multi-tenant SaaS apps before and can move quickly while documenting your work, I’d love to hear how you would approach this build and which SaaS patterns you would apply.