Aracuda Inspection SaaS Platform

Built Aracuda, a scalable, multi-role CRM and SaaS marketplace platform for inspection-based service businesses. This was a solo Laravel build from the ground up, developing centralized systems to manage clients, agents, inspectors, bookings, bidding, inspections, payments, and subscriptions — replacing manual spreadsheet operations with a fully automated SaaS workflow. The platform was built to function as real subscription software, not just an internal tool, with billing, plan management, and role-based dashboards for five distinct user types: admins, buyers, inspectors, agents, and staff. It's the kind of multi-sided SaaS marketplace platform that needs bidding, scheduling, document handling, and payments to all work together reliably.

Architected a Laravel and MySQL backend built around security from the ground up — prepared statements, hashed credentials, and role-based access control across every one of the five user roles. Integrated a payment gateway with a full subscription and billing module so the platform could charge for plans and handle payment splits automatically instead of manually. Implemented a secure multi-role bidding system letting agents bid on and win inspection jobs, built automated inspection scheduling to remove manual coordination, enabled secure document uploads for inspection reports with per-client storage isolation, and shipped an interactive analytics reporting dashboard giving admins real-time visibility across bookings, bidding activity, and revenue. Every part of the system was designed as a repeatable SaaS workflow — new clients, agents, and inspectors can be onboarded without custom development work, which is what makes it a genuine multi-role marketplace platform rather than a one-off internal tool.

The main risk on a five-role marketplace is workflow bugs — a booking getting stuck between bidding and assignment, or a role seeing data it shouldn't. I modelled the booking lifecycle as an explicit state machine (open → bidding → assigned → inspected → paid) rather than inferring state from scattered flags, which made the transitions predictable and testable. Securing document uploads required validating file types and size limits server-side, isolating storage per client, and guarding against path traversal — uploads from inspectors and agents are exactly the kind of user input that's easy to get wrong. I also used prepared statements and hashed credentials throughout to close off SQL injection and credential-exposure risks. Building this as real SaaS software also meant the subscription and billing logic had to be resilient on its own — a failed payment or plan downgrade could never be allowed to silently break a client's access to the platform.