Questions people ask before they sign.

An operating layer for your GTM agents. OTTO 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.

Because building before you've assessed is how teams end up with agents nobody needed. The Blueprint is a $6,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.

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.

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.

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

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.

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.

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.

No, and OTTO 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.

Almost never. OTTO 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.

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.

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

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

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. Foundation gives you an inventory; Growth adds full access control and audit trail; Scale adds advanced governance, security and compliance.

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.

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.

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

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 GTM motion hostage to the retainer, and access we hold is revoked at the end of the engagement.

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.

Teams doing roughly $10M–$100M in revenue, with a real CRM and GTM stack already in place. 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.

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

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.

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 OTTO isn't right for where you are, we'll say so. Book one here.