Landing Page Qualification Review
Use the shared quality bar in ../references/output-standard.md and ../references/skill-design-principles.md when those files are available.
Use this skill when
- the user shares lead source, CRM stage, sales note, form, landing page or campaign data tied to landing page qualification review.
- the next decision could change targeting, qualification, scoring, follow-up, sales handoff or budget.
- lead volume looks acceptable but SQL, opportunity, closed-won, rejection or response-speed data raises doubt.
Do not use this skill for broad lead-generation advice without source, CRM, sales or qualification evidence. Use it when a real B2B lead quality decision is on the table.
Required input
- business model, ICP, offer, ACV or deal value range, sales cycle and main conversion goal.
- ad, landing page, lead form, CRM, call note, email or campaign data relevant to this diagnostic.
- time window, traffic source, lead volume and downstream outcomes where available.
- what decision the user is trying to make next: create, fix, scale, pause, brief sales or investigate.
- If an input is missing, continue with a clearly marked assumption instead of inventing data.
Analysis workflow
- Identify what the page qualifies for: budget, urgency, company fit, role fit, pain, use case or implementation readiness.
- Check whether the hero and offer attract the right buyer or just any interested visitor.
- Review the form, proof, objections and CTA for qualification signals or lack of friction.
- Compare page promise with sales acceptance, disqualification reasons and lead-to-opportunity drop-off.
- Recommend qualification copy, form, proof or CTA changes that improve lead quality without adding unnecessary friction.
Decision rules
- If the data does not connect to revenue, pipeline, qualified leads or conversion quality, label the recommendation as a hypothesis.
- If platform metrics and downstream data disagree, trust the downstream source for business quality and platform data for delivery mechanics.
- If the issue could be tracking, offer, audience, page or follow-up, do not collapse it into one cause without evidence.
- Do not recommend more budget until lead quality, follow-up and tracking confidence are separated.
Output format
| Finding |
Evidence |
Lead quality impact |
Recommended action |
Confidence |
| Specific diagnostic claim |
Data, screenshot, report, note or missing-data marker |
Business or signal consequence |
Smallest useful next step and owner |
High / Medium / Low |
End with:
Decision: fix / test / monitor / ask for data / do not act yetApproval needed: yes/no and what would change if approvedMissing data: only the inputs that would materially change the recommendation
Practical example
User: "Here are CRM stages, source data and sales notes for landing page qualification review. What should we change before the next campaign move?"
Assistant should: judge the page on who it filters out, not on who it attracts, and stop at the qualification changes worth testing.
Guardrails
- Do not make changes to live campaigns, pages, tags, containers, CRM fields or customer messages.
- Do not claim performance impact without evidence.
- Mark missing data clearly.
- Keep recommendations practical for a performance operator, founder or owner with a real advertising problem.
1---2name: landing-page-qualification-review3description: Diagnoses whether the page attracts the right leads or just more leads. Use when the page fills the pipeline with the wrong people, or before sending paid traffic to it.4---56# Landing Page Qualification Review78Use the shared quality bar in `../references/output-standard.md` and `../references/skill-design-principles.md` when those files are available.910## Use this skill when1112- the user shares lead source, CRM stage, sales note, form, landing page or campaign data tied to landing page qualification review.13- the next decision could change targeting, qualification, scoring, follow-up, sales handoff or budget.14- lead volume looks acceptable but SQL, opportunity, closed-won, rejection or response-speed data raises doubt.1516Do not use this skill for broad lead-generation advice without source, CRM, sales or qualification evidence. Use it when a real B2B lead quality decision is on the table.1718## Required input1920- business model, ICP, offer, ACV or deal value range, sales cycle and main conversion goal.21- ad, landing page, lead form, CRM, call note, email or campaign data relevant to this diagnostic.22- time window, traffic source, lead volume and downstream outcomes where available.23- what decision the user is trying to make next: create, fix, scale, pause, brief sales or investigate.24- If an input is missing, continue with a clearly marked assumption instead of inventing data.2526## Analysis workflow27281. Identify what the page qualifies for: budget, urgency, company fit, role fit, pain, use case or implementation readiness.292. Check whether the hero and offer attract the right buyer or just any interested visitor.303. Review the form, proof, objections and CTA for qualification signals or lack of friction.314. Compare page promise with sales acceptance, disqualification reasons and lead-to-opportunity drop-off.325. Recommend qualification copy, form, proof or CTA changes that improve lead quality without adding unnecessary friction.3334## Decision rules3536- If the data does not connect to revenue, pipeline, qualified leads or conversion quality, label the recommendation as a hypothesis.37- If platform metrics and downstream data disagree, trust the downstream source for business quality and platform data for delivery mechanics.38- If the issue could be tracking, offer, audience, page or follow-up, do not collapse it into one cause without evidence.39- Do not recommend more budget until lead quality, follow-up and tracking confidence are separated.4041## Output format4243| Finding | Evidence | Lead quality impact | Recommended action | Confidence |44|---|---|---|---|---|45| Specific diagnostic claim | Data, screenshot, report, note or missing-data marker | Business or signal consequence | Smallest useful next step and owner | High / Medium / Low |4647End with:4849- `Decision:` fix / test / monitor / ask for data / do not act yet50- `Approval needed:` yes/no and what would change if approved51- `Missing data:` only the inputs that would materially change the recommendation5253## Practical example5455User: "Here are CRM stages, source data and sales notes for landing page qualification review. What should we change before the next campaign move?"5657Assistant should: judge the page on who it filters out, not on who it attracts, and stop at the qualification changes worth testing.5859## Guardrails6061- Do not make changes to live campaigns, pages, tags, containers, CRM fields or customer messages.62- Do not claim performance impact without evidence.63- Mark missing data clearly.64- Keep recommendations practical for a performance operator, founder or owner with a real advertising problem.
mardab96