Appearance
The Problem
Sam started as a sharp work buddy for John. Within two weeks it was running the entire marketing intelligence operation: monitoring funnel conversion rates, auditing Braze email flows, generating creative briefs, watching 4 GitHub repos for code changes, running PostHog queries, pulling Looker dashboards, and reporting 3× a day to Slack.
The result: a single agent holding an enormous context window, memory that drifts between sessions, tasks that interfere with each other, and increasing unreliability on the most critical data reporting work.
Christian (CTO) and John have flagged it. Alex has been brought in to vivisect Sam and propose the decomposition.
The Solution John and Luke Have in Mind
A Marketing Master Agent that orchestrates 5 specialized sub-agents, each owning a domain:
| Agent | Domain | Key Integrations |
|---|---|---|
| Data Agent | Reporting & Analytics | PostHog, Looker, NorthBeam, GitHub |
| Creative Agent | All Creative Work | Higgsfield, Shotstack, Google Drive, Braze |
| Media Buying Agent | Meta & TikTok | Meta Ads API, NorthBeam, TikTok |
| Funnel Agent | CRO & Optimization | Sanity CMS, PostHog, GitHub funnel repos |
| Prospect Agent | Email & SMS | Braze, Zendesk, Google Calendar |
How to Read This
This site has four sections:
Current State — What Sam is today: configuration, integrations, memory, conversation history, automation, skills, artifacts, and security.
Workflows — How Sam actually operates day-to-day. What it does for funnel monitoring, creative work, Braze operations, GitHub watching, and reporting.
Decomposition — The proposed split: candidate skills, 5 sub-agents, integration routing, and migration plan.
Gaps & Issues — Missing OpenClaw features, known bugs, security concerns, and the stuck version update.
For Stakeholders: How to Review
This document is a working research artifact. It is not a final plan — it is a map of what exists so that the right decisions can be made about how to proceed.
What we need from you:
- ✅ Confirm or deny the integration assignments (does the right team own the right data?)
- ✅ Flag any workflows we missed or misunderstood
- ✅ Prioritize which agent to build first
- ✅ Identify any access restrictions or compliance concerns with the proposed decomposition
Confidential
This document contains internal FuturHealth operational details. Do not share externally.
Research conducted: March 19, 2026 | Based on backup: 2026-03-18T23:08:38Z