## TL;DR

A good weekly report is boring in structure and interesting in insight: same sections, new learnings.
The template should take 30 minutes to fill, not 3 hours.
Applies to growth teams, solo founders, and agent-run growth loops.

## The query

```text
how to build a weekly growth report template
```

## Use this when

- You report growth weekly to a team or founder.
- The report should take minutes to fill, not hours.
- You want structure that stays useful over time.

## Not for

- You need real-time monitoring (build a dashboard, not a report).
- The audience wants a narrative essay (write a memo instead).
- Nothing changed this week (still send it; 'no change' is information).

## Steps

1. Define the five sections: headline metric, funnel, experiments, learnings, next week.
   Expected output: A fixed template everyone recognizes.
2. Fill the headline metric and funnel with the week's numbers and week-over-week deltas.
   Expected output: Numbers with context, not raw totals.
3. Write learnings as decisions, not observations: what you will do differently.
   Expected output: Actionable takeaways, not a data dump.
4. Send on the same day each week and keep an archive.
   Expected output: A cadence the team relies on and a history you can search.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_r4e1K6acjW_hhRW5CxvjLg
