Texas CL Launch — Scope of Work (Jul 28)

1 Where things stand right now

• Dallas is live and proven. The DFW page is fully dressed, the bot answers messages, and the lead-transfer pipeline was proven end to end today — a test lead landed as a text on your phone from the 626 number. You forward Dallas leads to Dan by hand, and that is deliberate (human in the loop until DripJobs delivery is approved).
• The Texas statewide page and the Austin page were created today, but both still need two clicks from you before anything can run on them: claim them into Business Manager, then give the automation user access. Houston and San Antonio pages are already claimed but have been stuck at the access step since yesterday.
• None of the 4 new pages are dressed yet — no profile photo, cover, or first post. All the artwork is rendered and waiting; one script dresses all four pages the moment access is granted.
• Today's ad scrapes are saved. Groundworks (599 ads), the basement-systems dealer network (427), Monroe Concrete Leveling (7), Virginia Crawl Space (6), and EyeFly/DryScale (29) are all in the swipe file — 2,791 ads total — and all 883 available ad videos are backed up to the Google Drive Ad-Library folder with zero failures.
• Decision on record from today: one Facebook page per state is the scaling model. Facebook caps page creation at roughly 2 per day, so per-city pages can't scale — the TX page runs every Texas metro as its own ad set inside one campaign.

2 Your three questions, answered

Did we save the scraped campaigns?

• Yes. Everything imported, videos archived to Drive, video download is now a permanent step of every scrape.

Did we split B2B vs B2C in the swipe file and the Drive library?

• Partially. Every ad is tagged by advertiser and format, and the split is obvious from the source — Hormozi, Kai Bax, Daniel Iles, DryScale are agency-style B2B; Groundworks, Monroe, and the basement dealers are homeowner B2C. But there is no explicit B2B/B2C label on the rows, and Drive is organized by advertiser, not by audience. That's a ~15-minute tagging pass, queued in the parking lot below.

Did we figure out lead routing by market?

• Designed, and the part you need today already works. The design decided today: each contact gets their market stamped when they come in, one bot handles everyone, and at hand-off time a lookup table says which market goes to which buyer — Dallas to Dan, everywhere else to you as sales inventory. The lookup table isn't built yet, but it does not block launch: right now every qualified lead already texts your phone and you forward manually. While you are the only seller, that IS the routing.

3 One correction to your plan

• The plan of record: one bot for everyone, made market-aware. It already collects ZIP, and ZIP tells us the market.
• The rest of your plan stands as-is: different ad sets per city, each with its own caption and targeting, all under the one statewide page.

4 Your clicks (~15 minutes, unblocks everything)

• 1Claim the TX and Austin pages into Business Manager: Business Settings → Pages → Add → Add an existing Facebook Page. Self-approves instantly.
• 2Grant the automation user access to all four pages — TX, Austin, Houston, San Antonio. Houston and San Antonio have been waiting on exactly this since yesterday.
• 3Connect the TX page in the GHL sub-account's Facebook settings so the bot answers its messages.
• 4Answer the four open decisions at the bottom of this page (budget, ad account, Dallas placement, bot name).

5 Agent work (starts the moment your clicks land)

• 1Dress all four pages — profile photo, cover, first post — and send screenshot proof.
• 2Build Houston + Austin ad variants from the proven Dallas winners and the Monroe/Virginia playbook: free-estimate offer, symptom-checklist body, Messenger call-to-action, captions that name the city.
• 3Run creative preflight and produce the offline contact sheet for your approval.
• 4Build the campaign paused: one budget-optimized campaign on the TX page, one ad set per market — Houston and Austin, each 10-mile-plus radius, residents only.
• 5Wire market stamping so every lead carries its city: v1 uses the ZIP the bot already collects; the ad-set-level stamp ships with the bridge patch.
• 6Full readback plus screenshots of everything → you flip it live. Nothing activates without your go.

6 Not blocking today (parking lot)

• Vendor lookup table + automatic per-market routing — needed when the second buyer signs, not today.
• B2B/B2C tagging pass across the swipe file and Drive.
• San Antonio: page is sitting ready whenever you change your mind; skipped per your call.
• DripJobs auto-delivery to Dan — held because his intake webhook silently drops notes, media links, and lead source. Manual forwarding stands.

7 Open decisions for you

• 1Budget for the TX campaign. Dallas runs about $20/day today; suggested start is $50/day across Houston + Austin combined.
• 2Does Dallas move under the new TX-page campaign, or stay where it is? Recommendation: stays put — it's live, feeding Dan, and mid-learning. Moving it restarts learning for nothing.
• 3Which ad account builds the TX campaign. None of the stored tokens can currently see the account the Dallas concrete campaign runs on, so either re-connect the ads integration or the build happens in Ads Manager with the agent driving your browser.
• 4Bot identity on the TX page — keep the same bot persona statewide, or a neutral name?

8 Technical notes