Demo company
Acme Inc
Engineering consultancy · 64 people · Oslo · admin Kari
Designed to run in: Acme's own Azure subscription, EU regionAI: open-weight models, demo: models outside the EU allowed · production is EU-onlyPersonal data masked before every model call
5systems connected
8kinds of object
11links in use
3waiting for a yes
6personal-data fields masked
13fields hidden from agents
How Acme's stack is laid out
Inside · designed to run in Acme's own Azure subscription · EU region
Your peopleToday, dashboards and the Ask bar — signed in with the work login they already have
AgentsPropose actions; a person approves before anything is written
Model of your business8 kinds of object · 13 links between them
Connectors5 systems plugged in
Database, files, keysResources in your subscription, on your bill
Outside
Your systems, unchanged
CRMHRTime trackingERP & invoicingEmail
Nothing migrates. The hub reads and acts through each system's own API.AI models · demo: models outside the EU allowed · production is EU-onlyOpen-weight models deployed through Azure AI Foundry. They receive requests with names, emails and ids replaced by pseudonyms, and keep no memory between calls.
Waiting for a yes
The system proposes; a person at Acme approves. Nothing below happens until someone says so.
Link found — confirm itEmail → Email: thread starter?Found by the engine, not yet in use. Confirming it lets agents follow it.
New pattern foundThe hours ↔ pipeline card?CRM and time tracking share the client list. I can show hours spent against opportunity value per client — every Monday.
Connector ready for approvalIndustrySys (project management) — 14/14 calls OK in sandboxI found projects, milestones and progress in the API. Approve, and the tiles are minted automatically — Today gains two new cards.
The model of Acme's business
The things Acme's business is made of, and how the same customer shows up in different systems. Built by the engine from each connected system; nobody at Acme wrote it. Each card says what an AI agent is allowed to see.
CRMContact7 fields · 3 masked3 fields hidden from agents
CRMCustomer7 fields1 field hidden from agents
HREmployee9 fields · 2 masked3 fields hidden from agents
Time trackingTime entry8 fields1 field hidden from agents
ERP & invoicingInvoice9 fields1 field hidden from agents
EmailEmail6 fields · 1 masked1 field hidden from agents
Shared reference dataCurrency2 fieldsAgents see every field
Shared reference dataInternal note3 fieldsAgents can't see this at all
Links between themhow each was found · whether it is in use
Customer → EmployeeownerDeclared keyIn use
Contact → CustomercustomerDeclared keyIn use
Employee → EmployeemanagerDeclared keyIn use
Employee → EmployeementorDeclared keyIn use
Time entry → EmployeeemployeeDeclared keyIn use
Time entry → CustomercustomerDeclared keyIn use
Invoice → CustomercustomerDeclared keyIn use
Email → CustomercustomerDeclared keyIn use
Internal note → CustomercustomerDeclared keyIn use
Invoice → CustomerCustomer (by CRM id)Matched valueIn use
Invoice → CurrencyCurrencyMatched valueIn use
Time entry → Customercustomer codes on time entries are free text typed by people; joining them duplicates hoursRefusedNot joined
Email → Emailthread starterDeclared keyNeeds a look
“Not joined” means the engine refused a link that would give wrong numbers — it says why instead of guessing.
Why did this happen? — the audit log
An agent asked to log hours for an employee ({"hours":3.5}). Its mode is “always review”, so it waited for a person; Kari approved it, and only then was it written.
Agent proposed
agent:follow-up-assistantsuccess · {"action":"log_time","input":{"hours":3.5},"surface":"background"}
Approved
kari@acme.example (approver)success · {"proposal":0}
Every step is recorded with who did it and a fingerprint of the exact result, so it can be checked later.