Day 18: Build a Weekly Business Review That Keeps You Honest

The Point Of Today

A founder needs a rhythm for telling the truth about the business.

Without a rhythm, the loudest issue wins. A customer complaint, a delayed invoice, a new feature idea, or a promising sales call can take over the week. Each may matter, but none should replace a structured view of business health.

A weekly business review creates that structure. It gives you a fixed time to look at the numbers, the risks, the wins, and the decisions that need attention. It does not need to be complicated. In fact, if the review becomes complicated, it will probably stop happening.

Today you will design a weekly review that can be completed in 30 minutes and repeated every week.

Leading And Lagging Indicators

Good reviews include both leading and lagging indicators.

Lagging indicators tell you what already happened:

• Revenue.
• Profit.
• Churn.
• Customers won.
• Cash balance.
• Completed projects.

Leading indicators tell you what is likely to happen:

• Sales calls booked.
• Proposal conversion.
• Product activation.
• Support volume.
• Pipeline quality.
• Trial usage.
• Delivery backlog.

Founders tend to over-focus on lagging indicators because they feel concrete. But by the time revenue drops, the underlying issue may have started weeks earlier. Leading indicators give you time to intervene.

For example, if sales calls booked are down for two weeks, revenue may drop next month. If onboarding completion falls, retention may suffer later. If support tickets rise around one feature, product confusion may be growing.

Choose Metrics That Support Decisions

Do not track metrics because dashboards usually include them.

Track metrics that help you decide what to do. Each metric should connect to a question:

• Do we have enough pipeline?
• Are customers reaching value?
• Are we retaining the right customers?
• Is delivery quality holding?
• Is cash runway changing?
• Are we spending time on the highest-leverage work?

If a metric does not support a decision, it may not belong in the weekly review.

Eight to ten metrics are enough. More than that and the review becomes reporting theater. The goal is not to impress yourself with information. The goal is to see the business clearly enough to act.

Trigger Thresholds

A metric becomes more useful when you define a threshold.

For example:

• If weekly sales calls fall below five, investigate pipeline sources.
• If onboarding activation falls below 60%, review the first-week experience.
• If support tickets rise 30%, inspect the source of confusion.
• If runway drops below nine months, review spend and fundraising timeline.
• If proposal conversion falls below 25%, review sales qualification.

Thresholds prevent vague concern. They turn data into a decision rule.

You can adjust thresholds as the business matures. Early thresholds may be rough. That is fine. The act of defining them improves the review.

The 30-Minute Agenda

A weekly review should be short enough to survive busy weeks.

Use this agenda:

1. Five minutes: wins and notable events.
2. Ten minutes: metric review against thresholds.
3. Five minutes: risks, blockers, or surprises.
4. Five minutes: one decision or tradeoff.
5. Five minutes: next week's focus.

If you are a solo founder, run it alone. If you have a team, keep the group small. If advisors are involved, send them a summary rather than inviting them into every operational detail.

The review should end with one clear focus for the coming week. If everything matters equally, the review has not done its job.

Include Qualitative Notes

Numbers tell part of the story.

Qualitative notes often reveal the cause. A sales conversion number may be down because buyers are confused about pricing. Activation may be down because new customers misunderstood setup. Support may be up because one workflow is unclear.

Capture observations:

• What did customers say this week?
• What objections repeated?
• What felt harder than expected?
• What decision are we avoiding?
• What surprised us?

These notes become extremely valuable after several weeks. AI can analyze them for patterns that are hard to see in the moment.

Keep A Decision Log

Add one small section to the weekly review: decisions made.

This can be as simple as:

• Decision.
• Reason.
• Evidence used.
• What we expect to happen.
• When we will review it.

Founders forget why decisions were made because the context changes quickly. A decision log gives future-you a record of the thinking at the time. It also makes AI analysis more useful later because it can compare what you expected with what actually happened.

The goal is not bureaucracy. The goal is learning. A business improves faster when decisions leave a trace.

Today's Practice

Run the prompt and create the template.

Then fill it in immediately using whatever data you have. Do not wait for a perfect dashboard. A partly manual review done weekly is more valuable than an automated dashboard nobody trusts.

At the end, write one sentence:

"This week, the business most needs attention on [X] because [Y]."

That sentence is the point. The review exists to move you from scattered awareness to clear action.