Cost overruns: log one of four moves and set a revisit date

In the monthly numbers review, a line that runs over plan is a decision to log. Use one of four moves: reprice, hold more cash, switch suppliers, or postpone investment; then set a revisit date for the next review. The log keeps the overrun from becoming a mood and gives the team an operating decision. The entry is short enough to complete before the meeting moves to the next line item.

Cost pressure is common enough to plan for. In a May 2026 Mercury survey of 1,500 U.S. founders and startup operators, 75 percent said costs were higher than planned, up from 66 percent in 2025. None of the respondents said costs were far below the planned amount.

Inflation is part of the picture. In the same survey, 51 percent said inflation hurt their business in 2026, compared with 36 percent in 2025. Mercury's internal data showed companies incorporated in the previous six years kept a cash balance 27 percent larger in 2026 than in 2024.

The overrun is a decision, not a surprise

Most small teams already know the four moves. The problem is that they happen in a chat thread, in a hallway, or in a founder's head. A decision log gives the move a date, an owner, and a review point. It also keeps the monthly numbers meeting from becoming a blame session. The log is a working document, not a performance review.

Eight percent said they altered the business in response to economic pressure during the previous year, often by changing prices, cash buffers, suppliers, or investment timing. The share is small, but the changes are the same ones a first dozen-person team can make without a board memo.

The four moves are the ones that survive review

The template is short enough to fill in during the meeting. The four moves are reprice, hold more cash, switch suppliers, and postpone investment. They make the next review possible.

The checklist below gives the entry a shape that holds through the next meeting. It names the overrun, forces one move, sets the revisit date, and gives the review a close or carry state.

• Name the overrun. Put the line item, the amount over plan, and the owner in one sentence. If you cannot say it in one sentence, the line is not ready for a decision.
• Choose one move. Pick reprice, hold more cash, switch suppliers, or postpone investment. Do not log a mix unless one move is the main one.
• Set the revisit date. Put the next monthly numbers review on the entry. If the move is pricing, set a date to check churn, win rate, and margin. If it is cash, set a date to check runway. If it is suppliers, set a date to check quality and delivery. If it is postponed investment, set a date to check the business case.
• Close or carry. At the review, mark the entry closed, reopened, or carried. A carried entry gets a new revisit date and a one-line reason.

Pricing needs the most care. Among founders who shifted costs to customers, 68 percent raised prices by 5 to 10 percent. A small increase is easier to defend in a monthly review because the log can show what happened after the change. Cash entries state the extra buffer and the check date. Supplier entries name the old supplier, the new one, the expected saving, and the risk. Postponed-investment entries name the investment, amount, delay, and reason, and say plainly if the delay becomes a cancellation.

Staff cuts are the harsher edge of cost pressure. Twelve percent said they cut staff or reduced headcount because of higher operating costs sometime in the previous year. A decision log does not make that move easier; it makes the team say why the four standard moves were not enough.

The log is the meeting's first agenda item

Put the decision log before the income statement, before the burn chart, and before the questions. The numbers explain what happened. The log explains what the team chose to do about it. That order keeps the meeting from drifting into general anxiety.

At the next monthly numbers review, the team marks each entry closed, reopened, or carried. Closed entries show the move worked or the overrun is gone; reopened entries show the move failed and the team chooses again; carried entries stay live and need another check. The revisit date is the field that tells the team when to check the result.