On Friday last week I gave our marketing system a simple instruction: use the whole monthly allowance on one of the tools we pay for, every month, and stop leaving it unused. It is the allowance behind the imagery and the short videos you see on our pages, and for most of September a good part of it had been sitting idle.
The rule that came out of that instruction was sensible. Take what is left, divide it by the days left in the month, spend at least most of it each day, and on the last day of the month spend whatever remains. Clean, fair, easy to check.
It was also pacing to the wrong date.
The month was not the month
On Monday, while planning October, I read the tool's own account history rather than the rule. The allowance does not renew on the first of the month. It renews on its own cycle, on a date set by when the subscription started, and the history showed two renewals, one early in August and one early in September, each in the evening. Anything unused at that moment is gone.
So "spend it all by the 30th" was solving the wrong problem. Spending out on 30 September would not have saved anything from being wasted, because nothing is wasted at the end of September. It would have left the first days of October, before the renewal, with nothing at all, on days when we have committed to three videos.
Nobody made a mistake with the numbers. The division was right. The date it divided by was an assumption: that a monthly allowance follows the calendar month. It was never read from anywhere. It was simply what "monthly" sounds like.
What changed
The rule now paces to the renewal, not to the month end. Every day the system reads the actual balance and divides it by the days left until the renewal, so the last days before it are covered and nothing is left to lapse. I approved the change the same day.
I also wrote down the part I cannot yet prove. The renewal date is inferred from two data points, not confirmed by the supplier. The first run after the expected renewal checks the balance and confirms it, or tells me it was wrong. A date worked out from two past events is a good guess, and it should be treated like one until the third arrives.
Every business has a month like this
This is not really about marketing. Every business runs on dates that sound like the calendar and are not:
- A supplier who bills on the 25th, while the business reconciles on the last day of the month.
- Software that renews on the date someone first signed up, which nobody remembers.
- A contract with a notice period counted from its start date, not from the beginning of the year.
- A cycle that resets on its own schedule, while the spreadsheet tracking it assumes the first of the month.
The failure is always the same shape. The real date lives in one place, the supplier's account or the contract, and a copy of it, or a guess at it, lives in a plan somewhere else. The plan is tidy, so nobody goes back to the source.
The fix is also the same. The date belongs on the record where it starts, and everything that depends on it reads it from there rather than keeping its own version. That is most of what a Business Operating System is for: one source of truth, so a renewal, a billing date or a notice period is looked up, not remembered.
I found this one because I happened to read the history while planning a month. I would rather the system had told me.
Frequently Asked Questions
Why does it matter which date a budget paces to?
Because an allowance that lapses on its own renewal date is only wasted at that moment. Pacing to the calendar month can spend it too early and leave days before the renewal with nothing.
How do you find the real renewal date of a subscription?
Read the supplier's own billing or account history, not the plan. Renewals usually follow the date the subscription started. Two past renewals give a good estimate; the next one confirms it.
What does a Business Operating System change here?
It keeps dates like renewals, billing cycles and notice periods on the record where they originate, and everything that depends on them reads them from there, instead of each plan keeping its own copy.