Note /
What an add-on is
Installs come with a menu: thirteen published items in two fixed price tiers. 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 in one of two tiers: $400 for a standard connector, $700 for a complex build. The tier is fixed per item rather than negotiated per client, so you can total your own build 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, Pipedrive or similar), 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.
Five items are complex builds at $700, where the work is engineering rather than connection: a custom internal API wired in through a bespoke MCP server, a scheduled automations pack for crons, reports and watches, a voice agent front end (OptaAgent), a standalone security audit of an existing agent deployment, and framework migration. The full menu is numbered, with its tier, on the services page.
Built without touching the core
Every customisation, add-ons included, is built as skills, plugins and MCP servers on top of the vanilla framework core. No forks, no core patches. That is what keeps your deployment on the stable, staging-tested update path instead of stranded on an unmaintainable branch.
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.