Technical writers create documentation such as API references, user guides, knowledge base articles, SOPs, release notes, and training materials. Most freelance and small-business writers invoice software companies, medical device firms, engineering teams, and agencies, usually for a defined project or a block of hours each month.
Create an invoice for payment collection
Upload logo
PDF will be generated with filename:
Invoice_1001_Client_2026-10-14.pdf
Technical writers bill hourly, per project, per page, or on a monthly retainer. Hourly is most common for contract work embedded with a team, especially when scope shifts as engineers change the product. Fixed project fees work for well-defined deliverables like a 40-page user guide or an API reference for a set number of endpoints, and they should be based on an hours estimate with a buffer for review cycles. Per-page or per-word pricing is less common and tends to undervalue research and interviews, so many writers use it only as a sanity check. Retainers suit ongoing release notes, knowledge base upkeep, and docs-as-code work. Add separate line items for subject matter expert interviews, diagramming and screenshots, localization prep, and rush work. Software or tool costs (for example, a client-required authoring license) are usually either absorbed in the rate or billed at cost with approval.
| 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.
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Discovery: SME interviews and product walkthrough (3 sessions) | 5 hours | $85.00 | $425.00 |
| REST API reference: 24 endpoints, request and response examples | 28 hours | $100.00 | $2,800.00 |
| Getting Started guide (draft and final) | 10 hours | $85.00 | $850.00 |
| Diagrams and annotated screenshots | 6 hours | $65.00 | $390.00 |
| Review rounds 1 and 2: consolidating comments and revisions | 8 hours | $85.00 | $680.00 |
| Total | $5,145.00 | ||
Notes: Project: Developer Documentation v2, PO #4471. Work delivered via the client's docs repository, merged 6/14. Payment due within 30 days of invoice date. Late balances accrue 1.5% per month. Additional revision rounds beyond the two included are billed hourly.
Accounts payable teams at larger companies often reject invoices without a PO number, which delays payment.
Naming the guide, article set, or API version makes it clear what was delivered and ties billing to the statement of work.
Clients on hourly contracts want to see research, writing, review, and revision time separately, particularly when engineers questioned the total.
Tying each invoice to an approved milestone, such as outline or first draft, prevents disputes about whether payment is owed yet.
Documentation work often grows through review cycles, so showing how many rounds were included protects you when extra rounds are billed.
Stock images, translation vendors, or a client-required tool license should be itemized at cost with a reference to the approval.
US clients paying a contractor over the annual reporting threshold generally need a W-9 on file to issue a 1099.
Technical writers commonly ask for 25-50% upfront on fixed-fee projects, with the balance tied to milestones or delivery. Hourly contractors usually invoice every two weeks or monthly, and corporate clients often pay on net 30 or net 45 terms. Net 15 is reasonable for small businesses and startups. Late fees of 1-1.5% per month are common if stated in the contract in advance. Payment is typically by ACH or check, with credit cards less common because of processing fees. For first-time clients, consider requiring the deposit before starting and keeping final source files until the last payment clears.
Write into your agreement how many review rounds are included and what a round means, such as one consolidated set of comments per round. Without this, documentation projects can drift for weeks while product changes trigger rewrites.
Waiting on engineers for answers and access to builds is real project time. Include interview scheduling and follow-up in your estimate, or set a rule that delays caused by the client extend the timeline and may be billed.
Diagramming, screenshot capture, video, and publishing to a help center or docs site take significant time. Itemize them so clients see why a 20-page guide costs more than 20 pages of text.
Outline approved, first draft delivered, and final published are natural billing points. This keeps cash flow steady and gives you leverage if a client goes quiet.
Ongoing docs work often stays at the original rate for years. Include an annual adjustment clause or revisit the rate each renewal.
Hourly is safer when scope is unclear or the product is still changing. Project pricing works when deliverables are well defined, and you can estimate hours confidently. Many writers quote a fixed price based on estimated hours plus a buffer of 15-25% for review and rework.
Yes. Research, product walkthroughs, and testing the software are part of the job and are normally billable. List discovery as its own line item so the client sees it as a planned phase rather than padding.
Refer to the revision limit in your agreement and bill additional rounds at your hourly rate. If you did not set a limit, send a change order that states the new work and cost before continuing.
In the US, clients who pay you over the IRS reporting threshold during the year generally ask for a W-9 so they can issue a 1099-NEC. Sending it at the start of the engagement avoids payment delays later. Check current IRS rules or ask a tax professional.
Yes, for work completed. Your contract should say that you are paid for hours worked or milestones reached through the cancellation date, and that any deposit is non-refundable up to that point.
Send a Technical Writer estimate for approval, then turn it into an invoice when the work is done.
Technical Writer estimate template