Feature pages become outdated super fast on a SaaS site. A feature is released in a smaller form than planned, the page still explains the larger plan, and support spends the next year explaining the difference to users who read the page and believed it.
In this case, what the writer starts with is the product rather than the spec. The product itself, what it does or what it does not, and what plan it falls upon. However, explaining the last one results in more refund requests than any phrasing on the page ever would.
Two questions define the value of a feature page. What does this page replace that is currently working? What does the required change cost? Most feature pages are no help whatsoever describing either what they replace or what it costs to replace them. A user who has interacted with the feature page can describe what aspect of the user’s week is removed, and that is the selling point.
A model that writes a feature page with the current marketing will only reinvent your own claims to you with extra jargon. It will never write the most important line, which is explaining what the feature cannot do yet.
We need release notes and time with the internal specs author for twenty minutes. Reverse-engineering marketing copy is easy for developers. Then the writer opens the feature in a test account and documents the outcome, not what the spec says will happen.
While a feature page may never close a deal on its own, it does get opened in comparison tabs, sent to the technical evaluator, and brought back up when renewal time comes and someone asks why they are paying this much. Although, that’s only helpful if someone is writing it for the skeptical second reader in mind. In that case, it’s useful at all three of those points.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical feature page | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single feature page | 600 | $60 | $0.60 | $60.60 |
| Detailed feature page | 1,000 | $100 | $1 | $101 |
| Flagship feature page | 1,600 | $160 | $1.60 | $161.60 |
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
When the feature changes materially, which, for most teams, happens roughly two to three times a year. A page describing a version that shipped eighteen months ago erodes trust with the users that carefully check for page updates. Changelog us and we’ll update the page at the same per-word rate.
We’ll still write them as ‘coming soon’, but we’ll ask for a date you can publish. We’ve seen support tickets being generated and refund obligations being created in some markets by pages describing unreleased behavior as current.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
I’ve written and purchased a lot of feature copy, and most of it is vibes instead of verbs, which is a huge loss. This was not the case. It clearly stated what a feature did and what the change was in the system. It got our sales team reading it on the phone.
The customer we used in this example sent us a nice email saying it was the least stressful case study she’s had to do. This has never happened to us. I have to say the article is awesome, too. The customer liked the interview, but what I will remember is the process.
Mostly excellent. Your improvements to the auth section are better than what our engineers wrote. Your pagination endpoints, however, were explained in the spec according to how they behave rather than how they are, which required two revisions. Our spec is incorrect in that area as well.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees