Top Tier Strategies — Launch Punch List

Flag 1 · Confirm the number

On the call Dan said "founding 300" and "299 other people." Our locked offer says founding 100. Someone changed it or misspoke. Pin down which number is real before it lands in early-bird copy.

Flag 2 · The one item with schedule risk

The county-map + search rebuild is homeowner-facing, touches 80+ pages, and Dan said it may not be ready until Tue/Wed but wants it Monday. It is the long pole. Everything else here is quick or already built.

P1 do now / high priority P2 before launch verify confirm it's actually built decided settled on the call 0 of 0 done

A Consumer site — map & search longest lead time

P1 Map drills to COUNTY level, not city. City labels overpopulate and overlap. Confirmed on both calls.
P1 Add a search bar below the "pick your city" box: search by city name, zip code, and radius, plus a "use my location" GPS pin. ~50-mile default radius floated.
P1 County → city list populates. Land on a county, the city list fills with that county's municipalities (Airbnb / real-estate zoom-and-list pattern).
P1 Cascade the new map to ALL pages. Only the homepage got the new map a week ago. Every other city/service page still shows the old single-left map.
P2 Close the north-of-Fort-Worth coverage gap. Keller, Justin, Tarrant/Denton are booming; people say "Fort Worth" but live in Keller. County + search fixes it — make sure those cities are reachable.
decided List view over fancy map for granularity. JR's steer: keep a high-level map as the cool entry point, let the list + search do the real work.

B Lead pipeline & Slack alerts (admin GHL)

P2 Label "Qualified" as a billing trigger. Suzanne writes the warning, make it red, fire/bomb/💲 emoji. It charges the contractor a credit. Contractors aren't in this pipeline, but the action bills them.
decided Keep the trigger as-is — NO "are you sure" confirm. Dan asked for one; team said no. It's a training issue; the 1-minute pull-back window is the safeguard. Just add the label.
decided 🔥 Recalled stage added to the admin pipeline. Order is New Lead → 🔥 Recalled → Contacted → Qualified → Routed → Billed. Red-flagged. Remaining work is the automations below.
P1 Recall trigger moves the lead into 🔥 Recalled + fires the owner alert. On a 48-hour no-action recall: move the lead into the Recalled stage and send the flaming SMS + email to the lead owner. Confirm both fire.
P1 Automation: New Lead → Slack. Every inbound lead posts to the New Lead Slack channel the moment it lands, so the team sees it for speed-to-lead. Include name, project type, source, and the contact-record link.
P1 Automation: 🔥 Recalled → Slack. When a lead drops into Recalled, post to the Recalled Slack channel on top of the flaming SMS + email to the lead owner. This is the "we're behind, grab it now" alarm.
P1 Connect Slack: New Lead + Recalled channels. Slack is added; Suzanne is wiring both channels so the two automations above have somewhere to post. Confirm each channel receives a test post.
decided Mute the New Lead channel, keep Recalled alerting. New Lead fires on every inbound and goes noisy fast; leave it as a scannable feed with notifications off. Recalled is the one that should actively ping people, so the team doesn't learn to ignore both.

C Contractor lead-funnel & billing

P2 Notify a contractor when their lead funnel is OFF for a while. "You're not receiving leads right now." Gentle nudge = you're not buying. JR: easy, good idea.
decided Rejected: the "6 hours to expiry" reminder. GHL already notifies and 48h is in the T&S. Do not build.
verify Confirm the pause / zero-credit nuances. Stays paused if manually paused, stays on if it was on. Verify in testing.

D Early-bird link & contractor-facing page

P1 Link the "for contractors" / early-bird page. It exists but isn't linked from anywhere. Katherine needs it NOW to send contractors before Monday.
P1 Get Dan a working hyperlink for the HFS owner (funding). His old one is dead. Also send him the schematic link.
decided Early-bird link shuts off Monday. After launch, recruitment moves to normal ads / social / booking links. No public contractor site — the funnel is gated (Uber "no driver website" model).
verify Confirm the thank-you page after email submit. On the contractor single page: "someone will contact you within X" → feeds the video + Facebook group. Matt flagged it felt like nothing happened on submit.

E Onboarding, timeline & SOPs

P1 Reconcile Katherine's onboarding schematic with Suzanne's. They've never been merged. Send Suzanne the flow maps and she builds them into the one unified schematic.
P1 Formalize the purchase → site-live timeline into an SOP. ~5 days working estimate, made granular so sales can answer "when does my site go live." JR called this one of the most important open questions.
P2 Decide the site-ready notification flow. Does the team get notified when a site is ready, or does the system email the contractor directly? Tied to when contractors get their GHL handed over.
P2 Re-audit and update all the mini-schematics before pushing live. Built incrementally; some are stale.

F Case studies & image verification confirm these are actually built

verify Case-study submission routes to admin for verification before going live. Suzanne said "I believe" — it was a speculation, not confirmed built.
verify Stock-photo / AI-image metadata check + admin flag is implemented. Suzanne: "I don't know if we've actually marked it." May only be conceptual right now.
verify Protect the payoff chain. Each verified case study → city+niche page → card → contractor's project page → mini site. The whole chain depends on the verify step working.

G Homepage "sticky moment"

P2 Build the garage-photo → 3 AI before/after generator in the homepage header (next few days). Upload a photo, get three renders, "I like #2," hooks them into browsing.

H Access & team

P1 Add all team members as users/admins on the GHL accounts. So the sidebar links (editor, lead billing, NPS) render instead of a "wah-wah" page. Suzanne saw names she didn't recognize.
P1 Get Matt access. His email setup isn't finished, so he can't get in yet. He's the self-taught technical tester who'll try to break things before clients do.
P2 Connect Matt with Suzanne one-on-one. Brian is the West-Coast / late-hours GHL backup.
P1 Send the dev-site link to the whole team. So they can click every button and send granular feedback (screenshots/snips). Wanted before Monday, not a hard deadline.
decided Guardrail: nobody touches GHL wiring without coordinating with Suzanne. It breaks easily. Also: don't edit the live Mendez mini-site while poking around.

I Keep in view

verify Confirm the one API issue JR said resolves "by tomorrow" is fixed. Everything else is essentially built and could go live now.
decided Homeowner site goes live to homeowners at cart open (~Jul 17) but the team wants it done Monday so nothing is being polished at the last minute.
decided Launch shape: mini group starts Monday, 12-day run, open cart July 17, war room goes official.
decided Don't let anyone frame the knowledge-base as generic point-and-click AI. The 3%-AI, sounds-like-Dan, voice-corpus pitch landed well and feeds a future chatbot upsell.