#Key Achievements
Achievements
- Operational Efficiency·Eliminated inter-team lead theft via a proprietary locking mechanism, ensuring strict lead ownership and reducing team conflicts.
- Workflow Integration·Developed a custom browser extension for WhatsApp and Gmail, providing real-time customer context directly within the communication interface.
- Performance Tracking·Engineered an objective, data-driven performance engine to calculate fair, transparent compensation for marketing teams.
#Project Overview
In late January 2026, I was commissioned as a sole developer to modernize a legacy workflow for a previous client. The core objective was to move away from disorganized manual tracking and establish a system that could monitor marketer performance while preventing "lead collision"—where multiple agents inadvertently overlap on the same customer.
The system needed to track granular metrics: conversion rates over specific periods, contact volume per marketer, and organization-wide database integrity for educational institutions and partner organizations.
#Challenges
The primary challenge was not just technical, but Change Management. The target users were professionals in their 30s and 40s who required a highly intuitive UX to adopt the new system over their existing habits.
While the initial timeline was an aggressive two-week sprint, the project evolved due to shifting requirements and bureaucratic hurdles. By maintaining a weekly iterative release cycle and managing client expectations, I delivered a final product by late March that solved critical business issues: customer "juggling," duplicate entries, and marketing fraud.
The requirement for a multi-branch rollout necessitated a robust Multi-Tenant Role-Based Access Control (RBAC) system to ensure absolute data isolation across different organizational branches.
#Technical Deep Dive
#Multi-Tenant Architecture & Granular RBAC
Drawing on my experience with scalable SaaS architectures, I implemented a shared-database multi-tenant model.
- Logic: Global roles are identified via a
nulltenant ID, while branch-specific roles are scoped to a uniquetenant_id. - Performance: I implemented Redis-based caching for user permissions to minimize database connection overhead and ensure sub-100ms authorization checks.
- Security: A global Middleware layer automatically scopes every request to the authenticated
tenant_id, creating a logical "wall" that prevents cross-tenant data leakage.
#Contextual Browser Integration (WhatsApp & Gmail)
To increase user adoption, I aimed to eliminate "Alt-Tab fatigue." I developed a browser extension that bridges the CRM with communication tools.
- Engineering Decision: I bypassed high-risk headless automation (like Puppeteer) in favor of a DOM-based interaction layer using WA-JS. This operates within the user's existing browser session, significantly reducing the risk of account flagging.
- Business Value: This allows marketers to view CRM data overlays and sync chat logs directly from the WhatsApp Web interface, turning a standard social tool into a data-rich business workstation.
#Real-time Synchronization with Laravel Reverb
I implemented a WebSocket layer using Laravel Reverb to provide live data updates. Administrators can now monitor marketing activities and lead status changes as they happen, eliminating the need for manual dashboard refreshes and improving decision-making speed.
#Production-Grade Infrastructure
As the sole engineer, I established a modern DevOps pipeline to ensure the system's long-term stability:
- Containerization & Service Orchestration: I utilized Docker to decouple the system into specialized services, including the core application, socket server (Laravel Reverb), cron scheduler, and worker queues. This modularity allows for independent scaling and isolation of failure points.
- CI/CD & High Availability: I implemented automated deployment pipelines with health-check verification. This setup enables Zero-Downtime Deployments, ensuring that marketing activities are never interrupted during update**.
- Distributed Storage with MinIO (S3-Compatible): For robust file management, I integrated MinIO to provide an S3-compatible object storage layer. This ensures that customer attachments and media are handled efficiently, with a clear path for future migration to AWS S3 or other cloud providers without code changes**.
This infrastructure resulting in modularized each services
Want to discuss the multi-tenancy architecture or the extension integration in more detail? Let's talk.
