How it works

You tell your agent that growth has stalled. It does not reach for a SWOT.

It asks who decides, by when, and what number would count as success. Then it writes down the answer it would give if the project ended today, and spends the rest of the time trying to prove itself wrong. Every number gets a source, or it gets called what it is: an assumption.

Then the partner reads it. Expect "so what?", expect numbers that don't tie, expect the premortem. If it survives, it ships.

A real partner review

We gave the partner a weak board summary from a fictional bakery chain and asked: "Is it ready?"

It also caught a problem nobody had planted: read correctly, the plan falls EUR 4.1m short of its own target.

The firm, in three skills

strategy-engagement

Turns a vague briefing into a sharp question, a first answer and a plan to test it. Then does the research.

strategy-deliverables

The model and the deck. Excel with live formulas, slides in HTML and PPTX, or a one-page memo.

partner-review

Reads anything before it leaves the building. Returns it, or lets it go with fixes.

Six playbooks come with it:

Growth

Market entry

Turnaround

Pricing

M&A

Operating model

Install

Runs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and other agents that load skills. Then talk to it like you would to a partner: "We're a 60-million bakery chain and growth has stalled. What should we do?"

What it believes

• The question comes before the analysis.
• Answer first, then try to kill it.
• A number without a source is an assumption, and it says so.
• Nothing leaves without the partner.

Free, open source, MIT licensed.

Built by people who have run agencies and worked alongside strategy consultants on client projects for years.