Let AI assemble the board pack from live systems — approved before directors see it.

Business situation

ABC Limited’s board meets monthly. Before each meeting, the finance team collects the management accounts from Xero, the pipeline from Salesforce, headcount and operating measures, and the actions from the last meeting, and writes a pack. Two non-executive directors read the pack in advance and increasingly ask their own AI to help them prepare questions.

Why existing tools alone are insufficient

Assembling the pack by hand is slow and error-prone. An AI connected to everything could assemble it, but would also be able to share drafts, and non-executives’ own AI tools would receive the pack as an attachment with no boundary on where it goes next. The board needs the approved pack, not the ledger behind it.

Systems involved

• Xero — management accounts.
• Salesforce — the pipeline summary.
• KroyDB — headcount and operating measures.
• SharePoint — previous minutes and the action log.
• Board Channel — where approved packs are shared with directors.

Kroy architecture

Claude connects to Kroy. Xero, Salesforce and Microsoft 365 are connected to Kroy by the finance team. The Prepare Board Pack Skill may read reports and create a draft pack. A board Channel carries a projection of approved packs and minutes only. Non-executive directors are guests in the Channel and can connect their own AI.

Workflow

1. The financial controller asks Claude: “Prepare the board pack for this month.”
2. Kroy returns management accounts via xero.reports.read, the pipeline via salesforce.report.read, operating measures from KroyDB and last month’s actions from SharePoint.
3. Claude drafts the pack — financial summary, pipeline, people, and progress on actions — and saves it with artifact.create.
4. The controller asks: “Send the draft to the board so they have it early.” Kroy refuses: the pack has not been approved.
5. Claude requests approval.request. The finance director revises the commentary and approves the pack. Kroy adds it to the board Channel.
6. A non-executive director asks their own ChatGPT: “What were the main reasons for the margin movement?” Kroy returns the approved pack, and ChatGPT answers from it.
7. The director’s ChatGPT asks for the underlying Xero transactions. Kroy refuses: the board Channel’s projection contains approved packs, not ledger detail.

Agent permissions

Claude acts under the controller’s delegation and can read and draft. Directors’ AI acts under each director’s delegation, bounded by the board Channel.

Human permissions

The finance director approves each pack. Directors read the board Channel. The company secretary manages who is a guest.

State changes

• A draft pack Artifact is created, then approved.
• The approved pack is added to the board Channel.
• Board actions from the pack are linked to the meeting.

Audit outcome

Kroy records each source read, the draft, the refused early share, the approval, each director’s access and the refused ledger request.

External sharing

Non-executive directors are guests in the board Channel. Their access can be ended at any time, for example when a term ends.

Security considerations

• Drafts never reach directors; approval is enforced by Kroy.
• Directors’ AI is bounded by the projection, not by the AI provider.
• Credentials for Xero, Salesforce and Microsoft 365 stay in Kroy.

Setup requirements

• Xero, Salesforce and Microsoft 365 connected to Kroy.
• Claude connected to Kroy.
• A board Channel with a projection of approved packs and minutes.
• Non-executive directors invited as guests.