Do we need to replace our CRM and ERP?
We start with your existing applications, assess their interfaces and connect the required data and functions. Available connections depend on the programs and access they provide.
Tools & knowledge
Your CRM, ERP and files stay as they are. We connect them, make the knowledge in them findable and give AI agents their own, limited tools.
Discuss a connectionNothing gets replaced. We connect what is there.
Example 1: knowledge base
Contracts in the CRM, orders in the ERP, guides in files: we link them into one knowledge base that agents answer from, with sources. Permissions are checked first. Example: pre-filling tenders from approved answers.
Central knowledge base
Link · prepare · authorise
Illustrative architecture · scope depends on your applications
Invoices and orders arrive by email, as PDFs or spreadsheets. We extract them, check required fields and duplicates and pass them to the ERP after approval. Unclear cases go for review.
Email, PDF or sheet
Date: 5/4 / 2026-04-05
Contact: duplicate entry
Required fields & duplicates
Formats & field mapping
ERP after approval
One date format
Mapping checked
Unclear documents go for review.
Example 3: custom MCP
MCP is an open standard through which AI agents call tools. A custom MCP server defines what an agent may see and do in your ERP, CRM or ticket system. For example: read an order status, fetch customer context, save a draft. We check existing connectors first.
Read order status
Save a draft
Check access → Run function → Return result
User permissions, shared service accounts and write actions are handled separately. The interface checks permissions, not the agent. Anyone who cannot see margins in the ERP cannot see them through the agent either.
Sometimes a small interface is missing: to review drafts, fix an import or see cost and usage. We build that addition around your workflow, without introducing a new large system.
Review view · Import fixes · Cost and performance dashboard
The agreed integration or application, tested example cases and documentation for use and operation. Access, accounts and subscriptions are in your name, so you can carry on without us if you choose.
Switzerland, the EU or your own environment: we plan hosting, data paths, costs and support with your IT team.
We start with your existing applications, assess their interfaces and connect the required data and functions. Available connections depend on the programs and access they provide.
The knowledge base follows the agreed employee permissions. Answers should refer to approved sources; agents receive scoped tools rather than unrestricted access to systems.
Show us the applications involved and the step between them. Together, we will establish what is already available and what needs adding.
Let’s talk about your project