startup-stack

Weekly Recap

Copy to stack/10-pulse/recaps/YYYY-MM-DD.md. Or run prompts/12-weekly-recap.md and it will fill this in from the stack and your answers.

Copy to stack/10-pulse/recaps/YYYY-MM-DD.md. Or run prompts/12-weekly-recap.md and it will fill this in from the stack and your answers.

Thirty minutes. One page. Same shape every week. Never edited after the fact.


1. The numbers

MetricThis weekLast weekΔ
[metric 1]
[metric 2]
[metric 3]
Cash in bank
Runway (weeks)

2. What moved

Things that actually happened. Shipped, signed, launched, hired, fixed. Countable.

- - -

3. What did not move

Last week's commitments still open, with an honest reason.

CommitmentWeeks openWhy notStill doing it?

Anything here for three weeks running is not a scheduling problem. Say so.

4. What we learned

The market told you something. Objections heard, prices rejected, a channel that produced nothing, a competitor's move, why a deal died.

- -

Objections heard this week: → log into stack/02-customer

ObjectionFromHeard before?

5. Next week

Three to five commitments, each with a number attached.

#CommitmentNumberBy
1
2
3

✗ "push on sales" → ✓ "visit 25 kirana stores, place stock in at least 4" ✗ "work on fundraising" → ✓ "add 40 investors to the CRM, send 20 connection requests" ✗ "improve the ads" → ✓ "double the daily ad budget for 5 days, log cost per lead daily"

A commitment without a number cannot be graded, so it is always half-done and never failed.

6. Where I need help

Specific and askable.

- -


Stack updates made this week: [which sections were corrected or added to]

Confidence in the plan this week: [higher / same / lower] — and why in one line.

Generated from worksheets/weekly-recap.md in the repository. Edit the markdown, not this page.