1 Today at a glance
- Lead hand-off is fixed and proven. A test lead ran the whole path — tagged qualified → queued → texted to Dan — with phone-carrier confirmation. Before today, no lead had ever made that trip automatically.
- Two new Facebook pages are live: Texas statewide + Austin concrete-leveling pages (one page per state is the new scaling play — ~15× faster than per-city pages).
- The 30-day focus is locked. 96 unrelated tasks are parked until Aug 27, every dashboard and the task board now hide them, and the war-plan page is live.
- The task board (Linear) is live with two-way sync. 28 active cards, plain-English titles, agents can only pick up work you've explicitly promoted.
- The books are clean: every session from today is saved to the brain and backed up (1,645 of 1,645 in the archive), and the task helpers no longer leak parked tasks anywhere.
2 Your links — everything in one place
Start here
Scoreboards
Fresh today — needs your eyes
Reference docs
| What | Where |
|---|
| Operating playbook (how the whole business runs) | Documents/Claude/02-Areas/Team/Internal Docs/operating-playbook/index.html |
| Lead outcome definitions (what counts as qualified, transferred, won) | 01-Projects/St_Pierre_Digital/Internal-Docs/qualified-conversation-outcomes-2026-07-28.md |
| CRM tag audit (what tags actually exist vs what they should be) | 01-Projects/St_Pierre_Digital/Internal-Docs/ghl-tag-audit-2026-07-28.md |
| Task-board build plan (phases still open: feel test, old-tool retirement, agent identity) | stpierre-linear-workspace-sow.pages.dev |
3 The plan — one SOW, four steps
The goal: concrete-leveling leads flowing to Dan every day — 25 hand-offs a week. Everything below serves that; everything else is parked until Aug 27.
| Step | Outcome that proves it | Who |
|---|
| 1 · Prove delivery (this week) | A real customer message reaches Dan's phone within 5 minutes, three days straight | You + agents |
| 2 · Scale volume | Ad sheet live, Dallas budget confirmed, Texas + Austin pages open for business, next markets minted | You approve, agents build |
| 3 · Keep it healthy | Daily ad batch, fresh reply drafts, green morning health report — without you touching anything | Agents |
| 4 · Package it | Dan's setup becomes a reusable checklist so client #2 onboards in days, not weeks | Collins (gated) |
Sections 4–6 below are the complete task lists for each step, with everything each person needs.
4 Waiting on you — calls, clicks, approvals
Phone (revenue today)
- Call the three leads that have sat cold since Jul 21: Cindy, Richard, Ann (they're on today's call sheet), and reply to the three unanswered Level King leads.
- Send the four ready-to-go follow-up drafts before the reply window closes tomorrow (Jul 29).
- Text Dan for the two missing pieces: his follow-up-software key + his exact service area. This unblocks lead delivery into his system and widening ads to Fort Worth / Arlington / Grand Prairie.
Clicks (15–20 min, guides ready)
- CRM fixes — the audit pack has numbered click-paths: confirm the "qualified" tag step, delete or fix the dead auto-transfer automation (it has no trigger and has never fired — the new rail routes around it), add the phone+ZIP gate, clear 4 stale review tags.
- Facebook — claim the new TX and ATX pages into the business account, then assign the messenger system user to all four concrete-leveling pages. After that, agents dress the pages (photos, details) automatically.
Approvals (one sitting)
- Review + activate the concrete-leveling ad sheet (built, paused).
- Confirm the Dallas campaign's budget intent — it's live at $100/day but still named "$50/day".
- The standing queue: remove the "I'm a real person" line from client bots · landing-page form fixes (tracking + sign-up question placement) · turn on call recording in the CRM · decide cold-email capacity · lift the manual-send hold when ready.
- Submit the Facebook app review before the trial deadline — this keeps the client bot running.
5 Running on autopilot — agents handle these
- In progress: 3-day watch on the Dallas client bot — proving one real lead runs every step and reaches Dan within 5 minutes.
- Daily ad batch for each active client + our own account — staged paused with screenshots for your OK, never self-launching.
- Reply drafts kept current for every live lead (sending stays manual until you lift the hold).
- Morning health report checked; anything red gets fixed and logged with an undo.
- Client messages cleared and check-ins hit daily.
- Next market pages minted as Facebook's daily limit allows: Oklahoma City next, then Tulsa.
- New ad creative wave + bot qualification tune (~55% → 70%) staged as approval packs.
- Page dress-up (photos/details) for all four pages — blocked until you do the Facebook claim + assign clicks above.
6 Collins' build list — gated until you say go
Four cards are labeled for Collins on the task board. Nothing gets sent to him without your explicit go (scope + pay + go, per your rule).
- Map today's client-setup steps — what's built vs missing
- Turn Dan's setup into a reusable checklist for the next client
- Design the setter tracking + coaching system
- Build the daily coaching brief for each setter
Heads-up from today's audit: these cards are not yet send-ready. Each has a one-line goal but no links, no access notes, and no background — Collins can't see your internal notes, so he couldn't finish any of them from the card alone. Before sending, each needs a context pack: relevant links (playbook, boards, call-data source), what access to request, and the definition of done. Say the word and I'll draft all four packs for your review.
7 Board health check — your three questions, audited
| Question | Verdict | Detail |
|---|
| Plain English, jargon-free? |
27 / 32 pass |
All 28 active cards read clean; code names live only in collapsed technical notes. Fails: 1 old technical card (the Facebook-login checkpoint one, parked) + Linear's own 4 sample onboarding cards — worth archiving. |
| Does each card link its notes, deliverables, SOW? |
No |
No card links any deliverable or plan doc. Every card has a one-line definition of done + an internal reference id. AI agents can follow that id into the brain; a human can't. Top ~10 cards should get 2–3 links each (this page makes that easy). |
| Could Collins execute his cards alone? |
Not yet |
All four Collins cards fail the hand-off test (see section 6). Fix = context packs, ~30 min of work, ready on your go. |
| Are AI-ready cards complete? |
Pass, with caveat |
7 agent-ready cards all carry a definition of done + brain reference id, and agents resolve full context through that id. Caveat: the card alone isn't enough without brain access — fine for our agents, but add links if outside tools ever pick them up. |
| Everything non-Dan parked? |
Mostly |
96 tasks parked and hidden from every surface (verified zero leaks). Borderline calls still active: "get our own ads running again" + "ship our own daily ad batch" (that's marketing your agency, not Dan's leads) and the two landing-page form approvals. Your call: park them to Aug 27 or confirm they stay. |
8 Cleanups & technical notes
- 15-min housekeeping queue: fix the stale brain copy in the home folder (root cause found today — the page-publishing tool keeps regenerating it), commit today's uncommitted code changes, and lock down the client report link before client #2 onboards.
Technical notes (for agents — safe to ignore)
- Handoff rows written today: 2004–2008 (5 rich captures) + id backfill on row 1970. All carry real harness session ids (local_<uuid>).
- ~/brain.py shadow root cause: publish-page / resource-doc-creator Step 0 bootstrap writes system_files.brain_bootstrap to ~/brain.py — correct in Cowork sandboxes, harmful on the real Mac. Skill fix queued.
- Meta write path: system-user token CAN write to the concrete-leveling client ad account (act_3289323034532141); the permission block applies to the B2B account only. Memory updated.
- CRM workflow copies on record are stale June templates — fresh grabs via audit-pack click-paths (Akash-only in the CRM UI).
- Linear sync: echo guard disabled until agent OAuth identity (P7); receiver workflow 3xeSHn6EYegPjG6a; map-aware upsert fixed duplicate rows.
- Rule reaffirmed today: no transfer-rail fix counts until an end-to-end synthetic-lead test with carrier delivery proof passes.