Landing page copy

Review the site copy before it is in the CMS.

Design, product, and the founder check the promises. Agent connect rewrites a headline that offered a feature you do not ship.

Set it up for your agentHow agent connect works
livesite/pricing-page.md

Pricing page

Owner: Meera Shah. Site: Cobaltfern Analytics. Three plans.

New pricing-page copy for Cobaltfern Analytics. Three plans, in the words the docs already use. This file is reviewed here, then it goes into the CMS. It does not go live from this draft.

Headline

Export every workspace to a spreadsheet before the trial ends.Three plans. The docs list what each one includes.

The old headline promises an export we do not ship. The docs wording does not. Use the docs line, and do not add a feature in the headline to make the page sound larger. The trial can end without a spreadsheet. Do not invent a file the product does not write.

Plans

Plan names: Harborwide Enterprise, Cobaltfern Studio Plus, and Yardlight Unlimited.

  • Those names do not fit the cards. Shorter labels are a separate edit, and they are not in this pass.
  • Smallest plan: one workspace. Middle plan: shared workspaces. The docs already say this.
  • Largest plan: the middle plan plus priority support. No fourth plan, and no renamed middle.
  • Card order follows the docs: smallest, middle, largest.

Do not add

  • Do not mention a spreadsheet export. It is not in the product, and the old headline did.
  • Do not invent a plan name to fill a card. Three plans, as the docs list them. Field, Studio, and Yard can wait for a later pass. This pass only removes the export we do not ship.

Harborwide Enterprise

Ana Lima

These plan names will not fit the cards. We need shorter labels.

Rohan Mehta

Field, Studio, Yard. Do not invent a fourth.

Export every workspace

Rohan Mehta

@agent this headline promises a feature we do not ship, use the docs wording.

agent

Rewrote the headline to match the docs. Removed the unshipped export promise.

resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: Cobaltfern Analytics pricing-page copy in Gander, with a design thread and a scripted agent connect reply.

How site copy gets reviewed today

Reviewing copy inside the CMS is sometimes the only shared surface. It is also late, and the agent that drafted the words is not in the CMS.

A shared doc is a fine markup pass. It forks when the agent revises the file in the repo. A design review catches layout and can miss a promise the product does not keep.

Do not promise the export

Meera Shah asks her agent for new pricing-page copy for Cobaltfern Analytics: three plans, plain language. The agent writes site/pricing-page.md in the site repo. Meera runs gander watch and sends the link to Ana Lima and Rohan Mehta.

Ana highlights the plan names and says they will not fit the cards. Rohan replies with shorter labels. Human thread.

Rohan starts a new comment on the headline: "@agent this headline promises a feature we do not ship, use the docs wording." Meera's agent rewrites the headline to match the docs, replies, and resolves the thread. Ana sees it on the same link. The copy goes into the CMS after that, not before.

Who's in the doc

WriterDesignerFounderThe author's agent

Writer Marketing or founder. Sends the draft before the CMS.

Designer Checks length, hierarchy, and what the layout can hold.

Founder Checks that the promise is true.

The author's agent Rewrites the line when someone uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit landing page copy

CursorThe copy lives in the site repo, next to the page, with MCP for agent connect.
Claude CodeSame repo. The session that drafted the page hears agent connect through MCP.
Grok BotA prose draft from a brief, if the file is on the author's machine and MCP is connected.

Catch the unshipped promise on the draft, before the CMS has a version the agent cannot see.

See how it works on the homepage