eoma

Docs › Start here

What EOMA does, and what you do

An honest division of labour — what runs without you, what needs your approval, and what EOMA cannot do at all.

In 10 seconds

The short version

EOMA is closer to "does the work" than "gives you a dashboard", but the honest answer has a boundary in it and the boundary is worth understanding before you buy.

Automatic, forever, without you: asking the engines, reading the answers, scoring them, tracking competitors, finding the gaps, and keeping your board of what to do current (on Growth and above, with new actions written every week from those gaps). You could ignore EOMA for a month and come back to a full history and a current board.

Automatic once you say go: producing the actual work. Press Start on an action and an agent researches it, drafts it, and brings it back finished. Most weeks that is a real page, a schema block, a correction — not an outline.

Always yours: deciding whether it goes live. EOMA will not publish to your site without you approving that specific piece and choosing the destination. On a repository it opens a pull request and stops; merging is yours.

Never EOMA's: anything that needs a person in the world. Calling a supplier, getting listed in a trade directory that requires a phone verification, changing your prices, getting a journalist to write about you. Those appear on your board under a header that says EOMA cannot do them, with the steps written out.

The rough shape: EOMA removes the finding out and most of the making, and leaves you the deciding and the doing things in the world.

How it works

What runs with no input from you at all

How often
Asking your questions to four AI engines and recording the answers Every 3 days on paid plans
Scoring those answers across eight axes After every collection
Folding competitor names, tracking who the engines cite Continuous
Weekly search-results checks on your tracked keywords Weekly
Social listening on X and LinkedIn (Growth and above) Weekly
Writing new actions from your measurements and topping the list up (Growth and above) Weekly
Emailing you when something needs your attention As it happens

What needs one click from you

What is entirely yours

What this means for you

You do not need an engineer, and you do not need a marketing team. The connections are sign-in approvals; the output arrives as drafts to approve rather than code to deploy. Almost every EOMA customer is a founder without an in-house marketing function — that is who the product is shaped for.

But you do need about an hour in week one. Setup, reading your question set, and connecting one publishing surface. Skipping the second of those is the single most common way people end up with months of measurement pointed at a market adjacent to their own.

And you need roughly one decision a week after that. Your plan lets EOMA run three done-for-you jobs at a time on Growth, and a seat frees as each one finishes; on Starter it gives you three in total, which do not renew. Realistically that is a weekly appointment of fifteen minutes: read the board, start the one that matters, approve last week's draft — on Starter, the starting part happens three times in all.

Do not expect EOMA to close the loop on your repository yet. When you merge a pull request, nothing in EOMA notices automatically — the row stays In progress until someone closes it. This is a known gap being worked on, and it is the one place where the hand-off is genuinely rougher than it should be.

The measurement is worth something even if you never start an action. Knowing which questions you lose, and to whom, is a real input into decisions EOMA has nothing to do with — pricing, positioning, which market to enter next.

Common misunderstandings

People assume Actually
"This is an analytics product, so I have to interpret it myself." The recommendation list is the interpretation. The screens exist so you can check the reasoning, not so you can do the reasoning.
"It is an autopilot, so I can leave it running." Measurement runs unattended; work does not. Nothing is produced until you press Start, and nothing is published until you approve.
"It will publish things to my site without asking." It cannot. Approval names the specific piece and the specific destination, and the live-site path asks you to confirm that visitors will see it immediately.
"If EOMA cannot publish it, the work is wasted." Every draft exports as Markdown, HTML or PDF, or copies as a prompt. You can apply it by hand and mark the row done.
"The recommendations are generic content-marketing advice." On Growth and above, the weekly ones are generated from your own measured gaps: a specific question you lost, to a specific competitor, on a specific engine. Starter's board holds a fixed set of six routines instead.
"I can hand this to an agency and stop thinking about it." You can, and several customers do. The setup accuracy and the weekly approval still need somebody who knows the business.
Reading this as a machine? The same page in Markdown: /docs/start-here/what-eoma-does-and-what-you-do.md

On this page