How to Write a Product Description from Your Highlights (With Citations)

The Student Product Seller's Problem

Here is a situation more common than most marketing textbooks acknowledge: a student or lifelong learner creates something — a digital template, a course outline, a study guide, a productivity system — and then needs to describe it to potential buyers. They've spent months reading books about entrepreneurship, product marketing, and customer psychology. They've highlighted the passages that resonated with what they're building. They understand, at least theoretically, what a good product description should do.

And then they open a blank document and write something like: "This productivity template helps you organize your tasks efficiently and achieve your goals."

Which is the kind of sentence that appears in every product listing that sells nothing.

The irony is that the highlights sitting in their notes contain exactly the material they need. When you highlight April Dunford writing about positioning — "Positioning defines how your product is the best in the world at delivering some value that a well-defined set of customers cares a lot about" — you've marked a passage that, properly translated, tells you what your product description needs to accomplish. When you highlight Donald Miller on customer-centric storytelling — "the customer is the hero, not your brand" — you've flagged the structural principle that explains why your first draft failed.

The challenge is the translation step: from highlighted theory to applied copy.

---

What Highlights Contain for Product Description Writing

Highlights from books and articles on product marketing, copywriting, and business strategy contain three types of material useful for writing a product description from your highlights:

1. Positioning frameworks: Books like April Dunford's Obviously Awesome (2019) or Al Ries and Jack Trout's Positioning (1981) provide explicit frameworks for answering the product description's foundational question: who is this for, and what is it the best option at accomplishing for them? Highlights from these books are raw positioning inputs.

2. Benefit language patterns: Copywriting books like Donald Miller's Building a StoryBrand (2017) or Ann Handley's Everybody Writes (2014) provide examples of how features translate into benefits — and why the translation matters. Highlights from these sections model the writing pattern directly.

3. Customer psychology research: Academic and applied research on what drives purchasing decisions — the Baymard Institute's ecommerce studies, Nielsen Norman Group's UX writing research, or behavioral economics findings highlighted from Daniel Kahneman's Thinking, Fast and Slow — provide the evidence basis for specific copy choices.

Each type serves a different step in the product description writing process.

---

Step 1: Sort Highlights by Product Description Element

Before drafting, go through your highlights and sort them into five buckets corresponding to the five elements of a product description:

Bucket 1 — Positioning (who is this for, and best at what): Look for highlights about audience definition and competitive positioning. Dunford's Obviously Awesome chapter on positioning components is especially useful here. The positioning work answers the product description's implicit opening question: "Is this for me?"

Bucket 2 — Hook language (customer problem in customer words): Look for highlights about customer-centric storytelling — anything where the book describes the problem from the customer's perspective, not the maker's. Miller's StoryBrand framework (the customer has a problem; the guide helps them solve it) directly models the hook structure.

Bucket 3 — Feature-benefit translation: Look for highlights where the author translates a feature or specification into a customer outcome. Many business and copywriting books do this explicitly to illustrate the principle. These translation examples model the pattern your copy needs to follow.

Bucket 4 — Social proof and credibility: Look for highlights about what forms of evidence customers find persuasive — research findings about review formats, case study structures, or what makes a testimonial credible versus vague. Cialdini's Influence (1984) chapters on social proof are heavily highlighted by students for exactly this reason.

Bucket 5 — Call to action: Look for highlights about decision architecture — what makes a next step feel low-risk. Books on behavioral design, growth, and UX often have highlighted sections on friction reduction and CTA framing.

---

Step 2: Apply Frameworks to Your Product

Once sorted, apply each bucket's content directly to your product:

From your Bucket 1 (positioning) highlights, complete the April Dunford positioning exercise as it applies to your product:

POSITIONING FROM HIGHLIGHTS

Best alternatives: [What would the customer do instead — Excel, pen and paper, nothing, competitor A?]
Unique attributes: [What does my product do that alternatives don't or can't do well?]
Value these enable: [What outcome does each unique attribute produce for the customer?]
Best-fit customers: [Describe one specific person this is perfect for — not everyone]
Market frame of reference: [What category does this live in — budget tracker? study system? workflow template?]

From your Bucket 2 (hook) highlights, answer Miller's two questions:

• What external problem does the customer have? (The surface-level problem)
• What internal problem — the frustration or fear beneath the surface — does it really create?

The hook names the internal problem in the customer's own words, not the external feature that solves it.

From your Bucket 3 (feature-benefit) highlights, complete the translation table for each feature:

FEATURE → BENEFIT TABLE

Feature 1: [What the product does]
  → Benefit: [What the customer experiences as a result]
  → Evidence basis: [Which highlighted passage models this translation]

Feature 2: [...]
  → Benefit: [...]
  → Evidence basis: [...]

---

Before/After Worked Example

Context: Mia is a third-year marketing student who has built a personal budgeting template on Notion and wants to sell it on Gumroad. She's taken a consumer behavior course and highlighted sections of Influence (Cialdini), Building a StoryBrand (Miller), and Obviously Awesome (Dunford). Her template tracks spending by category, projects monthly totals, and compares actual vs. planned spending in a visual dashboard.

Her highlights include:

From Building a StoryBrand: "When you clarify your message, customers will listen. And the most important clarity is about the problem the customer has — especially the internal problem beneath the external problem."

From Obviously Awesome: "Features are the attributes of your product. Value is what the customer gets from those features. You can't win on features. You can only win on value."

From Influence: "Social proof is most powerful when the person being influenced identifies with the person providing the proof."

From a Nielsen Norman Group article she highlighted: "Product copy that leads with the user's goal — not the product's function — has 64% higher comprehension scores in user testing."

Her first draft (pre-highlights application):

Mia's Budget Tracker — Notion Template

A comprehensive budget tracking template for Notion. Features include category spending tracking, monthly projections, and actual vs. planned comparison dashboard. Perfect for anyone who wants to manage their finances better. Includes 5 customizable views and automatic rollup calculations.

Price: $12. Download immediately after purchase.

Feature list. No hook. "Perfect for anyone" is the opposite of Dunford's positioning. No benefit translations. No social proof. Generic CTA.

After (from highlights-driven process):

---

You know what you're supposed to be spending. You just don't know where it actually goes.

Mia's Budget Tracker is a ready-to-use Notion template built for students and young professionals who want to stop doing the math in their head and start seeing the truth of where their money goes — every month, automatically.

Once you copy the template to your Notion workspace, you get:

• Category breakdown that fills itself in — log a transaction, see your monthly spending by category update in real time. No formulas to maintain, no spreadsheet columns to add.
• Planned vs. actual comparison at a glance — the dashboard shows where you're over budget before the month ends, not after. You can actually adjust.
• Rolling projections — shows what you'll spend by month-end at your current rate. The number you always wanted but couldn't calculate without an hour and a calculator.

Built by a marketing student who spent two months tracking spending in a spreadsheet before deciding there had to be a better way. Used it herself for six months before packaging it.

Get the template for $12 — instant Notion access after checkout.

The hook ("you know what you're supposed to be spending") names the internal problem Mia identified from Miller: the frustration of feeling out of control. Benefits replace features. The social proof ("built by a student who used it herself for six months") is the peer-identification form Cialdini describes. The CTA removes friction by naming the immediate outcome.

---

What to Do When Your Highlights Are Too Theoretical

Highlights from academic and theory-focused texts are often written at a level of abstraction that doesn't directly map to copy. The Dunford positioning framework is a process for building positioning, not a template for copy. Miller's StoryBrand model is a narrative structure, not a headline formula.

The translation from theory to application is the work. When a highlight describes a principle — "lead with the customer's goal, not the product's function" — the product description writer's job is to find the specific customer goal and the specific product function and make the connection.

Three questions that force the translation:

1. What is the specific version of this principle that applies to my product, for my customer?
2. If I were writing an example of this principle for my product, what would it say?
3. Which sentence in my current draft violates this principle, and how do I fix it?

These questions turn abstract highlights into concrete editing directives. The theory doesn't write the copy — it judges the copy you've already written and tells you what's wrong with it.

---

Prompts to Reuse

Product Description From Highlights

I'm writing a product description for: [Product name and one-sentence description]
Customer: [Specific person this is for — not everyone]
Where it will appear: [Gumroad / app store / course marketplace / website / pricing page]

My highlights give me the following inputs:

POSITIONING (who this is for, best at what):
  "[Highlighted passage that informed my positioning]"
  Source: [Book/article, author, year]
  Application: "[How this applies to my product's positioning]"

HOOK (customer's internal problem):
  "[Highlighted passage about customer-centric problem framing]"
  Source: [...]
  The internal problem for my customer: "[What they're actually frustrated about]"

FEATURE → BENEFIT TRANSLATIONS:
  Feature 1: "[What my product does]" → Benefit: "[Customer outcome]"
    Highlights basis: "[Which framework modeled this translation]"
  Feature 2: "[...]" → Benefit: "[...]"
  Feature 3: "[...]" → Benefit: "[...]"

SOCIAL PROOF:
  "[Type of social proof I can offer, based on what Cialdini / research says is most persuasive for this customer]"

Write a product description that applies these inputs. The description should:
- Open with the customer's internal problem in their language (from hook material)
- State the primary benefit — what the product makes possible — in the second sentence
- List 2-4 features as benefits (customer outcomes, not specifications)
- Include one social proof signal in the form most relevant to this customer
- Close with a specific CTA that names what happens immediately after they take action

Avoid hollow adjectives (powerful, seamless, intuitive). Every claim needs to be specific.

---

Checklist Before Publishing

Before publishing the product description:

• Hook names the internal frustration — not the feature, not the product category
• No hollow adjectives — every "powerful" and "seamless" replaced with a specific claim
• Every feature is a benefit — what the customer experiences, not what the product does
• Social proof is specific — who uses it / what they achieved, not "customers love it"
• CTA names the immediate outcome — "instant Notion access after checkout," not "buy now"
• Positioning is applied — this description is clearly not for everyone; it's clearly for one type of person

---

Key Takeaways

1. Highlights from marketing and copywriting books are direct inputs to product descriptions: a highlighted passage from Obviously Awesome or StoryBrand isn't just theory — it's a framework you can apply to your specific product in the next step.
2. The sorting step is the work: before drafting, sort highlights into the five product description buckets (positioning, hook, feature-benefit, social proof, CTA) — each bucket becomes one section of the description.
3. Theory highlights require translation: a principle like "lead with the customer's goal" doesn't write the copy for you; the translation step is asking "what is the specific customer goal for my product?" and building the copy from that answer.
4. Student and DIY products have natural social proof: "built by someone who had this problem and couldn't find a solution" is the peer-identification form Cialdini identifies as most persuasive — and it's honest, which makes it more effective.
5. Three lengths from the same highlights: marketplace long form (250-400 words), pricing page medium (80-120 words), and summary short form (40-60 words) all use the same sorted highlight inputs — draft all three at once.

---

Conclusion

The practical value of the books students highlight about marketing, positioning, and copywriting is not limited to passing exams or understanding theory. Every framework that gets highlighted is a direct tool for writing better product descriptions. Positioning frameworks answer who the description is for. Customer-centric storytelling models answer how to write the hook. Feature-benefit translation examples show the exact pattern that replaces feature lists with copy that converts.

The highlighted passages don't write the description. They structure the thinking that makes the description specific, honest, and recognizable to the customer it's for.

Try WebSnips free — save and annotate the marketing, copywriting, and business books you're reading, tag highlights by product description element, and access your organized framework library every time you're writing copy for a new product.