WTP × Carlile Advisors — July 22 Meeting Roadmap

Meeting: Wednesday, July 22, 2026, 1:00–3:30 PM ET Format: In-office work session Attendees confirmed: Tucker Carlile, Chris Thomas Prepared: July 21, 2026

The headline

We have moved past the audit/demo phase and now have real operating systems in use. The best next move is to finish August social production, make the Social Engine trustworthy for Alexa, and launch one measurable read-only ads exception loop. Do not open five new workstreams tomorrow.

What Tucker should say first

Since our July 15 call, the August social plan has moved from a five-client pilot to a full managed-roster production board. We now have 57 accounts and 240 August drafts, using 219 prepared client images, plus a structured review-and-revision loop. The goal today is to get the remaining inputs and decisions needed to finish August, make the workflow dependable for Alexa, and agree on one next system with measurable ROI.

Current-state scorecard

Green — shipped or working

• Original AI Audit + Roadmap delivered; relationship moved into implementation.
• Claude Team and core connectors established.
• Social Engine foundation exists: onboarding, asset handling, generation, editing/review, feedback storage, and SocialPilot integration path.
• August managed roster generated: 57 accounts / 240 draft posts.
• Review board live: https://wtp-august-pilot.pages.dev.
• 219 client images prepared for the board; 21 original cards were initially image-needed placeholders.
• First review pass operationalized: 57 comments indexed, 33 before/after comparisons, 30 alternative posts across 17 clients, and 11 new/repaired media files. Originals are preserved; nothing has been published.
• Rebecca's daily-operator foundation exists around email/calendar, Composio, and a leads/clients/timeline sheet.
• Ernie's Google Ads/MCC connection and tools exist; one analysis surfaced roughly $1,200/month in apparent keyword waste.
• Meta Ads MCP was reported connected by Chris on July 15.
• Claude /remote-control was enabled for Ernie on July 20.

Yellow — working, but not production-complete

• The August board is generated, but final approval, scheduling, and publishing are not complete.
• Alexa's feedback is being captured, but the main app still needs to prove that client-specific feedback reliably changes the next output.
• Missing/conditional source material remains: real testimonial language, August blog URLs, media for photo-thin accounts, and WTP's own service-post details.
• The first reviewer pass covers the early alphabet through Kennesaw plus global issues; the rest of the 57-account board still needs review ownership and a deadline.
• Drive structure is agreed conceptually, but Content for Claude / final photos / final videos / final deliverables is not verified across the roster.
• Rebecca's daily brief needs a live validation pass: correct PMAX Gmail, RB2B connection, sheet writes, and scheduled run.
• Google Ads has proof of value, but no verified fleet-wide scheduled exception report yet.

Red / blocked on decisions or inputs

• Supabase Free → Pro: requested July 15 and followed up July 17; no email approval or completed upgrade is verified. Do not claim it is complete.
• Cross-practice similarity rule: decide how similar dental topics may be across practices before they must be differentiated.
• Thin-account volume rule: decide whether one- and two-post accounts should remain at contracted July volume or receive additional August posts.
• Assign owners for testimonial text, blog URLs, missing/approved media, and WTP service details.
• Confirm the operating system of record: app/review board for creation and approval, with Asana/SocialPilot handling which downstream statuses.
• Confirm API/model cost ownership and security cleanup, including old shared SocialPilot credentials.

Recommended outcomes for the 2.5-hour session

Leave with five decisions, not another idea list:

1. August definition of done and target date.
2. Named owners for every missing testimonial, blog URL, photo, and remaining review.
3. Approval for Supabase Pro, or an explicit alternative capacity plan.
4. A one-week Social Engine reliability-hardening scope before new features.
5. Selection of one next measurable loop: read-only Google/Meta ads exception reporting.

Working agenda

1:00–1:15 — Align on outcomes

• Re-state the headline and show the current-state scorecard.
• Ask Chris: “At 3:30, what would make this session feel like a win?”
• Confirm that August completion is priority one.

1:15–1:55 — Finish the August operating plan

• Open the 57-account review board.
• Show three proof points: a strong untouched account, a revised caption/testimonial, and a repaired photo-less account.
• Decide the cross-practice similarity rule.
• Decide whether thin one-/two-post accounts keep contracted volume.
• Assign the remaining board review and deadline.
• Assign source owners:
• testimonials;
• August blog links;
• missing/approved client media;
• WTP service-post details.
• Agree on the exact handoff: generated → Alexa review → final approval → SocialPilot scheduling.

1:55–2:25 — Make the Social Engine trustworthy

• If possible, bring Alexa into this block.
• Test one concrete feedback instruction end-to-end.
• Approve a narrow reliability sprint:
• truthful approval/save states;
• visible failed scheduling/push jobs;
• retry and exhausted-job handling;
• durable client rules for logos, overlays, photos, and tone;
• operator walkthrough for Alexa.
• Decide whether the review board is the temporary August control surface while the main app is hardened.

2:25–2:50 — Infrastructure and source-of-truth decisions

• Upgrade WTP Supabase to Pro, or explicitly defer with a capacity limit.
• Approve a 10-client Drive-structure pilot before scaling the folder standard across the fleet.
• Confirm model/API cost ownership.
• Confirm what lives in the app, Asana, Drive, and SocialPilot.
• Capture WTP's definitive verticals/services and SEO rules still needed for the content engine.

2:50–3:15 — Choose the next ROI loop

• If possible, bring Ernie into this block.
• Recommend a read-only exception report, not another dashboard:
• nightly Meta lead-measurement/tracking checks;
• weekly Google Ads waste/opportunity scan;
• account, issue, evidence, estimated impact, and recommended next action;
• human approval before any account changes.
• Use the ~$1,200/month keyword finding and the 28-of-32 Meta measurement finding as proof points.
• Select a 5–10 account pilot and name the report recipient/cadence.

3:15–3:30 — Lock owners, dates, and success measures

• Recap every decision aloud.
• Put owner and due date beside each open item.
• Agree on the next weekly checkpoint.
• Define the month-end scorecard.

Recommended 30-day roadmap

Week 1 — Close August

• Resolve the two content-policy decisions.
• Collect testimonial/blog/photo/service inputs.
• Finish review of the remaining board.
• Apply/approve revisions and schedule the first completed batch.
• Upgrade Supabase or cap the rollout deliberately.

Success measures: approved/scheduled post count, accounts completed, missing inputs remaining, Alexa review time per account.

Week 1–2 — Harden the Social Engine

• Fix reliability gaps before adding features.
• Prove a feedback instruction changes the next output.
• Make failed saves/pushes visible and retryable.
• Record a short operator walkthrough for Alexa.
• Decide the temporary and long-term system of record.

Success measures: save/push failure rate, successful retry rate, regeneration acceptance rate, operator time saved.

Week 2 — Standardize source assets

• Pilot the Content for Claude folder convention on 10 representative clients.
• Include final photos, final videos, final deliverables, testimonials, services, and client rules.
• Expand only after the pilot is easy for Alexa/Andrea to maintain.

Success measures: percentage of pilot clients with complete final assets, time to find an approved asset, rejected/raw-asset incidents.

Week 2–3 — Validate the internal operator loops

• Run Rebecca's morning brief live and verify PMAX Gmail, calendar, RB2B, sheet updates, and scheduled execution.
• Validate Ernie's Ads and form-monitoring loops with dry-run/read-only output.

Success measures: successful scheduled runs, useful actions produced, stale/duplicate items, manual cleanup required.

Week 3–4 — Launch one fleet audit MVP

• Pilot nightly Meta measurement checks and a weekly Google Ads exception report on 5–10 accounts.
• Deliver a short exception report to Chris with evidence and estimated impact.
• Keep all changes human-approved.

Success measures: accounts checked, issues found, estimated waste/risk caught, false positives, time-to-resolution.

Parking lot — explicitly not the next 30-day focus

• RB2B/Leadfeeder/Streak unified sales dashboard beyond maintaining the current connectors.
• Full client reporting rebuild.
• Video repurposing platform.
• Direct-mail/Lob system.
• Lacrosse film product.
• Broad Asana automation or replacement.
• New self-serve client intake portal.

These are valid later lanes, but opening them now would dilute August completion and production reliability.

Questions Tucker should ask Chris

1. Is the July tracker volume the contractually correct August target, even when an account has only one or two posts?
2. How much repeated topic structure across dental practices is acceptable if the brand voice, examples, and photos differ?
3. Who at WTP owns the final source of truth for testimonials, blogs, and approved photos?
4. Can we upgrade Supabase to Pro today?
5. For August, should the review board be the approval control surface while the app is hardened?
6. Which 5–10 ad accounts should be in the first exception-report pilot?
7. Who should receive the report, and what threshold deserves an immediate alert?
8. What single outcome would make the next 30 days obviously worth the engagement?

Tucker's guardrails

• Do not claim all 72 dental clients or the next 70 clients are fully onboarded in the application.
• Distinguish the generated August review board from production app onboarding and scheduling.
• Do not allow generated testimonial text to masquerade as an exact customer review; require an approved source.
• Keep Google/Meta automation read-only or dry-run until WTP explicitly approves changes.
• Do not leave without owners and dates.

Evidence and links

• August board: https://wtp-august-pilot.pages.dev
• Meta audit: https://pmax-wtp-ads-audit.netlify.app
• July 20 review record: feedback/2026-07-20-before-after-review.md
• August source: social-engine-build/august-2026/
• July 8 onsite analysis: notes/2026-07-08-full-transcript-analysis-chris-rebecca-ernie-alexa.md
• Social app reliability review: notes/2026-07-02-social-app-pre-onsite-review.md
• Calendar: Chris accepted the July 22 1:00–3:30 PM event on July 21.