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.
One word changes the answer
The CRM line names HubSpot and Pipedrive and then says similar. No other connection line does. Chat surfaces are Teams, WhatsApp, Telegram, Email or Signal. Accounting is Xero or QuickBooks. Then Google Workspace or Microsoft 365, and a helpdesk connection meaning Zendesk or Freshdesk. If your system is named there, it is a standard connector at $400 one-off and you can total it yourself from the menu. If it is a near neighbour of one of those lines rather than the thing named, that is worth asking about rather than assuming either way.
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 rather than a special case: a custom internal API via a bespoke MCP server, priced as a complex build at $700 one-off. It carries a published price rather than a scoping conversation, which is worth knowing if you assumed anything custom would have to be quoted.
If it is a product we have not named
Then it is not on the menu, and we would rather say so than stretch a list to cover it. Work beyond the menu is priced on application once it has been scoped, anchored on $850 a day. That is a worse answer than a fixed price and it is the true one. It also makes this a question worth asking early: if the system you most need reached is not named above, 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 on top of vanilla framework core, with no forks and no core patches, 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.