Book descriptions that turn browsers into buyers
A 4-paragraph blurb framework, twelve templates, and a worksheet. Your retail page copy, done in an afternoon.
How this page works: there is no app running here — just method. Copy a template, fill in the worksheet below, then paste the result into EarnDraft to draft the book. Free to start, no signup to read.
On this page
What is the 4-paragraph blurb framework?
Browsers skim: hook, pain, contents, credential. Paragraph 1 opens with the reader's want in one or two lines — this is what shows before the “read more” cut, so it must stand alone. Paragraph 2 names the pain or the stakes. Paragraph 3 lists what the book delivers, ideally as bullets. Paragraph 4 gives your credential and one clear call to action.
Write it in second person (“you”) until the credential paragraph, where you switch to first or third person (“I” / “[Name] has…”). That switch is the moment browsing becomes trusting — don't blur it.
- P1 — Hook: the outcome, in the reader's own words.
- P2 — Pain: what staying stuck costs.
- P3 — Contents: what they get, as scannable bullets.
- P4 — Credential + CTA: why you, then one action.
Why do the first two lines decide everything?
Retail pages truncate descriptions, so most shoppers never expand them. Your first two lines must contain the outcome and the reader — no throat-clearing, no “in this groundbreaking book”. Read your opener out of context: if a stranger can't tell what the book delivers, rewrite it.
The fix is mechanical: lead every draft with “For [reader] who want [outcome]” in some form, then vary from there. Boring-but-clear beats clever-but-truncated every time.
Blurb ready? Put a real book behind it.
Draft the full ebook from one sentence, then paste this description on your live page.
What does a finished blurb look like?
For “The Freelancer's First $1k”: “Your first paying client is closer than you think. If you're a new designer sending proposals into the void, this short guide walks you from samples to signed project. Inside: the one-page offer that answers pricing before it's asked, three outreach scripts that got replies, and the delivery checklist that turns one project into referrals. Written by a designer who crossed $1k in month two. Scroll up and start tonight.”
Four paragraphs, each doing one job: hook names the outcome, pain names the void, contents lists three concrete items, credential plus CTA closes. Steal the skeleton, not the sentences.
Which blurb mistakes kill conversions?
Feature-dumping (“12 chapters, 140 pages!”) instead of outcome-selling — readers buy results, not page counts. Vague superlatives (“ultimate”, “groundbreaking”) that could describe any book. And ending without a call to action, as if the buy button weren't the whole point of the page.
Also: writing the blurb before the book is finished. The description must match the contents exactly — disappointed readers quote mismatches in reviews. Draft it now from your book outline, finalize it after the draft.
Twelve blurb templates to copy
Full skeletons with [BRACKETS]. Fill them in, then trim anything that doesn't earn its line.
- 01 · Direct PromiseFor [reader] who want [outcome]: [Book] walks you from [start] to [finish] in [scope]. Inside: [item], [item], [item]. From [credential]. Start tonight.
- 02 · Pain AgitatorTired of [pain]? [Book] is the short guide that [outcome] — without [common dread]. You'll get [item], [item], and [item]. [Credential]. Scroll up and fix it.
- 03 · Question HookWhat if [outcome] took [scope] instead of [old expectation]? [Book] shows [reader] how: [item], [item], [item]. Written by [credential].
- 04 · Mistakes Rescue[Reader] keep making the same [Number] [topic] mistakes. This book names each one and shows the fix — [item], [item], [item]. Stop paying for [pain].
- 05 · Beginner WelcomeNew to [topic]? Start here. [Book] explains [outcome] in plain English: [item], [item], [item]. No jargon, no assumed knowledge — just the path.
- 06 · System SellerThe [Method] method has helped [who] [outcome]. This book is the complete system: [item], [item], [item]. Follow it in order; [scope] is enough.
- 07 · Story Opener[Author] was [relatable low point] — until [turning point]. This book distills what worked into [item], [item], and [item] for [reader].
- 08 · Checklist PitchEverything [reader] need for [outcome], nothing they don't. [Number] checklists covering [item], [item], and [item]. Check them off, [outcome].
- 09 · Contrarian TakeForget [common advice]. [Book] argues [contrarian claim] — and proves it with [item], [item], and [item]. For [reader] ready to [outcome] differently.
- 10 · Workbook InviteDon't just read about [outcome] — practice it. [Number] guided exercises take you from [start] to [finish], with [item] and [item] worked examples. Pens out.
- 11 · Report AuthorityWe [researched/surveyed/tested] [scope] to answer [question]. Key findings: [item], [item], [item]. Essential for [reader] who decide about [topic].
- 12 · Gentle GuideA calm, short guide to [outcome] for [reader]. No hustle, no shame — just [item], [item], and [item] at your own pace. Start wherever you are.
The blurb worksheet
Answer each line with raw material from your book — phrases, not polished prose. Assemble at the end.
1.Hook in one line
“For [reader] who want [outcome]” — must survive truncation.
2.The pain, in their words
What does staying stuck cost them? Quote readers if you can.
3.Three contents bullets
Concrete items: scripts, checklists, systems — not chapter titles.
4.Your one-line credential
Result or role that earns trust, e.g. “priced 40 projects”.
5.One call to action
“Scroll up and start tonight” — name the action.
6.Assemble + cut 20%
Build the 4 paragraphs, then delete the weakest fifth.
Keep going
Sibling micro-tools plus the generator that turns your answers into a finished book.
Frequently asked questions
About 150 to 250 words: four short paragraphs plus a few bullets. Long enough to sell, short enough to read on a phone. If it scrolls past two phone screens, cut it.
Sell the book with a blurb that earns it
Free to start · No credit card · You own the output