Tool 1 of the Get Paid Kit · For technical writers

Technical writer hourly rate calculator

This free calculator works out the hourly rate a technical writer should charge, starting from the income you need — not from a per-page rate copied off a job board. It adds the reading, expert interviews and review cycles documentation quietly carries, divides by the hours that actually produce finished pages, and then converts the result back into per-page terms, because that is how a lot of documentation is really bought.

Runs in your browser. Nothing you enter is uploaded, sent to a server or stored anywhere except this device.

The pricing reality for freelance technical writers

Technical writing is sold by the hour, by the page and by the project, and each model hides a different cost. Per-page pricing hides the research: a single page of documentation can sit on top of specifications, tickets, product time and an hour with the engineer who built the feature, none of which produce pages at all. Per-project pricing hides the review cycles — a fee agreed for one draft quietly stretches across three rounds of expert corrections. Hourly billing hides the reading between drafts, when the writer is getting the subject into their head well enough to explain it.

That invisible work is where technical writing rates quietly fall apart. Reading source material, interviewing subject-matter experts, testing the procedure you are documenting, chasing reviewers and folding their comments back in — for many technical writers it takes half the week or more, before pitching, quoting and admin get their share. That is why the preset below starts billable time at 55% rather than the 100% a per-page rate silently assumes: the pages are the product, but they are not the whole job. Technical writers who also sell marketing copy can run the same maths with the copywriter presets for that side of the practice.

The numbers below are starting presets, not a survey: an $85,000 target income, $3,500 a year of expenses — a realistic shape for authoring and diagram tools, reference books and professional memberships — and 55% billable time. With those starting numbers the calculator lands near $123 an hour. Change any figure to match your own books; the point is not the preset, it is that every cost gets counted before the per-page rate is quoted, not discovered after the second review round.

Your numbers — technical writer presets

Your recommended rate

$0 / hour
$0Day rate (8 hours)
0Billable hours per year
Income + expenses needed$0
Grossed up for tax$0
With profit margin$0
Working weeks0
Total working hours0
Billable hours0

Your rate is saved on this device only, so the Proposal Generator can show it when you price a project.

Easy to miss

Costs technical writers forget to put in the rate

  • Reading and research time. Specifications, tickets, existing docs and the product itself have to be absorbed before a word is drafted. On unfamiliar subjects the reading can outweigh the writing, and it is skilled work, not overhead.
  • Expert interview time. Scheduling engineers, interviewing them, transcribing what they said and checking it against the product — the interview is an hour; the work around it is several.
  • Review-cycle rework. Every round of expert comments is real writing time: corrections, restructures, new screenshots, re-checks. If the quote never caps the rounds, the fee stays fixed while the pages keep changing.
  • Docs tooling. Authoring tools, screenshot and diagram software, terminology and style tools renew every month, in quiet months as reliably as busy ones.
  • Keeping docs current. Products change after release, and someone has to update the pages: versioning, deprecations, revised procedures. Maintenance is steady, priceable work — if it was ever put in the rate.
The maths

How this calculator works

Start with the hours you can genuinely sell. Take 52 weeks, subtract your vacation weeks, multiply by your hours per week, then multiply by your billable percentage. With the technical writer presets — four weeks off, 40 hours a week, 55% billable — that is 1,056 billable hours a year, well under the 2,080 hours a salaried job is counted on. That gap is why dividing a target salary by 2,080 always underprices technical writing.

Next, work out what those hours must bring in. Add your desired income and your annual business expenses together — $88,500 on the presets — gross the total up for tax by dividing by one minus your tax rate — at a 25% estimate, divide by 0.75 to get $118,000 — then add your profit margin to reach $129,800 and divide by your billable hours. That final number, $123, is the rate below which the year stops adding up.

Now convert it back into the units clients buy. If a finished documentation page takes about two and a half hours end to end — reading, drafting, the expert interview and the corrections folded in — $123 an hour works out at roughly $308 a page. A dense reference page might carry four hours and price near $492; a light update to an existing page might take one hour and price near $123. These are conversions of this example, not market rates — the point is the direction of travel. Take any per-page offer and divide it by the hours that page type really takes: $150 a page at two and a half hours pays $60 an hour, however substantial the page count looks.

Disclaimer: This is a planning estimate, not tax advice. Tax rates, deductions and allowances vary by country, state and business structure. Enter the rate you expect to pay, and check significant decisions with a qualified accountant.
Questions

Technical writer rate questions

Time yourself on real pages, end to end: reading the source material, drafting, interviewing the expert, and folding in their corrections. Using the presets here, a finished page that takes about two and a half hours at $123 an hour prices near $308 a page. Pages are not uniform — an API reference page and a getting-started guide are different animals — so keep a pace per page type rather than one number for everything. These are conversions of this example, not market rates; what matters is that the page price is built from your hours, not guessed.
Often less than half. The draft is the visible tip: underneath it sit reading specifications and tickets, using the product, interviewing the engineers who built it, checking terminology, and reworking pages after expert review. That invisible share is exactly why the billable preset here starts at 55% rather than 100% — a rate built only on drafting hours quietly donates the research. When you estimate a documentation project, count the reading and interview hours as line items, not as overhead you absorb.
Agree the number of review rounds in the quote, and name what happens after them: further rounds are billed at your hourly rate. Expert review is essential — it is how the page becomes correct — but an open-ended review loop turns a fixed fee into an open-ended discount, because experts comment in their own time and every comment round is your time. Also separate calendar from hours: a page can wait a week for an expert's eyes while only costing you three hours, so quote delivery dates around their availability, not just your drafting speed.