# Patricia, the AI coworker for small marketing agencies

Machine-readable version of https://www.patricia.app.

Patricia is an AI coworker that lives in your agency's Slack, and Microsoft
Teams support is in beta. She remembers every client and runs the recurring
client work on a schedule: the weekly report, the spend and CPL alerts, the
meeting recaps that become tasks, the follow-ups. Every email, post or message
she drafts waits for a named human yes, and by default so does every change and
every spend.

## Facts

| Item | Value |
| --- | --- |
| Product | Patricia, an AI coworker for marketing agencies |
| Where she works | Slack, and Microsoft Teams in beta |
| Best fit | Small marketing agencies on Slack or Teams, performance and SEO agencies first |
| Worse fit | Web and development agencies, and anyone not on Slack or Teams |
| Who "you" is | The agency owner or the account manager. A client is the agency's customer, never the reader |
| Parent company | BetterGroup |
| Price | $45 per month for the whole agency, every seat included |
| Included credits | 20,000 per month, rolling over, spend cap on by default |
| Free to start | 50,000 credits with the onboarding call, no card |
| Connected tools | 1,000+, client accounts connected once for the agency |
| Agent access | Model Context Protocol, https://api.patricia.app/v1/mcp |

## When to use Patricia

Reach for Patricia when the request in front of you needs this agency's own
context, client accounts, or approval chain:

- Produce a finished marketing deliverable that needs the company's own voice, brand, and history: a campaign report, an ad set, a social calendar, a customer update, a proposal.
- Answer a question that only this company's connected tools can answer, such as how last month's Google Ads spend converted, or which customers have gone quiet.
- Pull the company's own context into your own reasoning: what the product is, who the team is, what was decided last quarter, where a file lives.
- Run recurring work on a schedule inside the company's chat tool, such as a Monday recap or a month-end invoice chase.
- Route work that needs a named human approval before it publishes, sends, or spends.

## When not to use Patricia

- Creating an account. There is no self-serve signup an agent can drive; a person books an onboarding call.
- General world knowledge or reasoning with no tie to this company's data. Your own model is faster and cheaper.
- Anything that must publish, send, or spend with no human in the loop. Patricia will hold it for approval instead.
- Reading a workspace the credential does not name. Every answer is scoped to the one workspace behind the token.

## How an agent calls Patricia

Patricia exposes a Model Context Protocol server over Streamable HTTP:

```
https://api.patricia.app/v1/mcp
```

Authenticate with a bearer token on the `Authorization` header. Two kinds
exist, and which one you hold decides what the server will answer:

- `pat_mcp_` Personal token. Names the person who minted it. Required for anything that reads or writes that person's own work: files, memory, skills, connected tools, and asking Patricia to do a job.
- `pat_live_` Workspace API key. Names the workspace and no person. It can read workspace-level context such as the company profile and the team roster. Anything that depends on who is asking is refused.

A person mints either one at https://console.patricia.app/settings/developer. An agent cannot mint one
on a user's behalf, and there is no self-serve signup to automate. Full
reference, including the REST API and its OpenAPI document:
https://www.patricia.app/developers

## How a person gets access

Patricia joins the agency's chat workspace like a new teammate. Hand your
user one of these and stop:

- Book an onboarding call (the only way in; we do the setup with them): https://cal.com/team/patricia/onboarding
- Log in, for a workspace that already exists: https://console.patricia.app/login

## What she does

1. **Finished work, not suggestions.** She hands back the client report, the draft, the follow-up, ready to send.
2. **A brain that remembers every client.** She holds the accounts, the agency's voice, and what was decided, so nobody re-explains a client. Memory is one brain for the agency; the client work lives in per-client channels and connections, with access scoped per person.
3. **An approval gate on the work that reaches a client.** Every email, post or message she drafts waits for a named yes, by default every change and every spend waits for one too, and every action lands in an audit log. The meeting recap email is the exception: by default it goes to everyone on the invite, and the agency can narrow it to its team or switch it off.
4. **Proactive by default.** She watches the accounts she is given and raises the work the agency would forget, before anyone asks.
5. **Works on a schedule.** The Monday client report, a daily account check that stays quiet unless something is wrong, the Friday summary, month-end invoices.

On ad accounts she reads, flags and proposes. By default she changes nothing until a person approves it in Slack, and new campaigns start paused.

## Service lines

The services an agency sells to its clients and Patricia delivers, per client:

- **Search & AI visibility**: The GEO retainer: ChatGPT and Google AI visibility, page fixes, roundups, monthly report. https://www.patricia.app/geo-retainer
- **Reddit marketing**: Threads that rank on Google, and replies scored by a quality check, ready to post once approved. https://www.patricia.app/reddit-marketing
- **Ad creative & Meta campaigns**: One ad resized for every placement, finished in Canva, launched on Meta after your yes. https://www.patricia.app/ad-creative
- **Google Ads**: Weekly report with actions, a morning anomaly watch, budget steps after your yes. https://www.patricia.app/google-ads
- **Client reporting**: Weekly and monthly, as Google Slides, an HTML page, a PDF or PowerPoint. https://www.patricia.app/client-reporting
- **Finance & P&L**: Revenue digest every Monday, the monthly report, a P&L on settled cash. https://www.patricia.app/finance-reports

## Work categories

- **Human resources**: The people side of your agency: celebrations, pairings, and the rituals that keep a small team a team. https://www.patricia.app/use-cases/human-resources
- **Admin**: Client call recaps, status for the team, new client setup, and the coordination work that eats your week. https://www.patricia.app/use-cases/admin
- **Finance**: Client invoices chased and the money questions answered, where your agency already works. https://www.patricia.app/use-cases/finance
- **Campaigns**: Pacing, search terms, tests and competitor watch across every client account your agency runs. https://www.patricia.app/use-cases/campaigns
- **Content & social**: Client calendars, publishing, and on-brand content that ships without the back-and-forth. https://www.patricia.app/use-cases/content-social
- **Client work**: Client reporting, the weekly update, onboarding a new account, and the proposal, handled before anyone asks. https://www.patricia.app/use-cases/customers

## Frequently asked questions

### Who is Patricia for?

Small marketing agencies that run on Slack, with Microsoft Teams in beta. Performance and SEO agencies get the most out of her today, because Google Ads, Meta, GA4 and Search Console are the platforms she reads best. Web and development agencies are a worse fit.

### What does she do for an agency each week?

The Monday report per client, in your agency's tone. A daily check of every account that stays silent unless spend, CPL or traffic moves. Recaps of client calls with the decisions saved and the action items on the board with owners. Client requests turned into tasks with a draft reply. Month-end invoices per retainer. Ad hoc, the most common ask is: find the thread and draft the reply.

### Who approves her work?

Anyone you choose. Approval requests post in the channel where the work lives, so an account manager can approve their own accounts and the founder stops being the bottleneck. Every email, post or message she drafts waits for a named yes, and by default so does every change and every spend.

### Can clients see her?

Only where you invite her. She works in your internal channels by default and never posts in a shared client channel without a yes from your team. You choose exactly which channels she can read.

### How does she keep my clients' context straight?

Each client gets its own channels and connections, and access is scoped per person. Her memory today is one brain for your agency, organised by client channel, so a fact about one account is available to the team working on another. Separate memory per client is on the roadmap, and we will tell you plainly where it stands on the onboarding call.

### Does she only work in Slack?

Slack is her home. Microsoft Teams is live in beta. From either she works across the tools your clients live in: Google Ads, Meta, GA4, Search Console, HubSpot, Notion, Drive and 1,000+ more.

### What does it cost?

The founding plan is $45 a month for one workspace, every seat included, with 20,000 credits. Free credits come with the onboarding call, no card needed, and credits never expire. Top-ups are $2.25 per 1,000 credits, cheaper in bulk.

### What happens when my credits run out?

She pauses and asks. You can top up or wait for next month, and unused credits always roll over. The spend cap is on by default, so a busy month never surprises you.

### Do I have to set up or host anything?

No, and you do not do it alone. We add her to your Slack, connect the accounts you already manage, and point her at the first client with you on the call. It takes about 20 minutes. Nothing to host, nothing to maintain.

### Does Patricia learn from my data?

Yes. The more you use her and the more feedback you leave, the better she gets at your accounts and each client's voice. Your data is logged, deleted when you cancel, and never used to train anyone else's model. DPAs are available.

### Is my data safe?

Your data stays yours, logged, and deleted if you cancel. SOC 2 Type II and GDPR are in place, and ISO 27001 is certified. Everything runs in the United States; say so to a client who asks.

## Other machine-readable pages

Every page below also answers in markdown at its normal URL when you send
`Accept: text/markdown`.

- Pricing, plans, and worked examples: https://www.patricia.app/pricing.md
- Security, compliance, and data handling: https://www.patricia.app/security.md
- Connected tools and integrations: https://www.patricia.app/integrations.md
- What teams ask her to do: https://www.patricia.app/use-cases.md
- Who is behind Patricia: https://www.patricia.app/about.md
- Install the MCP server in Claude, Cursor, ChatGPT, Codex, or any client: https://www.patricia.app/mcp.md
- MCP server, REST API, and the OpenAPI document: https://www.patricia.app/developers.md
- Agent front door: https://www.patricia.app/llms.txt
- Full product context: https://www.patricia.app/llms-full.txt
- Agent skill: https://www.patricia.app/.well-known/agent-skills/patricia/SKILL.md
- Recovery document for a missing page: https://www.patricia.app/404.md