Your Sunday-night business briefing prompt

The briefing prompt

Paste this. Fill in the bracketed sections. Hit enter.

You are my weekly business advisor. Read my briefing below and produce
a structured Monday-morning plan.

THE WEEK JUST FINISHED (5 sentences)
1. What I shipped this week: [list 2-3 things]
2. What I didn't ship that I'd hoped to: [1-2 things]
3. What's on my mind: [1-2 things, candid]
4. Where I felt blocked or stalled: [1-2 specific things]
5. Significant moments in customer / supplier / team relationships:
   [1-2 things]

THE WEEK AHEAD (3 sentences)
1. The big rocks I want to ship: [2-3 outcomes]
2. Commitments already locked in the calendar: [meetings, deliverables]
3. Anything I'm privately dreading or excited about: [be honest]

OUTPUT REQUIRED
1. RANKED PRIORITIES for the week ahead (top 3, with reasoning).
2. BLOCKERS to clear before Wednesday, what's stopping each priority,
   and the specific first action to unblock.
3. THREE SPECIFIC ACTIONS to take Monday-to-Wednesday. Time-boxed.
4. THE ONE DECISION I'M AVOIDING. Identify it honestly, even if I
   didn't name it explicitly above. If you're not sure what it is,
   ask me one clarifying question.
5. PATTERN-SPOTTING (skip on first run). If we've done this briefing
   before, name any pattern you've noticed across recent weeks, what
   I keep mentioning, what I keep avoiding, what I keep saying I'll
   ship but don't.

Honest, useful, not sycophantic. Tell me the truth even if it stings.
Australian English, no exclamation marks.

That’s it. The whole workflow is one prompt + the 5+3 sentence briefing + the read-and-reply cycle.

What makes this work better than journaling

We’ve watched a lot of small business operators try weekly review systems. Manual journaling, GTD weekly review, Sunday planning sessions, the works. Most stop within 4-6 weeks. Three reasons this Claude-mediated version sticks where the manual versions don’t:

1. Activation cost is low. Writing a page is hard at 8pm Sunday. Writing 8 sentences is easy. Lower friction = sustained habit.
2. Pattern-spotting is automated. Most manual journals never get re-read. Claude has the conversational continuity to notice “this is the third week you’ve said you’ll deal with the supplier issue” without you having to re-read 3 weeks of journals.
3. Push-back is built in. The prompt asks Claude to identify the decision you’re avoiding. Most operators feel the friction of that question, and the friction surfaces what was previously vague.

What you’ll discover in week 3

Almost every operator who runs this workflow weekly for 3-4 weeks discovers the same 2-3 patterns:

• A stalled decision they’ve been mentioning but not acting on. (Hiring, firing, raising prices, killing an offering, telling a customer no.)
• A relationship cooling that they’ve been managing but not addressing. (A supplier, a client, a team member, a partner.)
• An offering not landing that they’ve been investing in despite signals. (A service line, a product, a channel.)

The Sunday briefing surfaces these because the explicit “what you’re avoiding” question forces them up. Once surfaced, action becomes possible.

What the briefing is NOT for

Be honest about limits.

• Operational scheduling. This is not your calendar; you still need a calendar.
• Project management. This is not your task tracker; you still need Asana / Linear / Notion / sticky notes.
• Detailed planning. The output is high-level priorities and unblock actions, not Gantt charts.
• Therapy. AI is not a therapist. If the patterns surfacing are emotional / personal / stress-laden, those need a human (friend, partner, therapist). The Sunday briefing surfaces; it doesn’t process.

Variants we’ve seen work

Variant 1: The end-of-day mini-briefing (5 minutes)

Last thing every workday, paste a 4-sentence end-of-day summary into Claude. Less ambitious than the Sunday weekly; useful for operators who want shorter feedback loops. We cover this in The first 10 prompts.

Variant 2: The monthly retro (45 minutes, last Sunday of the month)

Once a month, longer version. Paste 4-5 of your weekly briefings from the past month back into Claude and ask for: monthly themes, what’s improving, what’s regressing, the one big bet for the next month. The compounding insight from this is unreasonable. Most operators we’ve seen do this monthly retro for 6+ months become noticeably sharper in their decision-making.

Variant 3: The team-leader version

Same prompt structure, with two additions: (1) “what should I delegate but haven’t?” and (2) “what does my team need from me this week that I haven’t said yet?” The team-version surfaces management-specific avoidances that the solo version doesn’t.

Setup once: make this stick

Three small things that compound:

1. Calendar a 15-minute Sunday slot. Every Sunday, same time. Habits beat motivation.
2. Save the prompt as a Claude Project with your voice file pre-loaded. The Project becomes your weekly advisor; the chat history compounds the pattern-spotting.
3. Keep the chat history. Don’t delete past briefings. Claude reads back over recent weeks to surface patterns. The longer the history, the sharper the pattern recognition.

If you do nothing else with AI this year, do this. Solo-operator use is highest here.

What’s next

• The inbox cleanup playbook for the daily companion workflow.
• The first 10 prompts every Australian SMB owner should run for the broader set.
• Claude for the not-quite-beginner for the deep dive on Projects + voice files + compounding workflows.