Lead engine, website & ops dashboard
Case study · Group-travel company · Sep – Oct 2026 · site live
Enquiries came in from three places, and nobody had the full list.
Every enquiry lands in HubSpot, tagged by trip. Leads who aren't ready get a paced email series, serious ones alert the team at once, and a reply stops the emails.
Results
- 3 systems shipped: automation, site, dashboard
- 5 tools integrated
- ~520 commits across 2 codebases
How it works, step by step
- Website: Enquiry form: which trip, and how to reach you
- Social chat: A chat bot asks budget and travel dates
- Make: Chooses the right follow-up for each lead
- HubSpot: One contact per person, tagged by trip
- Nurture: A paced email series until they're ready
- Alert: The team is told straight away
- Reply stop: When a person replies, the emails stop
- Dashboard: Bookings and pipeline on one screen
Delivered for this client
- Lead engine (Automation): Chat and web forms into HubSpot, with nurture, alerts and reply stop
- New website + CMS (Website): Rebuilt on Next.js and Payload, with automatic tests; live
- Team dashboard (App): Contacts, deals and email history in one place, with AI insights
- Email list move (Automation): Old mailing list moved into HubSpot, sending fixed
Role and stack
Automation, full-stack and CRM engineering. Built with Make, ManyChat, HubSpot, Next.js, Payload CMS.
Built by Usama Ali, a GTM & AI Automation Engineer who designs, builds and runs end-to-end systems for sales and operations. Get in touch.