Skill 詳細
sales-funnel-blueprint
Designs measurable sales funnels and conversion paths.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
--- name: sales-funnel-blueprint description: Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online. --- # 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. ## Step 1: pin the inputs Do not design before you have these five. Ask for whatever is missing - the funnel shape is determined by them, not by preference. | Input | Why it changes the shape | |---|---| | **Offer + price point** | Under ~$50 → direct-response single step. $50-500 → landing + checkout + upsell. $500+ → lead capture + call booking, not instant checkout. | | **Traffic source** | Paid social = cold, needs the full pitch on the page. Search = warmer, shorter page. Email list = shortest. Affiliate = needs a distinct pre-sell. | | **Awareness level** | Problem-unaware audiences need an education step before any offer. Solution-aware can go straight to the offer. | | **Fulfilment** | Digital = instant delivery, upsells easy. Physical = shipping costs, returns, delivery expectations to set. Service = booking calendar, not checkout. | | **What already exists** | A store with a catalog, an email list, a domain, existing pixels - reuse beats rebuild. | If the price point and the traffic source conflict (e.g. $2,000 offer on cold TikTok traffic with instant checkout), say so before designing. That conflict, not the page design, is what will fail. ## Step 2: pick the shape Choose one, then adapt. Do not invent a novel funnel shape for a standard offer. | Shape | Steps | Fits | |---|---|---| | **Direct offer** | LP (with offer) → checkout → thank-you | Impulse price, solution-aware traffic, single SKU | | **Tripwire → core** | LP → low-price checkout → one-click upsell to core → thank-you | Cold paid traffic; buys the customer cheaply, monetizes on step 2 | | **Lead magnet → nurture** | Opt-in LP → thank-you/delivery → email sequence → offer LP | Long consideration, or offer needs trust built first | | **VSL / long-form** | VSL LP → checkout (revealed after N minutes or below fold) → upsell chain | Info products, $100-2,000, cold traffic | | **Application** | LP → qualification form → booking page → confirmation | $500+ services, sales-call close | | **Store funnel** | Ad → product LP → checkout → post-purchase upsell → order confirmation | Ecommerce with an existing catalog | ## Step 3: spec each page For every page in the chosen shape, produce this block. Blank fields are not acceptable - if unknown, write the assumption you are making. ``` ### <Page name> - type: LANDING | CHECKOUT | UPSELL | THANKYOU | ERROR Goal (one action): Traffic in (from where, what state of mind): Above the fold: headline / subhead / hero / primary CTA text Body sections (in order, with the job each one does): Proof required (specific, not "add testimonials"): Objections handled here (list them, and the line that handles each): Fields collected (justify each one): Price shown: yes/no, and hoGitHub で全文を読む (外部ページ)