Roadmap communication is mostly the management of disappointment. Something slipped, something got cut, and something a paying customer depends on is being switched off in six months. Those three messages are harder to write than any launch announcement you will ever publish.
Most people’s instinct is to make the delay sound less severe, but this will buy only a quiet week and will cost the trust you need the next time a delay happens. We write the version that survives a second reading.
Roadmap notifications must spell out exactly what the change is and be vague on nothing that matters. This is only possible if you know which customer relies on the feature being turned off, what they will have to build after the feature is turned off, and approximately how long that will take. If you can’t get this right, you will end up publishing a notification that appears to be calm and will end up creating hundreds of ticket requests for clarification.
Delay and deprecation notices show where AI is least convincing. Text generated text tends to reach for words to reassure, even if the date is only half way down. Users can even read the corporate tone as a clear indication to avoid this particular product. In this case, the tone used costs the company a renewal rather than a click.
We tell Product what we mean by certainty, what we mean by likely, and what is aspiration. We then only include certainty and likelihood statements in our proposal. The approver of the commitment language gets to review it early on in the process rather than at the very end. For a deprecation, we draft the migration instructions before we publish the announcing deprecation which includes a link to our migration instructions.
Support has the first look of all customer-facing messages. They know the one sentence that will breach the support ticket threshold, and which named accounts need the courtesy of a private advanced notification. The people in the room with them read the notification to see what the work commitments were. Your customer facing message should resemble the version your account managers have ceased to be concerned about.
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 roadmap communication | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single update post | 450 | $45 | $0.45 | $45.45 |
| Quarterly roadmap post | 900 | $90 | $0.90 | $90.90 |
| Deprecation and migration set | 1,800 | $180 | $1.80 | $181.80 |
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.
Yes. Send two or three pieces you like the sound of, or your style guide. Matching an established voice is ordinary work for a writer and close to impossible for a model that has never read your back catalogue.
Certainly. This is the best time to sketch out a rough direction. Quarters, sequencing, and rough themes are extremely helpful in this phase. They indicate rough direction to your team and to your customers. We will push you to be specific about what you have in the works, because customers have a knack for assuming the worst when you are vague there.
The attached information shows support for the ticket load, accuracy, an owner of the timeline, and legal if the contract references the feature. Legal is needed to review the contract. We’d also prefer drafts in a format that allows each reviewer to check off only their section rather than force a full review of the notice.
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.
Our release notes went unread, but they serve the purpose of listing what breaks and what doesn’t when considering whether to upgrade. Two customers actually took the time to send thank yous in the same week, something that had never happened before.
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