LANE C — THE CLAIM-SITE MACHINE

In hand right now

• 77 Tampa contractors with NO website (harvested Oct 21–22) — each with business name, trade, phone, address.
• Trade mix: Handyman 12 · Electricians 8 · Window Installers 7 · Landscapers 7 · General Contractors 7 · Concrete 7 · Painters 5 · Remodelers 3 · Flooring 3 · Cabinet Makers 3 · Pool Builders 2 · Garage Door 2 · Fencing 2 · Drywall 2 · Roofers 1 · Plumbers 1 · HVAC 1.
• Caller sheet is already built for this: the Oct 22 caller sheet carries all 77 with an empty Claim Link column, plus columns for called date/time, consent to text/email, and outcome — the mechanic was designed in before the system existed.

Channel reality (read off the data)

• Emails are almost all "not on listing" → text and call are the strong channels; email is the exception, not the plan.
• A few records lack even a phone number → they wait for enrichment (Branch 2) or get dropped. No guessing numbers.

The next reservoirs

• 1,041 contractors already sitting in GoHighLevel — filter for no-website and they become wave two, after the 77 prove the machine.
• Lead-hunter feed: the Agent K / buying-signal work feeds new no-website businesses as they surface.
• Directory spillover: men who claim a directory listing (truck-stop builders, pizza franchise, trade directories) but still have no site of their own.

The honesty label

Every name in this branch is a PROSPECT. A prospect becomes a lead only when he agrees to be set — in this machine, the claim is that moment of agreement. No counter, report, or conversation may call them leads before then.

Pulled per business, before any build

• Business name exactly as listed · trade / category · phone · street address.
• Service area (the towns he actually works) · hours · services named on the listing.
• Photos from his listing · rating and review count · review text already on record.

The build-ready record

• One clean record per business: name · trade · phone · address/area · hours · service list · photo set · reviews on record · claim-URL slug.
• Caller-sheet fields ride along: consent to text/email (Y + date), called date/time, outcome/notes — so outreach never flies blind.

Gaps, handled honestly

• Ratings and reviews are mostly absent from the current file ("not on listing") — they get pulled from the live listing at build time, or the site simply carries none.
• Never invented: no rating, review, service, or year-in-business appears on a site unless the listing itself says it.

The template

• Bill's design law, no exceptions: light background, dark letters, modern sans-serif only, big plain type, mobile-first — he will open it on his phone from a job site.
• Per-trade variants: the skeleton is one; the service lists, photos, and headlines change per trade (16+ trades in the file) so a plumber never sees a roofer's page.
• On the page: his name, his trade, his services, his service area, his hours, a big click-to-call button on his real number, his real photos, his real reviews where they exist, and a quote-request form.

Hosting

• One page per business on a subdirectory / subdomain of ours — the prospect opens a link and sees his finished site, live, not a mockup or a promise.
• Each site's URL goes straight into the caller sheet's Claim Link column — one tracked link per business.
• Looking costs him nothing — that is the whole pitch (Bill's reassurance line: going to the site is just a look at what his website could look like).

The QA gate — no exceptions

• Before ANY outreach, a test journey is traced end to end: build → claim link → claim page → test payment → onboarding trigger — the same clean-trace standard Bill set for GHL workflows.
• Every generated page is checked for the accuracy rule: a site may only say what the man's listing says.

First screen

• His website, live, with his name on it. The Oct 31 framing: "your website is already built — take a look."
• The claim offer sits beside the preview, in plain words: claim it and it becomes yours, in your name.

What claiming includes

• The finished site, exactly as shown.
• Hosting, maintenance, and upgrades under the monthly care plan.
• Changes and corrections handled through the support queue (Branch 7).
• His own domain, secured in his name, as the site's permanent home (the transfer fires at payment — Branch 6).

The guided walk-through (Bill's banked dialogue, Oct 30)

"Congratulations." → "Do you like your site?" → "Would you like to make any changes?" → "Is all the information current?" → "Would you like to add some information?" → "What products and features would you like to add to the site?" → then the payment link: "Follow this link to put in your credit card information to process your transaction."

• The cart on this page takes one payment: the claim/build fee + the first month of the care plan — both prices are X — OPEN DECISION (Branch 11).
• Honest frame: looking is free, nothing charges until he claims, no fake countdowns, no pressure copy.

The opener (Bill's words, banked Oct 30)

"Hello. Please follow this link to approve your new website."

• Email form of the same line: "Follow this link to look at your new website."
• Updated frame (Oct 31): the site is already built — the message invites a look, not a leap.

Channels & cadence

• Strength order: TEXT first (the file is phone-rich, email-poor) → CALL → EMAIL only where an address actually exists.
• Sequence: Day 0 text with the claim link → call attempt → follow-up text → email where available → final call.
• The cadence stops the instant he replies, claims, or opts out.
• Larry works the phones: Bill demos the call on camera, Larry sells the claim sites by phone for commission, the back end fulfills (Bill's Oct 30–31 plan).

Opt-out — non-negotiable

• A working opt-out rides on every channel — STOP on texts, unsubscribe on email, do-not-call honored on calls. Bill's own standing rule, written after his own 444 autodialer drip harassed him with no way out.
• An opt-out kills the entire sequence for that man, everywhere, immediately.
• Consent is tracked in the caller sheet before any repeat contact.

The lock

Building previews sends nothing. Outreach fires only on Bill's mark — final copy plus prices. Until that mark, this machine is loaded and silent.

The cart

• Stripe shopping cart on the claim page, running through the business till (Bill Becker Inc / Lionific register — a client's own money never mixes into it).
• Line 1 — one-time claim/build fee: X — OPEN DECISION Bill has not set it. (His Oct 30 dictation allows tiers by page count.)
• Line 2 — monthly care plan (hosting, maintenance, upgrades): X / mo — OPEN DECISION Bill has not set it.

What a successful payment triggers — automatically

• Domain secured in HIS name — the name becomes his asset, not ours (launch-order doctrine).
• Site transferred to his domain; launch checklist fires: DNS, SSL, click-to-call test, listing links pointed at the site.
• Onboarding queue entry created (Branch 7) · receipt and welcome message sent.
• Caller sheet updated: CLAIMED → PAID. He is now a customer, and a lead by Bill's definition — he agreed.

Failed payment

• Card declined → a polite retry link plus one human call from the queue. No claim, no charge, no penalty — the site stays in preview.
• Abandoned cart → one reminder inside the normal cadence, then the sequence stops like any other ending.
• Refund posture: a published policy in Bill's own words at a company address, backed by delivery we control (standing rule).

Roles

• Pintox (Saif) — builds and maintains the engine and the sites.
• Maheen — runs the support queue; transmits builds; first voice the client reaches.
• Bill — sells; his mark gates every send and every price.
• Larry — sells by phone on commission; the back end fulfills what he sells.
• Tubby — specs, QA traces, and the record.

Onboarding, step by step

• Claim paid → owner's facts confirmed with him (the walk-through's "is all the information current?" step becomes the record).
• Domain secured in his name → site launched on it → Google listing pointed at the site.
• Welcome note delivered: where his site lives, how to request a change, what the care plan covers.

The stack underneath

• Every client gets his own GoHighLevel sub-account (standing architecture) — CRM, follow-ups, and review requests live there, not in a spreadsheet.
• Support rule: change requests are logged, scoped honestly if beyond the plan, built by Pintox, and QA'd before the client ever sees them.
• The socket: a claimed site plugs the man into the whole Lionific stack — money in, and a real user list grows. That is the finish line of this lane.

First ring (his business, working harder)

• His own domain + email on it, if not taken at claim.
• 877-Amber AI phone answering — the phone gets answered on ring one; he never misses a job because he was on a roof. (Which name she is billed under follows the name fork — Branch 11.)
• Review engine — automated review requests running out of his GHL sub-account.

Second ring (being found)

• Ads management and the SEO / citation program: map listings across Apple, Microsoft, Chrome, DuckDuckGo "and everything else," plus search-engine and directory submissions — with the custodian rule attached: published counts must match what the program actually delivers.
• Directory listings — Tampa Vibe and the trade directories; a claimed site is the natural listing upgrade.
• The education ladder from Bill's banked script: CRM → sales funnel → the full package — offered in that order, never all at once.

Doctrine

Separation Doctrine holds: one piece, one company, one message. The funding door is a different door and is never sold off a claim page.

The funnel counters (reported to the war board)

• Only PAID is money. Only CLAIMED and beyond is a lead. Every earlier stage is prospects in motion.

Unit economics (placeholders until Bill prices it)

• Revenue per claim: X one-time + X / mo recurring — every claim stacks another monthly that repeats while Bill does something else. That stacking is the entire point of the lane.
• Cost side: template build (one-time, amortized across every site) + Pintox time per launch + outreach cost per prospect.
• Break-even per batch = batch cost ÷ (claim fee + expected months of care plan). The formula is fixed; the numbers land the day the prices do.

Kill criteria — decided now, not in the moment

• Pilot: if Bill won't approve the look of the 5, the template dies and is rebuilt before any batch runs.
• Batch: high views but near-zero claims after the full cadence = the offer or the price is wrong — stop, re-price, and do not blast the 1,041 on a broken offer.
• Channel: any channel drawing complaint or opt-out spikes gets paused the same day.

• Opt-out on every channel, honored instantly — Bill's standing rule, born of the 444 drip that harassed him with no way out.
• No invented claims on any site: no made-up ratings, reviews, services, or years in business — listing facts only.
• Prospects ≠ leads — in every counter, report, script, and conversation. Always.
• No outreach sends without Bill's mark on the final copy and the prices. Building is not sending.
• Separation Doctrine: one piece, one company, one message — on every claim page and every message.
• His data stays his: a man's site shows his business only; a client's customer money never runs through our till.
• Looking is always free. Fake urgency, fake scarcity, and pressure copy are banned from this machine.