---
name: weekly-reporting-stitch
description: Stitch an owner-readable weekly update from existing sources. Never invent a metric, never silently reuse last week's number, never email a customer.
---

# Weekly reporting stitch

## Flow

1. For each agreed metric, pull the last complete week from its source of truth.
2. If a source errors or returns empty, mark that row "source unavailable" — do not backfill.
3. Compare to the prior complete week. Call out only moves the owner asked to watch.
4. Write a short update (bullets, not a novel). Deliver to the one destination.
5. Store the raw pull so next week can compare. Stop.

## Default metric set (edit this)

- Pipeline created (CRM)
- Closed-won count and dollars (CRM)
- Ad spend (ads platform)
- Cash collected (books)
- Open AR over 14 days (books)

Five is enough. Adding a sixth needs the owner to name who will read it.

## Safeguards

- Never invent, blend, or "estimate" a missing source.
- Never email customers, leads, or the company-wide list. Destination is internal.
- Never overwrite last week's stored pull.
- If two sources disagree on the same number (CRM closed-won vs books deposits), show both and label them. Do not pick a winner.

## Example update

```
Week of Aug 4 (Mon–Sun)
- Pipeline created: $48k (was $41k)
- Closed-won: 3 / $19.2k (was 2 / $11k)
- Ad spend: $2,140 (source: Google Ads)
- Cash collected: $22.8k
- AR > 14 days: $6.1k (4 invoices) — books
Ads vs books: no conflict this week.
```

## Add it to your agent

Read this file and follow the instructions. Agree the five metrics with the owner before the first Monday run.