# Partner Run Sheet: one page per client when you resell agent work

> A free kit for agencies that resell agent work run by another team, and for the teams that run it. Keep one file with the agency, the operator and every client: what the client was told about who runs the work, each desk and who approves changes to it, every account and who owns it, support hours and urgent reply time, two escalation contacts, data limits, the off switch and what the client keeps if the arrangement ends. A checker lists what is missing per client, writes one run sheet each, and the agency owner signs only the clean ones.

- URL: https://paperchasewebb.ai/bots/marketplace/items/partner-run-sheet-one-page-per-client-when-you-resell-agent-work/
- Type: Prompt pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Claude Code, Codex, Grok Bot, Hermes (named in the listing); One Python script, a template, a fictional studio example with two clients, and agent rules for each harness. Tested on Linux
- Price: Free USD
- Difficulty: Beginner
- Setup time: 15 min
- Time to result: First run sheet in about 15 minutes
- Format: Markdown (.md) file, partner-run-sheet-one-page-per-client-when-you-resell-agent-work.md
- Version: 1.0, updated 2026-11-03
- License: Personal and commercial use.

## What you end up with

Every client has one page both teams agree on, and a signature that goes stale the moment that page changes.

## What you get

- The method: write who runs it, who owns what and how it stops, per client, before something breaks
- partner.py: 5 file checks and 7 findings (client not told, account not in the client's name, operator approving its own changes, thin support, no data limits, no off switch, no exit plan)
- One run sheet per client and a partner checklist with the open items counted
- Sign-off refused inside an agent session, from anyone but the agency owner, while items are open, or after that client's entry changed
- AGENTS.md, CLAUDE.md, a Grok Bot standing order and a Hermes skill, a fictional example, and 29 tests

## Who it is for

Agencies and operators who sell agent work under one brand and run it with another team.

## Tools needed

- Python 3.8 or newer: partner.py: file check, 7 findings per client, one run sheet per client, a partner checklist, agency owner sign-off and status; standard library only
- Grok Bot, Claude Code, Codex or Hermes (optional): fills the file from the agreement, runs the check and drafts each fix under AGENTS.md; never signs, moves an account or contacts anyone
- You need: Python 3.8 or newer
- You need: Your partner agreement, the account list and the support plan for each client

Cost to run: Free. Python is free.

## How it works

1. **Run the example.** Unpack the file and run python3 partner.py check example/partners.json. Expected: The bakery is ready to sign; the auto glass shop has 7 open items.
2. **Fill one real client.** Copy templates/partners.json and fill one client from your agreement, account list and support plan. Expected: partner.py check lists that client's open items.
3. **Sheets and fixes.** Run sheets, then draft a fix for each open item and take it to the client. Expected: One run sheet per client and checklist.md.
4. **Sign at your own terminal.** When a client has no open items, the agency owner runs approve for that client. Expected: status shows signed, and CHANGED if the entry is edited later.

## Sample prompt: Weekly partner check (Grok Bot, Claude Code, Codex, Hermes)

```
Follow AGENTS.md. Run partner.py status, then sheets for any client with open items, and send the agency owner each run sheet with a drafted fix per item. Do not sign, edit signed.json, move an account or contact the client or the operator.
```

One prompt.

## Free preview of partner-run-sheet-one-page-per-client-when-you-resell-agent-work.md

````markdown
# Partner Run Sheet

**Reselling agent work under your own brand? Keep one page per client that says who runs it, who owns every account, who approves changes, and what the client keeps if the partner arrangement ends.**

Version 1.0, 2026-11-03. By PaperChaseWebb Inc. Free. Works with Grok Bot, Claude Code, Codex and Hermes, or by hand. Python 3.8 or newer, no installs.

## The problem

An agency sells the work. Another team runs the agents. The client sees one brand. That setup is common and it can be fine, until something breaks at night and nobody knows who answers, or the arrangement ends and the client finds out their phone number belongs to a company they never signed with.

Most of that trouble is decided in advance by a few written answers. This kit makes you write them per client and will not let the page be signed while one is missing.

## What you get out of it

- One run sheet per client: brand shown, who operates, desks and approvers, accounts and owners, support, escalation, data limits, off switch, exit.
- A partner checklist across every client with the open items counted.
- A signature from the agency owner on each clean sheet, which goes stale on its own if that client's entry changes.

## Who it is for

Agencies and consultants who resell or white-label agent work run by a partner, and operators who run agents behind someone else's brand and want the same page on both sides.

Not a contract and not legal advice. It records what your agreement says and poin
````

## Test record

- Date: Nov 3, 2026
- What was run: tests/test_partner.py (29 tests) unpacked from the pack file and run fresh on Linux, Python 3.8, 3.9, 3.11, 3.12 and 3.13; check, sheets, approve and status on the fictional example.
- Result: 29 passed, 0 failed on all five versions; the example has one client ready to sign and one with 7 open items; sign-off refused in agent sessions, without a terminal, for the wrong name, with open items and after an entry edit; the partner file is never modified.
- Not run: macOS or Windows. A real partner agreement. A live Grok Bot, Claude Code, Codex or Hermes session.

Copied from this item's dated test notes. What was not run stays in.

## Worth knowing

- It checks what is written, not what is true. A disclosure sentence the client never saw passes the check.
- One agency and one operator per file.
- On 2026-11-03: 29 tests passed on Python 3.8, 3.9, 3.11, 3.12 and 3.13 on Linux, run from the files unpacked out of the pack. Agent rules guide; they were not loaded inside each harness for this release.
- Not a contract and not legal advice.

## Questions

**Do I have to tell the client who runs the work?** The kit flags it as open until the file holds the sentence the client has actually seen. How much you disclose is your call and your agreement's.

**Can my agent sign a run sheet?** No. Sign-off is refused inside an agent session and for anyone but the agency owner named in the file.

**What if an account is in the operator's name?** It stays open until the account moves to the client or a transfer note says when and how it will.

**What should I pair it with?** Clean Handover (free) gets the client running if a provider stops, and Retainer Scope Sheet ($29) itemizes what each client's monthly covers.

## How to get it

Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/partner-run-sheet-one-page-per-client-when-you-resell-agent-work/, no signup.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com