The Hidden Cost of ‘Can You Just…’ Requests (And How to Track Them)

“Can you just change the phone number in the footer?”

Sure. Takes two minutes. Not worth raising an invoice for. You do it, you move on.

“Can you just swap out that hero image? I’ll send you the file.”

Fine. Five minutes. Still not worth the hassle of a formal request.

“Can you just add a new page for our summer offer? Nothing fancy, just copy the layout from the services page.”

Okay, now we’re talking about 30-45 minutes. But they said “just,” so it must be small, right?

This is the “can you just” trap. And if you’re a solo developer managing ongoing client work, you’re probably losing thousands to it every year without realising.

The maths nobody wants to do

Let’s be conservative.

Say you get three “can you just” requests a week across your client base. They average 20 minutes each. That’s an hour a week of unbilled work.

Over a year, that’s 50 hours.

At £65 an hour, that’s £3,250 a year. Gone. Not invoiced. Not tracked. Just absorbed into the cost of being helpful.

And that’s the conservative number. Most developers I’ve spoken to reckon it’s closer to double that once they actually start paying attention.

The individual requests feel too small to bill for. But the total is anything but small.

Why this keeps happening

The root cause isn’t that you’re too generous (though you might be). It’s that there’s no system forcing these requests to be visible.

Think about how a typical “can you just” arrives. It’s a casual email, a WhatsApp message, or a throwaway line at the end of a Zoom call. It’s informal by design. The client isn’t trying to sneak work past you. They genuinely think it’s a two-minute job and they’re asking nicely.

But because the request arrives informally, it never enters any kind of tracking system. It goes straight from their mouth (or their inbox) to your to-do list, which might be a mental note, a sticky note, or a starred email.

There’s no estimate step. No approval step. No record of what was asked or when it was done. It just… happens.

And because there’s no record, you can’t bill for it. Even if you wanted to, you’d have to go back through your emails and WhatsApp messages to piece together what you did, when, and for whom. Nobody does that. So the work goes unbilled.

The trust problem

Here’s the uncomfortable bit. If you start billing for every small request, some clients will feel nickel-and-dimed. “You’re charging me to change a phone number?”

This is a valid concern. You don’t want to damage the relationship over a two-minute task.

But the solution isn’t to absorb all the small stuff for free. The solution is to make everything visible and let the numbers speak for themselves.

When every request goes through a proper channel, the client can see the full picture of what they’ve asked for that month. Suddenly it’s not “you’re charging me to change a phone number.” It’s “oh, I’ve submitted twelve requests this month and seven of them were outside of what we agreed.”

Visibility changes the conversation entirely. It stops being about individual tasks being too small to bill, and starts being about the total volume of work being real and worth paying for.

How to fix it without being awkward

Make every request go through the same channel

This is the most important change. If a client emails you a “can you just,” reply with something like: “Happy to do that. Can you pop it into your portal so I’ve got it tracked? Takes 30 seconds.”

You’re not saying no. You’re not being difficult. You’re just routing the request into a system where it becomes visible and trackable.

After a few weeks of this, most clients start submitting requests through the proper channel by default. Not because you forced them, but because it’s easy and they can see the benefit (they get status updates, for one thing).

Attach an estimate to everything

Even if the estimate is “£0 - included in your retainer” or “15 minutes, no charge,” the act of estimating makes the work visible. The client sees it. You see it. And over time, you both have a clear picture of how much work is actually being done.

For requests that are genuinely billable, the estimate creates a natural approval step. The client sees “£50 - 45 minutes” and either approves it or decides it’s not worth it right now. Either way, you’ve avoided doing the work and then having an awkward conversation about the invoice.

Review monthly

At the end of each month, look at the total number of requests per client and how many were “can you just” tasks. If a client is consistently sending ten or fifteen small requests a month, that’s a conversation worth having. Not an angry one. A productive one.

“I’ve noticed we’re averaging about twelve requests a month, which is great because it means the site is getting attention. Some of these are covered by your retainer, but a few are outside of scope. Want me to flag those upfront so there are no surprises on the invoice?”

That’s a professional conversation. It builds trust. And it only works because you have the data to back it up.

The bigger picture

The “can you just” problem is really a visibility problem. When requests arrive informally and get handled informally, nobody has a clear picture of how much work is actually being done.

Once you start tracking everything, two things happen.

First, you stop losing money to unbilled work. Not because you’ve become ruthless about billing, but because you’ve made it easy to see what’s been done and what it’s worth.

Second, your clients start to appreciate the work more. When they can see a list of fifteen things you’ve done for them this month, they understand the value. When it’s all invisible, done behind the scenes through email threads, they forget. And forgetting leads to “why am I paying for this retainer?” conversations that nobody enjoys.

Track everything. Estimate everything. Bill fairly. That’s the system.

TaskClarity makes every client request visible. Clients submit through their portal, you add an estimate, they approve with one click. Nothing gets lost and nothing goes unbilled. Built for solo developers who are tired of absorbing the cost of “can you just.”