Adapting Asana's Managed Agents architecture to the SEO Navigator Agency OS — six department agents, seven internal workstreams, and ClickUp as the work graph.
Asana's pitch is that they own the work graph and Anthropic owns the outcome execution. The split scales because each side stays in its lane. The Agency OS we've been mapping is structurally the same shape — six dept agents (SEO Sentinel, Content Catalyst, Revenue Relay, Ad Arbitrage, Build Bot, PM Pulse) sitting on top of a ClickUp work graph, with Claude Skills as the curated expertise layer and Managed Agents as the execution harness. This document walks through what each Asana slide looks like once we swap their categories for ours.
The vision Ara opened with — humans and agents collaborating across departments instead of one human prompting one agent in isolation — is the same vision that motivated the SEO Navigator skills library and the Agency OS. Six dept agents, each a curated bundle of Claude Skills, sit on top of a shared ClickUp work graph. Below them is a centaur team where every human is paired with at least one AI teammate. The arc is the agency itself.
Today, every department uses Claude in isolation. The SEO team's session doesn't know what Content just shipped. The CRM workflow has no memory of the campaign brief Ads is running. Each silo gets faster — the agency as a whole doesn't. Multiplayer mode means a shared agent layer mediated by ClickUp — task graph, RACI, and Skills memory all in one place. A correction one team makes ("Sun Stoppers' brand voice is now warmer, less technical") gets written to shared memory, and the next dept agent inherits it.
Asana's framing — that AI is failing not because the model is weak but because it's missing five pieces of context — is true at our scale, just with agency-specific surfaces. Who means which client we're working on without re-pasting context. What means whether this is a brief, a deliverable, a campaign, or a report. By when means our monthly client-reporting cycle and campaign timing. How means the agency methodology — Koray's semantic SEO, the EAV/URR triples, the CQS rubric. Why means the client's commercial OKRs and our retention pressure.
The QueryMind work, the GHL CRM build, the SOP library, and the Agency OS Memory section are all closing different parts of this gap. ClickUp is the place those streams converge.
ClickUp's Workspace → Space → Folder → List → Task → Subtask hierarchy is structurally identical to Asana's Mission → Goals → Portfolios → Projects → Tasks. The three pillars adapt directly: a superior data model lives in ClickUp custom fields (Dept, Workstream, RACI, ICE Score, Phase, Dev Flag, Automation Status, SOP Link, KPI Impacted). A multiplayer architecture lives in RACI-on-every-template plus cross-folder linking. Security and guardrails live in our human gates — CEO sign-off on hires, ad copy review before launch, OKR calibration sessions.
Where Asana put cross-functional Operations/PMO workstreams on top with ICP departments below, ours has the seven internal workstreams from the 2026 blueprint as the connective layer, with the six department agents as the columns underneath. The workstreams aren't a separate system — they're the cross-functional programs that every dept agent participates in.
Not every workstream is the same shape. Some have crisp, gradeable outputs that fit the Managed Agents harness today; others are mostly human craft that AI assists. The table below maps each workstream to its primary Claude Skill and an honest readiness call.
| WS | Workstream | Primary Skill | Phase | Managed Agents fit |
|---|---|---|---|---|
| 01 | Workflow + SOP systemSOPs, workflow maps, RACI | seo-navigator-agency-os | W1–2 | High — gradeable outputs |
| 02 | Onboarding simplificationChecklists, role packs | seo-navigator-agency-os | W3–6 | Medium — DoD per role |
| 03 | Communication + automationSlack ↔ ClickUp routing | seo-navigator-agency-os | W3–7 | Medium — needs Zack integration |
| 04 | Internal "brain" systemMeta Agent · digests | managed-agents-doc | W7–9 | High — but Phase 2 |
| 05 | Recurring tasks + templatesTemplate Vault | seo-navigator-agency-os | W1–2 | High — start here |
| 06 | Performance frameworkSOWs, KPIs, OKRs | seo-navigator-agency-os | W3–7 | Medium — depends on SOW gate |
| 07 | Culture + mindset upgradeWorkshops, coaching | — | W4–12 | Low — human-led, AI drafts only |
The pattern is the same one Asana hit: the workstreams with the clearest grader rubrics (templates, SOPs, KPI scorecards) move fastest. The ones tied to human relationship and behavior (culture, sensitive client conversations) stay human-led, with AI as a drafting assistant only.
The before/after table Ara showed translates almost line-for-line into our reality. Today, every Claude Skill in the library is invoked through Claude Code or the chat interface; Jake reviews every output before it reaches a client. That pattern works at our current scale but it's the bottleneck Ara was describing — one long single-threaded conversation with the founder driving. Managed Agents replaces that with a managed harness where the rubric (our DoD) is the spec the grader iterates against.
We can focus on what's unique to us — the agency methodology, the ClickUp work graph, the client relationships — while Anthropic handles outcome quality. — Ara, Asana (paraphrased for our context)
The architecture split is the load-bearing insight. SEO Navigator owns: the ClickUp work graph (workspaces, lists, tasks, RACI, custom fields), the Skills library (Koray methodology, EAV/URR triples, CQS rubric, GHL playbooks), the GHL CRM context, the human gates, the client relationships. Managed Agents owns: multi-step task execution, verification against our DoDs, code execution for HTML deliverables, and parallel agent orchestration. Neither side does the other's job.
The verification loop is what makes the architecture work. The grader iterates until the outcome meets the rubric — no human babysitting. For us the rubric is the DoD already written for each workstream. Faster prototyping comes from Skills as packaged expertise. Quality verification comes from running the DoD as the grader spec. The outcome evaluator closes the loop by holding the agent to the KPI scorecard.
Asana's three forward bets translate to ours almost directly: multi-step workflows are the seven WS pipelines from the 2026 blueprint, team patterns are the six centaur dept agents, and proactive moves are the Meta Agent that workstream 4 (Internal Brain) is designed to deliver in Phase 2. The 12-week roadmap stays the same — stabilize W1–2, standardize W3–6, automate W7–12.
Seven WS pipelines, end-to-end with DoD rubrics
Six dept agents paired with the team — humans own WHAT and WHY
Meta Agent in WS4 — wakes up when it spots blockers
The good news: we already have rubrics. Every workstream in the 2026 blueprint has a written DoD ("every recurring workflow has template + SOP + video + RACI"; "deadline reminders firing automatically"; etc). Those become the grader specs without rewriting them. Where we don't have rubrics — culture, client relationships — we shouldn't try to manufacture one.
Asana keeps skills shrink-wrapped, governed centrally, with no customer authoring for now. We do too — the skills library (seo-navigator-agency-os, consensus-content-audit, google-ads-radius-optimizer, etc.) is curated and versioned. The risk to watch: as the skill count grows, we need a clear ownership map for who maintains each, who tests them, and who decides when to deprecate.
Asana said integrations happen at both the agent loop and the MCP layer. For us that means: the ClickUp MCP, the GHL MCP (the BusyBee fork or the official 36-tool endpoint), and the Slack MCP all need to be reachable from inside Managed Agents, not just from Claude Code. The integration story is symmetrical, not stacked.
Workstream 5 (recurring tasks + templates) and workstream 1 (workflow + SOPs) are the highest-ICE places to begin — both have clear DoDs and AI-automatable outputs. Workstream 4 (Internal Brain) is the most exciting but explicitly Phase 2 (W9+). Don't skip phases.
1. Pick the first Managed Agent prototype. The cleanest fit is workstream 5 (recurring tasks + templates) — the DoD is "Template Vault populated, 80% of execution on existing templates" — that's a measurable rubric. Build a Managed Agent whose job is "given a process description, produce a ClickUp template + SOP doc + RACI mapping that passes the DoD." Run it for 2 weeks. Compare against Jake-driven baseline.
2. Build the rubric translation layer. Every workstream's DoD currently lives in the command center HTML doc. Those need to be machine-readable rubrics that a grader can score against. This is a one-time documentation pass — turn each DoD bullet into a checklist item with an explicit pass/fail signal.
3. Figure out which dept agent gets packaged first. SEO Sentinel has the most volume (37h/wk) but Content Catalyst has the cleanest gradeable output (briefs against the EAV rubric). PM Pulse is the most universal across clients. Pick one for the v1 packaging effort and hold off on the others until we have data.