scorecard-marketing
Scorecard Marketing builds interactive quiz and assessment funnels designed to generate qualified leads through psychological engagement. Use this skill when creating lead magnets, quiz funnels, assessment tools, or score-based segmentation systems that drive conversions through personalized result pages and automated follow-up sequences. The system applies a proven 4-step methodology covering landing page design, question architecture, dynamic scoring by tier, and conversion optimization, achieving 30-50% conversion rates compared to 3-10% for traditional PDF lead magnets.
git clone --depth 1 https://github.com/wondelai/skills /tmp/scorecard-marketing && cp -r /tmp/scorecard-marketing/plugins/marketing-cro/skills/scorecard-marketing ~/.claude/skills/scorecard-marketingSKILL.md
# Scorecard Marketing Skill
A proven 4-step system for generating qualified leads through interactive assessments that arrive with rich data about each prospect.
## Core Principle
**Everything is downstream from lead generation.** People buy to resolve psychological tension between their current reality and desired reality — a scorecard awakens dormant desires by asking revealing questions.
**The foundation:** Active searchers are harder to sell to (already decided, set budget); people with dormant desires buy from whoever helped them uncover the need. Interactive assessments create psychological engagement static content cannot — which is why they convert several times better than a PDF download (see [Conversion Benchmarks](#conversion-benchmarks)).
## Scoring
**Goal: 10/10.** Score a funnel against the six [Quick Diagnostic](#quick-diagnostic) rows: `score = round(satisfied_rows / 6 × 10)`. Read the bands as: **9-10** = all six pass (dormant-desire hook, email captured first, scored categories, unique per-tier content and CTA, tier-segmented follow-up); **5-7** = the funnel exists but generic results or late email capture cost it 2-3 rows; **≤3** = no concept hook or no scoring. Always give the current score and the specific rows to close to reach 10/10.
## The 4-Step Scorecard System
### 1. Landing Page
**Core concept:** The landing page exists for one purpose: get visitors to start the questionnaire. It must create enough curiosity and promise enough value that clicking "Start" feels irresistible.
**Why it works:** A concept hook taps a dormant desire; framing around a score triggers the primal drive to measure, rank, and improve. Curiosity plus low commitment ("takes 3 minutes") removes friction.
**Key insights:**
- The concept hook is the single most important element — it defines what visitors score themselves on. The 5 hook types: **moving toward** (goal), **pain removal**, **readiness** (decision validation), **category** (compare yourself to a standard), **knowledge** (test what you know)
- "Moving toward" hooks ("Are you ready to [goal]?") outperform fear-based hooks
- The 3 Cs — Clarity, Credibility, Connection — must all be present
- Bonuses (free book, consultation, report) lift completion; a time expectation ("less than 3 minutes") reduces abandonment
**Product applications:**
| Context | Landing Page Element | Example |
|---------|---------------------|---------|
| **Concept hook** | Frame around a score visitors want | "What's Your Marketing Score?" |
| **Moving toward** | Goal-oriented hook | "Are you ready to scale your business?" |
| **Readiness check** | Decision validation hook | "Should you launch a second location? Complete this checklist" |
**Copy patterns:**
- "[HEADLINE: Concept hook + promise] Are you ready to [desired outcome]?"
- "Answer [X] quick questions to discover [specific insight] and get personalized recommendations"
- "[CTA BUTTON] Start the Quiz (Takes less than 3 minutes)"
**Ethical boundary:** The hook must promise value the assessment actually delivers — never bait-and-switch into a sales pitch disguised as results.
See [references/industry-examples.md](references/industry-examples.md) when you need a starting hook for a specific niche — 50+ scorecard concepts and landing-page headlines across industries.
### 2. Questionnaire
**Core concept:** The questionnaire collects lead data while providing a gamified experience: capture contact information first, then ask scored questions grouped into categories that surface pain points, desires, and qualification signals.
**Why it works:** People enjoy answering questions about themselves (self-referential encoding), and capturing email before questions retains the lead even on abandonment. Scored categories make results feel scientific, increasing trust in the recommendations.
**Key insights:**
- Lead capture form goes first (name, email, optional phone)
- Question count scales with funnel stage: 8-15 cold-to-warm, 20-50 warm-to-sales, 30-150 client-to-fan
- Group questions into 2-7 measurable categories; assign 1-5 points per answer, weighting significant answers higher
- Add qualifying questions (budget, urgency, company size) in an "Uncategorised" group
- Avoid salesy, leading, lookup, and jargon questions
**Product applications:**
| Context | Question Type | Example |
|---------|--------------|---------|
| **Yes/No** | Checklist items | "Do you work out 3+ times/week?" |
| **Sliding scale** | Degree/frequency | "How important is X to you?" |
| **Open text** | Rare — slows completion | "What has stopped you in the past?" |
**Copy patterns:**
- Use "you" language: "How confident are you in your..." not "Rate your confidence level in..."
- Progress indicators ("Question 5 of 12") reduce abandonment; "Almost done!" maintains momentum
- Category names should be meaningful to the respondent, not internal jargon
**Ethical boundary:** Don't collect data you won't use to improve their results — every qualifying question (budget, urgency, size) must visibly shape the recommendation, not just route them to sales.
See [references/psychology.md](references/psychology.md) when writing or critiquing questions — the tension taxonomy (pain/desire/frustration), the 4-6 quantification sweet spot, and the personalization stats.
### 3. Results Page
**Core concept:** The results page delivers personalized value based on the respondent's score, creating tension between where they are and where they could be, with a clear next step calibrated to their tier.
**Why it works:** Scored, personalized results feel more valuable than generic advice and trigger the drive to improve (see [Psychology](#psychology-behind-why-this-works) below).
**Key insights:**
- Show overall score plus category breakdown to highlight strengths and weaknesses
- Write dynamic content per tier — default Low / Medium / High; custom tiers ("Startup / Scaleup / Performer / Unicorn") increase engagement
- The sweet spot: prospBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "conversion funnel", "increase signups", or "people add to cart but dont buy". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.