How it connects to your tools
The assistant doesn't ask you to move your work somewhere new. It reaches into the tools you already use, your sheets, your store, your marketing, your analytics, and gets things done there. And when the tool you need isn't in the catalog yet, we build the connection.
A look under the hood: the breadth of what it plugs into, how a new integration gets added, and why each client only ever gets the ones they've been granted.
The short version
There's a catalog of dozens of integrations, spanning the tools businesses actually run on: documents and spreadsheets, project management, e-commerce, SEO and advertising, analytics, outreach, creative and media. Your assistant works inside those tools directly, reading a sheet, checking a store, pulling analytics, on your behalf. It's given only the connections you've been provisioned for, and if the tool you need isn't in the catalog, we build a custom one. The assistant meets your stack where it already is, rather than asking you to change how you work.
That's the idea. The rest of this page is the range it covers, how a new connection gets added, and the rule that keeps each client's access to exactly what's theirs.
It reaches into the tools you already use, only the ones you've been granted (green), plus custom connectors we build when something isn't in the catalog.
What it plugs into
A catalog of 35 integrations and growing, grouped by the work you do. The point isn't the count; it's that the assistant can act inside the systems your business already lives in, rather than being a separate place you have to copy things into.
The range covers the common ground of real operations:
| Dial | What it controls | Examples |
|---|---|---|
| Docs and files | Working inside your spreadsheets, drives, and documents, where a lot of the actual work lives. | Sheets, Drive, OneDrive, Notion |
| Project and work | Reading and updating the boards and task systems your team runs on. | Asana, ClickUp, Monday |
| E-commerce | Reaching into your store and your email/SMS marketing, across multiple brands. | store platform, email/SMS platform |
| SEO, ads, analytics | Pulling the real performance data behind search, ads, and traffic. | Ahrefs, Search Console, GA4, Ads |
| Outreach and research | Finding contacts and searching the live web for grounding. | Contact lookup, web search |
| Creative and media | Generating images, media, and voice when a workflow needs them. | Image + media + voice |
And we build custom ones
The catalog is the starting point, not the ceiling. When a client needs to work with a tool or a capability that isn't a standard connector, we build a purpose-made one and slot it in alongside the rest. If the thing you need to reach exists, we can connect to it.
Beyond the off-the-shelf integrations, the platform runs a set of custom-built services made for specific needs: advanced spreadsheet work, a live agent that joins and summarises meetings, specialised research services, and bespoke pipelines for particular clients. They're built as small, independent pieces that plug into the same catalog everything else uses, so a custom capability is a first-class citizen, not a bolt-on. The practical upshot: the answer to 'can it work with X?' is usually 'yes, and if not yet, we'll build it.'
You get only what's yours
Breadth available is not breadth switched on. Each client's assistant is given only the integrations that client has been provisioned for, granted deliberately, one by one. The catalog shows the range; your assistant holds your subset.
This matters for trust. The credentials for a tool are handed to a client's environment only when that client is entitled to it, and withheld otherwise, so one client's assistant never has reach into another client's accounts or tools. A new integration is added through a controlled admin process, evaluated, installed into the catalog, credentials wired up securely, and then made available to the clients who should have it, without rebuilding the whole platform. So the catalog can keep growing while every client's actual access stays scoped precisely to what they've been given.