Skip to main content
Skill Gallery
Conversion Paths Marketing And Content Combo

Landing Page Scorecard Funnel

A scorecard funnel is not just a quiz. It is a landing page, questionnaire, dynamic results page, and routing system. This skill gives agents the operating playbook and cites the source lineage behind it.

Sources

2

Refs

2

Steps

6

Outputs

3

What It Does

Use it when the job needs a real procedure.

Build an online assessment or diagnostic quiz.

Replace a generic lead magnet with a scorecard.

Qualify leads before a sales call.

Segment coaching, consulting, agency, SaaS, education, or service prospects.

Improve a landing page that collects emails but does not capture intent.

Outputs

funnel mapquestionnairerouting plan

The page is for humans first. The files in the rail make the same procedure available to agents.

Try It

Start with one of these prompts.

Design a scorecard funnel for this offer and ICP.

Try in BuildOS

Audit this landing page and tell me where the qualification path breaks.

Try in BuildOS

Procedure

The operating path

  1. 1

    Mode selection (run this first). Pick a mode before drafting — see Judgment for the standalone vs. setup-layered decision and its diagnostic.

  2. 2

    If setup-layered, load landing_page_scorecard_funnel.setup_layer_positioning and draft the four-part positioning layer (market insight → alternatives analysis → perfect-world scenario → then the scorecard) before writing any scorecard copy.

  3. 3

    Load landing_page_scorecard_funnel.funnel_build_specs and build the five landing-page sections in order: hook (form chosen by mode), assessment promise, differentiated-value proposition, credibility, CTA stack.

  4. 4

    Design the questionnaire to the 15-question spec in the same reference: contact capture, 10 best-practice scoring questions, Big 5 qualification questions.

  5. 5

    Design the dynamic results page and the high-fit / middle-fit / low-fit routing per the same reference.

  6. 6

    Assemble the deliverable using the Contract below.

Boundaries

What the skill refuses or checks carefully

Do not ask for more data than needed.

Do not make phone mandatory unless the funnel truly depends on phone contact.

Do not sell the product before the assessment promise is clear.

Do not route every respondent to the same CTA.

Do not call the results personalized if the page ignores the answers.

Do not hide the payoff behind vague "learn more" language.

Examples

Runtime examples

Worked Example

  • _Delivery handoffs_ — vs. "buy another PM tool": tools don't fix undefined handoffs; the score shows whether your problem is process or software.
  • _Owner dependency_ — vs. "hire an ops director": a $90k hire inherits the same chaos; the score shows what must be systematized before a hire can stick.
  • _Capacity & scope visibility_ — vs. "just push harder / do nothing": shows the margin leaking through unpriced scope creep.
  • _Contact capture:_ name (required), email (required), location inferred — not asked; phone optional at capture (require it at call booking instead, where the funnel actually depends on it).

Related Skills