Give AI the repeat work, not the keys.

Sort every recurring task into three buckets

List every recurring task your team touches in a month. Reports, audits, QA passes, content updates, monitoring, onboarding steps, all of it. Then sort each into exactly one bucket:

Then pick your first automation by time, not by noise: the biggest recurring time sink in bucket 1 goes first, not the loudest request.

Your first 30 days

1. List and sort. No tools required. Write down the recurring work and sort it into the three buckets. Also answer honestly: what can our AI touch right now? If that takes more than a sentence, inventory it first.
2. Automate exactly one read-only workflow. A report or an audit. One. Resist scope.
3. Surface it. Findings land on a dashboard or channel your team already watches. Escalation only: silence means healthy.
4. Add your first approval gate. Pick one bucket-2 task, wire in the human yes, and only then consider write access anywhere.

Don't run these systems yourself? This checklist is the agenda for a call with whoever does: your agency, your web team, or IT. A useful test: ask them which bucket your monthly report lives in. If they don't understand the question, that's information too.

The rules that make it safe

• A badge, not a key. The AI never holds a credential. Secrets live encrypted behind the door; the AI holds a revocable session that opens only what its role allows, logs every action, and dies the moment it's turned off. A compromised chat has nothing to steal.
• One gated door. Every AI request goes through a single access layer that checks permissions, writes a log line, and holds anything sensitive for approval. If a request didn't come through the door, it doesn't happen.
• Read is the default. Every new connection starts read-only and widens only when a real task demands it.
• Propose, don't publish. AI drafts changes; a human approves anything customer-facing.
• Identity, not shared keys. Access is tied to a named person's work account and revocable in one place. Offboarding is a single change, not a scavenger hunt.
• Check what your platform gates for you. Some vendors lock everything down; others hand you full access and the responsibility. Neither is wrong, but know which one you're holding before you connect it.

The technical deep dive

The system behind the talk is a centralized MCP server (Model Context Protocol) the whole team connects through. Single sign-on restricted to company accounts, every tool classified into read, content, or infrastructure tiers, per-site credentials encrypted at rest and health-checked daily, and an audit trail on every call. Around 140 tools sit behind the door, covering the website and store, hosting, analytics, search, support, security scanning, and reporting for 185 managed sites, with 20-plus automated checks running against every site, every night.

Design decisions that mattered most: generic REST proxy tools instead of one tool per endpoint, so new capabilities need no new code. Explicit tier classification for every write-shaped tool, enforced by tests, so nothing lands in a permissive tier by accident. Credentials validated before storage and probed on a schedule, so a dead key surfaces as an alert instead of a mystery. And administrator-level operations kept as operator scripts no AI agent can invoke at all.