The 'can you just' tax
Five-minute requests are never five minutes. Why untracked small asks quietly eat retainers, and how to get them raised, dated and counted.
· 4 min read · Agency operations
The message lands at 9:47 on a Tuesday, in a WhatsApp thread that was set up for emergencies. Can you just swap the hero image on the homepage before the board sees it? Two minutes, honestly.
It is a reasonable request from a reasonable client, and that is what makes it dangerous. You will say yes. You should probably say yes. The question is what happens to the yes afterwards, and right now the answer is nothing. It vanishes.
Five minutes is never five minutes
The swap itself might genuinely take five minutes. The request does not. Someone has to see the message, stop what they were doing, work out which image is meant, find the approved version among four files called hero-final, make the change, check it has not broken the layout on mobile, and reply. The designer who did all that then returns to the campaign work they were actually billing for and spends a while remembering where they were. Call it twenty-five minutes of real cost, recorded nowhere.
Then the multiplication starts. A client who sends one WhatsApp ask and gets an instant yes has learned something true: this channel works. The next ask arrives sooner, and the one after that arrives on a Sunday. None of it is malicious. Each request is small and sincere, and smallness is exactly why nobody writes it down. Unwritten is why it compounds.
The retainer leak
Run the arithmetic on one retainer. Six little asks a week, at a true cost of twenty-odd minutes each, is roughly ten hours a month. Nobody scoped those hours and nobody can see them, so the planned work starts running late for no reason anyone can point at. From the inside it feels like the month evaporating. From the client's side it looks like slippage.
The worst of it arrives at review time. The client remembers a couple of quick favours. You remember a steady stream of them, but cannot produce the list, because it lives in scrollback across two inboxes and three chat apps. Untracked work does not read as generosity. It reads as nothing at all, and a retainer that quietly over-delivers can still be cancelled for under-delivering.
The invoice nobody can send
Which brings us to the awkward bit: money. Everyone knows you cannot invoice for line items that exist only in chat history, so nobody tries. Raising a small request in the moment feels petty, since it was only two minutes. Raising twenty of them in a lump at month end feels retroactive, like presenting a tip jar after the meal. So the agency eats the cost and feels vaguely resentful, while the client, in perfect good faith, has no idea any of this is happening.
Neither side is behaving badly. Both sides lack a record. You cannot bill against a WhatsApp message, and you should not have to.
Raised, dated, counted
The fix is not learning to say no. Saying no to small requests is how retainers die for a different reason. A "can you just" is a legitimate request wearing casual clothes, and it needs what every request needs: a visible place to land, a date the client can see, and a line in the month's account of work.
The client still gets their image swapped, usually just as fast. What changes is that the request now exists. It sits in a shared list carrying a landing date the client can check without asking, and at review time it is one row among forty rather than a vague memory. The conversation about scope stops being about feelings and starts being about a list.
Getting clients there is easier than it looks, provided you never ask them to change first.
- Accept the ask in whatever channel it arrives. Policing the channel is friction, and friction sends clients back to WhatsApp for good.
- Raise it yourself, on the spot. Forward the message to a workspace email address that turns it into a ticket, or paste it in and let the AI draft the request while you finish your coffee. Thirty seconds, no ceremony.
- Reply where they asked, with a link. "Done, and I have raised it here so it is on the list. It lands Thursday." You answered in their channel; the record lives in yours.
- Let the dates do the persuading. Clients migrate to whichever channel reliably answers the question they actually care about, which is when do I get it. A chat thread cannot answer that. A raised request with a visible date can.
Within a month or two the raising starts to happen at their end, because raised requests are the ones that visibly land. The chat asks that remain are genuine emergencies, which is what the thread was for. The same shift eventually shrinks the Friday reporting ritual too; that one is covered in the status update email is a symptom, and the broader inbox version in stop running client work from your inbox.
Where HoopoeHQ fits
HoopoeHQ exists to make step two effortless: email a workspace address and the message becomes a ticket, and every ticket carries a landing date your client can see, inside a workspace that shows each client only their own work. The "can you just" keeps its charm and loses its invisibility. The 14-day trial needs no card, if you want to count next month properly.