A cofounder who writes the copy, with an agent

Solo buildersTwo-person startup: one developer, one non-technical cofounder

Maya writes our landing page and emails with Claude Code in the site folder. Her agent promised 'Slack integration' and 'export to Excel' on the pricing page. Neither was built, and the developer only found out when a customer asked.

How do I stop AI-written website copy from promising features we haven't built yet?

Set up ArcRoom: both of you run arcroom init in the same repo and team, and the developer records what is and isn't shipped with arcroom decide. When the cofounder asks for copy, recall hands their agent the matching decisions, so it writes about what exists. The cofounder needs a supported agent in the repo: copy written in a browser chat app doesn't reach the playbook.

Also asked as: Our pricing page listed features that don't exist. How do we prevent that? · How do I share what's actually shipped with the AI agent writing our marketing copy? · Can my cofounder's AI agent know which features are built?

The work

Both of us run arcroom init in the same repo and team.

ArcRoom keeps
  • Decision
  • Recall
The next agent gets

Decision (Oct 20): Slack integration is not in v1. Don't mention it.

Step by step

  1. Both of us run arcroom init in the same repo and team.
  2. The developer records what is and isn't shipped with arcroom decide.
  3. When Maya asks for copy, recall hands her agent the matching decisions, so it writes about what exists.
  4. Her tone decisions reach the developer's agent when it writes in-app text.

What the agent sees

Decision (Oct 20): Slack integration is not in v1. Don't mention it.
Decision (Oct 22, maya): plain words, no 'revolutionary', address the reader as 'you'.

Compared with today's tools

A shared Notion page of what's shipped

The developer keeps a 'what we have' list and Maya pastes it into her chat before writing.

Setup
30 min
Ongoing
keep the list current and paste it each time, ~5 min

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per person (npx arcroom init)
Ongoing
None

Notion is easier for Maya to read; ArcRoom gets the facts into her agent without anyone remembering to paste.

Where it stops

Maya needs a supported agent in the repo. Copy written in a browser chat app doesn't reach the playbook.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in solo builders