Mmcp.market

scorecard-marketing skill

by wondelai·wondelai/skills·2.3k stars·MIT

Build quiz and assessment funnels that generate qualified leads at 30-50% conversion. Use when the user mentions "quiz funnel", "scorecard", "lead magnet", "score-based segmentation", or "lead qualification". Also trigger when designing self-assessment tools, building calculators or graders for marketing, or creating personalized result pages that drive conversions. Covers concept hooks, question design, dynamic results by tier, and automated follow-up sequences. For landing page conversion, see cro-methodology. For full marketing plans, see one-page-marketing.

A100/100content scan

Is the scorecard-marketing skill safe?

Clean: nothing in its files matched our rules. We read 5 files in the folder on 2026-09-28.

No findings.

Install the scorecard-marketing skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/marketing-cro/skills/scorecard-marketing ~/.claude/skills/scorecard-marketing
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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).

Scoring

Goal: 10/10. Score a funnel against the six Quick Diagnostic rows: score = round(satisfiedrows / 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:

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 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:

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 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 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: prospects scoring "strong foundations with room to improve" convert best
  • PDF reports (personalized cover, detailed recommendations) extend value and travel into sales meetings
  • Different CTAs per tier: Low → free event; Medium → book + discovery call; High → direct consultation

Product applications:

Copy patterns:

  • "Your [Topic] Score is [X]/[Total]. Here's what that means..."
  • Low tier: "This area needs attention. Here are easy first steps... Our team specializes in helping people at your stage."
  • High tier: "Excellent foundation! Focus on maintaining standards. We work with advanced clients like yourself on [specific advanced offer]."

Ethical boundary: Never inflate or deflate the computed score to steer a prospect toward the offer — the tier must reflect their actual answers.

See references/technical-implementation.md when building the actual tool — scoring/weighting logic, conditional content rules, PDF generation, and platform comparison.

4. Sales and Marketing

Core concept: Turn assessment data into a systematic engine: promotion drives traffic to the landing page, while follow-up sequences segment leads by score tier and nurture them toward a conversion event.

Why it works: Scorecard leads arrive with self-reported pain points, qualification signals, and scores — sales conversations shift from discovery to recommendation, and automated segmentation gives every lead relevant follow-up.

Key insights:

  • Promote via LinkedIn polls, Facebook/Google ads, email lists, podcast CTAs, book QR codes
  • Fire the results email + PDF immediately after completion; send abandon emails to recover incomplete starts
  • Segment nurture campaigns by tier — not one-size-fits-all drip
  • Multi-step funnels for high-ticket: Stage 1 (8-15 questions, basic score), Stage 2 (15-25, detailed report), Stage 3 (30-50, baseline + roadmap)

Product applications:

Copy patterns:

  • "Take the [Topic] Scorecard" as a universal CTA across all channels
  • Results email: "Your [Topic] Score is ready. Here's what we recommend based on your results."
  • Nurture: "Last week you scored [X] on [category]. Here are 3 ways to improve that score this month."

Ethical boundary: Never weaponize self-reported pain points to pressure a prospect — the data they volunteered is for tailoring help, not for manufacturing urgency.

See references/analytics-optimization.md when a live funnel underperforms or you're setting up tracking — key metrics, what to A/B test, funnel-drop analysis, CRM integration, and lead scoring.

Scorecard Naming Strategy

Effective names combine topic clarity, outcome promise, and brevity.

Formulas:

  • "The [Topic] Scorecard" — "The Business Growth Scorecard"
  • "[Outcome] Readiness Assessment" — "Leadership Readiness Assessment"
  • "What's Your [Topic] Score?" — "What's Your Marketing Score?"
  • "The [Adjective] [Topic] Quiz" — "The Complete Wellness Quiz"

Conversion Benchmarks

  • Traditional PDF lead magnets: 3-10% conversion
  • Scorecard/quiz funnels: 30-50% conversion
  • Top performers: 70%+ with optimized landing pages

Psychology Behind Why This Works

  1. Tension creation: Questions surface dormant desires
  2. Reciprocity: You gave value (insights), they're open to conversation
  3. Self-qualification: They told you their problems and budget
  4. Personalization: people willingly trade data for a tailored result, then expect the offer to match it (the supporting stats live in references/psychology.md)
  5. Gamification: Primal drive to score, rank, and improve
  6. Commitment: Time invested increases follow-through

Implementation Checklist

  1. [ ] Define ideal customer and their desired outcome
  2. [ ] Choose a concept hook (one of the 5 types from the Landing Page section)
  3. [ ] Write 2-7 scoring categories based on your methodology
  4. [ ] Create 10-40 questions with point values
  5. [ ] Set up 3 scoring tiers with dynamic content
  6. [ ] Write landing page with 3 Cs (Clarity, Credibility, Connection)
  7. [ ] Configure lead form fields
  8. [ ] Set up automated email with results
  9. [ ] Create follow-up sequence by tier
  10. [ ] Test with 5-10 people before launch

Common Mistakes

Quick Diagnostic

More skills from wondelai/skills

  • A37signals-wayBuild 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.
  • A37signals-wayBuild 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.
  • A37signals-wayBuild 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.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Ablue-ocean-strategyCreate 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.
  • Ablue-ocean-strategyCreate 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.
  • Ablue-ocean-strategyCreate 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.
  • Aclean-architectureStructure 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.
  • Aclean-architectureStructure 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.
  • Aclean-architectureStructure 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.

All agent skills → · MCP servers