Good SaaS copy isn't clever. It's specific.
I'm Uchechi Rejoice. I write blog posts, comparison content, and product led articles for SaaS companies. Over the past two years I've built a process around real research, on the product and on the reader, instead of generic advice dressed up in industry language.
From the Griply case study below. Same claim, one version a reader forgets, one they act on.
I write to move a specific reader toward a specific action.
I figure out why a reader hesitates, then write content that removes that hesitation.
That means starting with a real mechanism, such as why a user quits or why a buyer stalls, instead of surface level advice. I read the product, the named competitors, and the psychology behind the reader's decision before I write a single line.
I've spent the last two years writing SaaS content this way. Some of the work below was written on assignment. Some was written entirely on spec, unpaid and unsolicited, for real products, because I'd rather show proof than promise it in an interview.
Six steps, same order, every time.
- 01Research the product, its docs, and its named competitors
- 02Find the real mechanism, the reason the reader hesitates or churns
- 03Structure the argument around that mechanism, not a template
- 04Draft in the reader's register, technical, skeptical, short on time
- 05Self edit for redundancy, rhythm, and claims I can actually back up
- 06Tie the piece to one clear, specific action
SaaS Work
Written for real SaaS products, researched from the ground up, including competitors and the psychology behind each product's core feature.
Why One Missed Day Makes You Quit
Griply had no content addressing one of its clearest product differentiators, flexible weekly targets instead of rigid daily streaks. Here's how the piece came together.
The problem
Most habit tracker content is generic motivational advice. Griply's actual product mechanic, replacing streaks with weekly targets, was a real, differentiated angle nobody was writing about, including Griply itself.
Product and competitor research
I read Griply's feature pages, help docs, and FAQ, and checked how they position against Todoist, TickTick, and Sunsama on their own site, so the piece used their real vocabulary, terms like "Perfect Week" and "goal first," instead of guessing at it.
The psychology
I researched why streak based habit apps cause people to quit and landed on two named, citable mechanisms, the "what the hell" effect (Polivy and Herman) and the abstinence violation effect from addiction research. This is what separates the piece from generic productivity content.
The strategy
Structure the piece around the psychology first, so the product feels like the logical answer to a real problem, not a feature dump bolted onto a listicle.
The result
A publish ready post with structured subheads, named competitor context, and a CTA tied to Griply's actual free tier limits, sent to their team cold, with no assignment or payment involved.
Read the piece →Which One Actually Helps You Finish Work
Comparison pages are the exact content type SaaS companies use to capture high intent, bottom of funnel buyers, so I researched and wrote one on my own rather than wait for an assignment. I worked through both products firsthand, mapped where each one actually wins for different types of teams, and structured the piece around the reader's real decision instead of a generic feature table.
Read the piece →Why Should I Care? Winning the First 5 Seconds on Your SaaS Homepage
A SaaS homepage has a few seconds to answer one question for a visitor, why should I care. Not what the software does, not how much technology went into it, and not how many features fit above the fold. I wrote this piece to break down what actually earns that first five seconds and how to structure a homepage around it.
Read the piece → This link currently opens to a sign in wall for visitors. Set sharing to "Anyone with the link can view" in Google Docs so it opens for people who click it.Adjacent Brand and Audience Work
Not SaaS, included because the research, structure, and audience first thinking transfer directly.
Mission Driven Storytelling and Audience Growth
The foundation needed content that turned passive readers into donors and volunteers, not another vague mission statement. I built a storytelling framework tied to their community impact goals and wrote audience focused content designed to attract donor interest, including a CSR focused piece aimed at corporate partners.
- Generated donor inquiries within weeks of publishing
- Maintained a consistent brand voice across outreach materials
Comparison Content for a Student Audience
Elevana needed to help students cut through the noise of comparing platforms, tabs, and conflicting advice while making academic and career decisions. I wrote a comparison focused piece that positioned Elevana's AI guidance as the simpler alternative to jumping between tools, aimed at building trust with a student reader rather than reading like a sales pitch.
Read the piece → This link currently opens to a sign in wall for visitors. Set sharing to "Anyone with the link can view" in Google Docs so it opens for people who click it.Standalone Pieces
Pieces written on spec to demonstrate range across technical AI and SaaS topics and conversion focused writing.
How to Track ChatGPT for You and Your Company
A technical piece on monitoring AI driven brand visibility, written for a SaaS marketing audience.
Read the piece →Conversion Is the Reality Check
A product led argument against vanity metrics, written to educate a SaaS marketing reader while driving a clear action.
Read the piece →4 Writing Frameworks for AI Visibility
Practical frameworks for SaaS marketers to improve visibility in AI powered search, covering ChatGPT, Claude, and Perplexity.
Read the piece →I like the puzzle of explaining something useful that's easy to describe badly.
I got into SaaS writing because I like solving problems with words, taking something a product does well but explains badly, and finding the version that actually lands. It also keeps me learning new products, new audiences, and new reasons people say yes or no. Two years into this, that's still exactly why I want to build my career here.
Four things I actually do, not four things I claim.
Research before writing
I don't guess at your audience's questions. I look them up, competitors, reviews, forums, the product itself, before I draft a word.
Specific over clever
Jargon free explanations that respect a technical reader's time, built around one clear claim per piece instead of ten vague ones.
Two years of proof, not promises
I can point to real pieces, on assignment and on spec, so you can see how I think before you hire me.
Reliable on deadline
Clear communication, on time delivery, and feedback taken seriously. Editorial trust is built one piece at a time.
Have a feature your customers overlook?
That's the kind of content I like writing. Open to freelance SaaS content work and remote roles. I typically reply within a day.