Onboarding shows you how many of your installs were out of curiosity. Each screen will cost you users. Every single screen has to justify its existence by answering a question rather than posing a promise.
The majority of the weight falls on the text. A permission prompt with a simple sincere sentence gets permission. The same prompt in a marketing sentence results in a no that the operating system will ask for once and never again.
A first run with clarity gives the user a sense of context and comprehension of the type of actions they agree to. At most, four well written screens can replace a support article. Be cautious with wording, as written poorly, the four screens can teach the user your product requires explains itself in slogans, and the user goes on to expect and interpret future on-screen browsing warnings similarly.
Created by laid-back developers, onboarding voice is optimistic, so each screen has a welcome message along with get started and you’re all set. Since there are no drop-off statistics available, it doesn’t have any view of your permission strategy and consequently, puts a cheerful message where an honest explanation of the complex situation is required. After iOS requests that single permission, it never does again.
Before we add anything into our structure, we benchmark the flow. Half of all onboarding issues are structural in nature. We then visit a clean install and a real hardware device to get a bird’s eye view of where the writer slowed down and noted the most concise pathway of steps to complete and activate the account. Copy comes after that, screen by screen, with the label of the button written first.
Being cross-functional, we schedule the review while we roll out onboarding copy. You receive the draft in a table that is screen-by-screen with the trigger, the character limit, and any dependencies noted. This allows three reviewers to comment on the document without a meeting. There are two revision cycles in the fourteen day period.
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 app onboarding | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Short | 500 | $50 | $0.50 | $50.50 |
| Standard | 1,000 | $100 | $1 | $101 |
| In-depth | 2,000 | $200 | $2 | $202 |
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.
Short enough that a new user sees something useful before they decide about you. Often it takes three screens and a permission prompt. Most benefits come when we delete a screen instead of rewriting it. We will let you know when deleting is better than writing.
Yes. We write two versions of an advertisement where the order of one aspect is switched. You learn something from the example. However, when five variations are made, nobody learns how to win from the example.
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.
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.
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.
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.
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