← How it works

Agentic Hub architecture

PeopleGoals and plansSet outcomes, priorities, and budgetsGuardrails and policyDefine limits, claims, and consent rulesApprovals and reviewApprove consequential work, handleescalationsAgentic HubCoordinates every agent and person against one planPlannerTurns goals into tasksRouterSends work to theright specialistShared contextPlans, facts,audiencesApprovalsTracks states,enforces reviewRun logRecords every decisionSpecialist agentsResearchAccounts, markets,sourcesContentDrafts, edits, checksDemandTargeting and outreachLifecycleJourneys and timingAnalyticsReporting and anomaliesTool connectors: scoped permissions, hard guardrails, every call loggedSystemsCRMCMS and siteEmailAdsAnalyticsKnowledge baseSignal data layerIdentity, consent, intent, and the unified event streamOutcomes and learning feed back into plans
  1. People
    • Goals and plansOutcomes, priorities, budgets
    • Guardrails and policyLimits, claims, consent rules
    • Approvals and reviewConsequential work, escalations
  2. Agentic HubCoordinates every agent and person against one plan
    • PlannerGoals into tasks
    • RouterRight specialist
    • Shared contextPlans, facts, audiences
    • ApprovalsStates and review
    • Run logEvery decision
  3. Specialist agents
    • Research
    • Content
    • Demand
    • Lifecycle
    • Analytics
  4. ConnectorsTool connectorsScoped permissions, hard guardrails, every call logged
  5. Systems
    • CRM
    • CMS and site
    • Email
    • Ads
    • Analytics
    • Knowledge base
  6. DataSignal data layerIdentity, consent, intent, and the unified event stream
  7. Outcomes and learning feed back into the hub's plans.
Agentic Hub architecture. People set direction and limits; the hub coordinates; agents act through governed connectors; outcomes feed back.

The Agentic Hub is the coordination layer between people, specialist agents, and the systems they act on. It plans, routes, holds shared context, enforces approvals, and records every run, so many agents can work as one system.

What each part does

01

People

Set goals, priorities, and budgets; define guardrails, claims, and consent rules; and approve consequential work.

02

Planner

Turns a goal into tasks with owners, dependencies, assumptions, and risks, and replans visibly when results change.

03

Router

Sends each task to the right specialist agent or person, asks for clarification when a request is ambiguous, and never forces a bad fit.

04

Shared context

Holds the campaign plan, approved facts, audience definitions, and decisions once, so every agent works from the same source.

05

States and approvals

Tracks where every piece of work stands and makes sure approval steps cannot be skipped.

06

Run log

Records every run, tool call, decision, approval, and outcome, which makes evaluation and audit possible.

07

Specialist agents

Narrow agents with one job each: research, content, demand, lifecycle, and analytics.

08

Connectors and systems

Agents reach the CRM, site, email, ads, analytics, and knowledge base only through scoped, logged connectors with hard guardrails.

09

Signal data layer

Identity, consent, intent, and the unified event stream underpin every decision, and outcomes flow back into plans.

See the architecture in the product

Marketix is built on these diagrams: specialist agents, governed connectors, and a hub that plans, routes, and records every run. Sign up for early access.