Per-Word, Per-Hour, Per-Project: Converting Freelance Writing Rates
The $0.50 a word that paid me $30 an hour
A few years back I took a job that looked like a steal: $0.50 per word for a 2,000-word piece on commercial HVAC financing. A thousand dollars. I’d been writing blog posts at $0.15 a word and felt like I’d finally cracked the code.
Then I actually did the work. Two days of reading lender terms I half-understood, three calls with the client’s sales lead, a fact-check pass, and two rounds of revisions because I’d buried the lede. By the time the invoice went out I’d spent roughly 33 hours on it. A thousand dollars over 33 hours is about $30 an hour. My “cheap” $0.15-a-word blog work, which I could draft at 500 words an hour with my eyes half closed, was quietly paying me far better.
That’s the whole problem with per-word rates. The number on the contract tells you nothing about what you’ll actually earn. The only rate that’s real is the one you can convert into dollars-per-hour after the work is done — and most writers never run that conversion until it’s too late to matter.
The conversion, both directions
The math itself is trivial. It’s the inputs people fumble.
Per-hour to per-word. Take your target hourly rate and divide it by the words you can finish in an hour:
$75/hour ÷ 500 words/hour = $0.15 per word
So if $75 an hour is your floor and you genuinely draft 500 usable words an hour on a given type of content, then $0.15 a word is $75 an hour. They’re the same rate wearing different clothes.
Per-word to per-hour. Reverse it. Multiply the per-word price by your real output:
$0.50/word × 60 words/hour = $30 per hour
That 60 words an hour is the killer. On heavily researched work — the HVAC piece, a regulatory explainer, anything where you read more than you type — your effective drafting speed collapses. A glamorous $0.50-a-word rate sinks to $30 an hour the moment the work requires you to actually know something before you write it. The per-word number went up and the hourly number went down. Always check the direction.
Your real speed depends entirely on what you’re writing
There is no such thing as “your writing speed.” There’s your speed at a specific content type, and the spread is enormous. Here’s a table I keep taped to the inside of my own pricing notes, with effective hourly worked out at a fixed $0.20 per word so you can see the same price produce wildly different paydays:
| Content type | Words per hour | Effective rate at $0.20/word |
|---|---|---|
| Quick listicle (“10 tips for…“) | 700 | $140/hr |
| Standard SEO blog post | 400 | $80/hr |
| Researched whitepaper | 150 | $30/hr |
| Technical / API documentation | 90 | $18/hr |
Same $0.20 a word. The listicle pays nearly eight times what the technical doc pays per hour, because words-per-hour is doing all the work and the price-per-word is doing almost none. This is why a flat “my rate is $0.20/word” is close to meaningless. A writer who quotes one per-word number across all four of those rows is getting robbed on two of them and overpaid on one, and has no idea which is which.
If you’ve never pinned down your real floor — the hourly number these conversions have to clear — it’s worth running your true hourly rate before you accept another per-word quote. You can’t tell whether $0.20 a word is good until you know what hour of your time has to earn.
The number that lies: drafting speed vs. true effective rate
Here’s the trap that swallowed my HVAC job. When writers estimate their speed, they time drafting — fingers on keys, prose appearing. But drafting is often the smallest slice of the job.
Take a 1,200-word researched blog post at $0.25/word — a $300 fee. Watch the hours stack:
| Phase | Hours |
|---|---|
| Research, interviews, reading | 3.0 |
| Outline | 0.5 |
| Drafting (1,200 words ≈ 400/hr) | 3.0 |
| Self-edit + fact-check | 1.5 |
| Two rounds of client revisions | 2.0 |
| Total | 10.0 |
Drafting alone — 3 hours for 1,200 words — looks like 400 words an hour, which feels like $100/hour at this price ($300 ÷ 3 hours of “writing”). But the true effective rate divides the fee by every hour the job consumed:
$300 ÷ 10 hours = $30 per hour
The drafting illusion said $100. Reality said $30. The difference is research and revisions — the hours nobody quotes for and everybody works. If you price off drafting speed, you’ll undercharge by two-thirds on anything that requires thinking, and you’ll do it cheerfully, because the spreadsheet looked fine.
Converting to a per-project price that protects your hourly
Once you know your true effective rate, per-project pricing stops being a gamble and becomes arithmetic. Say a client wants that same kind of 1,500-word researched piece and your protected floor is $75/hour.
Estimate the whole job, not the drafting:
- Research: 3.5 hours
- Outline: 0.5 hours
- Draft (1,500 words ≈ 400/hr): 3.75 hours
- Edit + fact-check: 1.5 hours
- Two revision rounds: 2.0 hours
- Total: 11.25 hours
11.25 hours × $75 = $843.75. Round up to a clean, intentional $875 flat — and notice what that implies per word: $875 ÷ 1,500 = $0.58 per word. If you’d quoted this piece at the $0.20-a-word rate that felt normal for your listicles, you’d have charged $300 for an eleven-hour job and earned about $27/hour. The per-project quote, built backward from your hourly floor, protects the number that actually pays your rent.
This is the same skeleton I use for any flat fee — estimate the real hours, multiply by a defensible rate, round up. I walk through a full project end to end in how to price a project.
When to refuse per-word and quote per-project instead
Per-word billing has exactly one honest use: predictable, low-research content where your words-per-hour barely moves. Listicles, simple SEO posts, product descriptions you could write in your sleep. There, per-word is fine — it’s fast to quote and the conversion stays stable.
The moment a job has any of these, stop quoting per word:
- Research-heavy work, where reading and interviews dwarf the writing. The word count no longer tracks the effort.
- A short, high-stakes deliverable — a 300-word homepage hero, a tagline, an executive summary. The value is in the thinking, not the volume. Charging per word on a tagline is professional self-harm.
- Strategy bundled with writing — a content brief, an SEO plan, a messaging framework. None of that is words on a page, and per-word pricing makes it invisible.
My rule, stated plainly: if the words-per-hour will swing by more than about 2x across the job, refuse per-word and quote the project. A stable-speed listicle can live on a per-word rate forever. A researched explainer, where one section flies and the next takes a day of reading, will betray you every time. Per-word rewards volume; some of your most valuable work is deliberately not voluminous.
If you’re still deciding which model fits a given client, the broader trade-offs — who eats scope creep, who keeps the efficiency gains — are laid out in hourly vs. project pricing. Writing rates are just that same decision wearing a word count.
The one habit that fixes all of this
Track your hours on every job, even the per-word ones, for a month. Then run the conversion backward: fee ÷ total hours = your real effective rate. You’ll find out fast which content types secretly underpay you, and you’ll stop accepting per-word quotes that look generous and pay like a part-time shift.
A closing note, because money on a page isn’t money in your account: every figure here is pre-tax. As a self-employed writer in the U.S. you’ll owe self-employment tax on top of income tax, which changes what a “$75/hour” job actually leaves you. This is an informational estimate, not financial or tax advice — check your obligations against the IRS or your state revenue department, or a qualified professional, before you bank on any take-home number.