The Favor You Don't Charge For Is the Most Expensive One

Last Tuesday, around 10:30pm, I was scrolling through our project group chat and saw a coworker's error screenshot: a script had thrown a KeyError halfway through, and the deliverable was due the next day. I skimmed the logs, found that a field was missing a nesting level in the API response, fixed three lines of the value-extraction logic, sent it back with a casual "no big deal." They said thanks, and that was that.

Two weeks later it hit me: ever since, whenever a script broke at the last minute and nobody had officially claimed it, I was the first person people thought of. Nobody assigned it to me. I never got paid for it. But it had quietly become a permanent part of my workload.

That's the part of a "zero-cost" favor everyone overlooks — it looks free, but it was never actually costless. The cost just never runs through the money ledger. It runs through a different one, the one nobody puts into words.

When you actually pay for something, the price gets negotiated, and the boundaries come with it: this much money buys this much work, anything beyond that can be refused, both sides know where they stand. But the moment it's "no big deal," "don't worry about it," "happy to help," no boundary ever gets drawn. You think you did a one-time favor. What lands in the other person's ledger is: this person is reliable, this person can handle it, I'll come back next time. Once that entry gets written into their default expectations, it's hard to erase.

The next time something similar comes up, they won't even feel like they're imposing on you — because in their ledger, this was already your job. You didn't charge anything, so your own ledger has nothing written on it. But theirs has quietly gained another line. That mismatch between the two ledgers is where the real cost of a "zero-cost" favor comes from.

The place ordinary tech workers get burned most often is exactly this: casually fixing a colleague's code, casually patching up a doc template. Each one looks trivial on its own. Do it ten times, and it turns into work nobody ever formally assigned you — work you're now just expected to do.

This hidden bill doesn't come due every time. Most of the time, "no big deal" really is no big deal, and the books stay even. It actually comes due when you're not at your best, or when the stakes of that particular favor happen to be higher: the ease you've built up over time turns into pressure — "isn't this the kind of thing you always handle?" — and one missed expectation can wipe out ten favors' worth of goodwill, leaving behind only "this time you dropped the ball."

By contrast, arrangements with a clear price tag are actually safer: once you've been paid, the responsibility ends there. Falling short is a competence problem, not a character problem. In the fuzzy territory of zero-cost favors, one slip gets read as an attitude problem instead.

Now, whenever a "no big deal" request comes my way, I ask myself one more question: am I willing to let this become the default expectation? If not, I need to say so on the spot — not wait until the tab has run up and then try to settle it.