What I write
- Concept explainers. They define a term an engineer has half-met and show how it works.
- Comparisons. They help an engineer choose between tools, with the tests or sources behind each claim.
- Best-of roundups. They compare the options in a category on the features an engineer cares about.
How I choose topics
I start from what your buyers ask. I listen to your calls, ask for sales call transcripts, and use Claude and other AI tools to summarise the topics people keep raising.
Then I check the search demand in Semrush. A topic goes on the list when your buyers ask about it and people search for it.
How I write it
I run your product before I write about it. A claim I can't check gets a source and a date, or it comes out.
Work you can check
- What is an agent harness?, an explainer for Firecrawl.
- Playwright vs Puppeteer, a comparison for Firecrawl.
- What is a cloud browser?, an explainer for TinyFish.
- What is agentic RAG?, which I wrote for Mem0, in an archived copy that shows my byline.
The portfolio links the rest.
How we'd work together
Email hello@ninadpathak.com with the product and the reader, or book a 30-minute call at https://zcal.co/ninadpathak/meet. This page lists no rate, so ask for a quote with the scope.
- We talk for 30 minutes about the reader and what the article has to do for them.
- You get a written brief and a timeline within 24 hours of that call.
- I need a demo account, API keys and an account with real data in it, because I run the product before I write about it.
- Once the brief is agreed, the first piece is a paid trial, and we carry on only if you're happy with it.
- A draft takes about 5 days from the brief and revisions take 2, so you can publish in one working week.
- There are two rounds of review at most.
- I deliver in Google Docs or as a Markdown pull request, or in whatever your team uses, and I can load it into your CMS if you'd like.
Once we've worked together for a while, the same cycle comes down to 4 days end to end.
After an article is live, I track it in Google Search Console and report what it ranks for.
Related reading
The developer content topic covers what to publish and how to write it. My pages on writing for AI products and the Stripe engineering blog show how I think about articles for engineers.
FAQ
What do technical article writing services include?
Topic research, a brief, the article and up to two rounds of review, with the products in the article run before it's written.
How do you pick what to write about?
From your sales calls and customer conversations first, then from search demand checked in Semrush.
Do you use AI to write?
I use AI to prepare research and to attack a draft. I check the product myself before I sign off on a claim.