I'm the CEO. I'll run this agency.
Run an AI Automation Agency with Agents
Connect Naive to Claude or ChatGPT
The buttons open a chat with this page’s prompt. If Naive isn’t connected yet, the assistant hands you the link first. Or connect it now:
https://api.vetta.sh/v1/mcpClaude
Opens Customize, then Connectors, with a custom connector named Naive and this URL filled in. Select Add, then Connect, sign in to Naive and select Approve.Open Claude settingsChatGPT
Open Plugins, select +, then Add custom MCP server. Name it Naive, paste this URL and choose OAuth. Sign in with your Naive account and select Approve. Business, Enterprise and Edu workspaces (admins and authorized developers) can use every tool. Pro accounts can connect read-only, so actions will not run. Plus and Free cannot add custom MCP servers yet.Open ChatGPT Plugins
A one-click Naive plugin for ChatGPT is coming.
Other agents
- Claude Code: run
claude mcp add --transport http naive https://api.vetta.sh/v1/mcp, then/mcpto sign in. - Codex: add
[mcp_servers.naive] url = "https://api.vetta.sh/v1/mcp"to config.toml, then runcodex mcp login naiveto sign in. - Cursor: add the URL to mcp.json, then sign in when Cursor asks.
- Clients that only take a header: use a token from Members in the studio.
Your team at work
One ask, approved by you, and the work comes back.
You approved the Northwind workflow
WorkflowNorthwind · new lead to first reply
- 1
Form sent
Their site's enquiry form writes a row to the CRM.
- 2
Sorted
The lead is tagged by service and size.
- 3
Reply drafted
A first reply, in their voice, waits in the queue.
- 4
Approved
A person at Northwind says yes before it sends.
Four steps, one approval. Your sales agent has the proposal draft for Northwind, waiting for your yes.
How it works
You ask. Your team does the work.
- 1
Get the company
Answer a few questions. Your CEO hires the team and sets up the apps.
- 2
Say what you need
Ask in a chat, as you would ask a person. The right agent picks it up.
- 3
Approve what goes out
Nothing sends or spends until you say yes. Each post waits for your yes until you choose Always allow.
The team
Your CEO and 8 agents. One chat.
site-builder
Keeps the public site true to the agency: rewrites hero, services, who-we-serve, process, pricing and FAQ from the project context. Proposes every change through update_site; nothing goes live without you.
sales
Works the pipeline end to end in the CRM: finds prospects that match the ideal client, adds them as leads with a why-now, drafts openers and follow-ups, moves stages, and turns a signed deal into a client. Picks up every reply the inbox seat logs; never sends without approval.
client-manager
Owns every signed client: runs onboarding, keeps each calendar honest, and flags a stall before the client notices. Drafts the check-in; you send it.
content-writer
Writes the agency's own blog: one post per slot, each against a named intent and keyword from the editorial calendar. Files drafts; you approve.
content-reviser
Keeps what is already published sharp: finds thin, stale or off-voice pages and posts and files a revision for each. Never rewrites what is performing.
gap-researcher
Compares the agency's site against named competitors: keywords they rank for that you do not, page types you lack, on-page elements missing. Files a gap report the writers work from.
proposal-writer
Turns a qualified lead into a proposal: scope, three package tiers from the pricing answer, timeline. Works when sales hands one over; logs it on the contact's CRM timeline.
inbox
Reads the company's inbox and logs each reply on its contact's CRM timeline for sales and the client manager. Sends the drafts a team's lead hands it, each one only once you approve it.
Questions
What exactly do I get when I deploy it?
A CRM with a workspace per client, a public site whose enquiry form writes straight into that CRM, and two agents. The sales agent works the pipeline each weekday. The client manager reviews every account once a week. The trade you sell is the one thing left out, because that is the part you bring.
Do I need to code or already run an agency?
No. You tell the CEO three things in plain words: what you sell and to whom, who your ideal client is, and how you price. The agents work from those answers, and you can change them later.
Can the agents send email on their own?
Never. They read the agency Gmail and draft replies and openers. Every send stops at Approvals with the message in front of you. Sending is a person's decision, every time, and the platform enforces it.
What does it cost to run?
Each agent has a daily cap and a cap per task, and the platform prices each task before it runs. A run that would go over the cap stops instead of spending. Between scheduled runs nothing is on, so the agency cannot surprise you on cost.