A travel agency came to me with a problem that sounds trivial until you see the cost of it. They were running WordPress with Forminator for lead capture. Enquiries arrived every day. Almost none of them were being handled properly.
The forms worked. The traffic was real. The leaks were entirely in what happened after submit.
What I actually found
Before writing any code I sat with how the team worked. Six separate problems, each small, compounding into lost revenue:
- No central system. Leads lived in three places at once: Forminator entries, an inbox, and a spreadsheet somebody maintained by hand.
- No tracking. Nobody could say whether a given lead had been contacted, was interested, or had already booked.
- Duplicate effort. Two sales reps regularly called the same person. Wasted time for the team, and a bad impression for the customer.
- No context. When a caller said "I asked about the Goa package yesterday", the rep answering had nothing in front of them.
- No reporting. The owner had zero visibility into lead volume, response time or conversion rate.
- Budget. HubSpot and Zoho were priced well beyond what a small team could justify, for features they would never touch.
Why I did not recommend a CRM
The obvious move is to sell the client another SaaS subscription. I did not, for two reasons. The data already lived in WordPress, so a CRM would mean syncing two systems and maintaining that sync forever. And the team needed perhaps five percent of what a real CRM does, at a recurring cost that never stops.
What they needed was a workflow, not a product.
What I built
A custom WordPress plugin, on PHP, JavaScript, MySQL and the standard plugin architecture. Eight pieces:
- Lead dashboard. One admin screen showing every Forminator submission, with filtering, search and pagination.
- A Sales Admin role. Built with the Roles and Capabilities API, it sees leads and nothing else. No posts, no plugins, no settings.
- Status management. Database-driven states: New, Positive, Negative, Follow Up, Converted, Closed.
- Activity logging. Every status change and action is written with a timestamp, so accountability is a matter of record rather than memory.
- Internal notes. Reps add context to a lead, and the full history is visible to the whole team. This is what killed the "I asked yesterday" problem.
- CSV export. One click, with columns generated from the form fields rather than hardcoded.
- Email notifications. Automatic alerts the moment a lead arrives.
- Auto-assignment. New leads route to a designated team member instead of sitting unclaimed.
Access, kept simple
Two roles, drawn tightly. The administrator gets the dashboard, leads, settings and user management. The Sales Admin can view leads, update statuses and add feedback. Nothing else in WordPress is reachable, which matters when the people using it every day are not WordPress users.
What changed
- Response times improved noticeably, because a new lead now announces itself.
- Duplicate follow-ups stopped entirely, because status is visible before anyone picks up the phone.
- Conversion became trackable, so the owner can see what is actually happening.
- No recurring software cost. The build was paid for once.
The takeaway
Sometimes the best solution is not adding more tools. It is building a smarter workflow on top of what already exists. This plugin later became the basis of DevXpert Lead Dashboard, which is now free and open source on the WordPress.org plugin directory.