CRM · Quickplus
CRM Platform Suite
Four CRMs, one steady release process.
Four production CRMs for recruitment, immigration, business-setup and call-centre businesses, with custom modules, safe imports and CI/CD.
Role
Full-stack developer and maintainer across all four CRMs
Period
Dec 2025 – Present
Stack
- PHP
- CodeIgniter
- MySQL
- jQuery
- JavaScript
- Tailwind CSS
- Bootstrap
- GitHub Actions
- OpenAI API
- Google Drive API
- 3CX telephony
Highlights
What stands out.
Custom modules
Recruitment contracts, customer documents and lead customisations on a CodeIgniter core.
Imports that can't duplicate
Hash-based de-duplication with rollback of the whole batch on any error.
Faster queries
Indexes added through migrations and the heaviest lead query rewritten.
CI/CD
GitHub Actions deploys: develop to staging, main to live.
The problem
The group runs four CRMs for recruitment, immigration, business-setup and call-centre teams. They capture a high volume of leads from WhatsApp, Meta ads and the website, distribute them automatically, and manage contracts, documents and telephony. They needed new modules, faster queries, imports that couldn't create duplicates, and a release process several developers could share safely.
What I built
| CRM | Business | My main contributions |
|---|---|---|
| Group lead hub | Business setup, recruitment, call centre | Recruitment-contracts module, lead customisations, database indexes and migrations, slow-query analysis, an optimised leads widget |
| Recruitment CRM | Recruitment and European work permits | Customer documents module (folders, permissions, bulk actions), contract builder, AI-generated job descriptions, GitHub Actions deploys |
| Call-centre CRM | Recruitment call centre | CSV lead import engine (de-duplication, rollback, validation), service types, call-centre dashboard, CI/CD to staging and live |
| Partner CRM | Partner business | Set up the instance to read leads and staff from the group hub's database, Google Drive integration, deployment guide and developer docs |
My role
I was a full-stack developer and maintainer across all four systems: new modules, performance work, data imports and the deployment pipelines.
Engineering highlights
- Query performance. Profiled slow queries, added indexes through migrations, and rewrote the heaviest leads query so filtering happens in SQL, not in PHP.
- Shared data across instances. The partner CRM reads leads and staff from the hub's database; I removed duplicate per-request connections and fixed the ambiguous-column joins this caused.
- Release discipline. Feature branches, pull requests, reverts and reapplies kept production stable while several developers worked on the same CRM.
How it fits together
The architecture.
All four CRMs share an extended CodeIgniter 3 HMVC core with custom modules. Leads arrive from WhatsApp and Meta, website forms, CSV imports and telephony; an auto-assign engine routes them by service. A REST API feeds other group systems, including the AI call analysis platform and the queue system.
Results
By the numbers.
Tech specs
What it’s built with.
- Framework
- PHP 8.1, CodeIgniter 3, HMVC modules
- Database
- MySQL (two connections), migrations, composite indexes
- Frontend
- jQuery, DataTables, Bootstrap, Tailwind
- Integrations
- WhatsApp and Meta lead API, 3CX telephony, OpenAI API, Google Drive API, webhooks
- DevOps
- GitHub Actions, SSH and rsync deploys, post-deploy scripts