What Should a Founder's Weekly Scorecard Track, and Why Does Cash Come First?

Our guide to handing off work so it does not come back covers why a founder who delegates needs metrics, and why a metric that moves before the outcome is more useful than one that reports it afterwards.

Why does cash come first every week?

In the Founder Blueprint, cash holds the first position on the scorecard and the position cannot be removed. An accountant or a banker reads cash first because a company can report a profit and still be unable to pay its bills when they fall due.

Profit and cash follow different timing. A company can recognize revenue while it waits for a customer to pay, and payroll can fall due before that payment arrives. Inventory can absorb money well before a sale produces cash, and supplier payment dates can bunch outflows into one difficult week.

Tax payments and debt service make further demands on the bank balance. A loan principal repayment consumes cash without appearing on the profit and loss statement the way wages do. A profitable month therefore gives an incomplete picture of the company's ability to meet the payments coming up.

Growth can add pressure. More work often means spending before customers settle their invoices, and one large customer paying late can leave a growing, profitable company short of the cash it needs to keep operating.

Reviewing cash first makes upcoming payment dates part of the weekly discussion. An early warning in the forecast may leave time to collect overdue invoices or reschedule discretionary spending. Waiting until a payment cannot be made leaves far fewer choices.

How do we calculate the weekly cash block?

The cash block reads three things: cash today, the change on last week, and weeks of runway. It counts as one row on the scorecard. Use the same weekly cutoff every time so the comparison holds.

Define which entities and bank accounts cash today covers. At the cutoff, start from those bank balances, deduct payments already issued that have not yet cleared, and leave out restricted funds and receipts that are not yet available to use. Show any undrawn borrowing facility separately, so available credit is never mistaken for cash.

The weekly change is this week's cash position minus last week's, measured the same way. A positive result means cash went up. Ask the owner to explain any material movement, especially borrowing or a one-off receipt that could make the operating position look stronger than it is.

For a business consuming cash, calculate runway by dividing available cash by average weekly net cash burn. Net cash burn is everything the company paid out over a chosen period, including capital spending, tax and loan repayments, minus everything it received, leaving out new borrowing and owner injections so they cannot disguise the underlying position. Divide that period's net outflow by its number of weeks to get the weekly average.

Write down the period and the exclusions you use. If recent weeks contain unusual transactions, note their effect on the average, so the team can see why runway moved.

Runway calculated this way is an estimate. As illustrative arithmetic, $120,000 of available cash and an average net burn of $10,000 a week give twelve weeks of runway, yet a $50,000 tax payment due in three weeks can take the balance far lower than the average implies. Check the estimate against a cash forecast that shows expected receipts and payments week by week.

When net cash burn is zero or negative, runway has no useful reading. Mark it as not applicable and read the lowest cash balance the forecast expects over the coming weeks, and the week it is expected. That forecast minimum is worth reading for a company burning cash too.

Runway is a calculation method, and there is no universal target for it. The leadership team sets its own cash floor, and any minimum runway it wants, from the obligations and uncertainty it faces. Write an explicit off-track rule for the block, including what happens when the forecast breaches the floor.

How do we choose the metrics for each function?

Start with the company's critical functions. For a services business these might include finance, sales, delivery, customer retention and hiring. Use the functions the company depends on today, and give each function one accountable owner, even when one person holds several functions.

Ask each owner what weekly figure would tell the leadership team whether their function is working. The right metric is one that would make the team investigate a problem or make a decision. Delivery might track commitments completed by their agreed dates. Hiring might track qualified candidates reaching a set interview stage for approved vacancies.

Each critical function should have at least one metric that lets the leadership team judge its performance without the founder inspecting the work. Start with one per function and add a second only where a material risk would otherwise stay invisible. In the Blueprint we keep the total between five and twelve, and a company's complexity can argue for a different count.

Revenue reports what has already happened. Put it on the scorecard when a reliable weekly figure supports a decision, give it an owner and a goal, and add a metric that moves before revenue does.

Test the source while you build. Ask the proposed owner to pull the figure during the first working session. A metric that takes days of manual reconstruction will not survive a weekly routine, and if it cannot be sourced weekly, it stays off this scorecard.

How do we write a target and an on-track line?

For every metric, record its definition, its owner, its weekly source and its numeric target. Add the reporting period and the rule that decides whether it is on track. Someone opening the sheet next week should be able to reproduce the result without asking what was meant.

A target needs a direction. For delivery commitments completed on time, on track might mean meeting or exceeding an agreed percentage. For overdue work, it might mean staying at or below an agreed count. These examples show the form of the rule, and the targets come from your own commitments and capacity.

Define what goes into the calculation. A worked definition, for illustration: the delivery completion rate is the commitments due in the reporting week that were completed by their agreed dates, divided by all commitments due that week. A commitment counts as complete when its agreed acceptance criteria are met, a customer-approved date change counts only if it was recorded before the original date, and a week with nothing due reads not applicable. Changing a definition after seeing a miss makes the history unreliable.

Set each target from the business plan or from an operating requirement the leadership team can explain. Where there is little history, use a provisional target and record the assumption behind it. Keep the definition stable long enough to learn from repeated readings.

Every valid reading gets one of two statuses: on track or off track. Context belongs in the discussion later in the meeting, and a near miss still goes to the issues list, where the team decides whether it needs action. A figure that is missing or unreliable is marked unavailable, with a date for fixing its source.

What could a services company's weekly scorecard contain?

The scorecard below is an illustration for a founder-led services company. It is a starting point for discussion, with no benchmark implied, and the owner roles are examples. A smaller company may give several rows to one person, provided each row has one accountable owner.

Before using any row, add the company's own numeric target and weekly source. A metric that suits one services company may be of little use to another. The hiring row, for example, belongs on the scorecard while filling approved vacancies is critical, and should be reconsidered when that changes.

Check that each row answers a different operating question. Overdue receivables can sit alongside cash when the reading helps the team assign collection actions.

What happens when a weekly metric is off track?

In the Blueprint the scorecard read takes about five minutes at the start of the weekly leadership meeting, and owners update their figures beforehand. Start with cash, then read each metric against its goal and state its status.

Every off-track metric moves to the issues list for later in the meeting. Record enough to identify the concern: an overdue receivables miss, for example, goes on the list with the actual balance and the target. Explanations wait until the team reaches that issue. Cash is the exception: if the cash block shows a payment the company cannot meet, the cash owner raises it with the founder the day it is found.

In the issues discussion, decide which causes need investigation and which actions the team can authorize. Give each agreed action one owner and a due date. Where several misses share a cause, discuss the cause once so the team does not create duplicate assignments.

A repeated miss calls for a review of the last response: check whether the agreed action was carried out and whether it changed the result. When the same explanation comes back week after week, the team should review the staffing and the process responsible for the result.

When should we cut or add a metric?

Review the scorecard each quarter. Check whether each metric still describes a critical function, whether its readings have informed decisions, and whether its source is still dependable. The quarterly review is the normal point to add or cut metrics, and a metric can change sooner when the responsibility it measures changes.

Cut a metric when it duplicates another reading, covers work that no longer matters, or gives the team nothing to act on. A metric that is consistently on track can stay if it monitors a continuing obligation.

Add a metric when an important problem has appeared more than once without warning from the existing scorecard. Identify the function responsible and find a weekly metric that would have shown the problem earlier. Check whether it can replace an existing row before the sheet grows. Cash stays first through every revision.

Why do weekly scorecards stop being useful?

Too many metrics make a fast read impossible. Rows tend to accumulate because someone once asked for them and nobody revisited the request. Use the quarterly review to bring the scorecard back to five to twelve metrics with a continuing purpose.

Metrics without an owner arrive late and produce concerns nobody picks up. Give one person responsibility for bringing a reliable reading and explaining a miss. Other people can supply data, and the owner stays accountable for the row.

A month-end figure repeated in the weekly columns adds no new information from one week to the next. A metric that updates only after month-end belongs in the monthly reporting process, and the scorecard needs a metric that is sourced weekly.

Recurring arguments about definitions make comparisons unreliable. Write down the calculation and the reporting cutoff. If a definition needs correcting, document the change so the team knows which periods can no longer be compared directly.

Solving problems during the read makes every remaining metric wait, so put the issue on the list and keep reading. A stale cash figure is a separate failure: the leadership team may be discussing money that has already been spent. Require a current cash reading before the meeting starts.

Who should prepare the cash figures?

The cash block needs one owner who produces it on time and can explain it. In a smaller company that is often the founder or a bookkeeper working to the founder. As the company grows, the controller or finance lead takes it on. If nobody inside the company can produce reliable weekly cash figures and a forecast, that gap is the first finance problem to solve, and our guide on when a founder needs a fractional CFO or COO covers whether a controller or a part-time executive fills it.

Where should we start this week?

Draft the first version in one working session with the leadership team. List the company's critical functions and give each one an owner. Ask each owner to propose a weekly metric and show where it will come from. Put the cash block first.

Set a numeric goal and write the on-track rule beside each metric. Agree the reporting cutoff and who prepares cash. Keep the first version small enough to read in a few minutes, and use it at next week's leadership meeting.

Move the misses to the issues list and work through them later in that meeting, and put the first quarterly review in the calendar now. This is the weekly scorecard we install through the Founder Blueprint, with each company choosing the metrics that fit its own operating responsibilities.

Frequently asked

Next step

If the harder question is whether the company can run the scorecard without you, the Leadership Scorecard is a ten-minute self-assessment across twelve leadership dimensions and the six drivers of founder-led growth, and it shows where the company still depends on you.