Most products rely on developers that are pressed for time, and so a lot of developer user interfaces (UIs) contain text that is written at random, usually the night before the deadline (or similar). This leads to most products having multiple tones of voice across the board and one space only that says No Data.
There are at least four different kinds and they are not interchangeable. First, use. Everything clears. No search results. Something failed. Need different sentences and different buttons in each of these cases.
By default, a blank screen is ambiguous to the user: they don’t know if the app is broken or perhaps still loading, or if this is the expected behavior. One sentence fixes that ambiguity. The second job of a single sentence is to assign a task and reduce the likelihood of user abandonment, because an empty list is the moment a user is most willing to be shown what to do next, and most likely to leave if nothing is shown.
Where AI falls down on empty states
Empty states show a remarkable degree of cheerfulness and uniformity, they all tend to say the same thing: ‘nothing here yet, go on and add the first item’. With this voice, giving a user a sync failure means telling them to get started… which, is the most annoying sentence to encounter at that given moment when some of their data is indeed, missing.
Our Software Writing Process for No-AI Empty States
We look for all the empty state variants in the product first, which usually yields more results than expected, along with a lot of duplicates. The writer sorts them by type. We then answer each variant informally based on the question the user is asking at the time. Given there are no search results, there are a few possible explanations. It may be a new account, or the search may be broken.
Reviewing No-AI Empty States With Your Product Team
We improve review speed by delivering one large table rather than multiple tables. Engineers verify that all checked actions have the corresponding states, and support will inform you which blank screens cause support tickets to be generated today.
What empty states cost
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 empty state
Words
Writing
Fee (1%)
You pay
Single screen
60
$6
$0.06
$6.06
Small set
150
$15
$0.15
$15.15
Whole flow
350
$35
$0.35
$35.35
Short pieces are billed at the 100-word minimum
An empty state is shorter than our 100-word minimum order, so a single one is charged as 100 words ($10.10). Most clients commission these in batches, which uses the minimum properly — ask for however many options you want and we will quote the set.
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.
Questions About No-AI Empty States
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.
More than expected. A mid-sized product can include between fifteen and forty lists when you take into account filtered lists, cleared inboxes, expired sessions and offline views. Our first pass is always an inventory, and it is normal for that list alone to cause you to reconsider your order.
Harmless things can carry jokes, and so new tasks I check off my list can be joked about. However, failed uploads, blank screens that appear after payment, and even cleared to-do lists, cannot be joked about. We match jokes to their respective consequences and mark the states that we deem safe for our personality.
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
What clients say about our empty states
Reviews from completed, paid orders in this category.
ATAna-Maria TImplementation Lead, Corvid Fleet
One prerequisite missing, otherwise ready
Ordering is clearly very good, and the screenshots are clearly explained. The guide assumes the customer has admin access, which a good number of them do not. We wrote a pre-req box ourselves in ten minutes. Everything else was complete.
Verified orderSetup guidesMarch 2026
ALAnders LEngineering Manager, Kestrel Systems
The error codes section alone
Our API documentation was written over an uneven four-year span. The author went through every single one and flagged six cases where our error responses were inconsistent with the description and raised them instead of just fixing them on the fly. That was worth the order.
Verified orderAPI documentationApril 2026
HJHenrik JCTO, Loomstack
Engineers read them now
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.