Here's what I walked into. Five locations. Ten tools. A pipeline board with 97 columns. 7,300 leads in a database, 84% of them dead. Zero attribution on a $5K/month ad spend. And a team spending nearly an hour a day per location on manual data entry.
Six weeks later: one system. 14 automated workflows per location. Full attribution. A re-engagement campaign running against 3,000 previously dead leads. And zero manual data handoffs between tools.
Here's how we got there.
Week 1: The Audit
Before building anything, I mapped everything. Every tool. Every data flow. Every manual workaround.
The stack: Monday.com for pipeline tracking. Typeform for intake. Make.com Enterprise for automation. Twilio for SMS. Calendly for scheduling. Zoom for calls. Jotform for forms. PandaDoc for contracts. Plus two industry-specific platforms that connected to none of the above.
The handoffs: Lead fills out a Typeform. Make.com webhook catches it and pushes to Monday.com. But the field mapping was incomplete — half the form fields didn't map to Monday columns, so someone manually filled them in. Twilio sent SMS but responses didn't log back to Monday. Calendly bookings updated Zoom but not the pipeline. PandaDoc contracts lived in their own world entirely.
Every gap between tools was a manual task. Every manual task was a place where data could be lost, delayed, or entered wrong.
The audit output: a complete tool map, a cost analysis showing $43K-93K per location per year in true stack cost, and $715K in recoverable revenue sitting in the inactive database.
Week 1 (Continued): What Stays vs What Goes
Not everything gets replaced. The audit mapped which tools the consolidated system would handle and which stayed exactly where they were.
Replaced: Monday.com (pipeline and CRM functions), Typeform (intake), Make.com (automation logic), Calendly (scheduling), Jotform (forms). These all moved into the new system — one pipeline, one form builder, one calendar, one automation engine.
Stayed: Twilio (SMS delivery — the new system uses it as a channel, not a replacement), Zoom (video calls), PandaDoc (contracts), and the two industry-specific platforms. These tools are best-in-class at what they do. Replacing them would add complexity, not reduce it.
Integrated: Twilio routes through the new CRM's messaging layer. Zoom syncs with the calendar. PandaDoc triggers on pipeline stage changes. The industry platforms get API write-backs for the data they need.
Weeks 2-3: Architecture and Build
The build started at the data layer. Custom fields designed for the operation — not default fields, not imported fields from Monday's 97-column mess. Clean. Structured. Consistent across locations.
Pipeline stages mapped to the actual journey: New Lead, Contacted, Tour Scheduled, Tour Completed, Application Started, Enrolled, Withdrawn. Each stage has clear entry criteria and automatic triggers.
Then the workflows. 14 automations per location:
- New lead intake: form submission triggers classification, tagging, and initial outreach sequence
- Follow-up cadence: 5-touch sequence over 14 days, personalised by segment
- No-response re-engagement: triggers at 48 hours, different content than initial outreach
- Tour booking confirmation: calendar sync, reminder sequence, staff notification
- Post-tour follow-up: triggered by tour completion status, different paths for converted vs not
- Reactivation campaign: targets inactive leads, personalised by age of lead and last touchpoint
- Attribution tracking: ad source to conversion, closed-loop reporting
Each workflow was built, tested with sample data, and validated before moving to the next one. No batch launch. No surprises on go-live day.
Weeks 4-5: Data Migration and Integration
This is where most migrations fail. The data migration.
7,300 contacts. Each one with history across multiple tools — some in Monday, some in Typeform submissions, some only in Twilio message logs. The goal: every contact arrives in the new system with their complete history intact. No orphaned records. No duplicate contacts. No lost conversation history.
The process: export from each source, deduplicate on email and phone, merge conversation histories, map fields to the new schema, validate record counts pre and post migration, and spot-check 5% of records manually.
Integration testing ran for a full week. Every webhook. Every automation trigger. Every edge case — what happens when a contact fills out two forms? When a booking cancels and rebooks? When a Twilio message fails to deliver? Each scenario tested and handled.
Week 6: Pilot and Go-Live
One location first. Always. Never launch five locations simultaneously.
The pilot location went live with the full system. Staff trained on the new workflows. Real leads flowing through. Real messages sending. Real data populating.
Week 6 was also the observation week. Watching the system handle real volume. Catching the edge cases that testing didn't surface. Tuning the automation timing. Adjusting message content based on actual response rates.
Once the pilot location was stable — all workflows running, staff comfortable, data clean — the rollout to remaining locations followed. Same architecture, location-specific customisation. Same training protocol. Sequential, not simultaneous.
- 10 tools, 23 manual handoffs
- 97 pipeline columns, most empty
- 45 min/day per location on data entry
- $5K/month ad spend, zero attribution
- 7,300 leads, 84% dead
- No re-engagement path
- 1 system + 3 integrated tools
- Clean field structure, consistent across locations
- Zero manual data handoffs
- Full ad attribution, closed-loop
- 3,000+ leads in active re-engagement
- 14 automated workflows per location
The Numbers After 90 Days
Software cost per location: down from $310-440/month to $130-350/month. That's the smallest win.
Staff time recovered: 45 minutes per day per location back. That's 195 hours per year per location redirected from data entry to actual operations work.
The re-engagement campaign against the previously dead database: 3,000+ leads now in an active nurture sequence. At even a conservative 3% conversion rate, that's 90 new customers from leads that were sitting in a spreadsheet doing nothing.
Attribution: for the first time, the business knows which ad creative drives which enrolment. That $5K/month ad spend is now accountable.
The ROI: The consolidation engagement paid for itself within the first quarter. The ongoing savings — staff time, ad efficiency, recovered pipeline — compound every month.
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 makes sense for your operation.
Book a Discovery Call