Keep the runtime you already operate
Models, compute, sessions, memory, tools, secrets and channels remain in OpenClaw or Hermes. MarketingOS does not require another AI subscription or move the server load to us.
Product
A marketing team that does not start over with every chat.
OpenClaw can call models, use tools and delegate assignments. It still needs the context of your business. MarketingOS keeps offers, audiences, goals, sources and decisions together and gives each specialist a clear brief.
The captures come from a reproducible Velunor Bikes product state. The company, domain, goals and metrics are invented. The Runtime capture is archived. The current Security capture shows product boundaries, but it is not evidence of a customer deployment.
01 / TODAY
The business goal comes before the activity.
The opening view brings the goal, metric, context status, next decision and latest evidence into one workspace.02 / STRATEGY
Business context is saved and revisioned.
Company, brand, audiences, offers, websites and markets share one version. The interface exposes its revision, hash and save state.03 / GOALS
KPIs stay bound to a source and time window.
The fictional business goal carries its metric. The source, demonstration window, current value and target remain visible.04 / SOURCES
Each source keeps its own state.
Website, SiteOne, Google Search Console, Google Analytics 4 and Bing remain separate sources. The displayed GA4 property mapping is a disconnected synthetic fixture with an analytics.readonly label, not evidence of connector availability or a provider call.05 / APPROVAL
The decision applies to the exact payload hash.
The target system, business goal, risk level and payload hash appear before the action. The disconnected synthetic fixture reviews a local brief and makes no provider call; it does not describe the availability of the managed Google review candidate.06 / RUNTIME ARCHIVE
This Runtime capture belongs to an earlier build.
The synthetic image predates the current tool bridge, workspace binding and heartbeat migration. It explains the layout of the status view only. The current source record for all eleven OpenClaw specialist routes is separate and does not turn this archived capture into runtime evidence.07 / AGENT TEAM
Twelve roles receive an actual status.
The showcase reports the orchestrator, Strategy Lead and Tech SEO as active. The remaining roles are available. These synthetic states only demonstrate how runtime presence appears in MarketingOS.08 / ADDONS
Available and planned never look the same.
The synthetic alpha presents SEO/GEO as the first implemented preview scope. Social Media, Lifecycle CRM and Paid Performance remain planned. The same applies to the Growth Bundle and Agency Pack. The source state is not presented as an approved customer package. Neither availability nor prices are invented.09 / SECURITY
Security profiles and open boundaries belong in the product.
The current capture shows the Direct default, the limited OpenClaw Secure state and the closed Hermes Secure profile. The displayed Velunor Bikes state is a disconnected synthetic fixture and makes no claim about the availability of the separate managed Google review candidate. This is technical UI evidence, not a security promise for a customer deployment.The team knows more than the last prompt
Brand, offers, audiences, markets, voice, websites, goals and KPIs live in a versioned context. An agent sees not only the task, but the business reason behind it.
One assistant becomes a set of clear specialists
In OpenClaw, one orchestrator coordinates eleven specialist marketing agents. Technical SEO, GEO, Content, Measurement, Demand and other roles receive only the part of the assignment they own.
Technical SEO begins with a real crawl
SiteOne installs as a required part of the SEO/GEO addon. Every specialist uses the same managed crawler and can inspect technical website state repeatedly instead of guessing from visible page copy.
A number keeps its origin
Website, crawl and Bing remain separate sources. For GSC, GA4 and GTM, the managed Google connector covers exactly eight incrementally selected capability groups. Three reads may run after authorization; property, period, freshness and known gaps remain visible.
A Google write is never autonomous
Each of the five writes requires an exact target and payload preview, one-time approval, at most one provider attempt, a receipt, provider post-check and rollback where supported or explicit recovery. GTM version creation and publish remain separate approvals. Google tokens stay server-side in the managed connector and never reach the browser, Local Agent, OpenClaw, Hermes or a model. General CMS, Bing and other writes stay closed without their own connector contract.
Completed and successful are different states
A receipt records what was technically executed. Rankings, mentions, leads or revenue need a later observation with a baseline and an appropriate measurement window.
The Control Surface makes the operation visible
Business context, goals, KPIs, sources, assignments, approvals, agent state, addons, security and audit are available in light and dark interfaces. A protected mobile view can run on the private network.
Continue
One discipline is implemented as a preview
SEO/GEO is the first implemented MarketingOS addon scope. No customer package has been approved yet. Social Media, Lifecycle/CRM, Paid Performance, the Growth Bundle and Agency Pack remain planned.