The question at every deadline is always the same: have I renewed? It is the right question if you want to keep a site up, and the wrong one if you want to know how the agency is doing.
Because the renewal, nearly always, is paid by you. The provider charges on the deadline date, using the card you left on file; the client pays when the invoice arrives, or after a chaser, or two months later. In between sits a sum of your own money, standing still, that nobody has ever given a name to.
This is not a bad debt problem — that is a different matter, and a rarer one. It is that part of your cash is permanently parked inside your clients’ services, and it shows up nowhere until you go looking for it.
Two dates that never match
Every renewal has two dates. There is the one when the money goes out: the real deadline, set by the provider, not negotiable, charged automatically if you left the card on file. And there is the one when the money comes back: the day the client pays, which depends on your invoice, on their timing and on their habits.
Between the two sits a gap that in our experience runs from a few weeks to several months, and it stretches longest exactly where the amounts are highest: on hosting and maintenance, not on the twelve-euro domain. On a single item it is not worth discussing. Across the whole client base, multiplied by every active service, it becomes a number worth knowing.
The awkward part is that you do not set this gap. The provider’s calendar sets one end of it and the client’s habits set the other, and you sit in the middle acting as a bank without ever having decided to.
The credit you do not call credit
If a client owes you three thousand euros for a project, you carry that figure in your head. If ten clients each owe you a hosting renewal, that total is nowhere in your head — and yet it is your money, already gone out.
The difference is purely psychological: you track the big job, you do not track the renewals, because they are small, repetitive and apparently automatic. In cash terms they are the same thing. Renewals are worse, in fact, because they go out on their own even when nobody authorised them that day.
There is a less obvious consequence too. Until you measure it, you cannot decide anything: you do not know whether it is worth asking some clients to pay in advance, you do not know which items are soaking up the most cash, and you do not know whether the client who always pays late is costing you more than they bring in. The number is not there to pick a fight with anyone. It is there so you know where you stand.
Why does it go unnoticed?
Deadlines are scattered across the whole year. Each single charge is small enough to slip past among the other transactions without being noticed, and it lands at a different moment from all the others. There is never a day when you see the total.
The way most deadline trackers are built does not help either. A sheet with client, service and date answers the question “when does it expire” perfectly well, and answers the question “how much have I fronted, and for how long” not at all. Answering that takes three pieces of information almost nobody records: how much went out, when it went out, and whether it came back.
And then there is the fact that most clients do pay, sooner or later. The money almost always returns, so the problem never blows up — it just leaves a chronic cash squeeze that gets blamed on something else.
Three questions before you pay upfront
Fronting the money is not wrong. With many clients it is the right call: it avoids arguments over small amounts, keeps the service running and saves you time. The problem starts when it becomes the default for everyone, without anyone ever choosing it.
There are three useful questions to ask before letting a charge go through. How large is the amount? Below a certain figure, paying upfront costs less than chasing the request. How did they pay the last three times? That is the only indicator that really matters, and you already have it. What happens if I do not renew? An expired domain takes down the site and the email together; a plugin licence, nearly always, takes down nothing for weeks.
Those three answers produce a split on their own: the items you front without thinking, the ones you confirm first, and the ones where the payment lands before the renewal. You do not need one rule for everyone. You need the rule to exist.
How do you front less without damaging the relationship?
The simplest way is also the least confrontational: move the conversation to before the deadline instead of after it. A notice sent thirty or forty days ahead, with the amount and the date written out, turns the renewal from a done deal into a shared decision — and anyone who wants to pay early can.
The second step is grouping. If a client has four services falling due at four different times, you have four amounts fronted, four invoices and four chasers. Aligning the deadlines on a single date, even at the cost of a pro-rata charge, cuts the work and shortens the window in which your money is out.
The third is saying it plainly. “I pay the renewal on the fifteenth and I send you the invoice the same day” is a sentence nobody argues with, and almost nobody says. With clients on larger amounts it is worth putting in the maintenance contract rather than in an email.
And when the money never comes back
In the vast majority of cases the money comes back and that is the end of it. Every so often it does not, and at that point the question changes: it is no longer how much is out, it is what do I do now.
The useful thing to know in advance is that the levers you hold are not all worth the same. Suspending maintenance takes nothing down and can be done without harm. Not renewing hosting puts the site offline but leaves the email running. Letting a domain lapse takes everything down at once and creates a problem you then have to fix yourself, with costs and delays that become yours even though the fault was not — we have written about that in what forgetting a domain renewal really costs.
So the order is the opposite of the instinctive one: start with what does the least damage and is easiest to switch back on, not with what makes the most noise. And start after you have given notice, not before.
What mistakes get made when fronting renewals?
- Treating money fronted as a bad debt problem. They are two different things: here the money comes back, and the cost is the time you spend without it.
- Recording what you invoice and not what you pay. With only one of the two figures you know neither the margin nor the exposure.
- Leaving the card on file with every provider without having decided which items should be charged automatically.
- Telling the client after you have renewed. By then the conversation is about an invoice, not about a choice.
- Applying the same rule to the client who pays on sight and the one who pays at ninety days. Those are two different risks and they deserve two different treatments.
Where do you start cutting what you front?
- Take the last twelve months of renewals and note, for each one, how much went out and on what date.
- Next to it, put the date the client paid. If you do not have it, that is a finding in itself: it means you never closed that item.
- Work out the difference in days and look at the average per client, not the overall one. That is where the two or three cases that really weigh show up.
- Split the clients into three groups — always front, ask first, payment received before renewal — and write it down somewhere other than your memory.
- Move the notices to before the deadline. If you are still keeping everything on a sheet, the comparison between a spreadsheet and a proper deadline tracker explains where it breaks; the wider setup is covered in how to organise a web agency’s client deadline tracker.
How do we avoid fronting money ourselves?
This is the sum that convinced us to stop using a spreadsheet. We knew when everything fell due; we did not know how much of our own money was sitting inside our clients’ services, and the first time we worked it out by hand the number looked wrong.
In Dotify — the deadline tracker we built for ourselves at EnneStudio, and it is ours — every deadline holds both the amount charged to the client and the cost paid to the provider, and payments received are recorded against the individual item. That is what the statuses are for: while a deadline is awaiting payment it counts towards your exposure, and once it is marked as paid it drops out. The how-much-is-out figure is a by-product, not a calculation to run at year end.
How amounts, payments received and costs work is covered in the documentation on deadline management; the plans start with a free forever version, five clients with three deadlines each — enough to see whether the numbers add up for you, not to move your whole client base in.
