[§] What I keep shipping
Not a portfolio of clients. A short list of operating patterns I keep running in real businesses, built over a decade-plus through Media Explode, my marketing agency, and run on my own books too. They move in real time on the radar at the top of the home page. Examples kept anonymous unless the client explicitly asked to be named.
[§ 01] Pattern · Lifecycle automation
From
COLD
To
LOOP
[§] Class · Marketing · Automation
A full lifecycle from signup through reminder, post-visit review request, and birthday promo. Webhook backbone tying intake to CRM to email to SMS.
What it is
Most small businesses see a steady flow of new customers and have no clean way to bring them back. The lifecycle pattern captures the signup (popup, intake form, loyalty enrollment), nudges the first transaction, follows up after the visit, and re-engages on birthdays and anniversaries. Every step writes back to the CRM, so the next campaign already knows who is active and who is drifting.
Why it works
The owner stops touching the system most weeks. Customers keep walking in saying ‘I got your email.’ The loop runs whether anyone is at the desk.
Where I've shipped it
Capture
Signup, intake form, loyalty enrollment
Nudge
Prompt the first transaction
Follow up
Post-visit review request
Re-engage
Birthday + anniversary promo
[§] CRM · single source of truth
Every stage writes back. The next campaign already knows who is active and who is drifting.
[§ 02] Pattern · Afterhours AI intake
From
9PM
To
24H
[§] Class · AI · Marketing
AI receptionist for afterhours calls with FAQ lookup, message capture, and customer-profile build. Profiles feed automated outreach.
What it is
Service businesses that close at night lose the calls that come in afterwards. The pattern wires an AI receptionist into the existing phone line: answers FAQ from a knowledge base, takes messages and summarizes them for staff in the morning, and quietly captures every caller's name and birthday into a profile. Those profiles then feed birthday outreach with a coupon, cross-sell to related products, or just a friendly note from the business.
Why it works
Routine questions get handled at 11pm without a human on call. The marketing back-end builds itself out of incoming calls instead of paid ads. Staff arrive to summaries, not voicemails.
Where I've shipped it
Afterhours call
Comes in once the doors are closed.
AI receptionist
Answers on the existing line, no human on call.
Answer FAQ
Pulled from the knowledge base, day or night.
Capture + summarize
Staff arrive to a summary, not a voicemail.
Build profile
Name and birthday written to the CRM.
[§] Caller profile
The marketing back-end builds itself out of calls, not paid ads.
[§ 03] Pattern · Multi-location franchise systems
From
ONE
To
ALL
[§] Class · Operations · Marketing
Central campaign management, local-store customization, unified reporting. Each location runs the same baseline system with local tailoring.
What it is
Before this pattern lands, each franchise location runs its own marketing in whatever shape the operator at that location has time for. Some have email lists, some have nothing, none have a shared system. Reporting to corporate is essentially ‘ask the manager.’ The pattern deploys a shared platform (HighLevel base, custom layered on top) with shared campaign templates that each location can localize, a unified pipeline for leads, and reporting that rolls up to corporate without anyone exporting a spreadsheet.
Why it works
Every location is on the same baseline. Corporate gets cross-location visibility. Local operators get a system they can actually run without becoming marketing experts.
Where I've shipped it
Corporate templates
One campaign baseline, built once.
Location
Same baseline, local offers and hours.
Location
Same baseline, local offers and hours.
Location
Same baseline, local offers and hours.
Unified reporting
Cross-location visibility, no spreadsheet exports.
[§] Shared platform
HighLevel base, custom layered on top. Every location runs the same engine.
[§ 04] Pattern · Cross-vendor recovery & rebuild
From
HLT
To
SCL
[§] Class · Paid · Operations
Diagnose the actual root cause across platforms. Coordinate resolutions between vendors. Rebuild the paid pipeline from scratch.
What it is
Sometimes a business gets caught between two SaaS vendors pointing at each other. A Shopify config triggers a Google Ads policy flag. A payment processor flags a category. Paid acquisition stops overnight. The pattern is multi-front: diagnose the actual root cause across both platforms, coordinate appeals and resolution between vendor support teams, then once reinstated, rebuild the campaigns and the strategy from scratch.
Why it works
Vendor cross-fires do not resolve themselves. They need someone willing to sit in the gap between platforms, debug at the interface level, and stay patient long enough to get a fresh account back to scale.
Where I've shipped it
A config on one trips a policy flag on the other. Paid acquisition stops overnight.
Diagnose
Find the real root cause across both platforms.
Coordinate
Run appeals between vendor support, then reinstated.
Rebuild + scale
Campaigns rebuilt from scratch, back to scale.
[§] My own books · I use what I build
[§] Caballeros Vacations
Travel agency · My own · Live
If it breaks here, the bill is mine.
Caballeros is my own travel agency. It runs on the same patterns described above, applied to my own bookings, my own marketing, and my own afterhours intake. Lifecycle automation runs every campaign. AI handles the late-night inquiries. The web stack catches the leads. The CRM ties it together.
It's the operating system I run my own business on, and it's the proof when I tell a client ‘here's what I'd build for you.’ I can point at Caballeros and say ‘here's what running it for years has actually taught me.’
I don't sell systems I don't run myself. Caballeros is where I run my own.
[§] Let's work together