Power-userClaude

๐Ÿ“Š Automate your weekly reports with Claude

Every owner and manager has a version of this: Friday arrives, and someone โ€” usually you โ€” spends an hour turning numbers into a readable update. This workflow gets it down to ten minutes, and the report gets better, not worse.

Step 1: Standardize the input

The secret isn't the prompt โ€” it's feeding the same shape of data every week. Make a simple template you fill (or export) weekly:

WEEKLY NUMBERS โ€” [week of] Sales/revenue: [number] (last week: [number]) New leads/inquiries: [number] (last week: [number]) Jobs completed: [list or number] In progress: [list with status] Problems that came up: [short notes] Wins worth mentioning: [short notes] Next week's focus: [notes]

Step 2: The report prompt (save it, reuse it)

You write my weekly business report. Audience: [me / my team / my partner / the bank]. Using the numbers below, write: 1. HEADLINE โ€” one sentence: is this week ahead, behind, or steady, and why. 2. THE NUMBERS โ€” a clean table comparing this week vs. last, with % change. 3. WHAT DROVE IT โ€” 2-3 bullets connecting the numbers to real events. Only use causes I actually gave you โ€” never invent explanations. 4. WATCH LIST โ€” anything trending the wrong way for 2+ weeks. 5. NEXT WEEK โ€” the stated focus, as 3 clear priorities. Plain language, no corporate filler, fits on one page. [paste this week's template]

Step 3: Build memory into it

Keep every weekly report in one running document. Monthly, paste the last four in:

Here are my last 4 weekly reports. What trends do I not see week-to-week? What's quietly improving, what's quietly slipping, and what one question should I be asking about next month?

Why this beats the old way

Consistency. Humans write good reports on good weeks and thin ones on busy weeks โ€” and busy weeks are exactly when the report matters. A standardized input plus a saved prompt means the quality never dips, and the trend view catches what Friday-afternoon eyes miss.

Check the math. AI occasionally fumbles arithmetic. The table takes 30 seconds to verify โ€” do it every week. Wrong numbers in a confident report are worse than no report.
Same trick works for any recurring doc: job-site updates, client status emails, board summaries. Standard input + saved prompt + running history = ten-minute documents.

Want this done for you?

We set up these exact systems for businesses like yours. One call, honest scope, no pressure.

Start your project