Note /
Is your system on the list
An agent is only as useful as the systems it can reach, so the menu names those systems rather than promising to fit your stack. The whole list sits on the services page. This is about the parts of it a list cannot tell you.
Named is not the same as exhaustive
The connection lines name systems: chat surfaces are Teams, WhatsApp, Telegram, Email or Signal, a CRM means HubSpot or Pipedrive, accounting means Xero or QuickBooks, then Google Workspace or Microsoft 365, and a helpdesk means Zendesk or Freshdesk. Those names are examples of their class rather than the whole of it. If your system is named, it is a standard connector at $400 one-off and you can total it yourself from the menu. If it is not named but does the same job as the ones that are, it is normally the same $400, and the price comes back with your enquiry response rather than being left for you to guess at.
Your first connection may already be paid for
A Solo Install at $3,000 includes one integration from the menu, so a single operator wiring in one system is not buying an add-on at all. A Team Install at $6,000 includes a Slack or Teams surface as part of the deployment. The $400 line starts applying to what comes after that first one, which is worth knowing before you total a build from the menu.
If it is your own software
Internal software with an API is a named item on the menu rather than a special case: a custom internal API reached through a bespoke MCP server. It is one of the three menu items that carries no fixed price, priced on application once scoped and anchored on $850 a day. That is deliberate. An API we have never seen sets its own timescale, and a fixed number pinned to it would be a guess dressed up as a price.
If it is nothing like anything on the list
The connection lines cover five classes of system: a chat surface, a CRM, accounting, an office suite, a helpdesk. A product that belongs to none of them, and is not your own internal software, sits beyond the menu entirely, and we would rather say so than stretch a list to cover it. It is priced the same way as the item above, on application once scoped and anchored on $850 a day.
So the practical difference between your own software and an unnamed third-party product is smaller than it looks: both end in a scoping conversation. Which makes this a question worth asking early rather than late. If the system you most need reached is the one nothing above describes, that is a conversation to have before an install rather than a discovery to make after one.
Whatever it connects to, it is built the same way
Every connection is built as skills, plugins and MCP servers at the framework’s own extension points, which is covered properly in the note on what an add-on is. Two consequences are worth stating here. A connection we build does not turn your deployment into a variant only we can maintain. And it runs on infrastructure you own, using credentials that never leave your environment, which is as true of the tenth connection as the first.