The problem
The team was tracking clients in a spreadsheet, tasks in Trello, invoices in a separate Excel file, and the calendar in Google Calendar. Lead handoffs slipped between cracks because no single view showed the same client across stages. The only person with full context was the founder, which is the classic bottleneck for a growing Lebanese B2B operation.
The solution
We designed and built a single-page CRM dashboard that consolidated client records, task pipelines, invoicing, and calendar coordination behind a clean, opinionated UI. The data model was deliberately small: clients, tasks, invoices, and events — each with the minimum fields needed for the team's actual workflow rather than a generic template.
Key features
- Dashboard analytics with at-a-glance KPIs (open tasks, this week's calls, outstanding invoices) so the team starts the day with priorities, not searching.
- Task tracking tied to clients, with status columns and quick-edit so updates take 5 seconds, not 5 clicks.
- Invoicing module with line items, dual-currency support (USD/LBP), and a clean print-to-PDF view appropriate for Lebanese-business invoicing norms.
- Calendar coordination linked to clients and tasks, so a meeting on the calendar drills into the client record without context-switching.
- Lead handoff flow that captures who owns what at each stage, eliminating the "who is following up with X" question that had been costing them response time.
Process
One week of discovery (interviews with the founder, two team leads, and the operations manager). One week of UX wireframing focused on the highest-traffic flows. Three weeks of build (HTML5, Tailwind CSS, vanilla JavaScript SPA architecture). One week of side-by-side rollout where the team kept their old tools as a safety net while we tuned. Old tools were retired four weeks after launch.
Tech stack
HTML5, CSS3, vanilla JavaScript, Tailwind CSS, single-page-application architecture with hash-based routing for fast navigation. The lightweight stack was a deliberate choice: no framework lock-in, no build pipeline complexity, and a UI that loads in under one second on Lebanese 4G.
Outcome
Independent measurement four weeks post-launch:
- Roughly 9 hours per week saved across the team in coordination overhead. The founder estimated the equivalent of half a part-time hire.
- +27% improvement in average lead response speed (measured first-touch to first-response on incoming leads).
- Cleaner lead handoff quality across teams, with zero "lost lead" reports in the first quarter post-launch versus 3–4 per month before.
The bigger qualitative win: the founder stopped being the only one who could answer "where are we with this client" — the dashboard answers that for everyone.
What this build is good for
This pattern fits Lebanese teams of 5–25 people who are running on Google Sheets, WhatsApp groups, and a generic SaaS CRM that does not match their workflow. If you are paying for a SaaS that bends 60% of the way to your process and your team works around the gaps, a focused custom dashboard like this typically pays for itself inside 12–18 months — and the workflow stays yours.