Client Onboarding Flows - Fresh vs Existing Ad Account
Audience: Engineers designing onboarding flows on top of Adros
Purpose: Define the two common onboarding journeys so an orchestration layer knows who to trigger, in what order, and with what handoff artifacts.
Pattern (external stack): the operator may work through an optional orchestration layer. That layer routes; Adros remains the marketing brain and execution plane.
Pattern (native Adros): the operator uses Adros CEO + Command Center and the same backend handles the tracked work.
Terminology (April 2026)
Older versions of this doc referenced legacy names such as Jarvis or Hermes. Public docs should use the runtime actor IDs below.
| Actor | ID | Role (summary) |
|---|---|---|
| Adros CEO | adros_ceo | Conversational coordinator; intake; routes work into tasks |
| Adros Research | adros_research | Managed Agent - keyword research, market research, competitor research, and audience research |
| Adros CMO | adros_cmo | Managed Agent - audits, strategy synthesis, structure/strategy, and optimization analysis |
| Adros CD | adros_cd | Copy and creative direction |
| Adros Deployer | adros_deployer | Launch and account change execution |
There is no public standalone "Data Analyst" runtime. Research maps to Adros Research, audits and strategy map to Adros CMO, creative maps to Adros CD, and go-live maps to Adros Deployer.
1. Shared backbone
Every client onboarding follows the same high-level backbone:
- Intake - who/what/where (business, goals, constraints)
- Research - market, competitors, personas, keywords
- Analysis - opportunity mapping or audit findings
- Structure - campaigns, ad sets, budgets
- Creative - copy and visuals
- Approval - operator reviews and approves
- Launch / Execute - deployment or account changes
- Monitor - ongoing alerts and follow-up work
Adros exposes 9 workflow guides that help orchestrators route these phases correctly.
2. Journey A - fresh client (no ad account, no history)
Typical trigger signals:
- "new client, just signed"
- "onboard [client]"
- "starting from scratch, no ads yet"
Recommended flow
- Intake - collect website, offer, budget range, goals, constraints
- Research lane - external research bridge or native research support gathers competitor, audience, and market inputs
- Ingest - Adros Research stores business context, personas, and brand context
- Research deliverables - Adros Research produces keyword research and market research deliverables as needed
- Structure - Adros CMO produces Meta/Google structure deliverables
- Creative - Adros CD produces copy and creative outputs
- Approval - operator reviews package
- Launch - Adros Deployer applies approved changes
- Monitor - ongoing monitoring begins or continues
Who does what (Fresh)
| Phase | Specialist | Tool/System | Artifact |
|---|---|---|---|
| Intake | Conductor or Adros CEO | Operator channel | Intake notes |
| Research | Research bridge and/or Adros Research | Research workflows | Research inputs |
| Ingest | Adros Research | Memory + brand tools | Populated Adros context |
| Research deliverables | Adros Research | Keyword/market research workflows | Research package |
| Structure | Adros CMO | Campaign-build workflows | Structure deliverables |
| Creative | Adros CD | Creative workflows | Copy + creative outputs |
| Approval | Operator | Command Center or external approval channel | Decision |
| Launch | Adros Deployer | Deployment tools | Live campaigns |
| Monitor | Adros | Daily monitoring loop | Alerts |
3. Journey B - existing ad account (already running ads)
Typical trigger signals:
- "audit this account"
- "take over [client]'s ads"
- "optimize existing campaigns"
Recommended flow
- Intake - collect business name, account IDs, and main concern
- Connect - confirm Google/Meta access
- Audit - Adros CMO runs the audit workflow
- Conditional research - if the audit reveals positioning, audience, or competitive gaps, route into Adros Research
- Ingest - Adros Research backfills context if new research was gathered
- Reallocation / fixes - Adros Deployer executes approved fixes or change plans
- Creative refresh - Adros CD only when needed
- Approval - operator reviews the proposed actions
- Execute - approved changes go live
- Monitor - ongoing monitoring continues
Who does what (Existing)
| Phase | Specialist | Tool/System | Artifact |
|---|---|---|---|
| Intake | Conductor or Adros CEO | Operator channel | Minimal context |
| Connect | Client + Adros | OAuth flow | Access granted |
| Audit | Adros CMO | Audit workflows | Audit deliverables |
| Research (conditional) | Adros Research | Research workflows | Supplemental research outputs |
| Ingest | Adros Research | Memory + brand tools | Updated business context |
| Reallocation / fixes | Adros Deployer | Execution tools | Applied or queued changes |
| Creative refresh (conditional) | Adros CD | Creative workflows | New copy + creatives |
| Approval | Operator | Command Center or external approval channel | Decision |
| Execute | Adros Deployer | Deployment tools | Updated campaigns |
| Monitor | Adros | Daily monitoring loop | Alerts |
4. Shared artifact contract
External conductors should think in terms of named artifacts handed from one phase to the next.
| Artifact | Produced by | Consumed by | Format |
|---|---|---|---|
| Research input package | Research bridge / Adros Research | Adros Research / Adros CMO | Structured docs, sheets, or JSON depending on workflow |
| Brand assets | Research bridge / brand extraction | Adros CD | DAM assets |
| Keyword research deliverable | Adros Research | Structure phase | Workbook/package output |
| Market research deliverable | Adros Research | Structure phase | Package output |
| Audit deliverable | Adros CMO | Adros Deployer / operator | Workbook/package output |
| Structure deliverable | Adros CMO | Adros CD / Adros Deployer | Workbook/package output |
| Copy + creative deliverable | Adros CD | Adros Deployer | Workbook + assets |
Important: public docs intentionally describe these at the package level. Specific file mixes can vary by workflow or deployment, so consumers should rely on task status and the package expectations exposed by their own environment.
5. Routing logic
At a high level:
- Fresh client: research first -> structure -> creative -> approval -> launch
- Existing client: audit first -> optional research -> fixes/creative -> approval -> execute
If you are building an external conductor, the safest pattern is:
- keep every phase as a tracked task
- route only at clear phase boundaries
- surface approvals only at review gates
- treat supplemental research as conditional, not mandatory
6. Public guidance for research bridges
Adros does not require a single vendor lock-in for research bridges. The public product direction is Perplexity + DataForSEO + Firecrawl + platform-native data. Whatever stack you use, keep the bridge thin:
- one structured input contract in
- one structured research payload out
- then hand control back to Adros for ingest and downstream routing
That keeps your orchestration layer stable even when providers change.