/ 00FAQ

Questions people ask before they sign.

Pricing, how the work actually runs, security and governance, and what you keep if the engagement ends. If something isn't answered here, ask it on a Colony Call.

Engagement & pricing

How ANTS is bought, scoped and committed to.

Does ANTS only work on sales and marketing?

No — that's where we started, and it's still where most colonies begin, but the model isn't sales-specific. If a piece of work has a clear trigger, a clear owner, and a real cost when it's missed, a colony worker can watch it — in finance, in operations, or anywhere else in the business.

How do you decide which department to start in?

The Blueprint. We look at where work is actually falling through — not where it's theoretically possible to add AI — and prioritize by what it's costing you: revenue, time, or risk. Most colonies start in one function and expand once the first workers prove out.

What exactly am I buying?

An operating layer for your agent colony. ANTS builds agents into the CRM and stack you already run, then stays under the hood tuning, monitoring and governing them every week. You are not buying software you log into, and you are not buying a project that ends at launch.

Why does every engagement start with a Blueprint?

Because building before you've assessed is how teams end up with agents nobody needed. The Blueprint is a $9,500 one-time assessment of the tools, workflows and people you already have, plus a prioritized roadmap of which agents to build first and why.

It's yours to keep regardless of what you do next, and 50% is credited toward year one if you sign a retainer. Full detail on the pricing page.

Why a 12-month term?

The first month is deployment. The value compounds from month three onward, as agents get tuned against live performance data. A month-to-month arrangement would push both of us toward quick wins over the work that actually moves revenue.

What is not covered by the retainer?

Third-party costs you already own or would need to add: CRM seats, enrichment data, sending infrastructure, and model API usage where an agent runs against your own account. Those get identified and estimated during the Blueprint so nothing arrives as a surprise.

How quickly do agents go live?

Depends on the tier. Outpost targets 3–4 workers live in the first 30 days, Colony 8–10 in the first 60, Supercolony 15+ in the first 90. Those are targets set during the Blueprint against your actual stack, not hard caps.

How the work runs

What actually happens week to week once you're live.

What does “managed” mean in practice?

Four things run continuously. We tune agents weekly against live performance data, not on a quarterly check-in. We monitor uptime and own incident response, so noticing a break isn't your team's job. We maintain a live agent inventory with access control and an audit trail. And we report monthly on what ran, what broke, what got fixed and what's next.

Who do we actually talk to?

A direct Slack channel with the people running your agents. Not a ticket queue, not a support portal, not an account manager who relays messages to a build team.

What happens when a CRM field changes or a vendor updates an API?

That's the failure mode that kills most in-house agents, and it's the specific thing a retainer covers. Monitoring catches the break, incident response fixes it, and the weekly tuning cycle absorbs the change properly rather than patching around it.

Will agents replace headcount on my team?

No, and ANTS isn't scoped that way. Agents extend the reps and marketers you already have by removing the prep, the follow-up lag and the signal-watching nobody has time for. The headcount plan is yours.

Do we have to change tools?

Almost never. ANTS starts by improving the return on the tools, technology and people you already have. If something genuinely can't support what you're trying to do, we'll say so in the Blueprint rather than working around it silently.

Security & governance

Access, auditability, and what happens when something goes wrong.

What access does ANTS need?

Scoped access, not standing administrative access. Each agent gets the permissions it needs to do its job and nothing beyond that. What's granted is agreed explicitly during the Blueprint, logged, and revoked at the end of an engagement.

Where does our data live?

In your systems. ANTS' agents operate inside your existing CRM, outbound tools, calendar and Slack. We do not copy your customer or pipeline data into a separate ANTS-owned database or platform. See the privacy policy for the fuller position.

Do you train models on our data?

No. Client data is not used to train any AI model that leaves your business.

How do you handle agent sprawl and shadow AI?

The Blueprint inventories what's already running before anything new gets built, including agents someone spun up in Claude, Cursor or an automation tool without review. From there every agent is owned, scoped and reviewable: a live inventory, access control, an audit trail of what each agent touched, and a kill switch.

The governance depth scales with tier. Outpost gives you an inventory; Colony adds full access control and audit trail; Supercolony adds advanced governance, security and compliance.

Is there an audit trail?

Yes. Every action an agent takes is logged, so if something goes wrong you can say exactly what the agent did and what it had access to. That's the difference between an incident and a mystery.

What if an agent does something wrong?

Incident response is part of the retainer. We own detection and the fix. The audit trail tells us what happened, the kill switch stops it, and the weekly tuning cycle addresses the underlying cause rather than the symptom.

Documentation & ownership

What you keep if the engagement ends.

Who owns the agents you build?

You own your data, your workflows and your business outcomes. ANTS retains its underlying methodology, tooling and general know-how. The Terms set this out formally.

What happens to our agents if we stop working with ANTS?

You get documentation for every agent built during the engagement, so your team or another provider can continue operating or rebuilding them. We don't hold your business hostage to the retainer, and access we hold is revoked at the end of the engagement.

Do we get the Blueprint if we don't sign a retainer?

Yes. It's a paid deliverable and it's yours to keep, including the prioritized roadmap. Some teams take it and build in-house. We'd rather that than sell a retainer to someone who doesn't need one.

Fit

Who this works for, and who it doesn't.

Who is ANTS a good fit for?

Teams doing roughly $10M–$100M in revenue, with real systems already in place across the functions you want covered — a CRM, an accounting platform, a PSA, a ticketing queue. Usually they've tried building agents in-house or with a point vendor and watched them stall. They want agents operated like infrastructure, not launched like a project and forgotten.

Who is it not a fit for?

Pre-revenue or pre-product-market-fit companies without repeatable processes yet to protect. Anyone looking for a one-time build with no ongoing management. And anyone who wants a chatbot on their website, which is not what ANTS does.

We already have agents running. Doesn't that mean we're covered?

Usually not. Building an agent and operating one are different problems, and the second is where things break. We wrote up the difference in detail on the build vs. managed page.

What happens on a Colony Call?

Twenty minutes, no pitch. We look at what's already running in your stack, flag where agent sprawl or shadow AI risk already exists, and tell you honestly which tier fits, if any. If ANTS isn't right for where you are, we'll say so. Book one here.

Ready to put a colony on the work slipping through the cracks?

20 minutes. We look at what you've already built or tried, and tell you honestly whether ANTS is a fit.

Book a Colony Call