Founder Weekly Strategy Review

Run a structured founder weekly review covering momentum, bottlenecks, customers, product, hiring, and financial focus for the next seven days.

The Prompt

You are a strategic operating partner for a startup founder. Run a weekly review that surfaces the truth, forces prioritization, and ends with a clear focus plan.

## 1. Review the Week
Summarize:
- Wins
- Misses
- Surprises
- Open loops still draining attention

## 2. Business Health Check
Assess:
- Revenue or pipeline movement
- Product progress
- Customer feedback signals
- Team execution
- Cash or runway concerns

## 3. Bottleneck Diagnosis
Identify:
- The single biggest bottleneck
- Whether it is strategic, operational, product, team, or market-related
- What evidence supports that diagnosis

## 4. Priority Reset
Recommend:
- Top 3 priorities for next week
- What should be deprioritized
- One decision the founder is avoiding
- One conversation the founder should have immediately

## 5. Output Format
Return:
1. Week in review
2. Business health summary
3. Core bottleneck
4. Top 3 priorities
5. Stop-doing list
6. Key decisions and conversations

Founder notes:
[PASTE WEEKLY NOTES, METRICS, OR BULLETS]

Optional context:
- Company stage: [IDEA / MVP / EARLY REVENUE / GROWTH]
- Team size: [NUMBER]
- Runway: [OPTIONAL]
- Current strategic focus: [OPTIONAL]

How to Use This Prompt

1. Paste the messy weekly notes, not a polished summary.
2. Include real metrics when possible.
3. Ask the model to force tradeoffs, not just list everything important.
4. Use the stop-doing list to cut attention leaks.
5. Reuse the same structure weekly so patterns become visible.

Example Input

Company stage: Early revenue
Team size: 6
Current strategic focus: Improve retention and close 3 enterprise pilots
Founder notes: [weekly notes pasted here]

Example Output

1. Week in Review

Momentum improved in pipeline, but product focus scattered across too many customer asks.

2. Core Bottleneck

The company is trying to serve both urgent customer requests and roadmap bets without a clear prioritization rule.

3. Top 3 Priorities

• Lock the retention improvement plan to one measurable customer workflow
• Assign ownership for enterprise pilot follow-up
• Stop accepting low-leverage roadmap requests without a clear revenue or retention link

When This Prompt Is Most Useful

Use this prompt when you need help with founder weekly strategy review but do not want a generic answer. It works best for founders, managers, consultants, and teams making practical business decisions who already have some context and want the AI to organize it into a decision memo, options analysis, operating plan, risk register, or next-step checklist. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.

This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.

Inputs to Prepare

Before running the prompt, gather:

• The real goal or decision you are trying to support
• The audience, customer, learner, stakeholder, or user involved
• Any source material the AI should use instead of guessing
• Constraints such as deadline, format, budget, word count, platform, or policy
• Examples of good and bad outputs if you have them
• The exact tone you want the final answer to use

For this page, the most important context is: business model, customer segment, current constraint, data available, decision deadline, and options already considered. If you leave that out, the model may still respond, but the result will usually be generic.

Example Input

Company: B2B SaaS at $35k MRR. Problem: onboarding drop-off. Goal: choose the next two experiments.

How to Review the Output

Do not use the first answer blindly. Check whether it:

• defines the decision before recommending actions
• compares options instead of forcing one answer
• turns strategy into measurable next steps
• makes assumptions visible instead of hiding them in confident language
• gives you something you can act on, test, or revise within the same work session

If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.

Common Failure Modes

• Too little context: the AI fills gaps with generic advice.
• No review criteria: the output sounds polished but is hard to judge.
• Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
• Overclaiming: the model may invent certainty when the source material is weak.

The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.

Practical Variations for Founder Weekly Strategy Review

• Diagnosis mode: Ask whether the real constraint is demand, positioning, operations, pricing, distribution, or execution.
• Options mode: Request three options with cost, upside, downside, risk, and evidence needed.
• Execution mode: Ask for a 30-day plan with owner, metric, checkpoint, and rollback condition.

Follow-Up Prompts

Use these after the first answer:

• “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
• “Give me a conservative version, a direct version, and a version optimized for speed.”
• “Create a final review checklist I can use before I publish, send, ship, or present this.”

What Makes This Page Different

This page is useful when you are working on founder weekly strategy review and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.