Note /
What an add-on is
Installs come with a menu: fourteen published items across four price lines, eleven of them with a number on. What an add-on actually is says a lot about how the whole service is built.
A module with a price on it
An add-on is a one-off module. Most carry a fixed price: $400 for a standard connector, $700 for a complex build, $2,000 for a standalone security audit. The price is fixed per item rather than negotiated per client, so you can total most builds from the menu before you speak to anyone. It is bought once, not rented: the monthly retainer maintains what is installed, and add-ons are how the installation grows. A Solo Install already includes one integration from the menu.
What is on the menu
Eight items are standard connectors at $400, and they are mostly wiring into tools you already run: an additional chat surface (Teams, WhatsApp, Telegram, Email or Signal), a CRM (HubSpot or Pipedrive), accounting (Xero or QuickBooks), Google Workspace or Microsoft 365, a helpdesk (Zendesk or Freshdesk), extra agent workspaces, additional training sessions, and backup and recovery setup. The systems named on those lines are examples of their class, so a system that is not named is normally on the same line, confirmed with your enquiry response.
Two items are complex builds at $700, where the work is engineering rather than connection: a scheduled automations pack for crons, reports and watches, and an agent activity audit trail. A standalone security audit of an existing agent deployment is its own line at $2,000, because a scoped assessment is several days of work rather than a module bolted onto an install.
Three items on the menu carry no fixed price at all: a custom internal API wired in through a bespoke MCP server, a framework migration, and a voice agent front end. All three are things we sell. None can be priced in advance, because the work is set by the system on the other side rather than by us, so each is quoted on application once scoped and anchored on $850 a day. The full menu is numbered, with its price, on the services page.
Built at the extension points
Most of the menu is built as skills, plugins and MCP servers at the framework’s own extension points, which is part of why those items can carry a fixed price: the work is bounded by an interface the framework already offers. Some requirements cannot be met at an extension point and reach the framework core instead. That is bespoke work rather than a menu line, and what you hold when it happens is its own note.
An add-on is not a support ticket
New features and new integrations sit outside SLA scope by design: they are sold from the menu, or quoted as bespoke work, rather than raised as tickets against the retainer. One line is worth reading twice: backup and recovery setup is on the menu, and the published exclusions say plainly that data loss where that add-on was declined is not covered. The add-on exists for exactly this reason. Declining it is a choice you are allowed to make, but it is made in the open, not discovered in small print.
Where the menu ends
Anything beyond the menu is fully bespoke: priced on application, anchored on $850 per day. The boundary is deliberate. Every standard price on this site is public, and work that cannot carry a published price is scoped first instead of guessed at.