zapier
My role
I was a senior writer and editor, full-time, for two years.
The project
I wrote and maintained feature guides for the blog. These were mid-funnel, long-form articles—2,000 words apiece, give or take—that showed users how our built-in tools work, with step-by-step setup instructions, screenshots, and use case inspiration.
Timeline
1–3 weeks per guide, from ideation to publication. I published the Zapier MCP feature guide within 48 hours.
My approach
As the content team contracted, I became solely responsible for these guides. To write them well, I stayed current on Zapier’s new products and product updates. That involved keeping in close contact with product teams, automating Slack channel monitoring, and prompting tools like Glean for insights.
When I decided to write or edit a feature guide, I used a prompt chain that I’d created, in Claude, to produce a strong first draft. This AI process cut down my writing by at least five hours per guide.
Once the guides were published, I’d share relevant ones in Zapier’s product newsletter, which I co-owned, broadening their reach to 1.3M readers.
When Zapier launched its MCP product, I was asked to produce a feature guide…well, immediately. Although I didn’t know what MCP technology was and I don’t have an engineering background, I got to work and published a guide within 48 hours.
What I delivered
34 feature guides, written from scratch or edited.
Noteworthy wins
Many of these guides drove signups and conversions, but the Zapier MCP feature guide was the standout performer:
Anthropic featured it prominently in one of their newsletters, driving significant traffic
When I left Zapier, it ranked 5th among 37 feature guides for signups, activations, and upgrades
It’s earned 1.5K+ backlinks from 80 domains
It appeared in 33 AI responses
Wikipedia cited it
Samples
Want me to write content for your team? Contact me.