This is the last part of the series. We have opened up the hosting line items, set the point at which to migrate, drawn the line between free and paid, and worked through images, mail, backups and upgrades. What remains is keeping those decisions from going stale.
Fixed costs cause trouble in a particular way. Not because one item suddenly gets expensive, but because something you no longer use keeps leaving the account and nobody is looking at it. Thirty minutes every six months catches all of it.
Start from the statement, not from a list
That order is the heart of this part. Begin with “let me list the tools we use” and the forgotten ones never make the list. Begin with the statement from your payment method and nothing escapes — the money leaves precisely on schedule whether or not you remember it.
There may be several payment methods to check: the business card, a personal card, an overseas payment account, direct debits. Business tools charged to a personal card are the ones most reliably forgotten, and the ones that cause trouble later when ownership has to be sorted out.
One question per line item
For each entry, ask one thing: “if I cancelled this today, what would stop?” Anything you cannot answer immediately is a candidate for cancellation. And where you can answer, ask whether the thing that stops still matters as much as it did.
What surfaces most often here is overlapping functionality: image optimisation running in both a plugin and the CDN, or backups running as both a hosting option and a plugin. Overlap does not merely cost twice — it obscures which one is actually doing the work, and that confusion is expensive during an incident.
Leave one page behind for next time
Record the result as a single table: name, purpose, monthly cost, renewal date, payment method, owning account, and what breaks if it goes. With that table in hand, the next review takes ten minutes rather than thirty.
The renewal column earns its keep. Annual contracts only give you a choice just before they roll over, and if you do not know the date you find out after the fact. While you build the table, put each renewal in the calendar with a reminder two weeks ahead.
Do not skip the owning account column either. Simply writing down whose account holds the domain, the hosting, the repository and the payments prevents the most common problem that arises when people change or a working relationship ends.
Closing the series
Running a site on a small fixed budget is not a skill of cutting things — it is a skill of deciding where the money goes. Recognise where free is genuinely enough, spend only where money actually reduces risk, and refresh that judgement twice a year, and a small budget still buys a site that does not wobble.
WordPress accommodates that kind of judgement very well. What causes problems is never the tool — it is time passing without a decision being made.
The work that is genuinely hard to do alone — version upgrades, performance work, security review, server configuration — is handled as one job by our optimization program, and the order in which we measure and fix is published on the process page. If handing over ongoing operations is the right call, an InfraGuard pass is where that lives.