The in-app copilot
The copilot is a chat surface inside the app that answers questions and drafts things for you to approve. It answers how Business-Gym works, it answers questions about your own workspace, and it can stage a draft — a workflow, a head configuration, a knowledge-base item. It proposes; you approve.
There is no code path by which it applies, publishes, sends or runs anything on its own. That is not a setting you can turn off — the capability simply does not exist in the product.
Where do you find it?
Section titled “Where do you find it?”A round sparkle button is fixed to the bottom-right corner of every screen in the app and opens the copilot page. It is the one persistent entry point, and it is hidden only on the concierge page, where the concierge chat widget already occupies that corner.
A head’s settings page also carries an “Ask the Copilot to build this” link. It opens the copilot with a relevant message already typed into the input — you still read it and press send.
What can it actually do for you?
Section titled “What can it actually do for you?”It can answer a question and it can stage a draft, and that is the whole of it. An answer comes back with the sources it used listed underneath, drawn from two separate pools — how the product works, and a snapshot of your own workspace. Your workspace data stays yours; it is never mixed with another tenant’s.
The drafts it can stage are a fixed list, and every one of them is a draft only:
- a new workflow, saved unpublished
- a head configuration change
- a revision of a head’s system prompt
- a knowledge-base item
- a feature proposal added to the founder review list
Asking questions and filing a feature proposal are open to any member. The four drafting capabilities require the admin role. There is deliberately no “execute” capability of any kind in that list.
The copilot answers in your interface language — German, English or French — and defaults to German.
What will it never do?
Section titled “What will it never do?”There is a hard never-list that is refused for every role including the owner, and refused even when you ask for it explicitly. It covers moving money, executing a trade, initiating a transfer, sending anything externally, distributing payslips, publishing a workflow, running a workflow, deleting tenant data, changing sharing permissions, reading secrets, changing billing, and reaching another tenant’s data.
Every request passes through the same three checks in order: the never-list, then default-deny for anything unrecognised, then your role. A capability the copilot has never heard of is denied rather than attempted.
This is the same floor described in autonomy and the hard floor: external send and money stay human-approved permanently.
What happens when you approve a draft?
Section titled “What happens when you approve a draft?”A staged draft appears on a review card showing what it does, how many steps it has, and an estimated cost per run, with Approve, Edit and Discard. Nothing is created until you press one of them.
Approving a workflow draft saves it and opens it in the visual editor. Edit takes you to the same editor. Discard drops the draft. Approving does not publish the workflow and does not run it — both of those are on the never-list for the copilot and are steps you take yourself.
What does it do when it cannot help?
Section titled “What does it do when it cannot help?”It tells you plainly. An ask it cannot satisfy returns an honest “I can’t do that yet” rather than an invented answer, and the gap is logged so the missing capability can be reviewed later. A refusal on the never-list or on your role comes back as a refusal, not as a silent non-answer.
If part of its product knowledge is unavailable at that moment, the answer carries a visible note saying it may be incomplete. If the service itself is unreachable, you get a “temporarily unavailable” message and nothing is staged.
Where do its feature proposals come from?
Section titled “Where do its feature proposals come from?”From real signals, never from a blank page. Admins get a proposals review page and a backlog page, both under the copilot. Each proposal shows the evidence and the signal sources it cites, and a proposal citing no signal never reaches the list.
One live source is Microsoft Clarity friction data — rage-clicks, dead-clicks, quick-backs and script errors on your marketing site, read-only. If Clarity is not connected, or has no data, it contributes zero observations rather than a fabricated one. See integrations for what each connector reads.
You mark each proposal approve, defer or reject. Approving materialises it into the backlog. Nothing is built from that page.
What is the copilot not?
Section titled “What is the copilot not?”It is not the inbound → approve → execute loop. That loop handles work arriving from outside — email and other channels — and routes it to a head. The copilot is a helper for you, inside the app, for questions and for building things.
It is also not a head. Heads own a function and work a queue; the copilot holds a conversation and stages drafts.