OMNICON TEAM

15 workstreams, one context each.

Omnicon began as a headless content management system. It now speaks MCP, and is being rebuilt as a CMS that AI agents can read and write directly. One workstream moves at a time, each in a conversation of its own.

Talk to us about Omnicon See the workstreams

workstreams this needs

kinds of user we build for

steps every workstream follows

WHO IT IS FOR

Omnicon is built for five kinds of user

The people who write, the people who wire it up, the people who publish and the people who own the account. And now a reader that is not a person at all: an AI agent is a user of this CMS too.

Editors and content teams

The people making the articles and the assets, and getting them live.

Workstreams serving them5

Web experience
Media management
SEO tooling
Help content
CS / QA

Developers

The people wiring Omnicon into their own sites and apps through the API and MCP.

Workstreams serving them3

API / MCP
App listings
Help content

Marketing and PR

The people who get the work found and in front of someone.

Workstreams serving them7

Web experience
SEO tooling
PR management tooling
Analytics
Ad server
PR / SNS
Sales

Account owners

The people holding the contract, the billing and the permissions.

Workstreams serving them7

Analytics
Ad server
Help content
CS / QA
Sales
Billing
Admin portal

AI agents

Reading and writing content over MCP. A user of the CMS that is not a person.

Workstreams serving them2

API / MCP
App listings

THE ROSTER

The workstreams behind Omnicon

One workstream, one objective. They divide into the content features themselves, what connects the CMS to the outside, what keeps users supported, and what keeps the service running. What follows is the set of workstreams this product needs, not only the ones busy today.

Working with content

Write it, hold it, publish it, and see whether it landed. The CMS proper.

Web experience

Make published content arrive fast and read well.

Editors Marketing

Media management

Keep images and video findable and reusable after the day they were uploaded.

Editors

SEO tooling

Let the writer fix how a piece will look in search before it goes out.

Editors Marketing

PR management tooling

Keep distribution lists and what came back from them in one place.

Marketing

Analytics

Feed what actually landed back into what gets made next.

Marketing Admins

Ad server

Let ad slots and placements be handled inside the CMS.

Marketing Admins

Connecting to the outside

Everything a person can do on screen, an API call or an agent should be able to do too.

API / MCP

Make what the screens can do available through the API and MCP as well.

Developers Agents

App listings

Stay findable and installable in the OpenAI, Claude and Microsoft marketplaces.

Developers Agents

Getting it out, and standing behind it

Be known, leave nobody stuck, and do not let defects pile up.

PR / SNS

Keep saying, outside, what Omnicon is actually for.

Marketing

Help content

Let people solve it themselves instead of waiting for support.

Editors Developers Admins

CS / QA

Answer what comes in, and turn it into a fault that cannot happen twice.

Editors Admins

Bug squash

Clear found defects as they arrive instead of letting a backlog grow.

Sales

Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.

Marketing Admins

Running the service

Contracts, billing, permissions. The unglamorous part that keeps it usable.

Billing

Bill what was used, correctly and on time.

Admins

Admin portal

Let the people running an account manage contracts and permissions themselves.

Admins

WHAT SHIPPED

How far towards agent-native

From headless to agent-native, one release at a time. These are the steps.

THE LOOP

How one workstream moves

Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.

See the eight steps

See how a change gets released

01
Set the objective
An editor, a developer or an agent — who it gets better for, and how. People decide that.
02
Open the session
One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.
03
Build it, review it
Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.
04
Check the number
Read how the published work was actually read, then rewrite the objective. More features is not a result.

ONE AT A TIME

That is how this much stays covered

The workstreams do not all run at once — one moves at a time. Rebuilding from headless to agent-native without stopping ads or billing works because one conversation only ever holds one workstream.

Instructions do not mix

Work on media management does not queue behind MCP support. Each moves on its own objective.

What is shared, and what is not

Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.

Context survives

Decisions accumulate inside each workstream, so picking it up again does not start from zero.

Long ones get their own branch

When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.

Ship small

Many small changes rather than one large one. We are holding other people's content, so each change stays inside a range we can roll back.

STILL OURS

What people decide

Agents can write now. The responsibility did not move.

Whether it goes out
An agent can take a draft a long way. Whether it gets published is a human decision, and in a CMS that is not a line we will move.
What we will not do
We can do more than before. That is exactly why the decisions worth our time are the ones to decline.
What we promise clients
Dates, estimates, quality. A company promises those, and a company is people.
What goes to production
Review and merge. A person presses the last button.

LET'S TALK

We can build your content platform the same way.

Omnicon is a CMS moving from headless to agent-native. If you want your own content reachable by AI, that is a conversation we are glad to have.

Talk to us