The 30-second version
- Tony sent a video + 22 documents (20 in the drop, 2 from today's call). The video is the important part: a cold-outreach replacement that's worked since ~2013 across every niche, city and country.
- The play: build a small local business directory, list businesses on it for free, then contact them to "verify your listing" — not to pitch. You sell services on the back end. Nobody hangs up on a courtesy call about their own free listing.
- The build from today's call — the Movers Factory: a client gives their facts once and one run produces both their website and a chat agent that already speaks their business, then closes the lead loop (a form submit finally reaches the operator) and two money loops (the client's subscription + the customer's deposit).
- Also shipped: a mover-industry sub-agency (mover.chat), a directory-submission app, table filters/sort, and the spec for our own "directory we own" (moverslist).
- Our angle: take the playbook, not the tooling. Everything the $99/mo product does, the ONE platform already does — and we add a pre-built AI demo the competitor can't match.
Part 1
The strategy — a foot in the door, not a pitch
The video is Keaton (@ItsKeaton) interviewing Tom Gattis, who runs a product called Smart Directory AI (a directory builder that lives inside GoHighLevel, $99/month). Tom is an ex-magician who stumbled onto this in Maui around 2013 and has taught it to thousands of agencies since.
The lightbulb: he noticed AARP runs a helpful-looking website for seniors, but really uses it as a front to collect leads it then sells insurance to. He realised he could do the same with a local directory — gather the exact businesses he wanted as clients by listing them for free, then sell marketing services to them on the back end.
Why it beats cold outreach in 2026: the market is drowning in "I can 10x you with AI" spam — a friend's A/B test showed just mentioning AI cut reply rates by more than half. Leading with a free listing you built for them sidesteps all of that. It isn't a pitch; it's a favour.
How the machine runs
- Seed it so it never looks emptyLoad ~100 real local businesses before telling anyone it exists. Launching an empty directory is the #1 killer. His product ships a ready-made site + hands you the first 100 businesses, plus 100 more each month.
- First email: "is your info correct?" — with zero linksPlain, personal, one ask: reply YES or tell me what to fix. No links = better inbox placement. He even leaves their website URL out on purpose, so the natural reply is "here's my URL, add it" — a second hook.
- Make it look busyAny listed business that isn't a target gets auto-upgraded to "premium" for free, so a brand-new directory looks packed. Visitors can't tell who paid.
- Courtesy call the opens & no-replies"I built this, you've got a free listing, just checking your info is right." Explicitly not a cold call. His ex-call-center setter, told to be gentle: after one week, "no one hangs up on me."
- The soft bridgeOnly at the very end: "By the way, I noticed you're not responding to your reviews — I could help with that. Want to hear more?" The pitch always comes after value is delivered, never as the opener.
- Permission-gated AI follow-upWhen they claim a listing, a checkbox grants permission to be contacted — including by an AI agent. That consent is what makes an automated next-day AI call legal (unconsented AI calling is a serious legal risk).
- Endless reasons to re-contact"We publish local events / news / a visibility report — want in?" The directory manufactures legitimate, value-first follow-up excuses forever, so the list never goes cold.
- Start tiny, then expandOne metro or one niche beats national. The Facebook analogy: Zuckerberg started with 3,000 Harvard students, not the world. Be the big fish in a small pond first.
Part 2
What we steal for OO
These are the transferable tactics — they work on our own directory→ONE funnel regardless of Tom's software.
"Verify your info", no links
The opening line our directory chatbot should lead with — not an audit pitch. Engineered for opens and replies.
Consent-on-claim gate
A tick-box at listing-claim captures permission, so next-day AI outreach is legal by construction. This is the load-bearing piece.
Pre-built AI demo
Where he ends on a services pitch, we end on a working quote-desk bot already trained on their business. A competitor mailing a mockup can't match it.
Owner-email scraping
He names D7 Lead Finder as the scraper that pulls owner emails — worth a look versus our current stack (owner-email verify is an open gap).
Directories rank well
Even a zero-traffic hyperlocal directory is a rare backlink and scores high with AI answer-engines (schema-marked). The free listing isn't hollow.
Local group posts
"I built a directory for [area] — add your business" in a local Facebook group reliably pulls 45–150 comments. No ad spend.
Part 3 · from today's call
The Movers Factory — one intake, a whole business
The headline build from our call. Until now a mover got a website or an agent, from two separate build paths that didn't share a single fact — the same business, told twice, built twice. The Factory makes it one intake and one build: the client gives their facts once (a form, their existing site's URL, or a chat), and one run produces both halves from the same source of truth.
One set of facts → the website and the agent
Built · on branchTen real pages (name, city, licence, a price that's consistent everywhere) plus a chat quote-desk that speaks their business — both from the one fact set, both reviewed by a human before anything publishes. Nothing invented: it only ever states what the facts give.
The lead loop finally closes
Built · on branchA visitor who fills the quote form now actually reaches the operator — a wake-up nudge with the move details and a link in their inbox. Before, that submit vanished into a row nobody was told about. This is the difference between a website and a booked move.
Two money loops, wired in
Built · on branchGo-live subscribes the client to the recurring plan (the agency's monthly becomes a workflow step, not a hand-sent invoice), and the customer journey takes a real Stripe deposit at booking. No new payment system — it reuses billing the platform already runs.
Status: built and green on branch do/movers-factory (14/14 tests passing), not yet merged to main. The full customer journey — qualify → quote-with-deposit → move-day → review/referral — ships as ready-to-run workflow templates.
Part 4
Everything else Tony shipped in the repo
mover.chat — a movers sub-agency
Live · legs 1–6A vertical agency sitting under Vespio (Vespio → mover.chat → moving-company clients). Sells the mover stack we already ship — website, chatbot, playbook, booking. Workspace live, sales agent answering, mover.chat serving, one demo client run end-to-end. Open: the demo-call booking leg.
Directory-submission app
LiveAt one.ie/u/vespio/directories — submits our clients into other people's directories (outbound citations / local SEO), 309-entry registry. Note: this is the opposite direction to the strategy above. Don't conflate the two.
moverslist — a directory we own
Spec'd · not builtThe buildable form of the video's play: a public /movers directory we seed, businesses claim, and the claim captures consent as a hard gate — no AI outreach fires without it. This is the one genuinely new build; the rest is composition of shipped pieces.
Filters + sort on tables/databases
LiveA usability upgrade to the data-grid UI across the platform.
He also dropped a full documentation set for the movers vertical (below) — the manifest is the map; start there if you go deeper.
Part 5 · the full set
Every document Tony sent, in detail
22 files in all — 20 from the drop plus the 2 from today's call. They're not 22 separate ideas; they're seven families that together describe one machine: find the mover → give them a site + agent → teach them → run their customer journey → bill it. Here's each one and what it's actually for.
The map
Start here — it indexes everything else.
| File | What it is |
|---|---|
| movers-manifest | The one index of the whole movers vertical: every artifact, its live status (a 4-label honesty system), its next action, and a diagram of how the legs — offer, education, website, booking, live client, corpus, agency — close a single loop. If you read one file, read this. |
The acquisition engine (the directory play)
The strategy from the video, turned into something we can build.
| File | What it is |
|---|---|
| movers-directory-strategy | The full playbook distilled from the Tom Gattis interview and re-grounded on our own stack: the free-listing door, the no-links verification email, the courtesy-call reframe, the "pre-built demo" synthesis that's our edge, permission-gated follow-up, a 30-day launch runbook, target funnel math, and a list of anti-patterns to avoid (empty directory, national-first, corporate tone). |
| movers-directory | The buildable spec for moverslist — a directory we own at /movers. Its load-bearing piece is the consent-on-claim gate: when a business claims its listing it grants per-channel, revocable permission, and no AI outreach can fire without a valid record. Consent is the whole compliance story. |
The agency — mover.chat
The storefront that sells the whole vertical, live under Vespio.
| File | What it is |
|---|---|
| mover-chat | The promise: eight live "legs" that together make the agency real — workspace provisioned, sales agent answering, mover.chat serving, a homepage that sells, a self-serve signup, the playbook linked, the demo call bookable, and one client run all the way through the factory. |
| mover-chat-plan | The design + runbook. Its core is a no-duplication contract: the four things asked for (website, chatbot, playbook, agency site) are each mapped to an asset that already exists, so nothing gets built twice. Plus the key decisions and the provisioning steps. |
| mover-chat-todo | The step-by-step build cycles that execute the promise above. |
| mover-chat-docs | Operator-facing: how the agency actually runs day to day, and how a new mover client is onboarded. |
The client website
A ready-made, best-practice moving-company site — the thing each client gets.
| File | What it is |
|---|---|
| movers-website | The promise: a 10-page website "pack" that drops into any client workspace, plus the lead-capture receiver that fixes a real gap — until now, forms on these pages saved data but told nobody. |
| movers-website-plan | The design of the pack and the capture receiver — the pages, the form fields (adds date + dropdown), the submit handlers. |
| movers-website-todo | The build cycles (roughly six, batched) that turn the spec into working software. |
| movers-website-docs | How the pack and the lead capture work once shipped. |
| movers-anatomy-of-perfect-movers-website | The deep reference (the biggest doc in the set): the physics of the trade (why "first number wins", the six-field form, claims that are illegal to make), all 22 possible pages with model copy, per-page SEO, ready-to-paste schema code, a fully-worked example city page, and a launch checklist. |
The Factory — from today's call
The newest work: one intake builds both halves of a client and closes the loops.
| File | What it is |
|---|---|
| movers-factory | The promise: the client's facts, given once, build both their website and their chat agent from the same source; the lead loop closes (a form submit reaches the operator); and two money loops wire in (the client's subscription + the customer's booking deposit). Seven deliverables, four already green. |
| movers-factory-features | The capability breakdown: a table of what it can do and who does it, six concrete use cases (from "live today" to "a review-and-referral three days after a completed move"), what's explicitly in and out of scope, its dependencies, and the success criteria. Green on branch, not yet merged. |
The education leg — the playbook
The free front door that earns trust and teaches the owner why each lever works.
| File | What it is |
|---|---|
| movers-playbook | The promise for /learn/movers: 11 lessons written in a mover's own language (already live), the free education front door marketing links to and clients walk through. |
| movers-playbook-plan | The design — the lesson registry, the AI tutor's directive, the content collection. |
| movers-playbook-todo | The build cycles that shipped the course. |
| movers-playbook-docs | How the course and its tutor work. |
| movers-playbook.pdf | The whole playbook packaged as a PDF — the shareable, print-ready version. |
| movers-playbook.epub | The same playbook as an e-book, for reading on a phone or e-reader. |
The backend & the brain
The plumbing under a client, and the structured knowledge every agent reads.
| File | What it is |
|---|---|
| mover-backend-tutorial | The full tutorial for standing up a compliance-grade moving-company backend — first the no-code way (declared data types + views), then the same thing in code. The technical foundation a mover's data sits on. |
| mover-foundation | The structured "company brain": company, people, brand, offer, market, customers, alignment — the seven-section knowledge base every mover agent reads on every turn, so it never has to re-ask what it already knows. |
All 22 raw files + the full 11,661-word video transcript are archived at:
source-docs/tony-system/2026-07-20-vespio-movers-directory-swarm/
One honest caveat
Every case-study number in the video is self-reported by the sellers and unverified — Donna "$40k/mo", Diane "15 sales in a day", Jam "$500 + $3,900", etc. Treat them as motivation, not proof. What was independently verified: the host's channel (78k+ subs) and that the product/site are real and live. The strategy is sound; the specific dollar figures are marketing.