saglitzdesign-mcp 0.3.1

package/knowledge/books/hooked-retention.md

@@ -0,0 +1,196 @@
+---
+id: hooked-retention
+title: "Hooked & Habit Design — Retention Mechanics for Apps"
+category: book
+platform: mobile
+tags: [retention, habits, onboarding, notifications, engagement, ethics]
+sources: ["Hooked (Nir Eyal)", "Indistractable (Nir Eyal)"]
+updated: 2026-07-08
+---
+
+# Hooked & Habit Design — Retention Mechanics for Apps
+
+Eyal's Hook Model: products form habits by cycling users through **Trigger → Action →
+Variable Reward → Investment**. Each pass strengthens the association between the user's
+internal itch and your product as the scratch. Habits form when a behavior occurs with
+enough **frequency** and **perceived utility**; low-frequency products (used monthly or less)
+should NOT chase habit loops — they need scheduled-trigger retention instead (see Part 4).
+
+**Foundational question before designing any loop (Eyal's own test):** Does the product
+materially improve the user's life, and would the maker use it themselves? Habit design on top
+of genuine value = facilitation. Habit design substituting for value = exploitation.
+
+---
+
+## Part 1 — The Four Phases, Applied
+
+### Phase 1: Trigger
+
+**External triggers** (designer-controlled) start the loop; **internal triggers** (emotions,
+routines, situations) sustain it. The endgame: the user's own feeling — boredom, uncertainty,
+FOMO, loneliness, "did anyone reply?" — cues the app without any notification.
+
+Design rules:
+- Identify the target internal trigger FIRST and write it down: "When the user feels [emotion/
+  situation], they open [app] to [relief]." All external triggers should rehearse exactly that pairing.
+- External trigger ladder (move users up it):
+  1. **Paid** (ads — acquisition only, never retention economics),
+  2. **Earned** (press, featuring — spiky, unreliable),
+  3. **Relationship** (invites, shares — the only viral trigger; design share moments at peak-reward points),
+  4. **Owned** (notifications, email, badges, home-screen icon — requires permission, drives the habit).
+- Notification design: every notification must carry the internal trigger's payload — information
+  the user actually itched for ("Anna replied"), not the app itching for the user ("We miss you!").
+- Time notification permission requests: ask AFTER demonstrating one clear reward moment, with a
+  pre-permission screen explaining the specific value ("Get notified the second a client pays you").
+  Never ask on first launch — a denied iOS prompt is nearly unrecoverable.
+
+### Phase 2: Action
+
+The simplest behavior done in anticipation of reward (open app, pull to refresh, tap a card).
+Fogg's model governs it: Behavior happens when **Motivation + Ability + Prompt** converge.
+Ability (simplicity) is the cheapest lever — simplicity along six factors: time, money, physical
+effort, brain cycles, social deviance, non-routineness.
+
+Design rules:
+- Count the steps from trigger to reward; remove every removable one. Each screen, field, or
+  decision between notification-tap and payoff bleeds users.
+- The core action should be doable in seconds: one thumb, no typing where a tap will do,
+  defaults over choices.
+- Cold-start rule: the app must show something rewarding even before the user has data/friends
+  (curated content, sample project, instant demo mode).
+- Login friction is habit poison: biometric auth, magic links, stay-signed-in by default.
+
+### Phase 3: Variable Reward
+
+Predictable rewards get boring; variability sustains engagement (the slot-machine mechanic —
+and precisely where ethical risk concentrates). Three reward types; strong products combine two or three:
+
+- **Rewards of the Tribe** (social): likes, replies, mentions, leaderboard moves, community
+  recognition. Variable because people are variable.
+- **Rewards of the Hunt** (resources/information): feeds, search results, deals, new content,
+  matching (jobs, dates, flights). Variable because the next scroll might be the good one.
+- **Rewards of the Self** (mastery/completion): streaks, levels, inbox-zero, skill progress,
+  personal records. Variable because your own performance varies.
+
+Design rules:
+- Map your product's natural reward type; don't bolt on foreign ones (badges on a tax app = noise).
+- Preserve genuine variability: perfectly predictable digests train ignoring; overly random
+  feeds train distrust. The reward must stay connected to what the user came for.
+- **Autonomy requirement:** rewards must arrive within the user's chosen pursuit. Users who feel
+  controlled (reactance) abandon; frame everything as serving their goal, not the metric.
+- Finite-use rule: give the loop natural stopping points (caught-up markers, "you're all done"
+  states). Infinite variability without closure is the manipulation signature.
+
+### Phase 4: Investment
+
+The user puts something IN — effort, data, content, reputation, followers, money — which
+(a) improves the product for them (stored value), and (b) loads the next trigger.
+
+Stored-value mechanics (each raises switching costs honestly, by making the product better):
+- **Content**: playlists, boards, notes, uploaded files.
+- **Data**: preferences, history, training the recommendations ("the more you use it, the better it gets").
+- **Followers/reputation**: audience, reviews earned, karma, verified status.
+- **Skill**: learned workflows, shortcuts, mastery of the tool.
+- **Customization**: configured dashboards, integrations connected, routines set.
+
+Design rules:
+- Ask for investment AFTER the variable reward, never before — reciprocity plus the moment of
+  peak satisfaction ("Loved that workout? Save it to your plan").
+- Keep each investment tiny; sequence them across sessions (bit of profile now, one preference next time).
+- Load the next trigger inside the investment: following someone creates future notifications;
+  setting a goal creates future progress alerts; posting invites future replies.
+
+---
+
+## Part 2 — Onboarding as Hook Rehearsal
+
+Onboarding's job: run the user through ONE full hook cycle as fast as possible, and identify
+your "aha" action (the behavior correlated with retention) — then design onboarding to cause it.
+
+Prescriptive sequence:
+1. **Promise recall** (screen 1): restate the outcome that made them install — in their words, one line.
+2. **Personalize as commitment**: 1-3 quick-tap questions ("What's your goal?") — investment
+   that tailors the first reward AND commits the user (see influence-persuasion.md).
+3. **First reward within ~60 seconds**: deliver a real taste of the core reward before any
+   account wall where the platform allows; if signup must come first, make it 1-tap (Apple/Google).
+4. **Permission asks in context**: notifications after first reward; other permissions at the
+   moment of relevant use, each with a value-framed pre-prompt.
+5. **First investment**: one small act of stored value (save, follow, connect, configure) before
+   session 1 ends — users who invest in session 1 return at far higher rates.
+6. **Load the return trigger**: end session 1 with a reason to come back that the USER set
+   ("We'll remind you Tuesday — your chosen practice day").
+- Day 1-7 lifecycle: each early notification/email should re-run the loop toward the aha action,
+  not announce features. Kill generic "welcome day 3" content.
+
+---
+
+## Part 3 — Notification & Engagement Ethics
+
+Notifications are borrowed attention; the budget is small and non-refundable.
+
+Rules:
+1. **User-value test per notification type:** would the user thank you for this interruption?
+   "Your ride is here" passes. "Someone might have posted" fails.
+2. **Granular controls, honest defaults:** per-category toggles, easy mute/snooze, digest options.
+   Defaulting everything ON and burying settings is a dark pattern that buys short-term DAU with
+   permission-revocation and uninstalls.
+3. **Respect rhythm:** quiet hours by default, timezone-aware, frequency caps per day. Batch
+   low-urgency items into digests.
+4. **No fabricated urgency or social pressure:** fake "X is waiting for you," ghost activity,
+   streak-shame notifications ("Don't lose your streak!" at 11pm targets anxiety, not value).
+5. **Re-permission gracefully:** if a user ignores 10 in a row, offer to reduce frequency —
+   voluntary retention beats resented retention (resentment shows up as uninstall, not as a metric you watch).
+
+**Streaks & gamification ethics:** streaks reward showing up (fine) but punish life (not fine).
+Ethical versions: streak freezes/repair, weekly targets instead of daily perfection, celebrate
+totals not just consecutive runs. If missing a day produces guilt disproportionate to the
+product's value, the mechanic is extracting, not serving.
+
+---
+
+## Part 4 — When Habit Loops Are Appropriate vs. Manipulative
+
+**Eyal's Manipulation Matrix** — two questions: Does it materially improve the user's life?
+Would the maker use it themselves?
+
+| | Maker uses it | Maker wouldn't use it |
+|---|---|---|
+| **Improves life** | **Facilitator** — build hooks confidently | **Peddler** — you're guessing; validate before hooking |
+| **Doesn't improve life** | **Entertainer** — fine, but fleeting; keep monetization honest | **Dealer** — exploitation; do not build |
+
+**Use full habit loops when:** the product's value genuinely compounds with frequent use
+(fitness, learning, communication, finance tracking, creative tools) AND natural frequency is
+weekly-or-better. Habit here = user's goal achieved with less friction.
+
+**Do NOT use habit loops when:**
+- Natural frequency is low (tax software, booking, insurance). Chasing DAU here produces spam.
+  Instead: **scheduled-trigger retention** — calendar-based re-engagement at genuinely relevant
+  moments ("your renewal is in 30 days"), excellent transactional messaging, and being flawlessly
+  findable at the next need (SEO/App Store presence as the "trigger").
+- Engagement is the cost, not the value (the user's goal is to spend LESS time — automation,
+  utilities). Retention metric should be task success + return-at-need, not session length.
+- The variable reward drifts from user goals to pure time-on-app (infinite feeds without
+  caught-up states, autoplay chains, engagement-bait recommendations). That's the Dealer quadrant.
+
+**Red flags an implementation crossed the line:**
+- Users report regret after sessions ("I wasted an hour") — regret is the anti-metric of ethical habit design.
+- Loops rely on anxiety (FOMO mechanics, decaying scores, expiring streaks) rather than reward.
+- Removing the mechanic would drop engagement but users would be happier.
+- You track and celebrate metrics you would hide from users.
+
+**Disengagement design (mark of a Facilitator):** caught-up states, session summaries, usage
+insights, easy pause/export/delete, one-tap unsubscribe. Products confident in their value make
+leaving easy — which itself builds the trust that keeps people.
+
+---
+
+## Quick-Reference Checklist (per feature/loop)
+
+1. Internal trigger named and written down? (emotion → app → relief)
+2. Steps from trigger to reward minimized? (count them)
+3. Reward type matches product nature (Tribe/Hunt/Self)? Genuine variability with stopping points?
+4. Investment asked after reward, tiny, and loads the next trigger?
+5. Notification passes the "would they thank you" test, with honest defaults and controls?
+6. Manipulation Matrix quadrant = Facilitator (or consciously Entertainer)?
+7. Frequency fit: is this a habit product, or should it use scheduled-trigger retention instead?
+8. Regret check: would heavy users endorse their own usage pattern?

package/knowledge/books/influence-persuasion.md

@@ -0,0 +1,232 @@
+---
+id: influence-persuasion
+title: "Influence & Persuasion — Cialdini Applied to Design"
+category: book
+platform: both
+tags: [persuasion, social-proof, marketing, conversion, ethics]
+sources: ["Influence (Robert Cialdini)", "Pre-Suasion (Robert Cialdini)"]
+updated: 2026-07-08
+---
+
+# Influence & Persuasion — Cialdini Applied to Web & App Design
+
+Cialdini identified seven universal levers of compliance. People use mental shortcuts to decide;
+each principle is a shortcut you can honestly trigger — or dishonestly exploit. This file gives,
+for each principle: the mechanism, concrete design/copy patterns, and the ethical line.
+
+**Master rule:** Persuasion is ethical when the claim is TRUE and the user would endorse the
+tactic if they saw how it worked. If a pattern only converts because the user misunderstood
+something, it is a dark pattern. Never fabricate; only amplify what is real.
+
+---
+
+## 1. Reciprocity
+
+**Mechanism:** People feel obligated to return favors. Giving first — genuinely and without
+immediate demand — creates goodwill that converts later.
+
+**Design patterns:**
+- Give real value BEFORE the email gate: free tool, calculator, template, audit, generous free tier.
+- Order matters: deliver the value, THEN ask. "Here's your result → want it emailed / want more?"
+- Content strategy: publish your best material free; the ask (signup, trial) comes after the reader got something.
+- Free trial without credit card = a gift; credit-card-required trial reads as a trap and weakens reciprocity.
+- Onboarding: get the user to their first win before asking for permissions, referrals, or upgrades.
+- Personalize the gift where possible — a tailored report beats a generic PDF.
+
+**Copy templates:**
+- "Free [tool/template/report] — no email required." (the "no email required" line itself builds trust)
+- Post-value ask: "Glad that helped. Want [next-level thing]? It takes 30 seconds."
+
+**Dark-pattern line:** Fake gifts with hidden costs ("free" that auto-enrolls in billing),
+gifts that guilt-trip ("we gave you X, so you owe us"), or gating the promised value after
+the user already paid attention. The gift must be real and unconditional.
+
+---
+
+## 2. Commitment & Consistency
+
+**Mechanism:** People act consistently with prior commitments, especially small, voluntary,
+public, or effortful ones. Small yes → bigger yes.
+
+**Design patterns:**
+- Multi-step forms: start with the easiest, lowest-stakes question (e.g., "What's your goal?"),
+  ask for email/payment LAST. Each completed step is a micro-commitment.
+- Quiz/configurator funnels: users who invested answers rarely abandon at the results gate.
+- Onboarding: ask users to state a goal ("I want to save $200/mo") and reflect it back later
+  ("You said you wanted X — here's your progress").
+- Progress bars on signup/checkout: visible progress makes abandoning feel like a loss.
+- Ask for the tiny thing first: "Try one free lesson" beats "Start your fitness journey."
+- App stores: "Continue" onboarding flows before the paywall — users who set up a profile convert better.
+
+**Copy templates:**
+- Step-1 question: "What are you trying to [achieve]?" (identity/goal, not contact info)
+- Reflection: "Because you chose [X], we recommend [Y]."
+
+**Dark-pattern line:** Manufactured commitment (pre-checked boxes claiming "I agree to receive
+offers"), shame-based confirmshaming ("No thanks, I hate saving money"), or making cancellation
+require re-committing through hostile flows. Commitments must be freely chosen and easy to reverse.
+
+---
+
+## 3. Social Proof
+
+**Mechanism:** Under uncertainty, people copy what similar others do. Proof from "people like me"
+beats proof from celebrities or big numbers alone.
+
+**Design patterns & placement rules:**
+- Place proof AT the point of decision, not only on a testimonials page: logos under the hero,
+  a testimonial beside the pricing table, a review snippet next to the CTA button.
+- Specificity beats volume: "4.8★ from 2,341 freelancers" > "loved by millions."
+- Match proof to segment: show enterprise logos to enterprise visitors, indie testimonials to indies.
+- Testimonial anatomy: full name + photo + role/company + a SPECIFIC outcome ("cut onboarding
+  time from 3 days to 4 hours"), not "great product!"
+- Numbers: show counts only when impressive ("Join 40,000 designers"); hide when small — low
+  numbers are negative social proof. Same for review scores below ~4.3.
+- App Store: screenshots featuring rating badges and press quotes; respond to reviews (visible responsiveness is proof).
+- Case studies ordered: problem → intervention → measurable result → quote.
+
+**Copy templates:**
+- Hero subline: "Trusted by [N] [specific audience] at [recognizable names]."
+- Near CTA: "[Name], [role]: '[specific measurable result].'"
+
+**Dark-pattern line:** Fake reviews, fabricated "23 people are viewing this," invented purchase
+notifications, cherry-picked ratings presented as averages. Also illegal in many jurisdictions.
+Real-time activity feeds are fine ONLY if the data is real.
+
+---
+
+## 4. Authority
+
+**Mechanism:** People defer to credible experts. Authority = expertise signals + trustworthiness
+signals. Admitting a weakness before your strongest point paradoxically boosts credibility.
+
+**Design patterns:**
+- Credential placement: certifications, security badges (SOC 2, GDPR), and press logos belong
+  near the moments of doubt — payment forms, data-permission prompts, pricing pages.
+- Founder/team expertise: "Built by ex-[credible org] engineers" works when true and relevant.
+- Content authority: publish original data, benchmarks, teardown analyses — cite your own research.
+- Design itself is authority: typography, consistency, and polish are read as competence. A sloppy
+  UI undermines every claim on the page.
+- The trustworthy-weakness move: "We're not the cheapest — we're the most accurate." Concede a
+  real minor drawback, then pivot to your strength.
+
+**Copy templates:**
+- "Rated [X] by [independent body]." / "Featured in [publications]."
+- Weakness-pivot: "Not for [wrong audience]. Built specifically for [right audience]."
+
+**Dark-pattern line:** Fake badges, invented awards, "as seen in" logos from paid placements
+dressed as editorial, actor "doctors." Borrowed authority must be genuine and verifiable.
+
+---
+
+## 5. Liking
+
+**Mechanism:** People say yes to those they like: similar to them, familiar, complimentary,
+cooperative toward shared goals.
+
+**Design patterns:**
+- Write like the customer talks. Mirror the audience's vocabulary (mine reviews, support tickets,
+  Reddit threads for verbatim phrases) — similarity through language.
+- Show real humans: team photos, founder notes, signed emails. Faces increase trust and liking.
+- Brand voice: warm, specific, occasionally imperfect beats corporate-neutral. Microcopy is a
+  liking channel (error messages, empty states, loading text).
+- About page is a conversion page: story, values, faces. Link it from checkout-adjacent doubt moments.
+- Imagery: show people who look like the target segment using the product.
+
+**Copy templates:**
+- Empathy-first opener: "You've tried [thing they tried]. It didn't stick. Here's why."
+- Founder note near pricing: "I built this because [genuine shared frustration]."
+
+**Dark-pattern line:** Fake personalization ("Hey {first_name}, I was just thinking about you"),
+simulated humans (bots posing as people), flattery scripts. Liking must come from genuine
+resonance, not impersonation.
+
+---
+
+## 6. Scarcity
+
+**Mechanism:** People value what is rare or disappearing; loss framing outweighs gain framing.
+Scarcity works via FOMO — and misfires into distrust the instant it looks fake.
+
+**Design patterns (ONLY when true):**
+- Real limits: cohort start dates, limited seats, genuinely expiring launch pricing, inventory counts.
+- Loss framing in copy: "Don't lose your 20% founding-member rate" > "Get 20% off."
+- Deadline mechanics: show the actual date ("Price increases March 1"), not a cookie-reset countdown.
+- Exclusivity as scarcity: waitlists and invite systems create honest scarcity when capacity is real.
+- App pricing: grandfathering ("lock in this price before v2") is honest scarcity.
+
+**Copy templates:**
+- "[N] seats left for the [date] cohort."
+- "Founding-member pricing ends [real date]. After that, $[higher price]."
+
+**Dark-pattern line — the brightest line in this file:** Countdown timers that reset on refresh,
+"only 2 left" on digital goods, evergreen "sales," fake deadlines. These convert short-term and
+destroy trust permanently; sophisticated audiences screenshot and shame them. If the scarcity
+isn't real, do not ship it.
+
+---
+
+## 7. Unity (Pre-Suasion's addition)
+
+**Mechanism:** Beyond liking — shared identity. "One of us" (profession, location, values,
+struggle) is the deepest lever. People don't just like their in-group; they self-persuade for it.
+
+**Design patterns:**
+- Identity-first headlines: "For indie iOS developers" outperforms generic benefit claims with
+  that audience — name the tribe above the fold.
+- Community as product surface: forums, Discord, user showcases; belonging drives retention.
+- Co-creation: beta programs, feature voting, "built with our users" — co-creators become advocates.
+- Values signaling when authentic: open-source, privacy-first, sustainability — stated plainly, proven with actions.
+- Segment-specific landing pages per tribe rather than one generic page.
+
+**Copy templates:**
+- "Made by [tribe], for [tribe]."
+- "Join [N] [tribe members] who [shared behavior]."
+
+**Dark-pattern line:** Astroturfed community, appropriating identities/causes the brand doesn't
+live, us-vs-them fear-mongering. Unity claims are audited hard by real members of the tribe.
+
+---
+
+## Pre-Suasion: The Moment Before the Message
+
+Pre-Suasion's core insight: what a person attends to IMMEDIATELY BEFORE a request shapes their
+response more than the request itself. Design controls attention sequence — use it.
+
+**Application rules:**
+1. **Prime the relevant frame before the ask.** Before a pricing page, show ROI/results content
+   (achievement frame). Before a security product's CTA, show the threat landscape (safety frame).
+2. **Openers set the channel.** A hero image of comfort primes comfort-seeking; an image of speed
+   primes efficiency evaluation. Choose hero imagery by the mindset you need at the CTA.
+3. **Questions are primes.** A pre-signup quiz asking "How much time do you lose to X weekly?"
+   makes the cost of the problem salient before the solution appears.
+4. **Section order is a persuasion decision.** Standard priming order for a landing page:
+   problem salience → possibility (demo/outcome) → proof → offer → scarcity/urgency (if true) → CTA.
+5. **Attention = importance.** Whatever you make prominent, users assume matters. Don't give
+   prime real estate to secondary messages.
+6. **The moment after "yes" is privileged.** Post-signup and post-purchase screens are peak
+   receptivity: ask for the referral, the review, or the deeper commitment there — not before.
+
+---
+
+## Quick-Reference: Principle → Placement Map
+
+| Page zone | Primary principles |
+|---|---|
+| Hero | Unity (name the tribe), Authority (one credibility marker) |
+| Below hero | Social proof (logos/counts) |
+| Feature sections | Reciprocity (show, teach, give), Pre-suasive ordering |
+| Pricing | Authority (badges), Social proof (testimonial per tier), Scarcity (if true) |
+| Checkout/signup | Commitment (progress), Authority (security), Liking (human microcopy) |
+| Post-conversion | Reciprocity return-ask, Unity (welcome to the tribe), reviews/referrals |
+| Onboarding | Commitment (goal-setting), Reciprocity (fast first win) |
+
+## Ethics Checklist (run before shipping any persuasion pattern)
+
+1. Is every factual element true and verifiable?
+2. Would the user endorse this tactic if we explained it to them?
+3. Does it still convert if the user is fully informed? (If not, it's deception.)
+4. Is the reverse action (unsubscribe, cancel, decline) as easy as the forward action?
+5. Are we amplifying a real strength, or manufacturing a false signal?
+
+Fail any one → redesign the pattern.

package/knowledge/books/positioning-messaging.md

@@ -0,0 +1,178 @@
+---
+id: positioning-messaging
+title: "Positioning & Messaging — Ries/Trout + Dunford Applied to Design"
+category: book
+platform: both
+tags: [positioning, messaging, strategy, homepage, category-design]
+sources: ["Positioning: The Battle for Your Mind (Al Ries & Jack Trout)", "Obviously Awesome (April Dunford)"]
+updated: 2026-07-08
+---
+
+# Positioning & Messaging — From Strategy to Homepage
+
+Positioning is the input; messaging, homepage, hero, and nav are outputs. If the homepage is
+hard to write, the positioning is broken — fix upstream first. This file: Ries & Trout's laws
+of the mind, Dunford's process for finding a position, and exact rules for translating a
+position into page decisions.
+
+---
+
+## Part 1 — Ries & Trout: How Minds Work (the constraints)
+
+Positioning happens in the PROSPECT'S mind, not in the product. The mind is the battlefield;
+these are its laws:
+
+1. **Minds are overloaded and simplify.** They store one or two words per brand ("Volvo =
+   safety"). Your positioning must compress to a phrase a distracted person retains.
+2. **Minds rank by ladders.** Each category is a mental ladder; buyers remember ~2-3 rungs.
+   If you're not top-3 in the prospect's category ladder, you're invisible in that category.
+3. **First beats better.** The first product IN THE MIND owns the category. You can't out-shout
+   an incumbent with "we're better" — minds reject contradiction of what they already believe.
+4. **If you can't be first, create a category you CAN be first in.** Reframe: not "another CRM"
+   but "the first CRM for solo consultants." Narrowing is how small players win.
+5. **Position against the leader, don't imitate.** Classic moves: the opposite ("the un-cola"),
+   the honest underdog ("we try harder"), the specialist vs. the generalist.
+6. **Line extension dilutes.** Each additional claim weakens the core one. A brand that means
+   everything means nothing — this kills homepages that list eight value props.
+7. **You cannot reposition yourself with words alone.** The mind keeps its first impression;
+   repositioning requires changing category, audience, or the competitor you're contrasted with.
+
+**Design consequence:** every page has ONE positioning job. The hero states one claim; everything
+below supports that single claim. Multiple audiences → multiple landing pages, not one crowded page.
+
+---
+
+## Part 2 — Dunford: Positioning as Process (Obviously Awesome)
+
+Dunford's definition: positioning = context-setting. The same product is "obviously awesome" in
+the right frame and mediocre in the wrong one. Five components, derived in strict order because
+each feeds the next:
+
+1. **Competitive alternatives** — what customers would ACTUALLY do without you. Includes
+   spreadsheets, interns, "do nothing" — not just named competitors. Ask real customers.
+2. **Unique attributes** — features/capabilities you have that the alternatives lack.
+   Only counts if true relative to the alternatives from step 1.
+3. **Value (and proof)** — the customer outcome each unique attribute enables, with evidence.
+   Attribute → benefit → measurable value. Cluster into 1-3 value themes.
+4. **Target market characteristics** — the buyers who care MOST intensely about that value:
+   who feels the pain hardest, buys fastest, churns least. Narrow beats broad.
+5. **Market category** — the frame you declare, chosen because it makes your value obvious
+   and triggers the right assumptions (pricing, competitors, features expected).
+   (+ optional 6th: **relevant trend** — only if it connects genuinely; trend without category
+   fit reads as hype.)
+
+### Dunford's 10-step method, condensed
+
+1. Understand the customers who love you — study best-fit customers, not the average.
+2. Form a positioning team — cross-functional (sales, product, marketing, founders); positioning by marketing alone fails.
+3. Drop positioning baggage — set aside "what we always said we were"; evaluate from zero.
+4. List true competitive alternatives — from the customer's view, including status quo/manual work.
+5. Isolate unique attributes — what you have that those alternatives don't.
+6. Map attributes to value themes — so what? for each attribute; group into 1-3 themes.
+7. Identify who cares most — the segment where the value is a hair-on-fire problem.
+8. Choose a market frame of reference — pick the category (see styles below).
+9. Layer on a relevant trend (optional) — trend + category, never trend alone.
+10. Capture and operationalize — a positioning canvas that drives messaging, sales decks, pricing, site, roadmap.
+
+### Three category-framing styles (step 8 choices)
+
+- **Head-to-head:** compete in an existing category to win it. Choose when you can plausibly
+  be a top player. Homepage says the category plainly and claims leadership on one axis.
+- **Big fish, small pond (subsegment):** dominate a niche of an existing category — "CRM for
+  real estate teams." The default choice for most startups. Homepage names the niche in the headline.
+- **Create a new category:** declare a new game where you're first (Ries & Trout's law 4).
+  Expensive — you must fund the education of the market. Choose only with resources, evangelism
+  capacity, and a genuinely new problem frame. Homepage must teach the problem before the product.
+
+---
+
+## Part 3 — Positioning → Homepage Decisions (the payoff)
+
+A visitor gives a homepage ~5 seconds to answer three questions: What is it? Is it for me?
+Why this one? Positioning components map directly:
+
+| Positioning component | Page element it drives |
+|---|---|
+| Market category | Headline noun / "What is it" clarity; nav labels; SEO page titles |
+| Target segment | "Is it for me" — hero subline or headline qualifier; imagery; social proof selection |
+| Value themes (top 1) | Headline claim / primary benefit |
+| Value themes (2-3) | The three feature/benefit sections below the fold |
+| Unique attributes | "How it works" / differentiator section; comparison page |
+| Competitive alternatives | Objection-handling copy; "Why not just use a spreadsheet?" section; comparison pages |
+| Proof of value | Testimonials/metrics placed beside each value claim |
+| Trend (if used) | Blog/announcement layer, not the hero |
+
+### Hero formulas by positioning maturity
+
+- **Unknown category or new category:** lead with clarity, not cleverness.
+  `[Category] that [key differentiated value] for [segment]`
+  e.g., "The invoicing tool that chases late payers for you — built for freelancers."
+- **Known category, subsegment play:**
+  `[Category] for [segment]` + subline carrying the #1 value theme.
+- **Head-to-head:**
+  `[Bold claim on your winning axis]` + subline naming category + proof.
+- **Category creation:**
+  Problem-reframe headline (`Stop [old-way pain]`) + subline declaring the new category.
+
+**Rules:**
+- The headline carries ONE value theme. Themes 2-3 get their own sections; never stack three benefits into one hero.
+- If a stranger can't say what the product is after reading only the hero, the hero fails —
+  clarity outranks distinctiveness, which outranks cleverness.
+- Vague aspirational heroes ("Unlock your potential") are positioning failures rendered in type.
+
+### Navigation as positioning
+
+- Nav labels declare category vocabulary: "Solutions for [segment A] / [segment B]" signals a
+  multi-segment platform; a single "Product" link signals a focused tool. Choose deliberately.
+- Persona- or use-case-based nav ("For agencies," "For in-house teams") = big-fish positioning made navigable.
+- A "Compare" or "vs" section in nav/footer = head-to-head posture; include competitor and
+  alternative-method pages ("[Product] vs spreadsheets") because "do nothing" is the biggest rival.
+- Pricing page visibility is a positioning signal: visible self-serve pricing = product-led,
+  SMB frame; "Contact sales" = enterprise frame. Mismatch confuses the category read.
+
+### Page-per-position rule
+
+One page = one segment = one ladder. When targeting multiple segments:
+- Homepage carries the broadest true position and routes quickly to segment pages.
+- Each segment landing page re-runs the full formula (their alternatives, their value words,
+  their proof) — not a find-and-replace of the persona name.
+- Ad/App-Store traffic should land on the matching segment page, never the generic homepage.
+
+### App Store / marketplace positioning
+
+- App name + subtitle = category + differentiator in ~60 characters. Subtitle is your positioning
+  statement compressed: "[category] for [segment]" or "[category] that [unique value]."
+- Screenshot 1 must answer "what is it" with the category frame; screenshots 2-4 carry value
+  themes in priority order; captions are positioning copy, not feature labels.
+- Keyword strategy follows the category choice: subsegment plays win niche keywords they can
+  rank #1 for (ladders again) rather than losing on the big category term.
+
+---
+
+## Part 4 — Diagnostics & Anti-patterns
+
+**Signs the positioning is broken (fix strategy before touching design):**
+- The team can't finish "It's a [category] for [segment] that [value]" in one breath, identically.
+- The homepage headline is an aspiration or pun rather than a claim.
+- Sales calls start with 10 minutes of "so what exactly is it?"
+- Best customers describe the product in different words than the website does. (Their words win — rewrite the site with them.)
+- Traffic converts differently by source for the "same" audience — the page frames the wrong category for some entrants.
+
+**Anti-patterns:**
+1. **The everything hero** — three value props in one headline (violates line-extension law).
+2. **Category cowardice** — refusing to name a category so as "not to be boxed in"; visitors box
+   you anyway, into the wrong box.
+3. **Premature category creation** — inventing "Revenue Intelligence Orchestration" with no
+   budget to teach it; big-fish-small-pond was available and cheaper.
+4. **Positioning against yourself** — copying the leader's message and layout, which only
+   reinforces the leader's rung (minds reject me-too claims).
+5. **Feature-first messaging** — attributes without the value translation (Dunford step 6 skipped);
+   every feature section needs its "so that…" clause.
+6. **Ignoring the do-nothing competitor** — no copy addressing "why change at all"; for most
+   products, inertia beats every named rival.
+
+**Quarterly positioning audit (run before any redesign):**
+1. Interview 5 best-fit recent customers: what were you doing before? what would you use if we vanished? what nearly stopped you buying?
+2. Rebuild the 5-component canvas from those answers.
+3. Diff canvas vs. current homepage hero, nav, and section order.
+4. Rewrite top-down: headline → subline → section order → proof placement → nav labels.