The Free Work Trap: 7 Things Freelancers Give Away Without Noticing

You already know not to do free spec work. Everyone knows. It's rule one in every freelancing guide ever written.

Here's what those guides miss: the free work that actually hurts you never arrives labeled as free work. It leaks out sideways. Discovery calls where you dispense the whole strategy. Proposals that read like consulting reports. "Quick questions" that show up eleven months after handoff. I tracked one month of my own time, and my honest estimate is that somewhere north of 15 hours went to work nobody paid for. Work that nobody, including me, ever decided to give away.

That last part is the actual problem. Not the giving. The not deciding.

Free Work You Choose vs. Free Work That Happens to You

Let me get one thing out of the way, because otherwise this post sounds like "never do anything for free," and I don't believe that.

I give away a lot on purpose. Free guides in almost every post. Detailed breakdowns of my pricing, my mistakes, my workflows. I wrote a whole piece about how sharing free guides is also a form of gatekeeping, and I stand by every free PDF on this site. That's marketing. I chose it, I budgeted for it, and it brings clients in the door.

Chosen free work builds a business. It compounds. A guide I wrote once gets read a thousand times.

Accidental free work does the opposite. It's invisible, it's one-to-one, and it compounds against you, because every time you absorb it quietly, you train the client that this is included. The difference between the two isn't the work. It's whether you decided.

So that's the test for everything below: did I choose this, or did it just happen to me?

Most of these won't feel like free work while they're happening. That's exactly why they work. Each one feels like being helpful, professional, easygoing. Add them up over a year and you've donated a full working month.

1. Consulting Disguised as a Sales Call

The discovery call where the prospect leaves with a plan. I've done this more times than I want to admit: 45 minutes in, I've diagnosed their SEO problem, named the three things to fix first, and explained why their current agency's approach isn't working. They thank me warmly. Then they take my diagnosis to a cheaper freelancer to execute it.

A discovery call should establish whether we fit and what the problem roughly is. The moment I'm explaining how to fix it, I've switched from selling to consulting. Nobody flipped a switch. I just kept talking.

2. The Proposal That Doubles as the Strategy

Same leak, in writing. A proposal that lists deliverables and a price is a proposal. A proposal that explains the keyword clusters you'd target, the site architecture you'd restructure, and the order you'd do it in is a strategy document with a price tag stapled to it. The client can reject the price and keep the strategy. Some do.

3. Post-Handoff "Quick Questions," Forever

The project ended in March. The email arrives in November: "Quick question, how do we update the banner again?" Five minutes, sure. But it's never one email, and it's never really five minutes once you've reloaded the whole project into your head. This one is so common I built my project handoff checklist partly to defend against it.

4. Debugging Things You Didn't Build

The client's newsletter tool breaks, or their domain settings, or a plugin someone else installed years ago. "You're our website guy, can you take a look?" And you look, because saying no feels petty over something small. Congratulations: you're now the unpaid IT department for systems you've never seen before. These are the worst hours of all, because you're debugging blind and you can't even bill for the learning curve.

5. Playing Help Desk for Tools You Didn't Sell

Cousin of leak four. The client buys some SaaS tool, can't configure it, and forwards you the support ticket they should be sending to the vendor. The vendor has a paid support team for exactly this. You are not it. But you answer faster than the vendor, so guess who gets asked.

6. Teaching, Unpaid

Training is a service. Agencies sell it as line items with day rates. Freelancers deliver it as "let me quickly show you how that works" screen shares that turn into 90-minute sessions, twice, because the second person on the client's team missed the first one. I like teaching. That's what makes this leak dangerous for me specifically: it doesn't feel like a leak, it feels like being good at my job.

7. Revision Round Four

The contract says two revision rounds. Round three arrives with "just a tiny thing." Round four arrives with "while we're at it." Each round is small enough that invoicing for it feels aggressive, so you eat it. The client isn't evil. They genuinely don't know that revisions are the deliverable. You never told them, because the earlier rounds were free too.

What This Actually Costs (My Rough Math)

I'm not going to pretend I have a precise ledger. I tracked one month, imperfectly, and stopped counting somewhere north of 15 hours of accidental free work. Some months are lighter. Some are worse, especially the ones right after a big handoff.

Call it 10 to 15 hours a month to be conservative. That's 120 to 180 hours a year. At any reasonable freelance rate, that's a five-figure hole in your revenue. Not from one dramatic non-paying client you'd remember and get angry about. From five-minute favors that never showed up on any invoice.

And that's just the direct cost. The sneakier cost is what those hours displace: the blog post you didn't write, the product you didn't ship, the evening you didn't take off. I've written before about the guilt freelancers feel when quoting clients, and I think it's the same muscle failing in both places. We're fine giving value. We panic when it's time to name its price.

Plugging the Leaks Without Becoming That Freelancer

Here's my fear, and maybe yours: turning into the freelancer who sends an invoice for a phone call. Nobody wants to work with that person. The good news is that plugging these leaks isn't about billing for every breath. It's about three habits.

Productize the audit. The consulting that leaks out of discovery calls and proposals is real work, so make it a real product. Mine is a paid audit: fixed price, fixed scope, a document the client keeps whether or not they hire me for the implementation. Discovery calls got shorter and easier the day the answer to "so what would you do?" became "that's exactly what the audit answers." Serious prospects buy it. The strategy shoppers don't, which tells you what they were shopping for.

Set a support window and say it out loud. Every project now ends with the same sentence: 30 days of included support for anything related to what I built, then a small monthly care plan or an hourly rate. Not buried in the contract. Said out loud at handoff. The November "quick question" still arrives, but now there's a slot for it, and answering "happy to help, that falls under the care plan" doesn't feel like a betrayal, because the rule existed before the question did.

Build the "happy to scope that" reflex. This is the one that fixed leaks four through seven for me. When the request is outside the project, the answer isn't "no" and it isn't silent absorption. It's "happy to take a look, let me scope it and send you a quick quote." One sentence. Warm, immediate, and it moves the decision back where it belongs: with the client, who now gets to decide if their quick question is worth money. Half the time the request quietly disappears, which tells you exactly how urgent it was. The same logic that made me stop replying to clients within 30 seconds applies here. Boundaries didn't cost me clients. They filtered my requests.

Choose Your Giveaways

I still do free work. Plenty of it. This post is free work. The difference is I picked it, I know why, and it reaches more than one person.

That's the whole trap, really. It's not that freelancers give too much away. It's that we let clients, timing, and our own discomfort decide what gets given, instead of deciding ourselves. Generosity is a strategy. Leakage is just poor accounting with good manners.

I haven't fully plugged all seven, if I'm honest. Leak six still gets me, because I like teaching too much to always stop myself. But I catch it now, which is more than I could say a year ago.

If you want a second pair of eyes on where your own projects are leaking, let's talk. Scoping things properly is, somewhat ironically, the thing I now do best.