Strategy memos

The memo your agent drafted, pressure-tested by the people who must execute it.

Leads comment on one memo. Agent connect adds a pre-mortem when a lead asks for the ways it fails.

Set it up for your agentHow agent connect works
livememos/warehouse-focus.md

Warehouse focus

Owner: Victor Lang. Company: Saltmarsh Robotics. Decision is not recorded here.

Proposal: Saltmarsh Robotics drops the consumer robot line and focuses on warehouse deployments. This memo is the argument. The decision, when they make one, lives wherever Saltmarsh already records decisions. Record it there, not here.

Revenue

Consumer revenue in this memo is the robot line only. Spare parts are not in the number.

Support still ships spare parts for robots already in the field. Those orders are small, and they are real. A memo that ignores them will get the revenue line sent back. Say the parts stream exists even if the proposal is to stop selling new robots.

What would stop

  • New consumer robot SKUs. The current service stock keeps moving until it is gone.
  • The consumer marketing calendar. Warehouse pilots keep their dates, including the one already booked.
  • Hiring tied to the consumer line. Warehouse hiring stays in the plan and is not a cut.

Pre-mortem

Q1 risks: to be written.Three ways this fails in Q1: parts revenue, a late warehouse pilot, a hiring gap.

Read those three before the leads treat the memo as a decision. This file does not record one. Victor has not signed anything in this draft. The decision, if they make one, is recorded somewhere else.

Spare parts are not in the number

Martin Achterberg

The consumer spare-parts stream is not in the number. Those parts still sell.

Elena Petrov

Support still ships those parts. The memo should say so.

Q1 risks

Elena Petrov

@agent add a pre-mortem: three ways this fails in Q1.

agent

Added three Q1 failure modes: parts revenue, a late warehouse pilot, and a hiring gap. Leaving this open so the leads can read them.

Start with @agent to ask the agent
ResolveReply
Fictional example: a Saltmarsh Robotics strategy memo in Gander, with a finance thread and a scripted agent connect reply.

How strategy memos get reviewed today

A doc comment pass works for a frozen memo. It lags when the agent is still revising the argument from the notes on the founder's machine.

A leadership meeting catches the disagreement and leaves it in someone's notebook. The people who were not in the room never see the thread on the paragraph.

Three ways this fails

Victor Lang asks his agent for a memo proposing that Saltmarsh Robotics drop the consumer robot line and focus on warehouses. He runs gander watch on memos/warehouse-focus.md and sends the link to Elena Petrov and Martin Achterberg.

Martin highlights the revenue line and says the consumer spare-parts stream is not in the number. Elena replies that support still sells those parts. Human thread.

Elena starts a new comment: "@agent add a pre-mortem: three ways this fails in Q1." Victor's agent adds three failure modes, replies, and leaves the thread open. Martin reads them on the same link. The decision, when they make one, lives wherever Saltmarsh already records decisions.

Who's in the doc

WriterCOO or leadCFOThe author's agent

Writer Founder or exec. Sends the memo.

COO or lead Checks whether the team can actually do it.

CFO Checks the number the memo treats as given.

The author's agent Adds the pre-mortem when a lead 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 strategy memos

Grok BotA memo from a brief, with agent connect through the Gander MCP server.
Claude CodeWhen the memo lives beside the planning notes, MCP carries agent connect.

Pressure-test the memo on the live draft, with the people who would have to carry it out.

See how it works on the homepage