Connected systems
Ask the systems you already run. Each one answers in plain English.
Your planning model, your CRM, your documents, your task tracker and your own written handbook. Connect one, and your people can ask it questions from Claude or Copilot and get the figures, the records or the right page back in seconds.
Every system you connect is a set of questions your people can finally ask.
What each system answers
Connect a system. Ask it anything you would ask a colleague.
These connect today. Each answer is read live from the system at the moment of asking, so it is as current as the system itself.
Planning model
Acterys, read over SQL. Plans, forecasts, actuals and the variances between them.
- Show me the five-year plan for this entity, by period.
- Which cost centres moved more than 3% this period?
- Anything unusual in this month's postings?
CRM
HubSpot. Deals, contacts, companies and the activity on them.
- Which of my deals have gone quiet for a month?
- What did we last discuss with this account, and when?
- Who are the contacts on this deal?
Documents
SharePoint. Contracts, statements of work and decks, down to the page.
- Find the statement of work for this project.
- What does the contract say about payment terms?
- Read me pages 14 and 15 of this agreement.
Tasks
ClickUp. Projects, lists, owners and due dates.
- Which tasks on this project are overdue, and who owns them?
- What is still open before we can hand this over?
Your handbook
Your own written process, approved by your people. No outside system needed.
- What is our process for a pre-release check?
- Which pre-release checks did we run, and when?
Several at once
One conversation can read more than one system, so the answer can join them up.
- Does this statement of work match the deal in the CRM?
- Which overdue tasks belong to our largest open deals?
Down to the page
Ask about a 32-page contract. Get the clause, with its page number.
The assistant finds the document, opens the pages that matter and answers from them. Nobody downloads a file or scrolls for the clause, and the answer says exactly where it came from.
Beyond these
The same questions, over the systems you run.
A tool asks for a category, not a product. It calls crm_read, never hubspot_read. So every system below is already described in the same vocabulary, and connecting one means building its adapter, not changing how your people ask or which tools answer them.
| Category | What it holds | Systems in the catalogue |
|---|---|---|
| Planning | The model your numbers live in. | Acterys |
| Customers and pipeline | Deals, contacts and what was said. | HubSpot, Salesforce, Microsoft Dynamics 365 Sales, Pipedrive, Zoho CRM |
| Delivery and tickets | What is being built and where it stands. | ClickUp, Jira, Azure DevOps, Asana, monday.com, Linear |
| Documents | Contracts, statements of work, decks and templates. | SharePoint, Confluence, Google Drive, Box, Dropbox, Notion |
| Finance | Budget, burn and margin. | Xero, QuickBooks Online, Microsoft Dynamics 365 Business Central, NetSuite, SAP S/4HANA, Sage Intacct |
| Support desk | Customer issues and their history. | Zendesk, ServiceNow |
Acterys, HubSpot, SharePoint and ClickUp connect today. The others are modelled in the same vocabulary, and we build the adapter for one when a client needs it. If yours is not listed, ask: most business systems land in one of these categories.
Whose rules apply
Your SharePoint sharing still applies.
Documents are opened as the person asking, so a SharePoint file they cannot open is a file their assistant cannot read either. Where a system is read through one connection your company sets up, the people and tools you choose here decide what is reached.