How Tomoe works.
Three steps: research your product, have every channel agent draft from that research, then publish only what your team approves. This is the flow we are building with our early beta teams.
Step 1, research
Tomoe writes your strategy first.
Tomoe reads your site, docs and pricing, and your repo if you connect it, then writes five documents. Your team can edit every one. Every agent reads them before it drafts anything, so the article, the reply and the email all describe your product the same way.
Product information
product.md
What you sell, who pays for it, and the problem it solves, in plain words.
Positioning
positioning.md
The one sentence a buyer should repeat after reading your homepage.
Competitor analysis
competitors.md
Who else the buyer is looking at, and where you are stronger or weaker.
Brand voice
brand-voice.md
How your brand writes, pulled from your site, docs and posts, so drafts sound like your company.
Content plan
content-plan.md
The topics, keywords and threads worth your team's time for the next month.
Step 2, execution
Every agent drafts from the same documents.
Each Monday Tomoe reads last week's Search Console queries and analytics, checks what your team approved and skipped, and writes a one-page plan. Each channel agent then drafts its part of that plan, and every draft waits for your team. Sending without asking is off for every channel until you turn it on for that channel.
SEO
In early betaArticles and landing pages built on keyword gaps from your Search Console.
Waits: In the queue as a full draft. Approve it and it publishes to your CMS.
AI search
In early betaAnswer blocks, comparison pages and FAQ sections for the questions buyers ask AI tools.
Waits: In the queue next to the article it belongs to.
A reply that answers the question in the thread, with no pitch dressed as advice.
Waits: In the queue with a link to the thread, so you can read it first.
X
In early betaPosts drawn from what your team shipped and learned this week.
Waits: In the queue with the planned time. Edit, move or drop any post.
Posts written for buyers and the people who sign off on them.
Waits: In the queue under the profile it will post from.
Writer
In early betaLong-form drafts, product page copy and newsletter sections.
Waits: In the queue as an editable draft with its sources listed.
Technical fixes
PlannedSmall, reviewable pull requests against your site's repo.
Waits: On GitHub as a pull request. You merge it, or you do not.
Finding buyers
PlannedA list of people who asked, with where they asked and what they said.
Waits: In the queue as a list you can trim before any email is written.
Outbound email
PlannedOne email per person, plus follow ups, never sent from your main domain.
Waits: In the queue one email at a time, until you approve it.
Step 3, publish
Approved work goes into your stack.
Numbers flow in to shape the plan, and approved work flows out to your CMS and accounts. Every Friday Tomoe writes a short report: what moved, what did not, and what changes next week.
Integrations are planned for launch. None of these are live yet.
Search Console
Planned for launchQueries you rank for, and nearly rank for, flow in to shape the plan.
Google Analytics
Planned for launchWhich pages bring signups flows in, so next week leans on them.
WordPress
Planned for launchApproved articles publish here as posts.
Webflow
Planned for launchApproved articles publish to your CMS collection.
Framer
Planned for launchApproved articles publish to your Framer CMS.
GitHub
Planned for launchTechnical fixes arrive as pull requests for your team to merge.
X
Planned for launchApproved posts go out from your account at the planned time.
LinkedIn
Planned for launchApproved posts go out from your company page or your team's profiles.
Reddit
Planned for launchThreads flow in. Replies go out only after you approve them.
Slack
Planned for launchDrafts and the weekly report arrive here, to approve without switching apps.
Telegram
Planned for launchThe same approval queue on your phone, one tap per draft.
