# Intake: weekly paid and pipeline summary (Acme Co, fictional)

Answers to assets/intake-template.md, given by the marketing ops lead on 2026-10-27. Every company, host and value here is invented.

1. Use case: one assistant writes a weekly paid performance and pipeline summary for the Monday marketing meeting. Three marketers use it once a week, attended, in an AI chat app on a business plan.
2. Systems and accounts: the Acme Co Google Ads account 123-456-7890, the Acme Co Meta ad account, and Acme Co's sales pipeline in the Example Co CRM. Out of scope: the partner business unit's pipeline in the same CRM, and every other ad account the freelancer manages.
3. Data: campaign spend, clicks, conversions and cost per conversion; deal names, stages, amounts, close dates, company names and owner names. No contact emails or phone numbers. No free text.
4. Writes: none. Nothing should be sent, paused, published or changed.
5. AI client: the chat app's desktop app on three laptops, business plan. No scheduled runs.
6. Servers:
   - adsbridge-mcp, an npm package for Google Ads and Meta reporting, recommended by a freelancer. Version not chosen yet. Needs `ADS_BRIDGE_TOKEN`.
   - exampleco-crm, hosted by the CRM vendor at `https://mcp.example.com/crm`, OAuth with PKCE, documented on the vendor's developer site.
7. Identity: per-user OAuth for the CRM with a custom View-only role; one shared adsbridge token, created by the freelancer.
8. Test environment: a CRM sandbox with fictional records and a Google Ads test account. No Meta test ad account yet.
9. Owners: marketing ops lead (connection owner), CRM admin (system owner), data protection lead (privacy owner).
10. Timing: wanted before quarterly planning. A sandbox pilot is acceptable.

Also supplied: the team's draft shared config ([example-acme-mcp-config.json](example-acme-mcp-config.json)), which still holds five servers from earlier experiments, and one marketer's Codex config ([example-acme-codex-config.toml](example-acme-codex-config.toml)).