Technical writers send estimates when a client asks for a defined documentation project, such as a user manual, API docs, or a knowledge base build. Clients usually compare your total price, timeline, and how much of the work you handle versus what their team supplies. Because the product is often unfinished, a good estimate is as much about assumptions as it is about price.
When to use estimates: Use estimates to provide project quotes and get client approval before starting work. Once approved, convert your estimate to an invoice with one click to collect payment.
Create an invoice for payment collection
Upload logo
PDF will be generated with filename:
Invoice_1001_Client_2026-10-14.pdf
State whether you are producing a PDF manual, help center articles, or Markdown in a repo, and roughly how many pages, topics, or endpoints, so both sides agree on the size of the job.
List what the client must provide, such as a test environment, existing docs, style guide, and engineer availability. Late access is the most common cause of schedule slips.
Specify how many interviews or hours of expert time you need, since limited access affects quality and your hours.
Say how many consolidated review cycles are included and who gives final approval, to prevent endless rework.
Clarify which authoring tools, version control, or content management system you will use and whether you are responsible for publishing.
Name items such as translation, video production, UI text rewrites, or ongoing maintenance, so they are quoted separately if requested.
Tie delivery dates to milestones and client inputs, and note that dates move if the product changes or feedback is late.
| Service | Priced | Typical range |
|---|---|---|
| General technical writing (contract) | per hour | $50-110 |
| API and developer documentation | per hour | $80-150 |
| User guide or manual (fixed scope) | per project | $2,500-12,000 |
| Knowledge base article | per article | $100-400 |
| SOP or process documentation | per document | $300-1,200 |
| Release notes and changelog upkeep | per month (retainer) | $500-2,000 |
| Documentation audit and content strategy | flat fee | $1,500-6,000 |
| Diagrams, screenshots, and short video walkthroughs | per hour | $45-100 |
Typical US ranges. Rates vary by region, experience, and job size.
Break the project into discovery, outline, drafting, graphics, review, and publishing. Add 15-25% for product changes and feedback cycles, then present a fixed price or a not-to-exceed cap.
Quote a paid discovery or documentation audit first, then price the main build once you understand the product. This reduces risk for both sides when the scope is vague.
Write assumptions such as number of endpoints, existing content reuse, and review rounds directly under the price. If the assumptions change, you have a clear basis for a revised quote.
Providing a core package and an expanded one that adds diagrams, a quick-start guide, or release-note maintenance lets clients choose without negotiating your rate.
Thirty days is typical. Product plans and your availability change, so state an expiration date and note that pricing may change after it.
Use a fixed price when the deliverables and inputs are clear. Use an hourly estimate with a cap when the product is still changing or access to experts is uncertain.
A short quote is usually free. For large documentation projects that need an audit of existing content or a sample, charge a paid discovery fee and apply it toward the project if the client proceeds.
Send a written change order describing the added work, hours, and cost before you proceed. Reference the assumptions in the original estimate to show what changed.
Use the Technical Writer invoice template to bill the client, or convert this estimate once it's approved.
Technical Writer invoice template