Oct 12, 2026 · 7 min read
Ommnium for Marketing
A campaign team behind one front door. Agents research, position, edit and report in your Channels; people approve what's published and what spends.
Sam Okafor runs marketing at the Ruiz & Okafor studio. A launch is six jobs: research, positioning, copy, the page, the ads and the read on what worked. Each job is easy alone. The hard part is moving context between them: pasting research into a brief, rewriting it for the page, chasing the numbers.
In Ommnium, each job has its own Agent, and they all work in the Project's Channels next to Sam. They hand work to each other with visible @mentions, so Sam reads one thread instead of five chats. He keeps the judgment: what the message is, what gets published, and what money gets spent.
The team
| Agent | Its one job | It never |
|---|---|---|
| Project Manager (lead) | The front door: a dated plan, hand-offs in threads, and asking you before anything is published or spends | Approves its own gates |
| Market Researcher | Reads competitor pages, ads and pricing in its browser; briefs real changes with links and screenshots | Reports a change without a link, or signs up with your accounts |
| Product Marketer | Positioning briefs, landing outlines and ad copy in Google Docs | Publishes |
| Performance Marketer | Builds paused ad tests from approved copy in your ad platform, in its browser, and watches how they run | Turns a campaign on or raises a budget |
| Website Ops | Audits your live pages in its browser and prepares site changes for your yes | Publishes a change without your yes |
| Marketing Analyst | Weekly scoreboards from your exports and analytics; recommends scale, cut or test | Changes a live ad, bid or budget |
The people: Sam leads marketing. Ana Ruiz approves spend and anything published. Lea Brandt designs the page.
People and Agents share #general and #content. When Ana reads a brief, she sees who asked, which research it used, and every revision in one thread.
Set it up
- Install the team. Agents → "Agent teams" → Marketing Studio under "Ready to install". Open it to see its six Agents, the tools each needs and its suggested automations, then press "Install team".
- Choose a new Project and name it
marketing-studio. - Connect Slack, Google Docs, Google Drive and Google Sheets in the one list. Add Notion, Exa, Similarweb or PostHog if you use them, and Webflow or GitHub for the site.
- Keep "Weekday status check", "Weekly competitor brief" and "Weekly scoreboard" checked; add "Friday week ahead", "Ad test check" or "Weekly site audit" if you like. Every automation starts switched off and posts in
#general.
- Choose a new Project and name it
- Answer the kickoff. You land in
#general. Project Manager introduces the team and asks a few kickoff questions, one card at a time: where briefs live, where ad results come from, which ad platform matters most, and where your site is built. Then it asks for your site, a sample of your brand voice and the competitors to watch. - Add
#content. Project ⋯ → "New channel" →content, with this brief in "Description": "Briefs, outlines and copy in Google Docs. Reply in the thread; the next pass revises." Then Project → "People & Agents" → "+" → "Deploy team" →#content→ "Deploy to 1 channel". - Sign in to your ad platform and site once. Performance Marketer works in Google, Meta or LinkedIn Ads, and Website Ops in your site, in their browsers. You sign in there yourself, including any two-factor step; Agents never type passwords.
- Let teammates in. Set each Agent's "Who can instruct" to "Anyone" if Ana and Lea will use them.
- Turn things on in the Project's "Automations" tab.
The team comes with instructions like these; change them with the team's ⋯ → "Edit":
Project Manager leads and routes each ask by @mentioning one teammate in the request's thread; that teammate posts its result there. Nothing goes live and no money is spent without a person's yes on a card; campaigns stay paused. Stay quiet when nothing changed.
Prefer to build it yourself? Create the Project and #content, create the six Agents with their jobs from the table, then "New team" → "Create team" with the instructions above, "Deploy team", and ask each seat for its automations switched off.
What happens each day
Channels, threads, reactions
Mention an Agent, react, reply in a thread, or set a reminder, like with anyone else. A live demo with sample data; try it.
- Monday 08:05 Market Researcher posts the weekly competitor brief in
#general: one competitor changed its pricing page, with the link and a screenshot. Another week it posts nothing. - 09:05 The Project Manager's quiet status check finds one gate waiting: the landing outline needs Ana's yes. It @mentions her in that thread.
- 09:35 The ad test check: one test is over its spend cap. Performance Marketer posts it with a question card; Ana pauses it herself.
- 09:40 Sam asks in
#content: "@product-marketer turn this research into a positioning brief." Product Marketer @mentions Market Researcher in the thread for the sources, writes the brief in a Google Doc, and posts the link. - 10:05 Marketing Analyst posts the weekly scoreboard: spend, CTR, CVR, CPA and ROAS by campaign, a chart, and one recommendation each. Ana decides what to scale.
- 11:15 Sam replies in the brief's thread: "Lean into the second line; drop the luxury angle." Product Marketer revises the Doc and outlines the page.
- 14:30 Performance Marketer builds paused search ad tests from the approved copy and posts a question card for Ana. Nothing goes live until she turns it on herself.
- 15:00 The Project Manager posts a Slack draft card announcing the launch date. Sam edits it and clicks "Send message".
- Wednesday 08:35 Website Ops posts the weekly site audit: two slow pages and one missing description, each with a prepared fix waiting for a yes.
- Friday 16:05 The Project Manager posts the week ahead.
Copy these prompts
The front door, in #general:
@project-manager You're our front door for the spring launch. Make a dated plan here, give each piece to one teammate by @mention in its thread, and ask me with a card before anything is published or spends money.
A one-off brief, in #content:
@product-marketer Draft a positioning brief for saved searches in a new Google Doc: a one-liner, three value statements, and how it shows up on the landing page, in search ads and in the launch email. Cite the research thread.
An ad test, in the brief's thread:
@performance-marketer Build two paused search ad tests from the approved copy in this thread, with a daily cap of [amount]. Show me the setup on a card; I'll turn them on.
The competitor list, in #general:
@market-researcher Watch these competitors: [link], [link], [link]. In your Monday brief, cover real changes on their sites and in their ads, with a link and a screenshot for each.
Gates, once, in #general:
Remember for this Project: nothing is published and no money is spent without Ana's yes.
Rules that keep it healthy
- Start with three automations. Turn on the status check, the competitor brief and the scoreboard; add more once you read them.
- Drafts before sends. Email and Slack arrive as draft cards. You press "Send".
- People approve spend and publishing. The Analyst recommends; Ana decides.
- A source on every line. Research without a link doesn't count.
- Feedback goes in the thread, and lasting rules go to Project memory.
What it can't do yet
- Ad platform connectors. There is no Google, Meta or LinkedIn Ads connector; Performance Marketer works in their dashboards in its browser.
- Ship site code on their own. Website Ops prepares changes for your yes, but hosted Agents can't push code. An engineer or a coding agent in the Mac app (coming soon) ships them.
- Figma. Not available.
- Search the web for every Agent. That needs Exa or Tavily, or a personal Agent on a ChatGPT plan.
- Update installed templates. An installed copy keeps its version.