Email, calendar and people
Microsoft 365
Read
People, calendar events and mail metadata.
Connect your systems
Three ways to bring a system in.
A few systems have a ready connector in the library or their own MCP server; for the rest, we build one on request. Whichever way a system comes in, it ends up in the same model of your business.
Connect your systems. This is where Fundarem solves “Connected systems”.
Three ways in
Library, your own MCP server, or a custom connector.
From the library
Your IT admin picks a ready connector and chooses which endpoints and fields to include.
Through its own MCP server
A system that runs an MCP server is connected as it is. You choose which of its tools to include, and we review the tool list with you first.
Custom connector
For a system with neither, we build the connector. You confirm the list of endpoints and columns.
All three end the same way: the system is mapped into the ontology, and your admin tags which columns hold personal or sensitive data before the first sync.
Library
Connectors that are ready today.
In the library, each one shows what it reads. After go-live, your admin adds more from the same library in your own installation, and new connectors reach it with software updates. Missing one? Request a connector and we send a quote.
CRM and sales
HubSpot
Read and write, set by your admin
Companies, contacts, deals, tickets, activities and the sales pipeline.
CRM and sales
Salesforce
Read and write, set by your admin
Accounts, contacts, opportunities, leads, cases and activities.
Accounting
Tripletex
Read and write, set by your admin
Accounts, customers, suppliers and vouchers.
Accounting
Xledger
Read and write, set by your admin
Customers, suppliers, employees, projects, accounts, ledger transactions and invoices.
Developer tools
Gitea
Read and write, set by your admin
Repositories, issues, pull requests, organisations, users and releases.
Bring your own MCP
Bring your own MCP server
A system your company already runs an MCP server for can be connected as it is.
- Your IT admin adds the server.
- A manager decides who may use it.
- Only then does it appear in your library.
Custom connectors
Spider
We have developed a tool, Spider, that creates custom connectors from the API documentation (97–99%); the rest is human in the loop.
A system with no ready connector in the library gets a custom connector. We build it for your system and run it with you; you confirm the result before it is switched on. A new system is connected in days, not in a project.
Pricing and payback
What a new connector costs.
A system that is not in the library is priced by how much work it takes to connect.
Not in the library? We build it.
Each size has a one-time build fee and a monthly connector fee, both priced on request.
Medium
The system has a documented REST API.
Large
The system's API is undocumented or complex.
Payback
The client who commissions a connector earns 20% of what later clients pay for it, as credit on their own bill, for 3 years or until it reaches 2x their build fee.
Who decides
Pick from the library. Your manager decides who uses what.
IT admin
Picks connectors from the library and connects them to your company's systems.
Manager
Decides which connectors are switched on, and who may use each one.
Everyone else
Works with what the manager has switched on, through agents and dashboards.
Next in the story
Every ready connector, with what it reads.
See what each one reads, and what happens when your system is not in the library.