CoPage for enterprise

Client work your firm can stand behind. Built by agents, on your standards.

CoPage is where consulting and pre-sales teams turn discovery calls into proposals, architectures and decks with the AI agents they already use: on your brand, checked against your review rules, signed off by your people. In our EU cloud or on your own infrastructure.

Examples of what agents build in CoPage. Your team works on its own templates, brand and review rules.

CoPage

A 24-month AI adoption programme for an industrial group: value case, use-case portfolio, operating model, AWS platform, plan and fees. Built by AI agents in CoPage from a brief, then reviewed and fixed by agents. Ostrell Vane and its clients are fictional; market figures are real and cited on the slides.

One workspace

Proposals and architectures, in one place.

Diagrams sit on slides and stay linked: fix one once, and every proposal that shows it updates.

Decks for pre-sales and delivery

From the discovery call to the proposal: the process in BPMN, the target architecture and the run cost, on slides in your brand that export to native PowerPoint.

Diagrams for architects and developers

Official Azure, AWS and Google Cloud icons, comments the agent acts on, and diagrams that live in the repo with the free CLI and open for editing again.

  • Weeks into hoursfor a proposal deck: agents build it from the call transcript, your team reviews and signs off.
  • Dozens of checksin ready packs, from Client-ready to Business case, run before anything reaches a client.
  • 3,000+ iconsofficial Azure, AWS and Google Cloud shapes, and general ones, built in and offline.

“Take a 10-minute break, come back and already talk over a visual version.”

Enterprise architect, consulting firm

Security and control

Agents do the work. Your firm stays in control.

What reaches a client is decided by your people and your rules, and you choose where your documents live.

Your data stays where you decide

CoPage Cloud stores documents in Frankfurt, in the EU. A private deployment runs on your own servers or cloud account. We never use your documents to train AI models.

People sign off. Agents don’t ship.

One agent edits a document at a time, and anyone on it can stop the agent. Every change is attributed, to a person or an agent acting for one, and any version can be restored.

Your rules, before the client sees it

Your brand guidelines become a theme. Check packs catch what your reviewers look for: leftover placeholders, personal data, mixed currencies, off-brand colors.

Integrations

Works with the tools your teams already use.

CoPage has no AI of its own for the work: your people’s agents build, under your company’s agreements with those providers.

  • Claude and ChatGPT

    People connect the assistant they already use, with no install.

  • Claude Code, Codex, Cursor, Copilot

    Coding agents work through the CLI or MCP, next to the code.

  • Azure, AWS, Google Cloud

    The official icon sets, so architectures look the way clients expect.

  • PowerPoint and PDF

    Native shapes, tables and charts that stay editable after export.

  • draw.io

    Bring existing diagrams in, take them back out.

  • Your meeting transcripts

    Teams, Zoom and Google Meet already write them; that’s where a proposal starts.

How we work with you

Start with one team. Grow from there.

You work with the people who build CoPage, from the first call to the rollout.

  1. 01

    Talk

    A 30-minute call about your team, the proposals you make and where your documents must stay.

  2. 02

    Pilot

    One team for 6–8 weeks: your brand as a theme, your review rules as checks, onboarding, and success criteria agreed up front.

  3. 03

    Roll out

    CoPage Cloud or a private deployment, onboarding for the wider team, and a direct line to the people who build CoPage.

Questions

Where is our data stored?

In CoPage Cloud, in Frankfurt, in the EU: documents in the app’s database and file storage. In a private deployment, wherever you run it. With the free CLI, diagrams stay in your repository on your computers.

Can we run CoPage on our own infrastructure?

Yes. A private deployment runs on your servers or in your cloud account, with your database and file storage, and nothing reaches our servers. We’re setting up the first ones with pilot teams.

Which AI models does CoPage use?

For the work itself, the ones your people already use: Claude, ChatGPT, Claude Code, Codex, Cursor or Copilot, under your agreements with those providers. AI checks in CoPage Cloud ask a model through OpenRouter; in a private deployment they use your provider, or stay off. Built-in checks need no AI.

Do you support single sign-on?

Not yet. Today people sign in with their email address. Single sign-on with Microsoft Entra ID, Okta or Google is on the way, and pilot teams decide which comes first.

Do you use our documents to train AI?

No. We never use your documents to train AI models, and we don’t sell or share them.

How is CoPage priced?

Per team, after a call: it depends on how many people use it and where it runs. The CoPage CLI for developers stays free.

Bring your next proposal to the pilot.

Tell us about your team and where your documents must stay. We reply within two working days.