Solo-founder agent ops playbook: run your business with agents without losing control

Using [inbox, calendar, task list, payments dashboard: whatever the agent can read], give me today's brief:
1. Meetings today with one line of prep each.
2. Messages that need me today, with a suggested next step. Do not draft replies yet.
3. Money: payments received, failed payments, refunds requested since yesterday.
4. Anything an agent did yesterday that I should check.
5. One thing I said I would do that is now overdue.
Under 200 words. If a source was unavailable, say so.

This runs at rung 0: read only. It is the safest first job to hand over and shows quickly where your data lives.

# Solo-founder agent ops playbook: run your business with agents without losing control

PaperChase agent use case pack (playbook), version 1.0. For founders and freelancers running a business of one or a few with ChatGPT, Claude, Codex, Claude Code, Cursor or automation tools. Time: one afternoon to set up, 30 minutes a week to run.

## The problem

You have agents drafting email, writing code, summarizing calls and pulling numbers. Each was set up on a different evening. Nobody (meaning you) knows which ones have access to what, what they cost last month, or what happens if one sends the wrong thing to a client. The work gets done, but the risk and the bills pile up quietly.

This playbook gives you a simple operating system: which jobs to hand to agents, how much power each one gets, one rules file they all follow, a weekly review and a plan for when something goes wrong.

## The permission ladder

Every agent job sits on one rung. Move a job up only after it has run cleanly for a while on the rung below.

| Rung | The agent can | You | Good for |
|---|---|---|---|
| 0. Read | Read and summarize | Act on the summary | Inbox digests, call notes, metrics |
| 1. Draft | Prepare a draft in the tool | Review, edit and send | Replies, proposals, posts, code changes as pull requests |
| 2. Act with approval | Take the action after you click approve | Approve each one | Labeling, calendar holds, small refunds |
| 3. Act alone, within limits | Act inside hard limits, logged | Review the log weekly | Tagging, filing, internal reports |

Anything that sends to clients, spends money, deletes data or publishes publicly stays at rung 1 or 2 unless you have a strong reason and a written limit.

## Contents

1. Job inventory and scoring
2. The permission ladder in practice
3. OPS.md: one house rules file for every agent
4. Daily brief and weekly review
5. Cost controls and the monthly budget table
6. Credential hygiene
7. The agent register
8. Incident runbook: five things that go wrong
9. Prompts for each part
10. Quarterly prune