A multi-location service franchise brought me in to fix their lead pipeline. Multiple locations across multiple states. Ten separate tools touching some piece of customer acquisition. And a Monday.com board with 97 columns that nobody fully understood anymore.
Here's what I walked into, what was broken, and what the migration actually looked like.
The Stack Before I Touched It
Monday.com. Make.com Enterprise. Twilio. Calendly. Zoom. Jotform. PandaDoc. Three other platform-specific tools.
Ten tools. All handling some piece of lead management. Monthly cost: $310–440 depending on usage spikes.
The Monday.com board was the center of gravity. 7,300 leads across all locations. Their API exposed 43 lead fields and 111 customer profile fields — and most of those fields were either empty or wrong.
The segmentation field returned null for every single record. That means every lead — regardless of what service they needed — got the exact same messaging. No personalization. No relevance. Just generic copy fired into the void.
Source attribution across all locations was tracked as a single label: "Online Web." Meta ads, organic search, referrals, walk-ins — all lumped together. They were spending $3–7K/month on Meta ads with zero campaign-level attribution. No way to know which ad produced which customer.
What Was Actually Broken
The board had 7,300 leads. Only 170 were in active pipeline. That's 2.3%.
The other 97.7% was sitting in various stages of "dead" — and nobody was trying to bring them back.
| Lead Status | Count | % of Pipeline |
|---|---|---|
| No Response (never followed up) | 2,149 | 29.6% |
| Marked "Not Interested" | 3,570 | 49.1% |
| Not Viable | 404 | 5.6% |
| Active Pipeline | 170 | 2.3% |
84% of every lead that ever entered the system hit a dead end with no path back. No re-engagement. No reactivation. Just silence.
I pulled a recent 4-month window to check whether this was legacy debt or an active problem. 676 new leads created. 541 went inactive. 80% inactive rate on fresh leads.
Those 541 leads: 100% had email on file. 96% had phone numbers. Fully reachable. Nobody was reaching them.
At their average customer lifetime value, even a conservative 2% reactivation rate on that group alone — $715K in recoverable revenue sitting in a column labeled "Dead."
The Follow-Up That Was Killing Them
- Day 0 and Day 1 SMS were word-for-word identical
- Post-visit email opened with "This is an automated message from..."
- 2–5 day gap between site visit and follow-up
- Leads auto-moved to "Dead" after 8 days
- No-show detection: manual staff confirmation
- No re-engagement sequence. Ever.
- Zero data captured on why customers left
- AI-personalized messaging by customer segment
- Follow-up fires within 15 minutes of visit
- Automated no-show detection via webhooks
- Manager notification: one-tap confirm/no-show
- 3 automated reminders before each visit
- 4-segment reactivation campaigns by timing
- Exit reasons captured on every departure
The gap between a prospect visiting and hearing back was 2–5 business days. In service sales, that window is where decisions happen. If you go dark for a week, you're following up after they've already signed with someone else.
What Migrates and What Stays
This is where most migrations go wrong. People try to move everything.
Rule of thumb: Only the lead funnel migrates to GHL. Operations, HR, billing, project management — all stay on Monday.com. Monday is good at operational tracking. It's bad at lead nurture and automation sequencing. Each tool keeps the job it's built for.
This franchise had 20 active Make.com scenarios. Only 5 retired — the ones handling lead intake and follow-up automation. Those got rebuilt natively in GHL. The other 15 stayed. They handle ops workflows that GHL doesn't touch.
Stack cost after migration: $130–350/month for GHL replacing the entire lead management layer. Net savings before you count a single recovered lead.
What Got Built
11 pipeline stages. Linear. No ambiguity about where a lead sits at any moment.
14 workflows for the pilot location alone. Every touchpoint — SMS, email, internal notification — runs through AI to generate personalized copy based on the customer's segment, the manager's notes, and where they sit in the pipeline.
Each location gets its own GHL sub-account with its own pipeline, email configuration, staff assignments, and localized branding. Same architecture, location-specific execution.
How You Sequence a Multi-Location Rollout
You don't launch every location at once. You pilot one, prove the system, then roll.
Audit & Map
Map every tool, every field, every automation scenario. Identify what GHL replaces vs what stays. Audit data quality.
Build Pipeline & Fields
Create stages, exit paths, custom fields. Structure before automation. Get the architecture right first.
Build Workflows & Integrations
Automated sequences, webhook integrations, AI personalization, no-show detection, notification systems.
Pilot Launch
Highest-volume location goes first. All intake paths tested. All automations verified. Staff trained.
Sequential Rollout
Remaining locations deploy the proven system with localized customization. Not a rebuild — a replication.
Multiple intake paths per location means double-digit intake configurations across the franchise. Each one mapped, tested, and verified before go-live. This is where DIY migrations break. Not on the pipeline stages — on the intake routing.
The Math
80% inactive rate on fresh leads dropping — because now there's actual follow-up, actual sequencing, actual re-engagement.
First-ever campaign attribution on $3–7K/month in ad spend. First-ever exit data on customer departures. First-ever segment-based personalization on outreach.
None of this is hypothetical. The system is built. The pilot is live.
Frequently Asked Questions
Running on a stack that grew by accident?
Tools added one at a time, never architected together. That's the problem I solve. Book 45 minutes and I'll map what moves, what stays, and what sequence makes sense for your operation.
Book a Discovery Call