LeadUp Lead Funnel Builder
Purpose
Build a complete funnel that turns ad clicks or organic visitors into qualified leads, then into customers. Covers traffic, landing page, form / WhatsApp flow, CRM capture, follow-up sequence, marketing automation, and tracking. India-friendly (UPI, WhatsApp, regional language) and global-ready.
When to use
Use when the user wants a funnel designed end-to-end. Do not
trigger when they want only a landing page audit (use
leadup-landing-page-cro-planner), an ads plan only (use
leadup-digital-ads-planner), or a single WhatsApp flow
(use leadup-whatsapp-automation-planner).
Trigger phrases: "lead funnel", "increase leads", "lead generation", "WhatsApp funnel", "client funnel", "sales funnel", "conversion funnel", "funnel for our business".
Inputs needed
- Business / product, market, audience.
- Funnel goal (calls / WhatsApp chats / form leads / signups / demos / bookings).
- Existing assets (LP, ads, CRM, tracking, BSP account).
- Traffic source mix (Google Ads, Meta Ads, SEO, social, referrals).
- Sales process (who follows up, in how long, with what).
- Constraints (budget, regulated category, language).
Ask at most 2 clarifying questions if the goal or traffic source is unclear.
Tools/resources to use
references/lead-funnel-framework.md— stage shape and rules.assets/lead-funnel.template.md— output shape.leadup-landing-page-cro-plannerfor the LP layer.leadup-digital-ads-plannerfor the paid traffic layer.leadup-whatsapp-automation-plannerfor WhatsApp flow.leadup-n8n-workflow-builderfor the automation glue.leadup-api-research-builderfor CRM / BSP integrations.leadup-human-content-editorfor public copy polish.
Step-by-step workflow
- Restate goal in one line and pick the funnel type (lead form, WhatsApp, call, demo booking, free trial signup, ecommerce buy).
- Map stages: Traffic → LP → Capture → Qualify → Follow-up → Close.
- Pick traffic sources per stage and split %.
- Spec the LP with above-fold, CTA, trust, form/WhatsApp choice,
mobile rules. Hand specifics to
leadup-landing-page-cro-planner. - Design capture:
- Form path: minimum fields, validation, success state, CRM event.
- WhatsApp path: click-to-chat, opt-in, BSP template, auto-reply.
- Define qualification (who is a hot lead, who is cold, how to route).
- Build follow-up sequence: who sends what, when, on which channel.
- Wire automation: n8n / Zapier / native CRM, with credential placeholders.
- Tracking checklist: GA4 events, pixel, CAPI, UTM convention, CRM stage events.
- Conversion-improvement checklist for the first 30 days.
- Hand-offs explicitly.
Required output format
One Markdown plan with these sections, in this order:
- Brief restate — goal, audience, funnel type.
- Funnel map — stage table: stage · channel · KPI · target band.
- Traffic plan — per source with share %, KPI, hand-off skill.
- Landing page spec — above-fold, CTA, trust, form/WhatsApp.
- Capture flow — form spec OR WhatsApp flow OR both.
- Qualification — criteria, routing rules.
- Follow-up sequence — touch · channel · template · timing.
- Automation — tool, trigger, nodes/steps, credentials placeholder.
- Tracking checklist — GA4 events, pixel, CAPI, UTM, CRM stages.
- Conversion improvement checklist — first 30 days.
- Assumptions and data confidence — verified / estimated / requires verification.
- Hand-offs — to other LeadUp skills.
Safety rules
- Do not invent CR, CPL, ROAS, follower counts. Use estimated bands with reasoning, or mark requires verification.
- Do not guarantee leads, conversions, or revenue. Use targets with stated assumptions.
- Do not propose dark patterns: fake countdowns, fake stock, hidden fees, opt-out by inertia.
- Do not propose WhatsApp tactics that violate Meta policy (mass-cold-outreach without opt-in, template spam).
- Respect opt-in / consent rules; for India, follow IT Rules / DPDP scope; for EU, follow GDPR.
- Keep PII handling honest: state where leads are stored, who can see
them, how long they're retained. Route to
leadup-pii-risk-reviewerfor confirmation. - For payments-in-funnel: route to
leadup-security-reviewandleadup-api-research-builder. - Public copy goes through
leadup-human-content-editorbefore publishing.
Common mistakes
- Designing a funnel without a tracking layer (no GA4 / pixel / UTM).
- "Form on the LP" with no auto-reply → leads go cold in 24 hours.
- Cold WhatsApp outreach without opt-in → BSP account suspension.
- 10-step nurture sequence on a 1-call sale.
- 1-touch follow-up on a 10-call sale.
- No routing rule for hot vs cold leads → sales spends time on cold.
- Forgetting language / timezone of the audience.
Troubleshooting
- No CRM: deliver a Google Sheets / Notion-based v1 with a clear
upgrade path; route to
leadup-api-research-builderwhen a CRM is picked. - No ad budget yet (organic only): lean into SEO + social + WhatsApp funnels; defer ads to a later phase.
- High-ticket sale (₹50K+/lead): lean into demo-call funnel + 5–7 touch sequence; lower volume, higher quality.
- Local-services business (salon, clinic, dentist): WhatsApp + Google Business + Maps reviews often outperform an LP form.
- Regulated category (clinic, finance, real estate): flag
qualification + claims for compliance; route to
leadup-pii-risk-reviewer. - User wants instant: deliver the funnel map + capture flow + first 3 follow-ups; build the rest in iteration 2.
Test prompts
Should trigger (5)
- "Build a lead funnel for our salon booking SaaS."
- "Increase leads for our jewellery client — design the full funnel."
- "Plan a WhatsApp funnel for a dental clinic in Coimbatore."
- "Design a demo-call funnel for our B2B booking tool."
- "Sales funnel for a tutoring centre — ads to follow-up."
Should NOT trigger (3)
- "Audit just this landing page." (→
leadup-landing-page-cro-planner) - "Plan our Meta Ads campaign only." (→
leadup-digital-ads-planner) - "Build one WhatsApp reminder flow." (→
leadup-whatsapp-automation-planner)
Functional test cases (2)
- Given "Indian salon booking SaaS, ₹50K/month budget, no CRM yet",
return a complete funnel plan with Google + Meta + WhatsApp +
organic mix, a 2-field LP form, a 5-step follow-up over 14 days,
automation in n8n with credential placeholders, a tracking
checklist, and a hand-off to
leadup-whatsapp-automation-plannerandleadup-n8n-workflow-builder. - Given a regulated category (a dental clinic running ads to a "free
consultation" funnel), return a plan that flags consent and claim
requirements, routes PII to
leadup-pii-risk-reviewer, removes guarantee language, and labels every metric estimated band / requires verification.
Success criteria
- All 12 sections present in order.
- No invented CR / CPL / ROAS.
- Capture flow defines either form OR WhatsApp OR both with concrete rules (fields, opt-in, auto-reply, CRM event).
- Follow-up sequence has exact timing per touch.
- Tracking checklist is concrete (events named, UTM convention defined).
- Compliance and PII routed where relevant.
- Hand-offs to other LeadUp skills are explicit.