What a program covers
- The topic plan. What to publish and in what order, drawn from what your buyers ask and what people search for.
- The review process. Who checks each draft against the product before it's published.
- The writers. Hiring, vetting and technical review when the work needs more than one person.
How I plan the topics
I start with your customers. Your calls and sales call transcripts tell me what buyers keep asking, and I use Claude and other AI tools to pull those topics together.
Then I check search demand in Semrush and put the two lists together. After pages are live, I track them in Google Search Console and adjust the plan.
How I run the writing
Every piece gets checked against the product before it ships. At Mem0 I hired writers who understood the subject, so drafts were accurate before they reached review.
Work you can check
- Mem0: I managed 13 writers and handled hiring, vetting and technical reviews.
- LinuxForDevices: monthly visits went from 487 to 203,400 in 15 months, by Semrush's figures for 2019 to 2022.
- DelightChat: a program built from zero to 50,000 monthly organic visits in 12 months, by Semrush's figures for 2021.
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 program 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 for each product the articles cover, 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.
Related reading
The developer content topic covers what to publish and who should write it. My page on documentation ROI covers how to measure one document, and the piece on the Stripe engineering blog shows a program that worked.
FAQ
What is a technical content program?
It's the topic plan, the review process and the writers behind a company's technical articles, run as one system so every piece is checked against the product.
Do you write the articles or manage writers?
Both. I write individual pieces, and I hire and manage writers when the plan needs more than one person.
How do you measure a content program?
I track the pages in Google Search Console after they go live and adjust the plan from what they rank for.