An AI harness gives your teams one AI workspace they can use safely
An AI workspace for your teams, connected to your systems through permissioned tools, with access set by role, a record of every action and training for staff.
Many staff already use AI tools on personal accounts the organisation cannot see. They paste company documents into them and write their own instructions. Nobody knows what was shared, what it cost or whether the answers were checked. Staff keep using the tools because they save time, so a ban alone does not stop it.
Staff use AI inside the permissions they already have
We set up the AI workspace your staff use, and the controls around it. Connectors (MCP) link it to your systems. Skills are saved, tested steps for tasks your teams repeat, such as drafting a reply or reading a contract. Access follows each person’s role. Every action is recorded, and a person sends anything that leaves.
Systems it touches
- Your ERP
- SharePoint and document stores
- Outlook and Teams
- CRM platforms
Example
A renewal reply drafted inside one person’s permissions
A made-up case that shows the mechanism. It describes no client.
- A sales coordinator asks the workspace to draft a reply to a customer who wants to renew early.
- The harness checks the coordinator’s role. It allows the CRM and the contracts folder, and blocks HR files.
- The connectors read the customer’s contract in SharePoint and the account record in the CRM.
- The workspace drafts the reply and quotes the renewal clause, with links to both sources.
- The coordinator corrects one line and sends the reply from Outlook.
- The audit log records the request, the two sources read and the draft.
It works in the systems you already have
The harness works with more than one AI product. ChatGPT Enterprise and Claude are common choices. For sensitive data, the workspace can run on an open model instead. The connectors use MCP, an open standard, so they keep working if you change product later. We recommend a product after testing the options on your own tasks.
Where your data staysPermissions limit what it can touch
Where a person approves
- Before anything the AI drafts is sent or posted
- Each role reaches only the systems and data it is already allowed to see
- Your system owners approve each new connector and skill before staff get it
- The harness uses each person’s own permissions. Staff see only what they could already open.
- Connectors start read-only. A connector that can change data is added only when you approve it.
- The audit log records every request, every system the AI read and every draft. It stays in your accounts.
- Usage and cost reports show which teams use it and for what. You can set limits for each team.
Everything we build is handed to your team
Who owns the code, and how handover works- The AI workspace, connected to your systemsSet up under your accounts. Your IT team holds the admin rights.
- Shared instructions and skills for the tasks your teams repeatWritten down and versioned in your repository.
- Access rules, an audit log, usage reports and trainingRole rules and logs in your own systems, and training notes your staff keep.
How we would start
Discovery, then one team first
We choose one team and the tasks they repeat most. We set up the workspace, connectors and skills for them, and train them. Then we review the audit log and the usage with you before more teams join.
How we work togetherQuestions
How is this different from just buying ChatGPT or Claude licences?
Licences give staff a chat tool. On its own, that tool does not know your systems, and each person writes their own instructions. The harness adds the connectors, the shared skills, the access rules, the audit log, the reports and the training. You may still buy the licences. The harness makes them safe to use on company work.
Can it use our data without the data leaving our control?
Yes, if you choose that setup. The connectors run inside your network, and the model can run on your servers or our private GPUs. Products from large providers process data in their own regions. Our security page shows where each option keeps data.
How does this relate to AI agents?
With the harness, your staff do the work with AI: a person asks and a person sends. An agent does a task from start to finish and waits for a person to approve the important steps. The harness is the lower-risk first step. Its connectors, access rules and audit log are the same base an agent needs later.
Name the team that would try the workspace first
Tell us the tasks they repeat. We will suggest the first connectors and skills to set up for them.
Start a project