Writing Help Docs for SaaS Companies: Rs 2,800 Per Article Journey

Short answer: Writing SaaS help docs requires actually knowing how to use the product, not deep coding knowledge. Rates run Rs 1,500 to 5,000 per article, or Rs 15,000 to 40,000 as a monthly retainer. Clients can come organically from offering unsolicited help on support tickets, or through direct LinkedIn outreach.

---

I was trying out a small SaaS company's project management tool one evening, and one particular feature just wasn't making sense no matter how long I stared at it. Went digging through their support ticket system to see if anyone else had run into the exact same confusion before giving up entirely.

Found the exact same question asked by 20-plus people over the previous two months, each time explained manually by the support team all over again, word for word almost. No documentation existed for that feature at all, not even a half-finished draft sitting somewhere unpublished.

Wrote a simple article covering exactly how the feature actually worked, screenshots included throughout, and emailed the whole thing straight to their support address: "This is completely free, use it in your docs if it's at all useful to anyone."

---

The response landed harder than expected

Two days later, a reply came in that I genuinely hadn't expected, the founder messaging directly rather than someone from support: "This is genuinely helpful. Could you do this for us regularly, on an ongoing basis?"

I was confused for a second, thinking, "I'm not even a professional technical writer." But he explained that's exactly what they needed, someone who understood the product and could explain it simply, not PhD-level technical prose.

First paid article came to Rs 1,900, covering a second, noticeably more complicated feature that involved several separate steps and a couple of edge cases.

---

The mistake I made misjudging scope

Next request was for an "API integration guide." I assumed it'd be straightforward, but once I actually started writing it, I realized I didn't even have basic API knowledge myself.

Took three days to learn enough (YouTube tutorials, documentation reading) just to write accurately about it at all. Told the client about the delay, which they accepted fine, though my own confidence took a hit.

Since that day, I ask upfront before accepting a new topic: "Do you have any existing notes or a draft I could start from?" That clears up scope before any work begins.

---

The rate increase, which the client offered on their own

After four months of consistent work, the client said unprompted: "Your work's been consistently solid. We're bumping you to Rs 2,800 per article from here on."

I'd never brought up a rate increase myself, they offered it entirely on their own. That's when it became clear consistency and reliability carry their own value, separate from writing quality alone.

---

Finding other SaaS clients, which wasn't organic this time

The first client came through pure luck. Finding more meant actually staying active on LinkedIn. Messaged SaaS founders directly, used their product first, gave specific feedback on it, then mentioned, "Noticed some gaps in your documentation, happy to help if useful."

1 response out of every 5 messages sent, which is pretty normal for cold outreach honestly, nothing unusual there. But that single response ended up being worth all the silence, another company brought me on part-time from it.

---

The real numbers, 10 months in

First client: Rs 2,800 per article, roughly 4 articles a month, Rs 11,200.

Second client: a monthly retainer of Rs 18,400, unlimited articles within scope (realistically 6 to 8 a month).

Third client (recent): Rs 2,200 per article, lower frequency, roughly 2 articles a month.

Total monthly income runs roughly Rs 33,600 to 38,400, combined across all three clients, on a part-time basis.

---

What still feels genuinely difficult

Keeping documentation in sync with product updates is by far the most time-consuming part. One feature change meant updating 6 older articles, which ate up two full days.

Now I run a proper "documentation audit" every single month just to catch whatever's quietly gone stale. It's cut down on those surprise update scrambles quite considerably since then.

---

Related to other writing paths

A technical writer's journey without an engineering degree looks strikingly similar to mine, both of us started without a technical background. Freelance content writing pays slightly less than help docs, since the demand for specificity and accuracy runs higher here.

---

A client who gave me a "simple" brief that wasn't simple at all

A fourth client asked, "Can you write a simple guide for our onboarding flow?" Heard "simple" and assumed it was an hour's work.

The onboarding flow actually had 7 steps, each one branching into multiple sub-options. The "simple" guide took 5 hours, since every sub-option created a different path depending on user type.

That project taught me something: "simple" means something different depending on whether you're the client or the writer, complexity on the writer's end depends entirely on the actual steps involved. Now I explore the product myself before accepting any brief labeled "simple," even if that costs an extra 20 minutes upfront.

Building a GitHub portfolio helped here too, showing new SaaS clients writing samples, especially when they want proof of technical accuracy before committing.

Wondering now if this could become full-time work eventually. For now, part-time with these clients stays entirely manageable...