Tracking · Reporting Cadence & Templates

Design a Manager-to-Founder Update Template

Build a weekly manager-to-founder update template that earns trust and triggers founder support, not surprise.

managerIntermediate⏱ 1 hr/week + far fewer founder interruptions
When to use
Use if you're a new-ish sales manager at an agency and your founder still wants to know what's happening without joining every call. This builds a 1-page update they get every Friday so they can stay out of the weeds — and you can stay in front of bad news.
The prompt
You are a sales manager at a digital marketing agency, reporting weekly to the founder.
Agency: [AGENCY_NAME] — [SERVICES] | Reporting period: weekly | Audience: founder (wants signal, not noise) | KPIs: [KPIS] | Team size: [TEAM_SIZE]
Design a manager-to-founder weekly update TEMPLATE that gives the founder confidence the sales org is being managed — covering forecast, team health, and asks.

- One page max
- Must include 'What's the action?' — asks of the founder this week
- Must surface bad news in the first 3 lines (no burying)
- Honest forecast call (commit / best / worst) every week
- Skim-readable in 
Markdown template with: (1) Forecast call (commit/best/worst + confidence), (2) Team health (per rep: green/yellow/red + 1-line why), (3) Pipeline highlights (top deal up, top deal at risk), (4) What I'm doing about it (manager actions), (5) Asks of founder (max 3). 1-line prompt under each section.
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — Service lines sold
  • [KPIS] — KPIs the founder cares about
  • [TEAM_SIZE] — Number of reps you manage
Example input
AGENCY_NAME: Crestline Digital | SERVICES: SEO + paid media | KPIS: new MRR, pipeline coverage, ramp of new hires | TEAM_SIZE: 4 AEs
Example output
# Crestline — Manager → Founder, Week of [DATE]

## Forecast call
- **Commit:** $__k | **Best:** $__k | **Worst:** $__k | **Confidence:** H/M/L
- _2-sentence narrative: what could move the call._

## Team health
| Rep | Status | Why |
|---|---|---|
| Maya | :green_circle: | On pace, 2 deals late stage |
| Dev | :yellow_circle: | Pipeline thin, coaching this week |
| Sara | :red_circle: | Missed last month, action plan started |

## Pipeline highlights
- **Top up:** _Deal name, $, why it moved_
- **Top risk:** _Deal name, $, what's wrong_

## What I'm doing about it
- _Manager actions this week (3 bullets)_

## What's the action? — Asks of founder
1. _Specific ask_
2. _Specific ask_
3. _Specific ask_
Pro tips
  • Always lead with the forecast call — that's the founder's #1 question.
  • Use rep colors consistently. Going from green to yellow should never be a surprise.
  • If you have no asks 3 weeks running, you're probably not asking for enough.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts