Case Study · 2025–2026
B2B SaaS / Operations Platform
Property Services Operations SaaS
Full-Stack Developer — Backend-Focused
An inherited B2B operations platform for coordinating work, review, notifications, reporting, and access across separate customer organizations. I led the Laravel backend implementation that converted the application from single-tenant to multi-tenant behavior, then strengthened workflow reliability, API contracts, real-time updates, file handling, and regression protection within a distributed team.
- Laravel 12
- PHP 8.3
- MySQL
- Redis
- PHPUnit
Platform Context
An already-live operations platform needed multi-tenant support without losing its established product.
The platform was already in use when our team inherited it from another development vendor. It needed to support separate customer organizations while keeping organization-aware access and operational data appropriately scoped. The work required evolving an existing Laravel API while preserving the broader team-delivered product and its React web and React Native mobile clients.
Leadership and Contribution Boundary
Backend leadership for the multi-tenant conversion within a shared-ownership platform.
My primary responsibility was the Laravel backend. I led the backend implementation of the single-tenant-to-multi-tenant conversion and contributed to the related authorization, workflow, API, testing, real-time, file-handling, and delivery work. The wider platform architecture, product direction, infrastructure ownership, and release delivery remained shared team work.
Multi-Tenant Backend Implementation
Organization-aware authorization gave separate customers an isolated operating context.
Led the backend conversion from single-tenant to multi-tenant behavior, including organization-aware authorization, lifecycle safeguards, and focused isolation testing. This established a maintainable foundation for separate customer operating contexts without presenting the work as sole ownership of the full SaaS.
Workflow and Client Consistency
Backend workflow behavior stayed consistent across web and mobile clients.
Strengthened backend workflow behavior and status consistency for the React web and React Native clients. The case study intentionally keeps the underlying business rules and detailed operational state model generalized.
Contracts and Real-Time Updates
Documented API contracts and authenticated real-time updates supported both clients.
Introduced OpenAPI/Swagger documentation for important Laravel API contracts. Set up Laravel Sail and Docker development support, including Laravel Reverb, and integrated authenticated real-time updates for the web and mobile applications.
Testing, Files, and Delivery Support
Focused regression coverage protected high-risk backend behavior through delivery.
Established and expanded focused PHPUnit feature and regression coverage around high-risk backend behavior. Also contributed to notifications, reporting, AWS S3-backed file handling, upload reliability, queued processing, and selected delivery configuration under the technical lead's guidance.
Technology Stack
Laravel at the core, with real-time, contract, and delivery context kept visible.
Primary backend stack
- Laravel 12
- PHP 8.3
- MySQL
- Redis
- PHPUnit
Application context
- React
- React Native
- Laravel Reverb
- OpenAPI / Swagger
Development and delivery context
- Laravel Sail
- Docker
- AWS S3
Available for senior remote opportunities