Sales Funnel Blueprint

Turns an offer into a build-ready sales funnel spec: which pages you need (landing, checkout, upsell, thank-you, error), what each page must say and collect, the price ladder from entry offer to back end, and the metric targets each step has to hit. It picks a funnel shape based on price point, traffic source, and awareness level, and insists on instrumentation like server-side purchase events and carried-through click IDs before launch. The strongest part is the forced inputs step: it won't design until it knows the offer, traffic source, and fulfilment, and it flags conflicts like a $2,000 offer on cold TikTok traffic with instant checkout. The benchmark ranges are starting points only, so treat them as a sanity check rather than targets. Handy when you're planning a launch and want the page list and measurement plan written down before touching a page builder.

skills.sh installs: 120.4K
GitHub stars: 8
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add autonnel/autonnel-skills --skill sales-funnel-blueprint --agent claude-code

Installs into .claude/skills of the current project.

Files

Sales Funnel Blueprint

Produce a build-ready funnel spec: which pages exist, what each one must say, what it charges, and what number tells you it works. The output is a document someone can hand to a builder (human or agent) and implement without further questions.

When to use

"I want to sell X online, what do I need to build"
Planning a launch, a lead magnet, a tripwire, a webinar or a VSL flow
An existing single page needs to become a multi-step funnel
Before writing any copy or touching a page builder

When not to use

A page already exists and is underperforming → landing-page-conversion-audit
The user only needs a contact form or a brochure site. Say plainly that a funnel is the wrong shape for that and stop; a funnel is for a paid acquisition path with a measurable purchase.