Funnel Building

Build the path from a specific visitor's first contact to a verified business outcome. A visit, form submission, booked call, attended call, and sale are different events. Give each step one job and make its handoff observable.

Begin with the decision and delivery

Use existing context first. Establish:

• Audience and source: who arrives, through which channel and promise, what they already know, and what they need to decide. Cold social, a referral, and branded search require different context.
• Outcome: the useful next visitor action and the actual business result, such as qualified attended calls or fulfilled purchases. Name the qualification criteria and counting rules.
• Offer: real deliverable, price or pricing process, terms, prerequisites, fit, proof, capacity, timeline, and what happens after a yes. Leave missing inputs explicit.
• Economics: spend and labor budget, margin, fulfillment and sales capacity, refunds or cancellations, and sustainable acquisition cost. Do not invent these inputs or forecast performance as fact.
• Evidence and access: product truth, permitted customer language, objections, approved proof, available tools, connected accounts, data permissions, and consent requirements.

If the offer cannot deliver the intended promise, fix its scope or promise before adding pages. Complete a reviewable plan and independent drafts while asking for missing load-bearing inputs.

Study the actual audience and useful examples

Inspect original customer questions and permitted conversations, the current product, and relevant original public funnels. Record source URLs, review dates, observed sequence, useful mechanism, and limits. Verify dynamic product facts, platform capabilities, prices, and sensitive claims with current primary sources.

Separate what was observed from interpretation. A polished page does not prove it converts; a creator's case study does not establish the same result for this audience. Adapt the mechanism into an original journey instead of copying assets, testimonials, or unsupported performance claims.

For an existing funnel, inspect the real entry URL and each handoff, then compare by source and cohort. Diagnose the first verified failure before prescribing another page or a different automation.

Choose the shortest complete path

Do not add a quiz, application, presell article, upsell, or sequence by default. Each step must solve a visitor or business problem. One main decision can include a useful lower-commitment route.

Map handoffs before building

Draw source → landing → action → record → delivery → next stage. For each transition identify:

• Visitor promise and expected next state.
• System of record and owner.
• Success evidence and identifiers connecting the stages.
• Failure, retry, duplicate, abandonment, and recovery behavior.
• Attribution and the actual channel consent or preference data.

Include ineligible, cancelled, no-show, refunded, or sold-out states when relevant. Check supported connector schemas and permissions before proposing an automated handoff. Connected accounts are optional capabilities, not standing authority to write or send.

Build the connected experience

1. Match the message. Preserve the incoming promise across post or ad, landing, form, email, and offer. Use the reader's own supported language and a concrete mechanism. If a copywriting skill is installed, use it; otherwise ground specifics, proof, and terms directly.
2. Make the offer decidable. State real inclusions, fit, price or pricing process, availability, prerequisites, timeline, and next step where they matter. Make scarcity, bonuses, guarantees, and deadlines operationally true.
3. Make the action usable. Collect only the fields needed at this stage. Inspect mobile, keyboard use, labels, errors, loading, and retry. Do not treat visitor confusion as disqualification.
4. Persist before success. Save the submission or transaction and confirm acknowledgment before displaying completion. Preserve source and relevant consent. Do not infer a CRM write from a browser success message.
5. Deliver the promise. Provide the real guide, confirmation, receipt, invitation, or service handoff. Booking is evidenced by the scheduling provider; payment by the processor; attendance by the event or operator record. A click or local “I booked” flag is not that evidence.
6. Continue appropriately. Prepare call questions, reminders, onboarding, fulfillment, or a relevant next offer. Preserve preferences and suppressions. A submitted form does not authorize every channel or unrelated nurture campaign.

Use the user's chosen stack and host. Inspect current official documentation and actual callable tools rather than assuming an integration exists. If a dependency is unavailable, finish independent assets, provide the exact field mapping or manual fallback, and label unconnected or simulated steps.

Keep proof and trust intact

• Never invent or launder customer quotes, results, authority badges, user counts, savings, time claims, prices, stock, deadlines, or product capabilities. Keep missing proof visible in drafts and out of publication-ready copy.
• Customer research supplies language and hypotheses; competitor outcomes do not prove this offer works. Explain uncertainty rather than hiding it.
• Identify sponsorship or commercial purpose where applicable. Do not make a paid presell article impersonate independent journalism or fabricate a customer experience. For US work, consult current FTC native advertising guidance and reviews/testimonials guidance as relevant.
• Give quizzes honest results with an understandable basis. Do not pretend every visitor receives a unique diagnosis if answers do not change it.
• Verify medical, financial, housing, or other high-stakes claims against current applicable primary guidance. Inspect housing wording, images, targeting, and eligibility rather than applying a universal banned-word list.
• Keep consent distinct from completing a form or buying. Use current applicable channel guidance and actual approved consent language. Make recurring charges, paid trial conversion, and material restrictions clear.

Verify the entire path

Test the exact entry URL through the intended outcome on desktop and mobile. Include duplicate submission, invalid input, slow or failing providers, broken delivery, cancellation and recovery paths when relevant. Use a sandbox or explicitly authorized designated test identities; do not message real prospects or spend funds as a casual verification step.

Check the saved record, owner assignment, asset or confirmation delivery, and provider-confirmed booking or payment as applicable. Distinguish local simulation, sandbox test, published page, and verified production handoffs. Inspect the rendered result; passing code checks does not prove the visitor experience.

Follow existing user authorization for publication and account writes. When authority is missing, complete the concrete reviewable result first and identify the exact action awaiting approval. Installing this skill grants no live-account mutation, sending, spending, or publication authority.

Measure and improve from actual events

Create an event map with source, campaign or creative, cohort, page/offer version, timestamp, and stage identifiers. Compare rates with explicit denominators: relevant visit → action start → completed request → delivered promise → qualified conversation → scheduled → attended → sale, as relevant. Track spend, labor, margin, opt-outs, cancellations, refunds, and support load alongside revenue.

Diagnose the first meaningful leak using observed events and qualitative evidence. Mark the proposed cause as a hypothesis, choose one material change when traffic permits, and define what observation would support it. With small samples, prefer usability findings and direct customer feedback over claiming an A/B winner. Do not scale spend on clicks or opt-ins when the intended downstream outcome remains unverified.

Deliverable

For a strategy, deliver the audience/source, real offer, step map, copy and proof needs, handoff owners, tracking plan, economics assumptions, and smallest useful test. For a build, implement and verify the in-scope connected steps, provide editable assets and the working destination, report live versus simulated handoffs, and name the precise remaining dependencies. Do not call imported contacts, drafts, or clicks new qualified leads.