# Beacon Funnel Build

> **When to use.** When the user asks for an end-to-end acquisition funnel — traffic source → landing page → email capture → nurture → offer → conversion — and needs the channel-level structure that ties stages together.

- Skill: `ferroxlabs/beacon-funnel-build` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ferroxlabs/beacon-funnel-build`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ferroxlabs/beacon-funnel-build/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: FerroxLabs (https://skillmd.com/u/ferroxlabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ferroxlabs/beacon-funnel-build

---


# funnel-build

**When to use.** When the user asks for an end-to-end acquisition funnel — traffic source → landing page → email capture → nurture → offer → conversion — and needs the channel-level structure that ties stages together.

**Procedure (stub).** Diagnose the See / Think / Do stage map first (route to channel-strategy). For each stage, pick the channel that feeds it and the next-step asset that catches the audience and moves them one rung. Common architecture: See-stage paid social → Think-stage lead magnet landing page → Care-stage welcome sequence → Do-stage sales sequence. Spec the bridge between each stage explicitly: what triggers the next step, what creative the next stage needs, and what measurement validates the bridge worked. Coordinate with Copy for landing-page words and email bodies; with Forge for the offer at the bottom; with Lens for the tracking. The funnel diagram is the deliverable; do not build inside any one platform's funnel-builder tool without first proving the architecture works on whiteboard logic.

**Status.** Default tier: user-toggle. Full procedure deferred to Phase 2. Until then, the channel-strategy skill handles cross-channel decisions.