Weekly status update

Q: What is a weekly status update?

A weekly status update is a short report that summarizes how a company performed in the past seven days — growth, product, customers, and operations. The best updates lead with numbers and are skim-able in under two minutes.

Q: How do you automate a weekly status update?

Connect your databases and SaaS tools (Stripe, HubSpot, GitHub, your product database) to a single source like Basedash, then schedule an AI automation to read across them every Friday and write the update in your voice.

Q: What should be in a weekly status update?

Most useful sections are a TL;DR, growth metrics versus prior week, product releases, notable customer events, and a short list of things to watch next week.

Q: Who should write the weekly status update?

Founders, COOs, chiefs of staff, and operators usually own it. Automating the first draft cuts the time from two hours to two minutes and keeps the cadence consistent.

A free, AI-generated weekly status update template. Pulls highlights, metrics, blockers, and next steps from your tools every Friday — no manual writing.

Use this template How automations work

Runs weekly Scheduled Delivered to Slack, Email

Weekly status update

Active

Trigger

Runs weekly

Instructions

Write a weekly status update covering the past seven days, in the voice of a thoughtful executive.

Delivery

Slack · Email

Example output

A realistic sample of what this automation delivers — your version draws on your data.

Weekly status update Runs weekly · Sent to Slack, Email

Sample output

Last 8 weeks

New signups

184 +6% (173)

Paying customers

24 +14% (21)

Weekly active

9.84K +12% (8.79K)

Open P1 issues

3 -2 (5)

TL;DR

New signups rose 6% to 184; verified users up 9% to 171.
24 new paying customers — best week of the quarter, led by mid-market.
Failed connector syncs dropped 41% after the Friday hotfix.
3 open P1s remain, down from 5 last week.

Growth. Weekly active users hit 9,840, up 12% week-over-week. Activation rate held at 41%, in line with the eight-week average.

Product. Shipped the multi-source automation editor on Tuesday and a faster chat retry on Thursday. Two material bugs hit prod and were rolled back within 30 minutes.

Customers. Two notable signups (Acme, RegionalCo). One mid-market churn — small account, not a pattern.

Operations. Recruiting filled two engineering offers; one design loop slipped a week. Burn rate steady at the 12-month plan.

Next week. Watch self-serve activation post-onboarding redesign; first onboarding contract is up for renewal.

The prompt

Copy, paste, customize.

Drop this into a Basedash automation. AI fills in the numbers from every source you've connected.

Instructions

Write a weekly status update covering the past seven days, in the voice of a thoughtful executive.

Look across every data source connected to Basedash and synthesize the most important movements. The reader should be able to skim it in under two minutes and walk away with an accurate sense of how the business performed.

Structure:

**TL;DR** — Three to five bullets that name the biggest moves of the week. Lead with the number.

**Growth** — New signups, activations, paying customers, and MRR/ARR change. Always compare to the prior week and call out anything outside ±10%.

**Product** — Notable releases, features shipped, or bugs that affected customers.

**Customers** — Notable signups, expansions, churn, or support spikes.

**Operations** — Anything that slowed us down (failing payments, on-call incidents, hiring, recruiting bottlenecks).

**Next week** — Two or three things to watch.

Rules: lead bullets with numbers. Use plain prose, no emojis. Don't repeat the same fact in multiple sections.

Data sources