What the workspace is
Your company’s own folder on GitHub. It holds all your marketing files and the history of every change. You don’t need to know GitHub: Claude reads and saves the files for you.
Open the Claude app and write as you would to a colleague. Claude does the work in your company’s workspace, which holds your guidelines, brand templates, website text and reports. The automations use your current tools through their APIs.
Your company’s own folder on GitHub. It holds all your marketing files and the history of every change. You don’t need to know GitHub: Claude reads and saves the files for you.
The Claude app in your browser or on your computer. No command line needed. The same workspace also works with ChatGPT’s Codex and GitHub Copilot.
Tone of voice, products, prices, languages and rules such as “figures come from the report, not from memory”. You never have to repeat them.
Transparency
Every action leaves a trace in a ticket: what the automation did, in which system, when, and which messages went out. Every change in your CRM is recorded too. Tickets live in the workspace or in your company’s own ticketing system, such as Jira.
Made-up example. Tickets show the events and the messages sent. Recipients’ contact details stay in the CRM.
What we already do
Every weekly report, trend check and failed run of ours creates a ticket, and the notification arrives by email.
Security
When you ask Claude for last week’s leads, the automation server fetches them from your CRM with its own credentials. Claude gets the result, never the CRM password. You create the API keys, and they get only the permissions they need.
Names and phone numbers from the contact form go straight to your CRM. The workspace records only the count: 14 leads this week. Customer service messages stay in your helpdesk system.
If someone asks to change the price list, the change goes to a preview first. It is published only once it has been approved.
You can see who changed the home page text and when, and get the previous version back with a single request.
When someone leaves, you remove them from your company’s GitHub account and their access to the workspace ends.
Each customer has their own automation server. Another customer’s automations cannot see your data.
We sign a data processing agreement covering the personal data the automations handle.
Ownership
Each customer has their own workspace, their own automation server and their own website. Nothing is shared with other customers.
| Part | Where it lives | If you stop the service |
|---|---|---|
| Workspace | In your company’s own GitHub account. We are members. | Stays as it is, with its full history. We remove our access. |
| Systems and data | Your current tools, such as the CRM, email and helpdesk. | Stay as they are. The automation only used them through their APIs. |
| Tools | A copy of the reporting, checking and template tools lives in the workspace. | The copy stays with you, and you can keep using it. |
| Automations | Your company’s own automation server, maintained by us. | We hand the server over to you, or give you the automations to install on your own server. |
| Website | Our server or yours. | Runs on any server. |
| Analytics | Your company’s own Google Analytics and Search Console accounts. | Stay with you. We remove our access. |