Guides
Practice from completed
rollouts.
No theory. Concrete steps, measured timings and the architecture underneath, distilled from completed customer rollouts between the fourth quarter of 2025 and the second quarter of 2026.
Two guides
CRM and ERP integration
How SIMOSphere AI connects Salesforce, HubSpot, SAP, Dynamics 365 and Odoo to language models through the Model Context Protocol: architecture, authentication, time to value. With a table of measured setup times per system.
EU AI Act compliance
Deployer obligations, risk classification, the Article 4 training duty, the evidence trail, the deadlines. With a six-step path and the questions we hear most.
Which guide for which question
The two texts answer different questions and are written for different roles.
| The question behind it | Who it is written for | |
|---|---|---|
| CRM and ERP integration | How long does connecting a line-of-business system take, and what decides that? | IT leadership and data management, plus any department that has to put a date in a plan |
| EU AI Act compliance | Which duties fall on us as a deployer, and what does evidence look like that survives an audit? | Compliance, legal and the executive team, plus the bodies that have to approve a rollout |
How these texts come about
Two guides rather than twenty
A guide gets written here only once the same question has come back across several rollouts. That keeps the count low and the content usable: what is in it came out of a real customer system rather than off a whiteboard.
Timings are experience from completed rollouts, not a commitment. They apply to connecting a well-maintained system. Elaborate custom fields, bridges to legacy systems and unresolved permissions land well above them.
Both texts are written to be usable without a sales call. If you start on your own after reading, they have done their job.
- Every figure comes from a completed rollout, not from an estimate
- Every step appears in the order in which it actually comes up
- What was not measured is not in there
Questions about the guides
Are the guides legal advice?
No. They summarize what was learned in customer projects and name the sources so you can look them up. Classifying your own use case and assessing your contracts remain the job of your legal department or your outside counsel.
Where do the timings come from?
From completed customer rollouts between the fourth quarter of 2025 and the second quarter of 2026. What was measured is the time from first access to the first dependable answer out of the connected system. The range runs from one to two hours for Nextcloud to two to five days for SAP S/4HANA.
Do the figures hold for my system?
For the systems named, with reasonable confidence; for anything else, not without a check. What decides it is rarely the interface but the permissions: a system where nobody can say who is allowed to see what will stretch any connection.
Can I get a guide for my own case?
Write to us and tell us which question is still open. If it comes up more than once, it becomes the next guide. Until then we answer it in conversation, including when no engagement comes out of it.
Your case is not covered?
Then tell us which question is still open. We write the next guide along whatever people actually ask about.