Pricing & Ordering

No-AI Technical Writing Pricing

As with everything else here, documentation is priced at $10 per 100 words with a 1% surcharge added. The amount of required preliminary reading for technical work is what differs the most.

Order content How it works

How No-AI Technical Writing Pricing Works

A 2,500-word integration guide amounts to around $250 worth of writing. We add $2.50 to every such Guide, so we charge you $252.50 and the writer keeps $250. Nothing about the writing affects this mathematics. An API reference, a troubleshooting guide, and a product announcement are all charged at the same per-word rate because the meter is on words rather than task complexity. There is no engineering surcharge, and no expedited options that you can buy to move this Guide to the head of the line.

The only real variable is scope, and technical scope is easy to miscalculate. A procedure must account for everything, including what happens when an install fails, and so documentation typically is more extensive than marketing collateral for a given product. We will require you to specify the system, the audience, and the format. We will provide you a range of words rather than a specific number.

It sounds generous, but time is not allocated for research as a separate line item. Writers have limits on how much time they can dedicate, given the orders schedule allows. If your system requires a week of research in order for people to explain it, put that in the brief and we can adjust the quote to account for a longer timeline. The alternative is a draft that is delivers on time and little to no value in the end.

Access beats budget

Proximity to the product is the common sticking point. Sandbox credentials, a staging URL, or a 20 minute call will yield greater accuracy than any amount of additional spend.

Pricing is per word, including a 1% convenience fee for each entry.
Release notes/changelog entries = 600 Words = $60.00 each + $0.60 convenience fee = $60.60

What Is Included in No-AI Technical Writing Pricing

The rate includes transforming the source material into the final document. This includes reading your specifications, tickets and pages, drafting the document, editing it, and running the final document through the verification suite. Twelve detection and plagiarism reports have been included with the delivery email. Two rounds of revisions are included with the order and will be available for 14 days.

We need to clarify what is not included in the rate. We return a document. For you, taking screenshots, preparing diagrams, or publishing the document to your document management system is on your side of the division. We will not send any code samples that others have not been able to run. If you need someone working in your toolchain or against a private repository, please contact us before you place your order so that we may be better able to respond with “Yes” or “No.”

Verification is included in the price. Each draft is measured against 12 detection platforms, Originality.ai, GPTZero, Turnitin, and Copyscape being among the included platforms, and the reports are delivered along with the file. As these tools are probabilistic in nature, and human documents can be flagged, the reports should be considered evidence, not proof. The idea is that one can display their reasoning and working.

  • Reviewing your specifications, tickets, and other existing documentation.
  • A first draft written start to finish by one named writer
  • Twelve detection and plagiarism reports sent with the delivery email.
  • Two revisions, valid for 14 days post-delivery.
  • Full copyright on delivery, with no attribution line required

Choosing the Right No-AI Technical Writing Pricing Option

Begin with the job the reader is trying to do. A 900 word troubleshooting page will not help someone who is stuck with an error message. Similarly, a locked approach when evaluating your API will call for a step-by-step guide. Length is determined by the job, so since you’re charging by the word, choosing the right job should save you a lot of money.

To start, purchase a single page for the first order rather than the page set. One individual page for a 1,200 word how to only costs $121.20 and generally answers the first and most important question: how well did the writer understand the product? A how to page written incorrectly is a small misfire that costs a small amount of money and a week. For the twenty pages, it would cost you nearly one quarter of the year.

When the format is established, the price of a greater quantity of work changes the dialogue more than the price per page. Ten pages cost what they cost, but a custom quote incorporates a project schedule and shared terminology for the duration of the project, which ensures the same writer throughout the project avoids using the same feature in three different documents and labeling them as different things.

  • Less than 1,000 words: single troubleshooting pages, release notes, and changelogs.
  • Between 1,000 and 2,000 words: setup instructions, how-to guides, and feature documentation.
  • Between 2,000 and 4,000 words: technical whitepapers, API guides, and architecture notes.
  • 5,000 words and larger: multi-page documentation sets and complete user manuals.
  • For work with an indefinite scope, request a custom quote with an associated writer and a term list.

One page first

The best way to test a writer on a subject with technical depth is to request a single complex page. You know they can handle the complex cases well if they are successful in addressing failure cases. Solving the rest of the requirements is then likely a scheduling issue.

No-AI Technical Writing Pricing FAQs

A human writer handles every part of this. Ask us on the contact page and a person will answer the same working day.

A human writer handles every part of this. Ask us on the contact page and a person will answer the same working day.

No. An explanation of distributed systems and a printer setup guide are both $10 per 100 words. Difficulty of the subject influences the schedule, but not the rate. If a subject requires more reading than a standard order allows, we quote more time rather than more money, and we inform you prior to charging.

The first 100 words cost $10 to write, and a ten-cent fee for every 50 words after that. In practice, technical pages usually need around 600 words to cover prerequisites, steps and failure cases, so almost anything under that is probably a changelog entry and not a page.

If you order the set together, yes, consistency in naming will be maintained because we create a term list for drafting. If you order them separately and distant in time from each other, then they may be assigned to different writers. This is valuable information when you divide a large project into smaller tasks in order to accommodate budgeting.

No, both of the included rounds cover our errors and anything that missed the brief you sent. If your product moves and the page requires new content, that is new writing at the same rate. We quote the difference instead of charging you the full page again.

Send this information through the contact page before you place an order. Terms must be agreed upon before a writer views anything proprietary, and it is a waste of your time and the writer’s time to draft an order and then have to stop to do paperwork. The material you send is exclusively for your order and will not be used for anything else.

Trying to pin down a technical work pricing figure usually brings up questions of scope. Fill out the product, audience, estimate of size, and the form, and you will receive a word count and total free of charge.

Content a person actually wrote

$10 per 100 words, and the writer keeps all of it. Our 1% sits on top, 0.5% goes to trees, and no generated text appears anywhere in the process.