Strategic Brief · Internal · Account Management

The 40 to 1 Account Management Framework — AICRO Synthesis

Synthesis of a 4-week 4-week consulting engagement (Feb 2026, paused March 2026, April reengagement planned) on running productized account management at agency scale. Re-ranked April 26 against AICRO's actual state — Client Health Dashboard, daily pulse, 11-client portfolio.

April 26, 2026 · For Josh Kulchin and the AICRO team · 78 framework prescriptions evaluated · top 10 actions re-ranked for AICRO reality, with the client-comms Slack layer as the headline lever

★TL;DR — The Framework in One Breath

Core thesis

One CSM can responsibly own 30 to 40 client accounts only if the day, the week, the dashboards, the tasks, and the management oversight are all engineered for it. The 40:1 ratio is what the system enables, not what willpower achieves. Take any one piece out — daily structure, 5-area visibility, task-driven SLAs, 42 automations, or performance-based comp — and the ratio collapses to 12-15 clients per CSM and churn climbs.

Capacity

40:1

Clients per CSM — drops to 25-30 with new hires

Automations

Across 8 categories in the flagship SOP

Onboarding SLA

14 days

Paid quote → first campaign live

Send checkpoint

1.5K → 2K

Framework: 1,500 sends. AICRO uses 2,000 in practice — adopted threshold for the auto-Recreate alert.

Visibility areas

Inbox, tasks, performance, churn, revenue

Reply benchmark

≥1%

Internal floor — deliverability signal

What this brief delivers

A snapshot of where AICRO stands against every framework prescription (32 Have / 17 Started / 27 Missing / 2 N/A).
Nine pillar deep-dives covering communications, onboarding, operational structure, KPIs, the 42-Zap automation architecture, enrichment, LinkedIn/InMail, tooling, and team comp.
Top 15 ranked automation candidates with effort estimates, framework evidence, and PRD seeds — drawn from a full 78-entry catalog at opportunities/_index.md.

1Engagement Overview

What was delivered, the cadence used, and the open thread left for April.

The engagement ran February 2026 as a 4-week consulting project: one pre-engagement scoping call (Jan 28) followed by four weekly working sessions (Feb 4 / 11 / 18 / 25). It was paused after Week 4 with an April 2026 reengagement planned.

Delivery cadence per session

Pre-call talking-points doc — sent the day before. Comprehensive walkthrough of what would be covered.
Live walkthrough call — 60-90 minutes, recorded.
Tabbed Q&A doc — answers to Doug and Josh's specific follow-up questions, each on its own tab.
Final SOP doc — shipped within ~7 days, with embedded Loom walkthroughs of every Zap and process.

Topics by week

Week	Topic	Key deliverable
Pre-engagement (Jan 28)	Scoping	Consulting agreement signed Feb 2; Month 1 scope doc
Week 1 (Feb 4)	Client Communications Framework	Comms cadence + 6 production-ready email templates + QBR Gamma deck + 12-tab Q&A
Week 2 (Feb 11)	Client Onboarding Deep Dive	Day 0-14 playbook + 17-section intake form + ICP-to-7-campaign mapping
Week 3 (Feb 18)	Operations, KPIs, Dashboards	40:1 CSM Structure SOP with the 42 automations across 8 categories — the flagship document
Week 4 (Feb 25)	Data Enrichment + InMails	16 evergreen Clay playbooks + waterfall pipeline + InMail avatar architecture

Open thread flagged for April

The Week 4 doc has a header "Template organization and reuse strategies" with no content underneath. The consultant flagged this as the priority to revisit when the engagement resumes. AICRO has 16 additional questions surfaced during synthesis — see Section 13 for the full April agenda.

2Implementation Status — The Snapshot

Where AICRO stands across 78 framework prescriptions, plus the 5 P0 gaps and 3 places we already do better.

Have

32 (41%)

Functionally working today

Started

17 (22%)

Partial / in flight / PRD'd

Missing

27 (35%)

Gap; would need to be built

N/A

2 (3%)

Doesn't apply at AICRO scale

Pillar-by-pillar status rollup

Pillar	Have	Started	Missing	N/A	Total
1 — Communications & Cadence	5	6	2	0	13
2 — Onboarding	1	6	3	0	10
3 — Operational Tracking	8	7	4	0	19
4 — Underperformance & Triage	6	3	3	0	12
5 — Tooling & Productization	11	1	9	2	23
6 — Enrichment & Sourcing	3	7	9	0	19
7 — LinkedIn / InMail	4	2	9	1	16
9 — Team & Compensation	4	6	9	1	20
Automation SOP (the 42 Zaps)	6	14	22	0	42

AICRO-reality top 5 P0 — re-ranked April 26

Monday Brief auto-Slack to per-client channel — branded "AICRO Reporting" app posts each Monday 9am ET to #{client}-weekly: This Week's Focus / Active Campaigns / Last Week at a Glance / Needs Your Attention / portal link. Headline AICRO lever — proactive client comms at scale.
Friday Wrap auto-Slack to per-client channel — same app posts Fridays 4pm ET: What We Delivered / This Week's Numbers / Hot Leads / On Your Radar / Coming Monday. Closes the weekly loop.
Mandatory 3-question onboarding capture — Josh is rebuilding Typeform now; add three required fields ("What does success look like at 90 days?" / "Biggest concern?" / "How will you measure ROI?") and store as required Airtable fields. Zero-marginal-cost while in flight.
No-Active-Campaign Slack alert + auto-task (Auto SOP #23) — the Client Health Dashboard already detects this state; wire a #aicro-ops ping plus an Airtable "Build replacement" task on the GTME.
2K-send Auto-Recreate task + Slack ping (Auto SOP #21, threshold corrected to AICRO's 2K) — at 2K sends with <1% reply or >3% bounce, auto-create Recreate Campaign task with 24h SLA + ping owner.

Combined effort: ~3-4 weeks for items 1-2 (Slack app + data pipeline), ~12 hours for items 3-5. Expected effect: client-perceived service quality jumps materially while internal accountability tightens. Items 6-10 in Section 12.

Top 3 places AICRO already does better

Custom MCP architecture for tool ecosystem. 240+ AI-callable tools across Supabase + Airtable + EmailBison + HeyReach + Google Workspace, type-safe, per-client credentialed. the framework runs on Zapier glue — structurally less powerful at scale.
Attribution rigor. AICRO's attribution-report skill produces triple-method full-funnel attribution (direct + influence + CRM continuous), CRM-agnostic, deal-level proof. the framework relies on lead counts.
Knowledge-graph compounding via three-layer architecture. L1 atomic concepts → L2 strategic docs → L3 domain ops. the framework relies on Google Docs + GetGuru, which compound slowly.

"Started" lines worth finishing first

17 prescriptions are partially implemented. Five highest-impact to push across the line:

Round-robin GTME assignment from HubSpot signed-quote (today: manual)
Underperformance auto-Recreate task (today: documented in alert-specs.md, not built)
Campaign-brief lifecycle PRD (today: spec in 02_product/prds/2026-03-12-campaign-brief-lifecycle.md; not shipped)
Onboarding "expectations + success criteria" required Airtable fields (today: KPI target captured, success def is freeform)
Day-of-week internal call cadence (today: /gtm-standup exists, day topic not enforced)

3The 40:1 Thesis — How One CSM Holds 30 Clients

The math, the architecture, and the daily workflow.

The math

A CSM doing 14 clients reactively spends ~30 min/client/week direct + 60 min/client/week communication = 21 hrs/week. Workable with overhead.
A CSM at 40 clients without structure would need ~60 hrs/week. Impossible.
The framework's automation SOP eliminates 10-15 minutes per client per week of admin work — across 40 clients, 6-10 hrs/week saved.
The day-structure rule (mornings comms, afternoons execution) recovers ~5-10 hrs/week of context-switching loss.
Cumulative recovery: 11-20 hrs/week per CSM — that's the 40:1 ratio.

The architecture (4 interlocking parts)

Daily Structure SOP — mornings communication, afternoons execution, end-of-day form. No call after midday unless emergency.
Management Oversight SOP — 5 visibility areas (inbox, tasks, performance, churn, revenue) with daily review cadence. Topic-per-day weekly calls.
Task-Driven Accountability — 100% of work flows through Airtable tasks with explicit SLAs (24h recreate, 72h normal, 14d onboarding). Round-robin assignment.
Performance-Based Comp — bonus eligibility tied to revenue under management, churn rate, EOD compliance, missed calls. Makes the tradeoff mechanical.

The CSM's daily workflow

flowchart TD Start["☀️ Start of day
(typically 9 AM)"] Morning["MORNING BLOCK
Communication & Clearing"] M1["1. Inbox Zero
All emails answered"] M2["2. Batched Calls
Onboarding · Strategy
· Churn · Billing"] M3["3. Aircall Fast Escalation
Bypass async delays"] M4["4. Loom > Calls
Save 2-3 calls/week"] Lunch["🕛 Hard cut at 12 PM
No calls after midday"] Afternoon["AFTERNOON BLOCK
Deep Work / Execution"] A1["1. Clear delayed tasks"] A2["2. KPI-triggered
campaign reviews"] A3["3. Proactive improvements"] A4["4. New campaign builds"] A5["5. Strategic Loom pitches"] EOD["📋 End-of-Day Form
(daily accountability)"] Manager["👀 Manager reads
EOD form next morning"] Start --> Morning Morning --> M1 Morning --> M2 Morning --> M3 Morning --> M4 M1 --> Lunch M2 --> Lunch M3 --> Lunch M4 --> Lunch Lunch --> Afternoon Afternoon --> A1 --> A2 --> A3 --> A4 --> A5 --> EOD EOD --> Manager classDef morning fill:#E0F2FE,stroke:#21A8F2,color:#0F172A classDef afternoon fill:#FEF3C7,stroke:#F59E0B,color:#0F172A classDef pivotal fill:#D1FAE5,stroke:#10B981,stroke-width:2px,color:#0F172A classDef text color:#0F172A class Morning,M1,M2,M3,M4 morning class Afternoon,A1,A2,A3,A4,A5 afternoon class EOD,Manager,Lunch pivotal class Start text

Mornings communicate, afternoons execute, EOD form closes the loop. The structure is what makes 40:1 possible.

The framework's load-bearing rule

"You can't automate management, and you can't automate CSMs actually doing their work properly. Dashboards help show what's happening, but they don't stop things from slipping through the cracks." Dashboards expose. Calls and the EOD form enforce.

4Pillar 1 — Client Communications

90% proactive, 10% reactive. One weekly report + Loom + 1.5K send checkpoint.

Principles

90/10 split. Reactive comms reserved for client-initiated churn. Everything else CSM-initiated.
Goals as the operating system. Every weekly update references the documented onboarding goals, not opinions.
One weekly report is enough. Daily reports cause over-analysis and premature pivots.
Loom over calls. A 5-minute Loom replaces a 30-minute call. Saves 2-3 calls per CSM per week.
Phone for emotion, async for facts. Anything emotional, churn-y, or expectation-misalignment gets a call.
Email channel, not Slack. At 25+ clients, Slack channels become 24/7 ping noise.
Reset expectations from agreed baseline, never from emotion. Anchor on the documented goal, not market conditions.

What they built

Weekly drafted reports. Daily Zap pulls Smartlead metrics → drafts templated weekly update in CSM's Front inbox → CSM fills metrics + Loom + sends. CSM never composes from scratch.
3-week per-campaign cadence. Week 1 early observations / Week 2 trend + continue-vs-pivot / Week 3 retrospective + next-campaign commit (48h).
Topic-per-day internal calls. Mon = client management / Tue = underperformance / Wed = task review / Thu = at-risk / Fri = catch-up.
1.5K send checkpoint. Auto-evaluates each campaign at exactly 1,500 sends against ≥1% reply, ≤3% bounce, ≥2 positive replies. Below any threshold → Recreate Campaign task with 24h SLA.
Front email management. Replaces individual Gmail. API hooks let Airtable draft into the CSM's Front inbox; manager has visibility across every CSM's threads.
Aircall for fast escalation. Multi-day async delays collapse to 10-minute calls. Same protocol for slow-input clients during onboarding.
4-stage churn comms flow. Pre-churn expectation reset → CSM-level recovery → Management-level recovery → 30-day post-churn win-back automation.

1.5K send triage tree

flowchart TD Trigger["📧 Campaign hits 1,500 sends"] Check{"Reply rate < 1% OR
Bounce rate > 3%?"} Pass["✅ Continue monitoring
Manual via Tue call"] Q2{"Reply rate > 1%?"} Offer["⚠️ Offer/angle issue
Pivot strategy"] Q3{"Copy & list clean?"} Fix["🔧 Fix and relaunch"] Q4{"Industry: Healthcare
or FinServ?"} ICP["🛡️ Email security blocks
Pitch ICP shift"] Q5{"Domain performance
vs client average"} Replace["🔁 Replace domain
(rotate, relaunch)"] OfferFinal["📬 Launch 6-8 NEW
campaigns, different angles
NOT iterations"] Trigger --> Check Check -- No --> Pass Check -- Yes --> Q2 Q2 -- Yes --> Offer Q2 -- No --> Q3 Q3 -- Issues --> Fix Q3 -- Clean --> Q4 Q4 -- Yes --> ICP Q4 -- No --> Q5 Q5 -- "40%+ below avg or
bounce > 3%" --> Replace Q5 -- "At/near avg" --> OfferFinal classDef pass fill:#D1FAE5,stroke:#10B981,color:#0F172A classDef warn fill:#FEF3C7,stroke:#F59E0B,color:#0F172A classDef danger fill:#FEE2E2,stroke:#EF4444,color:#0F172A classDef text color:#0F172A class Pass pass class Offer,Fix,ICP warn class Replace,OfferFinal danger class Trigger,Check,Q2,Q3,Q4,Q5 text

The framework's underperformance triage: deliverability → copy/list → industry → domain → offer. The recovery move when offer is the issue: launch 6-8 new angles, don't iterate on the failing campaign.

AICRO status

Have: Weekly briefs (weekly-briefs command + client-strategy-notes skill), client call cadence (every ~7 days), Loom standard, Client Health Dashboard with no-active-campaign view, daily Slack pulse with "0 positives in 3 days" + "runway ≤ 2d" + "bounce > 5%".
Started: Goal capture (KPI target only, not "success def"), Loom URL field unstructured, QBR via gtm-client-strategy not true QBR, day-of-week call topic not enforced.
Missing: Twice-weekly Slack briefs to per-client channels (the AICRO version of the consultant's email cadence — see Section 12 cards 1-2), 2K-send auto-Recreate task, 2-day no-contact reminder for owners.

AICRO's communication layer (the headline lever)

The framework prescribes one weekly drafted email per campaign. AICRO's bigger move: a branded "AICRO Reporting" Slack app that posts twice weekly to each client's #{client-slug}-weekly channel — Monday Brief 9am ET + Friday Wrap 4pm ET. Templated structure, data pulled from Airtable + Supabase + the Client Strategy Notes pipeline. Replaces ad-hoc Slack/email comms with predictable, branded touchpoints that scale to 25-30 clients per owner without losing presence. Mockups in Section 12 cards 1-2.

Two framings AICRO doesn't translate to

The framework's "60-day churn risk reminder" doesn't map to AICRO — your daily pulse already fires on "0 positives in 3 days," materially tighter. The framework's "45-day no-check-in" assumes a much sparser cadence than AICRO's 7-day check-ins. The meaningful AICRO version is "2-day no-contact" — owner hasn't messaged client in >2 business days → Slack ping. Tracked as a P1 item in Section 12 rather than P0.

📄 Read full Pillar 1 — 392 lines

5Pillar 2 — Onboarding Framework

Day 0 → Day 14. 17-section intake. ICP-to-7-campaign mapping.

Principles

14-day SLA from paid quote to first campaign live. Non-negotiable. Slow-input clients trigger daily Aircall protocol.
Capture expectations and success def at intake. The CSM later anchors all expectation conversations on these documented baselines.
Service-model-aware setup. Cold email = 3 tasks, LinkedIn = 1 task, cold call = 2 tasks + 8-item checklist.
Onboarding form answers auto-trigger campaign type tasks. If the client opted in to "Job Scrape," a Job Scrape build task auto-creates.

14-day onboarding flow

flowchart LR Day0["Day 0
HubSpot deal closed-won
(paid quote)"] Day1["Day 1
Auto: Onboarding form email
+ CSM round-robin assigned
+ Welcome email drafted
+ Slack tag"] Day3["Day 3
Form submitted
→ ICP defined
→ Tech setup tasks created"] Day5["Day 5
Onboarding call
(goals + success def
+ expectations align)"] Day7["Day 7
Inboxes provisioned
+ Campaign 1 in build"] Day10["Day 10
Campaign 1 client approval
(72h auto-approve fallback)"] Day14["Day 14
🚀 First campaign LIVE"] Slow["⚠️ Slow-input fallback
Daily Aircall until
onboarding call books"] Day0 --> Day1 --> Day3 --> Day5 --> Day7 --> Day10 --> Day14 Day3 -.-> Slow Day5 -.-> Slow classDef milestone fill:#E0F2FE,stroke:#21A8F2,color:#0F172A classDef live fill:#D1FAE5,stroke:#10B981,stroke-width:2px,color:#0F172A classDef warn fill:#FEF3C7,stroke:#F59E0B,color:#0F172A class Day0,Day1,Day3,Day5,Day7,Day10 milestone class Day14 live class Slow warn

Day 0 to Day 14 onboarding milestone framework. Slow-input fallback fires daily Aircall until the onboarding call books.

17-section intake form (key sections)

Contact info, goals, ICP definition, pain points, differentiation, targeting criteria, signals, advanced targeting opt-ins, lead notification setup, evergreen campaign-type opt-ins (6 types: Partnership / Department / Job Scrape / Tech / Local / Engagers), service model selection (cold email / LinkedIn / cold call), success criteria, monthly lead target. Every answer feeds a downstream automation: ICP → 7 campaign types, evergreen opt-ins → auto-task creation, KPI target → weekly report goals.

AICRO status

Have: HubSpot signed-quote → Typeform onboarding form, /client-new + /client-ingest for profile/access creation, EmailBison + HeyReach workspace setup.
Started: Manual GTME assignment (no round-robin), Typeform doesn't include 6 evergreen opt-ins, welcome email drafted manually, 14-day SLA informal.
Missing: Mandatory expectations + success def fields, auto-task generation per evergreen type, day-by-day onboarding progress dashboard.

📄 Read full Pillar 2 — 567 lines

6Pillar 3 — Operational Structure (the 40:1 itself)

5 visibility areas, daily review cadence, intervention triggers, EOD discipline.

Management Oversight — the 5 visibility areas

flowchart TB Manager["👤 Manager"] Inbox["📥 1. INBOX
Front shared inbox visibility
SLA: 4h response
Trigger: missed → CSM coaching"] Tasks["✅ 2. TASKS
Airtable Task Hub
SLA: 24h overdue
Trigger: 24h+ → escalation"] Perf["📊 3. CAMPAIGN PERFORMANCE
Smartlead + EmailBison dashboard
Trigger: 1.5K send + <1% reply
OR >3% bounce → Recreate task"] Churn["💔 4. CHURN
Risk dashboard
Trigger: 60d no leads
OR client signal → call"] Rev["💰 5. REVENUE
RUM dashboard
Trigger: failed payment
→ Slack alert + cancel SLA"] Manager --> Inbox Manager --> Tasks Manager --> Perf Manager --> Churn Manager --> Rev classDef area fill:#E0F2FE,stroke:#21A8F2,color:#0F172A classDef center fill:#0A0E1A,color:#FFF,stroke:#21A8F2,stroke-width:2px class Inbox,Tasks,Perf,Churn,Rev area class Manager center

The 5 visibility areas the manager reviews daily. Each has a defined SLA and intervention trigger. "Surprises are the failure mode."

Task-driven accountability — SLAs

Task type	SLA	Why
Recreate Campaign (1.5K trigger)	24 hours	Lost momentum compounds; quick replacement keeps lead flow
Normal campaign turn	72 hours	Client expectation set at onboarding; auto-approval kicks at 72h
Onboarding launch	14 days	Paid quote SLA; longer than 14d = expectation drift + churn risk
Internal response (CSM ↔ manager)	2 hours	Daytime team coordination ceiling
Inbox response (CSM ↔ client)	4 hours	Front-mediated; manager sees breach in inbox

The 8-section EOD form

Before logging off, every CSM completes a structured form: delayed task count, which clients are delayed and why, at-risk flags, manually-typed reply rate (forces dashboard review), bounce rate, revenue under management, churn percentage, plan of action for next day. "They have to type out their reply rate even though Airtable knows it. It forces them to see, 'Cool, I'm at 20% churn rate, I gotta pick up my socks.'" Manager reads each form the next morning.

AICRO status

Have: Airtable as source of truth, GTME Performance dashboard, KPI tracking per channel, task ownership, standardized statuses, lead reuse via Supabase.
Started: Approval-first enrichment (manual gate), 24h SLA tracked manually, weekly domain check on demand.
Missing: EOD form, 24/48/72h approval cadence, underperformance auto-Recreate, 75% rebuild trigger, daily inbox auto-reconnect.

📄 Read full Pillar 3 — 631 lines

7Pillar 4 — KPIs & Performance Metrics

Internal vs external KPIs. The 1.5K rule, the 75% trigger, the 3% catch-all guardrail.

Two-tier KPI framework

Metric	Internal target	External (client-facing)	Notes
Reply rate	≥1%	Not reported	Internal floor — deliverability signal, not performance
Bounce rate	≤2-3%	Not reported	3% catch-all guardrail; auto-pause if breached
Send volume	5K-20K/month/client	Reported	Per-client volume agreement set at onboarding
1.5K send checkpoint	Eval per campaign	Not reported	Triggers Recreate task if any threshold missed
Positive Reply Rate (PRR)	Email ≥25%, LinkedIn ≥40%	Reported	Primary client-facing metric
Monthly churn	<10% per CSM	Internal only	Bonus eligibility threshold

The three trigger numbers

Send checkpoint

1,500 → 2,000

Framework: 1,500 sends. AICRO uses 2,000. Auto-evaluate against ≥1% reply, ≤3% bounce, ≥2 positive replies. Below any → Recreate task with 24h SLA.

Completion trigger

75%

When a campaign is 75% through volume → auto-create rebuild task. Prevents dead-air gap before campaign ends.

Catch-all guardrail

Bounce ceiling for catch-all-heavy lists. Breach → auto-pause. Forces clean list discipline.

The notification anti-pattern

The framework deliberately rejects daily metric updates. The notification stack is 1 weekly client report + lead alerts + approval reminders + launch notifications + 75% rebuild trigger + EOD form for CSMs. Daily metrics drive client over-analysis and premature pivots. AICRO's /gtm-standup gives the team daily metrics — the framework would suggest the daily client-facing channel should not.

AICRO status

Have: Channel benchmarks codified in knowledge_base/business/campaign-performance-metrics.md, 1.5-2K eval rule documented, domain replacement triggers documented, Liquid syntax fallbacks.
Started: Multi-campaign recovery practiced ad-hoc, public-email fallback understood not productized.
Missing: Auto-Recreate task on underperformance, 24h SLA enforcement on Recreate tasks, 75% rebuild trigger, catch-all auto-pause.

📄 Read full Pillar 4 — 345 lines

8Pillar 5 — Automation Architecture (The 42 Zaps)

The flagship — 42 specific automations across 8 categories, the heart of how 40:1 actually works.

Architectural philosophy

The framework runs on a clean separation: Airtable is the source of truth for all client/campaign/task/lead data; Zapier is the orchestration layer (every automation is a Zap); Slack is the human nudge surface (no DMs — channel-based); the EOD form is the human checkpoint (machines can't validate that work was actually done well). The 42 Zaps map the daily-and-weekly operating cadence: every recurring action has a Zap that initiates it or alerts when it doesn't fire.

flowchart LR Airtable["📊 Airtable
(source of truth)"] Zaps["⚡ 42 Zaps
(orchestration)"] Slack["💬 Slack
(nudges)"] EOD["📋 EOD Form
(human checkpoint)"] subgraph Cats["8 Categories"] direction TB C1["1. Onboarding & Setup
(#1-5)"] C2["2. Evergreen Builder
(#6-12)"] C3["3. Approval & Launch
(#13-20)"] C4["4. Performance & Volume
(#21-24)"] C5["5. KPI & Maintenance
(#25-27)"] C6["6. Churn & Risk
(#28-32)"] C7["7. Billing & Revenue
(#33-36)"] C8["8. Comms & Milestones
(#37-42)"] end Airtable --> Zaps Zaps --> Slack Zaps --> Cats Cats --> Airtable Slack --> EOD EOD --> Airtable classDef hub fill:#0A0E1A,color:#FFF,stroke:#21A8F2,stroke-width:2px classDef cat fill:#E0F2FE,stroke:#21A8F2,color:#0F172A classDef other fill:#FEF3C7,stroke:#F59E0B,color:#0F172A class Airtable,Zaps hub class C1,C2,C3,C4,C5,C6,C7,C8 cat class Slack,EOD other

The 8-category automation architecture. Airtable is canonical, Zapier orchestrates, Slack nudges, the EOD form closes the loop.

The P0 spine — 5 missing automations to build first

Of the 22 framework automations AICRO is missing, these 5 are the spine: #16-18 (24/48/72h approval cadence + auto-approve), #21-23 (recreate triggers), #28 (daily churn risk reminder), #33 (failed payment alert), #41 (45-day no-check-in). Combined effort estimate: ~3 weeks. They unblock time-to-launch SLAs, prevent dead-air gaps, and surface churn risk before it's too late.

Category 1 — Onboarding & Client Setup (#1-5)

#	Name	Trigger → Action	AICRO
1	Onboarding form email	HubSpot deal closed-won → Typeform link in welcome email	Have
2	Full client setup post-form	Typeform submit → CSM assigned, Airtable profile, EB+HR workspaces, Slack channels, tasks	Started
3	Post-onboarding-call email draft	Fathom recording → drafted recap in Front	Missing
4	New Client profile creation	Manual trigger → folder structure + Airtable row	Have
5	New Client access creation	Auto-create EB workspace + HR workspace + portal access	Started

Category 2 — Evergreen Campaign Builder (#6-12)

#	Name	Trigger → Action	AICRO
6	Partnership campaign auto-task	Onboarding "Partnership: Yes" → build task	Missing
7	Department scrape auto-task	Onboarding "Department: Yes" → build task	Missing
8	Job scrape auto-task	Onboarding "Job Scrape: Yes" → build task	Missing
9	Tech scrape auto-task	Onboarding "Tech Scrape: Yes" → build task	Missing
10	Local business auto-task	Onboarding "Local: Yes" → build task	Missing
11	Engagers campaign auto-task	Onboarding "Engagers: Yes" → build task	Missing
12	Evergreen bundle task	2+ types selected → bundled build task	Missing

Category 3 — Campaign Approval & Launch Flow (#13-20)

#	Name	Trigger → Action	AICRO
13	Submitted → portal delivery	Campaign submit → portal record + client notification	Started
14	Approved → enrichment + launch task	Client approves → Clay enrichment + launch task	Started
15	Denied → edit task	Client denies → edit task w/ feedback	Missing
16	24h approval reminder	24h pending → Slack/email reminder	Missing
17	48h approval reminder	48h pending → escalation	Missing
18	72h auto-approve	72h pending → auto-approved + launch	Missing
19	Live → email draft	Campaign launches → drafted client email	Have
20	One-click launch	EB MCP → campaign + inbox assignment	Have

Category 4 — Campaign Performance & Volume (#21-24)

#	Name	Trigger → Action	AICRO
21	Recreate trigger (1.5K)	1.5K sent + <1% reply OR >3% bounce → 24h SLA Recreate task	Missing
22	75% completion trigger	Volume 75% spent → rebuild task	Missing
23	No active campaign guardrail	100% complete + 7d idle → auto-task	Started
24	Low volume trigger	Mid-month vol below pace → alert	Started

Category 5 — KPI & Maintenance (#25-27)

#	Name	Trigger → Action	AICRO
25	Daily KPI review task	Each AM → CSM dashboard review task	Started
26	Weekly Mon domain health	Mondays → domain health dashboard task	Started
27	Inbox auto-reconnect 12pm	Daily 12pm → reconnect SMTP/IMAP for any disconnected inbox	Missing

Category 6 — Churn & Risk Management (#28-32)

#	Name	Trigger → Action	AICRO
28	Daily churn risk reminder	60d no leads OR L7D <3 leads → daily Slack reminder	Started
29	Risk-Email-Tag → call task	Manager tags client at-risk → call task	Missing
30	Churn management assignment	Churn signal → CSM-level review task	Started
31	Offboarding form trigger	Cancel signal → offboarding form auto-sent	Missing
32	Manager follow-up post-offboarding	Offboarding submit → manager call task	Missing

Category 7 — Billing & Revenue Protection (#33-36)

#	Name	Trigger → Action	AICRO
33	Failed payment Slack alert	Stripe failed_payment webhook → Slack #billing	Missing
34	10-day non-payment cancel flow	10d unpaid → auto-cancel + offboarding	Missing
35	Pause client → billing pause task	Status "Paused" → finance task	Started
36	Close client → infra cleanup	Status "Closed" → delete inboxes, archive workspaces	Started

Category 8 — Client Communication & Milestones (#37-42)

#	Name	Trigger → Action	AICRO
37	First lead → email draft	First positive reply → drafted client celebration	Missing
38	10-lead milestone	10th positive reply → drafted celebration	Missing
39	25-lead milestone	25th positive reply → drafted celebration	Missing
40	30-lead milestone	30th positive reply → drafted celebration	Missing
41	45-day no check-in reminder	45d since last call → CSM call task	Missing
42	Post-check-in recap draft	Fathom call ends → drafted recap in Front	Have

Coverage summary: 6 fully Have (#1, #4, #19, #20, #42, partial #14), 14 Started, 22 Missing. The bolded entries above are the highest-impact missing automations.

📄 Read full Pillar 5 — 917 lines

9Pillar 6 — Data Enrichment

Waterfall pipeline, 16 evergreen campaign types, RevBase economics.

Waterfall enrichment pipeline

flowchart LR Source["🎯 List source
RevBase / Discolike /
Sales Nav"] Validate["✅ 8-9 provider
email validation
(Hypertide waterfall)"] Verify["🔍 Million Verifier
+ NeverBounce
(double-check)"] Catch["🚧 Scrubby
(catch-all detection)"] Personalize["🎨 Clay Playbook
(LinkedIn / hires /
case studies / etc)"] Smartlead["📤 Smartlead
(send)"] Source --> Validate --> Verify --> Catch --> Personalize --> Smartlead classDef step fill:#E0F2FE,stroke:#21A8F2,color:#0F172A classDef end1 fill:#D1FAE5,stroke:#10B981,stroke-width:2px,color:#0F172A class Source,Validate,Verify,Catch,Personalize step class Smartlead end1

The waterfall enrichment pipeline. Discolike for lookalikes, RevBase as primary, 8-9 provider validation, double email verification, 3% catch-all guardrail.

16 evergreen campaign types (Clay playbooks)

LinkedIn jobs scrape

Engagers (post engagement)

Partnerships

Tech scrape (BuiltWith)

Local business

Department scrape

Colleague reference

Ad analysis (FB Ad Lib)

Recently hired

Recently promoted

Company subcategory

Competitors

Case studies

ICP extraction

Website visitors (SEMrush)

BuiltWith tech-stack

The framework's QA philosophy

The CSM does an 80% scroll-check (fast manual review of names + titles + companies for ICP fit). The client is treated as the primary QA — if they approve a list, that's the QA pass. This is structurally different from AICRO's current pipeline where enrichment happens before client approval. Restructuring approval-first enrichment is a P1 candidate for AICRO.

Cost economics

RevBase is the framework's primary list-building tool, used across thousands of campaigns/year. Catch-all 3% bounce ceiling forces clean list discipline before sending. Per-campaign tracking at AICRO would confirm the productization economics.

📄 Read full Pillar 6 — 689 lines

10Pillar 7 — LinkedIn / InMail Sourcing

Avatar pool architecture, Open Profile detection, 10K InMails/client/month capacity.

The architecture

ProfilePros + UpWork source 100+ aged unbranded LinkedIn avatars. The avatars don't represent the client; they're a sourcing fleet.
NetNut detects Open Profiles. Only Open Profiles get InMail attempts — closed profiles return spent InMail credits.
GoLogin manages proxy + browser fingerprinting per avatar so LinkedIn doesn't link them.
Custom Airtable-native InMail sender (the framework's agency built this internally) supports 10K InMails/month/client.
2-message InMail sequence, 1-2 sentences each. Aged avatars look human, get reply rates well above HeyReach defaults.
Email-fail → InMail routing. When email validation fails for a lead, the system auto-routes to InMail attempt instead of dropping the lead.

What the framework says about AICRO scale

"Don't build the avatar pool at 10 clients." His framework's avatar fleet is ROI-positive at 25-30+ clients. AICRO's HeyReach-based stack is sufficient at current scale; revisit when the client count crosses 25.

Important caveat — InMail-only items

Both Pillar 7 plays in the original brief (Open Profile detection via NetNut, Email-Fail → InMail routing) only matter when an InMail program is running. AICRO is not currently sending InMails. These are good ideas conditional on launching an InMail channel; until then they're parked. The avatar pool / GoLogin / ProfilePros stack stays on the backlog regardless until ~25 clients.

📄 Read full Pillar 7 — 186 lines

11Tooling Stack — Theirs vs AICRO's

~30 tools across 4 categories, with Have / Equivalent / Don't Have / N/A status against AICRO.

Outbound stack

Tool	Use	AICRO equivalent / status
Hypertide + Smartlead	Email infra + sender	Hypertide for infra; EmailBison via 164-tool MCP as standard sender Have
HeyReach	LinkedIn outbound	48-tool custom MCP Have
RevBase	Primary list builder	RevBase via Gigasheet + `revbase-list-builder` skill Have
Discolike	Lookalike-domain scraper	Clay + ChatGPT substitute (slower) Missing
Followingg	LinkedIn follower scraping	None Missing
ProfilePros + UpWork	Avatar sourcing	Don't build at AICRO scale N/A
NetNut	Open Profile detection	None — recommended P0 Missing
GoLogin	Proxy / fingerprinting	Not relevant until avatar pool exists Missing

Enrichment & validation

Tool	Use	AICRO status
Clay	Personalization playbooks (16)	`clay-campaign-builder` skill; subset of playbooks productized Started
Million Verifier + NeverBounce	Double email verification	In Hypertide waterfall Have
Scrubby	Catch-all detection	Manual today Missing
BuiltWith	Tech-stack lookup	RevBase technographics substitute Missing
SEMrush via Apify	Website Visitors playbook	None Missing

Operations

Tool	Use	AICRO status
Airtable	Source of truth	Canonical + 19-tool MCP Have
Lovable	Client portal dashboards	AICRO Client Health Dashboard (`apps/portfolio-health/`) — Vite + React, daily snapshot from Airtable + Supabase, 5-tier composite (On Track / At Risk / Off Track) Have
Zapier	Automation orchestration	n8n self-hosted at `n8n.aicro.co` (~209 workflows) Have
Aircall	Fast escalation calls	None — recommended P1 Missing
Fathom	Call recording + summary	Standard Have
Loom	Async explainer	Standard Have
GetGuru	Knowledge base (CSM-facing)	`knowledge_base/methodology/` — not surfaced via Slack bot Missing
HubSpot	CRM	Standard + `attribution-report` skill Have
Typeform	Onboarding intake	Standard Have
Front	Shared inbox visibility	None — P2 until 5+ active CSMs Missing
Stripe + Mercury	Billing + banking	Standard Have
Gamma	QBR decks	AICRO branded skills produce higher quality N/A

Signal sources

Tool	Use	AICRO status
RB2B	Anonymous website visitor ID	Not on AICRO marketing site or any client site Missing
LinkedIn Sales Nav	Targeting	Per-client license Have
Facebook Ad Library	Ad analysis playbook	None Missing
Mimecast / Barracuda / Proofpoint	Email security pre-check	No deliverability blocker pre-check Missing

Build vs Buy at AICRO

Built (already there): Custom MCPs (240+ tools), n8n self-hosted, branded slide/doc skills, 41-skill plugin ecosystem, attribution-report, weekly briefs pipeline, Client Health Dashboard (apps/portfolio-health/). Buy (recommended): Aircall, NetNut, Discolike, RB2B. Don't bother yet per the framework: avatar pool, GoLogin, custom Snowflake-backed RevBase UI, custom Airtable-native InMail sender. Revisit at 25+ clients.

📄 Read full Pillar 8 — 230 lines

12AICRO-Reality Top 10 — The Roadmap

Re-ranked April 26 against AICRO's actual state. Two themes: (1) the Client Health Dashboard already detects most of the consultant's "alert" signals — much of the work is wiring action triggers (Slack post + Airtable task) onto signals you already compute; (2) the client-comms Slack layer (Monday Brief + Friday Wrap) is the single biggest lever AICRO wants to pull, and it goes beyond the framework.

P0 — this week (Slack-native, low-friction)

1. Monday Brief auto-Slack to per-client channel ★

P0 · M · NEW · client-facing

Branded "AICRO Reporting" Slack app posts every Monday 9:00 AM ET to #{client-slug}-weekly. Replicates the AICRO mockup: This Week's Focus (3 calendar items pulled from Airtable tasks/campaigns), Active Campaigns with traffic-light dots (running/refreshing/paused), Last Week at a Glance (positive replies + meetings booked + standout from Supabase), Needs Your Attention (open approvals + decisions with deadlines), client portal link.

First step: Extend the existing weekly-briefs command + client-strategy-notes skill into a Slack post template; provision per-client #{slug}-weekly channels (or repurpose existing); cron via GitHub Actions per feedback_scheduled_jobs_cloud_first. Pilot on one client (Capitalize or Balance Cash) for 2 weeks before fleet rollout.

2. Friday Wrap auto-Slack to per-client channel ★

P0 · M · NEW · client-facing

Same "AICRO Reporting" app posts each Friday 4:00 PM ET. Sections: What We Delivered (campaigns launched / refreshes shipped / lists finalized this week), This Week's Numbers (positive replies, meetings booked, top performer with PRR), Hot Leads This Week (3-5 named leads from warm-lead-classifier with role + signal), On Your Radar for Next Week (open decisions / blockers), Coming Monday (teaser for next week's Monday Brief).

First step: Reuse Monday Brief infrastructure with a different template + Friday cron. Hot Leads section pulls from the existing warm-lead-classifier Google Sheet output. Combined Mon+Fri build is ~3-4 weeks of pod time including Slack app branding, per-client channel provisioning, and 2-week pilot.

3. Mandatory 3-Question Onboarding Expectation Capture

P0 · S · Score 9.0 · Pillar 1/2 · Typeform rebuild in flight

Add three required Typeform fields: "What does success look like at 90 days?", "What's your biggest concern with this engagement?", "How will you measure ROI?". Captured to Airtable as required fields. Becomes the GTME's leverage in any expectation conversation. Zero-marginal-cost addition while you're already rebuilding the onboarding form.

First step: Add fields to the in-flight Typeform; add corresponding required Airtable columns; brief the GTME team to anchor expectation-reset conversations on these answers. PRD seed: opportunities/mandatory-onboarding-expectation-capture.md.

4. No-Active-Campaign Slack Alert + Auto-Task

P0 · S · Score 15.0 · Pillar 3/5 (Auto SOP #23)

The Client Health Dashboard already detects "no active campaign > X days" today. Wire it: when state hits, post in #aicro-ops AND create a "Build replacement campaign" Airtable task on the assigned GTME with 24h SLA. The signal exists; this just adds the trigger.

First step: ~2-4 hour build — extend the dashboard's daily snapshot or add a GH Action that reads snapshot.json, checks for the no-active-campaign condition, and writes via Airtable + Slack APIs. PRD seed: opportunities/no-active-campaign-auto-task.md.

5. 2K-Send Auto-Recreate Task + Slack Ping

P0 · S · Score 12.0 · Pillar 4/5 (Auto SOP #21, AICRO threshold)

At 2,000 sends per campaign (AICRO's preferred threshold over the consultant's 1.5K), evaluate against ≥1% reply, ≤3% bounce, ≥2 positive replies. Below any threshold → auto-create Recreate Campaign task with 24h SLA + Slack ping owner in #aicro-ops or per-client channel. Net-new — no standard check exists today at this volume.

First step: ~4-hour build — n8n cron + Supabase query for thresholds + Airtable task + Slack post. Reference partial spec already in 03_gtm/alert-specs.md (Alert #6). PRD seed: opportunities/1500-send-checkpoint-alert.md (rename to 2K).

P1 — next sprint

6. 75%-Runway → Auto-Task + Slack

P1 · S · Score 15.0 · Pillar 4/5 (Auto SOP #22, reframed for AICRO)

The consultant framed this as "75% campaign-completion." AICRO already tracks runway in the Client Health Dashboard with ≤2-day critical override. Wire the next tier: when a client/channel crosses 4-day runway OR 75% of allocated volume consumed, auto-create rebuild task + Slack ping. Layered onto an existing signal — minimal lift.

First step: ~2-3 hour build — formula in dashboard snapshot + GH Action trigger. PRD seed: opportunities/75-percent-completion-rebuild-trigger.md.

7. Lead Milestone Slack Celebrations

P1 · S · Auto SOP #37-40 · client-facing or internal

1st / 10th / 25th / 50th positive reply per client → Slack post in client-specific channel ("🎉 Acme just hit 25 positive replies — here's the latest one") OR in internal #aicro-wins. Lightweight, motivational, reinforces the client-comms cadence between Monday/Friday briefs. Could fold into the Friday Wrap's "Hot Leads" section instead of being a standalone post.

First step: ~3-hour build — Supabase trigger on inbound_messages.category = 'Interested' rollup count crossing milestone thresholds. PRD seed: write fresh under opportunities/lead-milestone-celebrations.md.

8. Daily EOD Form for GTMEs

P1 · S · Score 15.0 · Pillar 9 (behavior change is the lift)

The consultant's flagship accountability mechanism. Airtable form per GTME captures: delayed task count, at-risk client flags, manually-typed reply rate (forces dashboard view), bounce rate, RUM, churn %, plan for tomorrow. Manager reads next morning. Build is fast (~4 hours); the actual lift is getting GTMEs to submit it daily and Doug/Josh to read it.

First step: Build the form + Slack reminder + manager Loom announcing the new daily ritual. PRD seed: opportunities/eod-form-gtme.md.

9. Manager At-Risk Tag → Auto-Task + Slack

P1 · S · Auto SOP #29 · Pillar 5/9

When Doug or Josh tags a client as "at-risk" in Airtable (single-select field), auto-create a "Schedule recovery call" task on the assigned GTME within 24h + Slack ping in #aicro-ops. Codifies what's currently informal manager-to-GTME nudging.

First step: ~2-hour build — Airtable single-select + automation script that creates linked task + posts to Slack. PRD seed: write fresh under opportunities/at-risk-tag-auto-task.md.

10. 2-Day No-Contact Reminder (replaces the consultant's 45-day)

P1 · S · Pillar 1/9 (AICRO version of Auto SOP #41)

AICRO checks in with clients every ~7 days, so the consultant's "45-day no-check-in" is meaningless. The AICRO-tight version: track last_outbound_to_client per client (could come from Slack message logs once those land in Supabase, or Front API once Aircall/Front trial happens, or a manual Airtable button). When >2 business days elapsed, Slack ping the owner.

First step: Identify the canonical "last contacted" data source (likely Slack messages once slack_messages table is populated per the strategy-synthesis roadmap). PRD seed: write fresh under opportunities/2-day-no-contact-reminder.md.

Punted — with rationale

Deferred from the original top 15

24/48/72-Hour Approval Cadence + Auto-Approve (Auto SOP #16-18) — needs the AICRO portal first; punting until portal MVP. Existing PRD: 02_product/prds/2026-03-12-campaign-brief-lifecycle.md.
Failed Payment Slack Alert + 10-day Cancel Flow (Auto SOP #33-34) — useful but punt for now; Stripe webhooks not currently wired to #aicro-billing.
Open Profile Detection on HeyReach (NetNut) — InMail-program-specific; AICRO is not currently sending InMails. Defer until InMail program launches.
Email-Fail → InMail Routing — same caveat. Both Pillar 7 items are great ideas conditional on InMail being a live channel.
Sales-to-GTME Round-Robin Auto-Assignment — only 11 active clients; manual assignment is fine until ~20+ clients.
60-Day Churn-Risk Daily Slack Reminder (Auto SOP #28) — replaced by AICRO's existing daily pulse, which already fires on "0 positives in 3 days" (tighter than the consultant's 60-day).
45-Day No-Check-In Reminder (Auto SOP #41) — replaced by item #10 above (2-day no-contact), which matches AICRO's actual 7-day check-in cadence.

Sprint sequencing recommendation

Sprint 1 (now, ~3-4 weeks): Cards 1-2 (Monday Brief + Friday Wrap — biggest lift, biggest payoff) in parallel with Cards 3-5 (single-day wins). Sprint 2 (next 30 days): Cards 6-7 + finalize pilot of Mon/Fri briefs across 3-5 clients. Sprint 3 (60-90 days): Cards 8-10 + portal-dependent items + InMail program planning. Backlog: P2 catalog (avatar pool, custom build replacements, exotic playbooks) — revisit at 25+ clients.

📄 Full 78-entry catalog

13April Reengagement — Open Threads

The thread the consultant left open and 16 questions surfaced during synthesis.

The consultant's open thread

The Week 4 doc has a header "Template organization and reuse strategies" with no content underneath. The implicit question: how does the consultant's agency organize Clay templates for reuse across clients with overlapping ICPs, what naming conventions survive past 40 clients, how are deprecated templates retired, and is the model per-client / per-ICP / per-campaign-type?

16 questions for the April call (suggested agenda)

Operating model

PTO coverage at 30:1 — buddy system, manager backfill, or volume freeze?
CSM-to-Manager promotion path — what's the structured progression?
CSM training onboarding — Day 30 / 60 / 90 evaluation criteria?
The 12-15 vs 30-40 transition — what changes structurally as a CSM ramps up clients?

Automation philosophy

What gets automated next at 100+ clients/CSM — predictive churn? Auto-strategy-pivot recommendations?
AI-generated copy at scale — the consultant's position on Claude / GPT for copy? Quality regressions?
EOD form schema — exact fields, narrative vs structured, time to fill out?

Vendor stack

Discolike alternatives — Clay Companies vs Apollo Companies failure modes?
NetNut Open-Profile detection accuracy — false positives, cost per check?
Aircall vs OpenPhone vs Dialpad vs Google Voice acceptable substitutes?
Avatar pool sourcing — at what client count does it become worth the operational overhead?

Team mechanics

Daily EOD form fatigue — has the framework's agency seen CSMs game it? Management response?
Round-robin gaming — when CSMs feel one client is "easier," does it actually hold?
Performance-based comp variance — what % of total CSM comp is variable?

Specific automations

24/48/72h approval cadence — what does the actual reminder copy say?
Catch-all 3% guardrail mechanism — auto-pause? Auto-replace catch-alls with public emails?

Suggested April session order

30 min — Close the template organization thread
45 min — Walk us through the Day 1 implementation order of the 5 P0 gaps the consultant has built before
20 min — Avatar pool decision tree: at what client count does AICRO start? Phase 1 setup?
60-90 min — The 16 open questions above (split across multiple calls if needed)
30 min — the consultant's own April scope: refine existing SOPs vs open new pillars?

✎Sources

What this brief draws from.

Source materials (gitignored, on Josh's laptop only)

5 meeting transcripts — Jan 28 (pre-engagement) + Feb 4 / 11 / 18 / 25 (Weeks 1-4)
9 Google Doc deliverables — Consulting Agreement, Month 1 Scope, Week 1 Comms pre-call, Week 1 Q&A (4 tabs), Week 1 SOPs Complete (6 tabs), Week 2 Onboarding Playbook (7 tabs), Week 3 Operations pre-call (10 tabs), 40:1 CSM Structure SOP (the flagship — 42 Zaps), Week 4 Doc (8 tabs)
Collateral — Miro onboarding board, Gamma QBR deck, Loom 40:1 Zap walkthrough, vendor intros (No Accent Callers, Huzzle), tool inventory

Synthesis layer (committed, team-readable)

Pillar 1 — Client Communications · 392 lines
Pillar 2 — Onboarding Framework · 567 lines
Pillar 3 — Operational Structure (40:1) · 631 lines
Pillar 4 — KPIs & Performance · 345 lines
Pillar 5 — Automation Architecture (42 Zaps) · 917 lines
Pillar 6 — Data Enrichment · 689 lines
Pillar 7 — LinkedIn / InMail Sourcing · 186 lines
Pillar 8 — Tooling Stack · 230 lines
Pillar 9 — Team & Compensation · 365 lines
Pillar 10 — AICRO Implementation Status (the bridge) · 399 lines
Opportunities catalog (78 entries ranked)
Follow-ups + April reengagement priorities

AICRO repo references

03_gtm/alert-specs.md — n8n alert specifications (Lead Runway, Bounce Rate, Positive:Sent Ratio, Days Since Last Positive, Daily Send Volume, Campaign Milestone 1.5K)
02_product/prds/2026-03-12-campaign-brief-lifecycle.md — full PRD covering most of Auto SOP #13-20
02_product/crm-integration-architecture.md — HubSpot signed-quote → Airtable
knowledge_base/business/campaign-performance-metrics.md — channel benchmarks codified
knowledge_base/methodology/ — 21 atomic methodology nodes (deferred extraction target for Pillar 5/9 concepts)
apps/portfolio-health/ — AICRO Client Health Dashboard (Vite + React, 5-tier composite, daily Airtable/Supabase snapshot)
_mcp/CLAUDE.md — 240+ MCP tool architecture

Strategic synthesis · The 40 to 1 Account Management Framework · April 26, 2026 · josh@aicro.co
This file: 04_client_management/framework-synthesis.html