The Price In Your Head Isn't The Price In Their Budget
Why freelance tech writers often undercharge because they mistake "personal sticker shock" for business reality
One of the strangest moments in freelancing happens when we stare at our own proposal like it’s a ransom note.
We type in the number. We blink at it. Then we immediately begin negotiating against ourselves like a hostage trying to secure release before the SWAT team arrives.
👉🏾 “Maybe that’s too much.”
👉🏾 “Maybe we should lower it.”
👉🏾 “Maybe they’ll think we’re ridiculous.”
Meanwhile, somewhere inside a corporate office park with beige walls, flickering fluorescent lights, and an emotional support Keurig machine, our potential client is trying to figure out how to stop their documentation ecosystem from behaving like a haunted junk drawer.
But there we are, sweating over whether charging professional rates makes us “greedy” or will prevent us from getting the contract. Freelancing is fascinating that way. Half the job is technical skill. The other half is accidentally discovering we have unresolved feelings about money.
And yes — those feelings absolutely can make us charge less than we’re worth.
Our Brain Thinks We’re Shopping At Target
One of the biggest pricing mistakes we make is evaluating our own services as if we were personally standing in line deciding whether to buy scented candles and frozen pizza.
We see our fee through consumer eyes. 👀 The client usually sees it through business eyes. 📊
Those are not remotely the same thing.
👉🏾 Consumers ask: “Can I afford this?”
👉🏾 Businesses ask: “What happens if we don’t fix this?”
That distinction matters more than we realize.
If we’re proposing a $15,000 content strategy engagement, we may hear:
“Fifteen thousand dollars?! That’s insane.”
The client may hear:
“Oh thank God someone might finally fix this mess before the support team stages a mutiny.”
Those are two completely different emotional experiences attached to the same number. And we constantly confuse them.
Tech Writers Are Especially Vulnerable To This
Tech writers tend to be practical people. Yes, I know that’s a stereotype, but not a bad one. We’re usually helpful, process-oriented people.
We’re not generally wandering around in fur coats throwing champagne 🥂 glasses at interns while demanding gold-plated API documentation portals.
Most of us came from environments where we were expected to quietly solve impossible problems while pretending everything was “fine.” So when we become freelancers, we often carry employee thinking into business ownership.
We price based on how long the work takes, how hard it feels, or what we personally would spend. Instead, we should be pricing against the cost of confusion, operational inefficiency, customer frustration, support burden, compliance risk, or delayed product adoption.
Know this: Companies are rarely paying for us to make “documentation.” They’re paying us to help them build capabilities that allow them to reduce chaos. Sometimes enormous chaos.
Keep reading with a 7-day free trial
Subscribe to The Content Wrangler to keep reading this post and get 7 days of free access to the full post archives.


