Execution Plan — everything open, in one list

Friday, July 31, 2026 · Replaces the July 29 version. Built from every open workstream, so nothing lives anywhere else.

Newer page for “what’s next”: later on July 31 a follow-up priorities plan went live at stpierre-domino-sow-docs.pages.dev — for current priorities, start there. This page remains the July 31 close-out list: the day’s decisions, hands-on tasks, and everything delegated or dated.
How to use this page. This is the master list of everything open in the business today. Colored tags say who acts: needs a person · AI handles it · read if needed. Sections expand when clicked; the ★ boxes are the standing recommendation — the default move if nobody overrules it. Any dotted underlined word opens a plain-English explanation in a side card. Hands-on tasks have full click-by-click steps on the companion Unblock List, but each item here carries enough context to stand alone.
New here? The business in one paragraph

stpierre.ai (Akash’s company) runs Facebook ads that get homeowners asking for concrete-repair estimates. An automated chat assistant (Jordan) collects each homeowner’s details and phone number, and those ready-to-call homeowners (“leads”) are handed to Dan, a Dallas concrete-leveling contractor — the paying customer. A second bot (Jean) texts contractors who apply to become clients themselves. AI assistants (“the agents”) do all the software work in the background; anything tagged needs a person exists because money, logins, or certain screens require human hands. The goal of the current sprint: first stpierre.ai cash collected by August 16.

The recommended order today

1. Make the big ads decision (below) → 2. Reply to the 3 waiting homeowners → 3. Approve the chat-assistant fix → 4. Run down the quick yes/no list. Everything else is delegated to the agents or has a date on it.

Time needed from a person

About 20 minutes of decisions plus about 25 minutes of clicks and messages. The agents take everything else the moment someone says “go.”

Why this list looks like this

The thing holding the business back is signed-client cash — not tools, not dashboards. So every item here either produces a sales conversation, unblocks the flow of leads, or is deliberately parked with a date.

1 · Money on the table — do first; the only block that can produce revenue today needs a person

Reply to the 3 homeowners waiting in Facebook Messenger

Subhash Bhatia · Terry Williams · Mei Flower (Plano — wants an estimate on lifting a concrete step, offered to send photos).

Why: none of them left a phone number, because the chat assistant asked for ZIP code before phone number. Messenger is the only way to reach them now. The moment any of them gives a number, they flow to Dan automatically.

The exact message to paste (with a copy button) is on the Unblock List, task 1.

Approve the chat-assistant fix — the root cause of those three lost numbers

Why: the fix changes the questions the bot asks real homeowners — phone number first, photos optional, city can never block a lead, hand-off fires as soon as there’s a valid number. Because it changes what real customers see, it won’t ship without an explicit approval.

The full fix pack is staged for review at stpierre-approval-pack-docs.pages.dev.

★ Approve it as staged. This also settles an older open question about the hand-off wording — it’s the same fix, one approval covers both.

The Dan block — one text, one paste, one payment

  • Send Dan his pre-written text — asks for his booking link, has him check and delete the test cards on his board, and nudges him about one lead with no outcome. (Unblock List task 2, message embedded there.)
  • Paste the stricter “is this a real lead?” check into the chat assistant’s review step. The loose version currently in place calls ~90% of conversations qualified when the true rate is ~69% — every scoreboard number is inflated until this is pasted. (Unblock List task 5, Job E — exact text and clicks embedded.)
  • Pay the $40.01 unpaid balance on the Facebook ad account (a card charge failed). Facebook cuts off ad delivery over unpaid balances, and this is the account Dan’s leads come from. (Unblock List task 3.)

Confirm the call-backs from July 29 actually happened

Danny LaPorta (469-261-3962, call after noon) · Sam Etoum · Spencer Johnson. If any of them is still uncalled, they outrank everything below on this page — they are real homeowners who may never have been contacted.

2 · Quick decisions — one word each; every answer unblocks an agent instantly needs a person

Decision 1 — Facebook can’t tell which ad produces which lead. Approve the fix?

Why it matters: all 30 live Dallas ads report their leads to Facebook in a format Facebook can’t match back to the specific ad. So Facebook’s ad system is optimizing blind — it can’t learn which ads work and put money behind them. The fix is one small change to how the reporting message is formatted, ready to ship.

★ Approve the fix. Also: a second tracking container was set up long ago and has never received a single event — ★ remove it from the ads rather than trying to wire it up.

Decision 2 — Dan’s report page shows two numbers that aren’t real

Why it matters: the “Appointments booked” and “Jobs won” tiles on Dan’s private report are based on one number someone typed in by hand on July 19 — no live data feeds them — and the page stamps itself “Updated today” using the viewer’s clock. If Dan ever checks, it reads as dishonest.

★ Relabel both tiles “not tracked yet” and apply the ready-made fix that makes every page show its real last-updated date. Build a real feed only if Dan asks for one.

Decision 3 — Two automatic-message systems contradict each other. Which rule wins?

Why it matters: the house rule says pre-scripted funnel messages may send automatically once a human has read the copy once; anything unread stays off. Right now Jean’s follow-up texts (read and approved) are not automated yet, while a pack of 12 emails nobody has ever read is armed and will fire at the next person who books a call.

★ Apply the house rule both ways: the approved follow-up texts get built (Unblock List task 5, Job A), and the unread 12-email pack gets switched off until its copy is read (Job B — the single most urgent click in GoHighLevel today).

Decision 4 — Dallas ads cleanup (after the big decision above)

  • Budget: the campaign named “$50/day” actually spends $100/day. ★ Relaunch it at a true $50/day — matching the pause-branch plan.
  • Duplicate: an accidental duplicate ad set exists — paused, but loaded with 16 ads and one toggle away from doubling spend. ★ Delete it.
  • Audience exclusions: Akash said no to these once — confirm that still stands.

Decision 5 — Dashboard cleanup: say “go” once

Why it matters: an audit of all 27 reporting pages found four retired pages still serving June data stamped “updated just now,” the sales page’s data feed dead since about July 26, two pages disagreeing about the cash position (one says −$2,312, another +$1,653), and the ad landing pages showing a blank box for 8 seconds before the form loads.

★ Say “go” on the full cleanup: redirect the four dead pages to their live replacements, cut the daily list to 8 pages, repair the sales-page feed, put a real “last updated” banner on everything, and fix the slow-loading form. One “go” covers the whole pass.

Decision 6 — Jean (the contractor-side text bot): four approvals, then three builds

  • Approve the five follow-up texts (already drafted; sending 5 minutes to 3 days after someone applies) — including the decision to skip the “text STOP to opt out” line (applicants opted in; STOP still works automatically).
  • Approve the “introduce yourself as Jean” wording · confirm contractor texting stays on the CRM’s own texting (no iMessage) · add the rule “never invent facts — say you’ll check with Akash,” then re-run the bot’s 35 automated tests.
  • The three hands-on builds this unlocks (follow-up sequence, booking-calendar fix, escalation receiver) are Unblock List task 5, Jobs A–D — full steps embedded there.
3 · What the AI agents are handling — no input needed AI handles it

These are running now or start the moment the decisions above land. Listed so nothing is invisible — not because anyone needs to act.

  • Stuck-lead bug: leads released from “parked” stay frozen at “needs review” forever — three real people (Cindy, Richard, Rocky) were affected.
  • Honest scoreboard: the hand-off counter reads 25, but 12 of those were internal test runs — filtering them out (true count ≈ 10–13 real people).
  • Overzealous ZIP filter: a filter silently deletes any lead whose ZIP code isn’t from the Dallas area before it’s even saved — being removed.
  • Contact-sync speedup: the job that syncs contacts takes ~3.5 minutes and times out; being rebuilt to run in ~2 seconds.
  • Silent alarm: the internal alert function writes to a database table that doesn’t exist — meaning every alert ever “sent” failed silently. Being fixed.
  • Dead data pulls: the 7:00 AM ads-data pull has been dead since July 27, and the bank feed is two days stale — both being repaired.
  • Log audit: several automations were configured to keep no execution logs, which once hid a week of failures — auditing all of them.
  • Two wrongly-closed homeowners (Bradford Court and Mark Cope, filed “not interested” in error) — being re-opened.
  • Stage-name fix: the contractor-side forwarder still speaks last week’s pipeline stage names; the fix is built and waits only on a one-time human review of the change.
4 · Verify — things claimed done but not yet proven read if needed

House rule: distrust green checkmarks. Each of these says “working” somewhere, but hasn’t been proven with real-world evidence yet.

  • Did the 7 test alert texts from (626) 325-0175 physically arrive on Akash’s phone? The software says delivered; the phone is the truth. (Unblock List task 8.)
  • Tracy Justice Serio — a lead who was stuck one pipeline step too early; the patch that should have fixed her path is unproven.
  • The next real lead’s hand-off text should name the ad it came from — never yet confirmed on a natural (non-test) lead.
  • The automation platform’s monthly run allowance was at 80% of its limit — formal re-check due August 1 (tomorrow).
  • The weekend scheduled check-ins froze silently twice — watch this Sunday’s run.
  • A separate Facebook data relay has been silent since June 22 — different pipe from the fix in Decision 1; needs its own look.
5 · Dated housekeeping — parked on purpose, each with its date read if needed
  • Aug 1 — re-check the automation platform’s monthly run allowance.
  • Aug 13–16 — sprint review; the next 6-week goal gets set there, not before.
  • Aug 15 — cancel the Manus subscription (first spend its remaining paid credits on the three prepared research jobs).
  • Aug 20 — cancel the Adobe subscription (after finishing the video-captioning backlog that needs it).
  • Aug 23 — record the builder-vision walkthrough video while the Loom subscription is still paid (script already written).
  • Notion cleanup — three approvals waiting: re-check seven old chatbot bugs, save the still-true client facts, archive four dead pages.
  • Telegram group — create the HQ group and make the bot an admin; last step before the automated morning brief can be wired up.
  • 13 client access keys — needed for a tracking-consolidation project; nothing about Dan depends on it, so it waits.
Where this list came from read if needed
  • Built by sweeping all five open work sessions today (each one closed after sweeping): a dashboard-freshness fix, an appointment-sync investigation, an ads-tracking audit, a day-close operations sweep, and the 27-dashboard audit.
  • Also mined: the July 29 version of this list (34 items), the last three weeks of session hand-off notes, a prioritization audit, and the pre-written ads-pause battle plan.
  • Already finished and deliberately not repeated here: Rocky Sanders’ lead delivered · Cindy and Richard texted through · Tim Wines and Danny LaPorta handed to Dan · the lead hand-off pipeline rebuilt and proven end-to-end on July 28.
Technical notes (record-keeping identifiers)

Session sweeps → brain session_handoffs rows 2059–2063. Prior consolidations: Jul-29 close-out SOW · handoffs 2039–2058 · tripwire battle plan at _scratch/deliverables/2026-07-28/tripwire-battle-plan.html. Live database checks run Jul-31. Sprint 5 goal: first SP cash collected by Aug 16.

Companions: The Unblock List (the hands-on tasks with every step embedded) · First $100K in 100 days (the growth plan and the $1M math) · The Daily Operating Rhythm (how the day is structured) · Today’s Map (every document from today, explained).