From a discovery call transcript to a client-ready proposal deck

After a discovery call, the proposal is due before the follow-up: the process you heard, an architecture that fits, what it will cost to run. CoPage is where your agent builds those slides from the transcript and your team reviews them before anything reaches the client.

The CoPage app is in early access. Decks live only in the app; the free CLI handles diagrams.

#How it works

1. Save the transcript. Teams, Zoom and Google Meet can write one. CoPage doesn't record or transcribe calls.

2. Connect your agent to the CoPage app. Claude Code, Codex, Cursor and VS Code with Copilot connect through MCP: copage connect claude --cloud signs the agent in from your browser and gives it its own key, and Account → AI agents has the setup for each tool. In Claude or ChatGPT, add CoPage as a custom connector and sign in.

3. Ask for what you need. For example: "From this transcript, build the claims process in BPMN, the target architecture on Azure and the run cost, as a six-slide proposal deck in CoPage, in our theme."

4. Watch it build. The agent creates the deck and the diagrams, places each diagram on a slide and renders the slides to look at its work. Its edits appear live in the editor, highlighted, with Undo. One agent edits a document at a time, and anyone on it can stop the agent.

5. The checks run. The agent runs the Client-ready pack and fixes what it finds: connectors left loose, leftover placeholders (TODO, TBD, [Client name]), email addresses, phone numbers, IBANs or card numbers, money in more than one currency, and hidden slides that would still go out with the file. The pack also has two AI checks, for a professional tone and for personal details about a private person, which run in the app.

6. Your team reviews and signs off. Comment on a slide or an area of a diagram the way you would for a colleague; a comment for your agent is an instruction, and it replies when it's done. Edit anything by hand: the agent builds on your changes. Only people set a document's status (Draft, In review, Ready); agents can't mark their own work Ready, and people can lock finished slides or limit an agent to comments.

7. Export. Native PowerPoint (text, shapes, tables and charts you can edit; each diagram as one sharp picture) or PDF, one page per slide.

#What you get

• A deck in your brand: themes come from a brand color, a logo or a website, and new slides use the theme's type scale and master (logo, footer, page number).
• Linked diagrams: the process and the architecture are diagrams of their own, shown on slides. Fix one once and every slide that shows it updates. Export them separately as SVG, PNG or draw.io.
• A run cost slide as a native table or chart. The agent writes the figures and your team checks them: CoPage doesn't look up cloud prices.
• History of who changed what, a person or an agent acting for one. Versions from the last 30 days can be restored, and a version a person marks with a status is kept for good.

#A sample

On our home page, a fictional telco, Halden Mobile, wants an AI agent to handle billing disputes on Azure. The first version of its run cost lists one service in dollars while the rest is in euros; the currency check flags it and the agent fixes it. The client is fictional and the run reenacted; the diagrams and the cost table are real CoPage documents. The app's "Start from" templates also include three finished sample engagements of Ostrell Vane, a fictional consulting firm.

#Who it's for

Pre-sales engineers, solution architects and consultants who write proposals after discovery calls, and the managers who sign them off. Teams can run CoPage on its EU cloud (documents stored in Frankfurt) or, as a pilot, on their own infrastructure.

#Read more

• Connecting your agent: MCP, connectors and keys for each tool.
• Checks: the Client-ready pack and the rest of the library.
• Diagrams: what agents can draw and how diagrams sit on slides.
• CoPage for enterprise: pilots, private deployment, security. Request early access.