Technical writers get paid for one-off work by two kinds of buyer: a startup that needs one part of its docs fixed before a launch, and a career changer who wants a working technical writer to read their sample. Publish each job as a fixed-scope offer, such as a docs site review, one API reference page or a writing-sample edit, so the buyer attaches the docs URL, OpenAPI spec or sample and pays before you open it. On Brillay those are Custom Work listings. Short career questions like "can I move from Linux support into technical writing?" become Paid Questions you answer in writing, on your own time.
Who pays a technical writer for one docs job instead of a contract?
There are two groups, and they want very different things.
Startups and small dev-tool teams. The buyer is usually a founder, a developer-relations hire, or the one engineer who "owns docs" on top of a full sprint. The docs live in Docusaurus, Mintlify, ReadMe, GitBook or MkDocs, or in a Zendesk or Intercom help center. Something has gone wrong, and it tends to be one of these:
- The quickstart was written for v1 of the API and nobody has run it since v2 shipped.
- The API reference is auto-generated from the OpenAPI spec: forty endpoints, empty descriptions and no examples.
- The SDK ships in Python, Node and Go, but every code sample is Python.
- Support keeps answering the same three tickets the docs should have covered.
- A launch, an investor demo or a first enterprise customer is two weeks away.
They aren't ready to hire a full-time writer. They want someone who knows what good docs look like to say what's broken, or to write the one page that's missing.
People moving into technical writing. These are support engineers, sysadmins, QA testers, teachers, journalists and bootcamp grads. They ask the same handful of things:
- Is my writing sample good enough to send?
- Do I need Git and docs-as-code, or is Markdown enough?
- Is a certificate worth the money?
- What goes in a portfolio when every doc I've written sits behind a company login?
- A startup offered me a contract at $40 an hour. Is that low?
They'll pay a modest amount for a straight answer from someone who does the job.
Neither group wants persuasive copy. Nobody needs their docs to "convert." They need them correct, findable and in the right order: accurate parameter types, code that runs when you paste it, and a quickstart that gets a developer to a first successful API call. You're being paid for accuracy and structure.
Which docs jobs can you sell at a fixed price?
Choose two to four. The first three are Custom Work: you set the price, scope and delivery time, and the buyer sends a brief and up to 5 files and pays before you start.
1. Docs site review (Custom Work)
A written review of a defined slice of the site, for example the quickstart plus up to eight pages the buyer picks. What you check:
- information architecture: can a new reader find "authenticate" and "first request" without searching?
- page types: is each page clearly a tutorial, how-to, reference or explanation (the Diátaxis split), or is it all four at once?
- the quickstart run end to end in a clean environment, if they give you access
- prerequisites stated before step one, not halfway down
- code samples that copy and paste cleanly, with placeholders clearly marked
- one term for one concept ("API key," not also "secret," "token" and "access key")
- style against the Google developer documentation style guide, the Microsoft Writing Style Guide or their own guide
- missing error, troubleshooting and changelog content
What the buyer sends: the docs URL, or exported pages if the site is private; who the readers are (backend developers, no-code admins, IT buyers); the three tasks readers most need to finish; anything they already know is broken.
What you deliver: a findings note ranked fix now, fix next and nice to have, plus an annotated PDF, a marked-up file, or a screen recording of you walking the site. A Custom Work delivery holds a note, up to 5 files and links, and a recording can run up to 20 minutes. Three to five days suits most writers.
2. One API reference page (Custom Work)
One finished reference page for one endpoint or one resource, in Markdown or MDX so it drops straight into their docs tool. It includes:
- what the endpoint does and when to use it instead of its neighbors
- auth requirements and scopes
- a parameters table: name, type, required, description, default
- a sample request in curl plus one language the buyer picks
- a sample response, with nullable fields called out
- error codes and the usual cause of each
- rate limits and pagination, where they apply
What the buyer sends: the OpenAPI or Swagger spec (or the relevant section), one working request and response, a sandbox key if you'll call the API yourself, and their page template. Give it two to five days. Put "one endpoint" or "one resource with up to four operations" in the scope so a whole reference doesn't sneak in at the price of one page.
3. Writing sample and portfolio feedback (Custom Work)
A line-and-structure edit of one sample, plus notes on how it reads to a hiring manager. The buyer sends one sample (PDF, Word file or GitHub repo link), the kind of role they're after (API docs, end-user help, internal knowledge base), and their portfolio link if they want it looked at. You deliver the sample with comments, a note on the three biggest changes, and a plain verdict on whether it shows what hiring managers look for: a real task, a stated audience, task-based structure and steps someone has actually run. Two to four days is typical.
Career changers make predictable mistakes, which is why this offer is good value for them:
- The sample describes a product instead of walking someone through a task.
- Screenshots do work the words should do.
- No audience is stated anywhere.
- Nobody has tested the steps.
- A converted runbook still reads like a ticket comment.
4. Answer on breaking into tech writing (Paid Questions)
A Paid Question is one private question you answer in writing, with up to two follow-ups. The follower pays upfront as a guest, and you reply inside the window you set (1–24 hours or 1–5 days). There's no call and no calendar. Typical questions:
- "I've done Linux support for six years. How do I position that for a tech writing role?"
- "Is learning Vale and GitHub pull requests worth it before I apply?"
- "Should my portfolio piece be a tutorial or a reference page?"
- "How do I rewrite a confidential internal runbook into a public sample?"
A Paid Question is plain text both ways, with no attachments. If someone pastes a whole 12-page sample into the question box, answer what they asked and point them to offer 3.
What does a docs review listing look like when you write it like a spec?
Your Custom Work listing has fields for what the buyer gets, what you need, what's excluded and the delivery time. Most bad docs jobs go wrong at intake, so fill them in the way you'd write a page's prerequisites. For example:
Title: Quickstart and docs review for developer tools
What you get: a ranked findings note covering your quickstart plus up to eight pages you choose, an annotated PDF of every page reviewed, and a 15-minute screen recording of me running your quickstart.
What I need: your docs URL or exported pages; one sentence on who reads them; the three tasks they most need to finish; a sandbox key if you want the quickstart run against your API.
Not included: rewriting the pages; building or migrating your docs site; setting up a docs-as-code pipeline; pages beyond the eight you choose; ongoing maintenance.
Delivery: 5 days.
The brief and files arrive at checkout together with the payment, so you start with the sandbox key and the page list in hand instead of chasing them over email.
What does a finished docs review actually contain?
Startups are paying for findings their engineers can turn straight into tickets. A short excerpt from a typical review note:
- Fix now: Quickstart step 3 tells readers to set API_KEY, but the SDK reads ACME_API_KEY. The first request fails with a 401 and nothing on the page explains why.
- Fix now: The "Create a webhook" page shows a response field called event_type, while the spec and the live API return type.
- Fix next: Authentication is explained on four pages under three names. Pick one page and one term and link to it from the rest.
- Fix next: The reference lists 14 error codes without a cause or a fix. Start with the five that show up most in support tickets.
- Nice to have: Add a Vale configuration with your term list so new pages stay consistent after I'm gone.
Each finding names the page, the problem and the fix, and it's ranked. That's what separates a paid review from a "few thoughts" reply in a DM.
What's different if you're a UX writer or content designer?
The skills are similar, but the thing you work on is different. UX writers and content designers work on product microcopy: button labels, error messages, empty states, tooltips, permission prompts and onboarding screens. The buyers are different too: product teams at startups with no content designer, solo founders shipping an app, and junior content designers who want a senior opinion on their case studies.
App microcopy review (Custom Work). The buyer sends screenshots or a Figma export of a fixed number of screens (say ten), their voice and tone notes, and any character limits. You deliver annotated screenshots plus a string table with four columns: screen, current string, suggested string and reason. Common findings:
- error messages that blame the user ("Invalid input") instead of saying what to do
- buttons labeled "Submit" that should name the action ("Send invoice")
- two words for the same object across screens
- strings that will overflow once they're translated into German
- empty states that don't tell anyone the next step
Onboarding flow rewrite (Custom Work). One flow, from sign-up to the first meaningful action. The buyer sends the screens in order and names the activation step they care about. You deliver rewritten copy for every screen in a table engineers can paste from, with notes on any screen you'd cut.
Junior content designers mostly want portfolio help, which is closer to design critique than to docs. A Paid Question fits "how do I show impact in a case study when I can't share metrics?", and a Custom Work review fits one full case study. If you also review visual design, the designers page covers that side.
How do you handle a full docs project inside a five-day window?
You choose a delivery time of 1–24 hours or 1–5 days, and five days is the longest. Each order is one delivery, with no milestones and no built-in revision rounds.
That fits reviews well. It doesn't fit "write our whole developer portal," so don't sell that as one order. Sell a scoped piece that fits:
- one quickstart, not the whole getting-started section
- one API resource, not the full reference
- an information architecture proposal (a nav tree with a page type for each item), not the rewrite that follows it
- one help-center category of up to ten articles, not the whole help center
- one migration guide for one breaking change
Write that limit into the listing. If the startup likes the first piece, they order the next one, and both of you have seen real work before anyone commits to more.
Also write short support, correction and refund policies. Followers see them before they pay. After you deliver Custom Work, the buyer can open a support conversation on the order to flag a broken link, a wrong parameter type or a correction, and you reply in writing.
How should you price a docs review, an API page or a sample critique?
You set the price. Common starting points:
- Paid Question on breaking in: $25–$65. Short answers, mostly for career changers.
- Writing sample feedback: around $65 for one sample is a common starting point, rising to $150 if it includes a portfolio pass.
- Microcopy review (up to ten screens): $150–$300.
- Docs site review (quickstart plus up to eight pages): $200–$500, depending on depth and whether you run the code.
- One API reference page: $150–$400 per endpoint or resource, more for samples in several languages.
These are starting points, not a forecast of what you'll earn. Price the outcome, not the hours: the startup is buying "our quickstart works and our reference has examples." Running the code against a sandbox is the most valuable part of a review, so charge more for it than for reading alone. If you're thinking about a launch discount, read whether to discount your first paid offer first.
What Brillay costs:
No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate.
The details are on the pricing page.
Can a technical writing blog or free Linux tutorials earn money?
Say you write free tutorials on the side, such as Linux troubleshooting, Git explainers or "how I set up docs-as-code," and you want them to earn something beyond your day job. A blog on its own rarely pays much. It works better as the place readers find you, as long as there's something specific for them to buy:
- Paid Question: a reader stuck on a systemd unit file or a permissions error wants your read on their exact setup.
- Custom Work: a small team liked your docs-as-code post and wants their own repo's README and contributor docs reviewed.
- Tips: your guide saved someone an afternoon and they want to say thanks. A tip is a one-time thank-you, with nothing for you to deliver.
- Goals: you want to make something bigger and free, like a public style guide, a docs overhaul for an open-source project, or a home lab for new tutorials. A Goal is one named goal with a progress bar. Followers make one-time contributions, and every contribution is yours whether or not the goal is reached. There's no deadline unless you set one, and nothing to ship.
None of this guarantees income. It gives readers who already want to pay you a clear way to do it. Personalized Videos are also available, but they rarely fit documentation work, and most technical writers leave them off.
Why sell from your own link instead of DMs, marketplaces or booked calls?
You can keep using any of them. Each has a cost for this kind of work:
- DMs and email. A founder asks for "a quick look at our docs." You agree the scope in a thread, send an invoice and wait, and often the quick look ends up free.
- Freelance marketplaces. A founder you send there sees other writers ranked next to you, and your listing has to compete in search.
- Booked calls. You price an hour like an hour and find a slot that works across time zones. But engineering wants a written list of findings they can file as tickets, not a call recording.
On Brillay, a startup or career changer taps the link in your LinkedIn headline, GitHub profile, newsletter or portfolio site. They read the scope, send the brief and pay upfront by card as a guest, with no account to create. They see the public name you choose, not your legal name. There's no follower minimum and nothing to apply for, so a few hundred connections who happen to be founders and engineers is enough to start. How it works walks through each step.
How do you start this week?
- Choose two offers. A docs site review plus a Paid Question on breaking in covers both buyer groups.
- Write the review listing like the spec above: in scope, out of scope, what you need, delivery time.
- Write your support, correction and refund policies in two or three sentences each.
- Put your link where your buyers already find you: your LinkedIn headline, GitHub profile README, portfolio site, newsletter footer and the end of every tutorial.
- In your next post, share one real finding with the company anonymized ("an env var name that broke step 3 of a quickstart") and add: "I review quickstarts like this one. Link in bio."
You don't need anything made in advance, so you can create your Brillay page and publish the first listing today.
Frequently asked questions
Can I review docs that sit behind a login or in a private repo?
Yes, as long as the buyer can share them. Say in your listing what works for you: pages exported as PDF, Markdown files from the repo, or a staging link they're comfortable sharing. A Custom Work brief can include up to 5 files. If they want the quickstart run against their API, list a sandbox key as a requirement.
A startup's docs were mostly drafted with AI. Is that worth reviewing?
Often more than hand-written docs, because AI drafts tend to sound confident and be wrong: parameters that don't exist, outdated SDK methods, steps nobody has run. Check the docs against the spec and the live sandbox, and say so in your scope, since checking accuracy is the part they can't get from another draft.
Can I offer revisions?
There are no built-in revision rounds. Put your correction policy in writing, for example "I'll fix any factual error in my delivery within two days," and buyers see it before they pay. After a Custom Work delivery, the buyer can message you on the order about a correction and you reply there.
Will startups and students see my real name?
They see the public name you choose: on your page, at checkout, on their card statement and on their receipt. Your legal name goes only to Stripe, for identity verification and payouts.
What does Brillay cost a technical writer?
There's no subscription and no paid tier. The only cost is the platform fee listed in the pricing section above, and it applies only to orders that are actually paid. Card processing is separate.
Can I get paid where I live?
Creators in 41 countries can get paid, and followers pay by card from anywhere. That matters if you're a writer in one country reviewing docs for a startup in another.
Explore more