Button text is short, but is key to guiding users through a software feature and helpful in preventing users from making mistakes. As the last thing read, button text summarizes everything the user engaged with and serves as the only text a user is required to physically interact with (as opposed to free text that the user is able to skip).
The application of this rule is more difficult than stating it. However, you are probably not going to contradict yourself if you name the outcome of 200 buttons.
Buttons are read alone. Often, a user will scan a dialog for an escape route. ‘Submit’, ‘OK’, ‘Continue’ leave the result for the user to interpret from the context of which the scanning user has not read. ‘Delete 12 files’ cannot be misinterpreted, and that specificity is what prevents the support ticket starting ‘I thought it would just close’.
The safer option is to give a verbless model a list of buttons. Oftentimes, buttons to delete and buttons to save look similar. The lack of verbs leads to a needless confusion for the user and increases support calls. Submit, Confirm, and Continue are the three most common verbs used when no other verbs are available.
Clicking every button is the only way to see the name, even the buttons with cancel paths which is where the ambiguity tends to reside. So, we collect all of the labels into one list. That’s where teams tend to realize they have buttons that are labeled Save, Apply, Update, and Confirm that all do the same function.
One vague verb spreads. If Save is used to mean commit in one place and draft in another, users learn to disregard both and support begins to explain the distinction on a day to day basis. We provide you with the required labels and a short verb list that dictates which verb your product uses for which type of action, so new screens adopt the decision.
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 button text | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single option | 10 | $1 | $0.01 | $1.01 |
| Five variations | 30 | $3 | $0.03 | $3.03 |
| Full name set | 60 | $6 | $0.06 | $6.06 |
A button text 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.
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.
We write to the width you give us. Provide us with the pixel or character limit at your narrowest breakpoint and we will write within it including the longest language you plan to ship. A label that breaks in German and fits in English is a bug that can be found and fixed before a release.
Yes, and it’s almost always less expensive to buy both. The text above the button is a single piece of text. Buying them separately would give you a text box where you ask a question and a button to click that answers a different question, and that is how people cause misclicks.
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.
They requested access to our staging endpoint with read access and used it too. The auth section of your docs shows us the 409 error we return for duplicate idempotency keys. That error is not documented anywhere in our old docs. Contract documentation has never come back and educated me about my API before.
Our changelog has little snippets about why the change happened, and that seems to have solved the issue of support receiving the ‘what does this actually do?’ tickets. I honestly never thought that release notes would give us the answer for that.
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.
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