Funnels die in two places: discovery (when you misunderstand the offer) and the boring middle (when nobody owns the snapshot). This checklist covers the boring middle.
It’s the same 14-day shape we use at Funnelab on every GHL build — refined across 40-plus shipments. Adapt the day counts to your team’s velocity, but keep the order. [placeholder — replace with real shipped-build count once available]
Day 1–3 — Discovery you can act on
The goal isn’t to learn everything about the business. It’s to extract three things: the offer, the decision criteria, and the constraints.
- Run a 30-minute audit of the existing GHL sub-account (or current CRM). Note what gets archived, what stays, what needs rebuilding.
- Map the current sales process to a stage list — even if it’s broken. You can’t fix what you can’t name.
- Capture the offer in one sentence the client will sign off on. If they can’t say it back, you’re not done.
- List the integrations the funnel needs to touch (payments, calendars, fulfillment, support).
By end of Day 3 you should have a one-page build plan with a fixed quote.
Day 4–7 — Build the funnel shell
Now the shell goes in — pipelines, custom values, snapshots. No copy yet.
- Create the snapshot base. Name it
<client>_<offer>_v1so you can find it later. - Build the pipeline with stages mapped to the audit. Don’t reuse defaults.
- Add custom values for everything dynamic — booking URL, support email, brand name, calendar id. Future you will thank current you.
- Wire the funnel skeleton (opt-in → sales → order → thank-you). Just sections and blocks; placeholder text.
- Configure the GHL calendar with the right availability + buffer.
This phase ends when a fake test lead can move through every stage without breaking.
Day 8–11 — Wire automations
Workflows are where most builds rot in 6 months. Build them like you’ll have to hand them to someone else (because you will).
- One workflow per outcome. Don’t combine “send email” + “create task” + “move stage” into one mega-workflow.
- Name every workflow with the format:
<trigger> → <outcome>. Example:Opt-in submitted → 5-day nurture. - Wire failure alerts. A workflow that silently stops firing is worse than no workflow.
- Test on a fake contact end-to-end before any real lead touches it.
Day 12–14 — Ship + monitor
- Write the copy. Hero → problem → solution → proof → offer → FAQ → CTA. Test mobile.
- Record a hand-off Loom walking through the snapshot, pipeline, automations, and where to edit copy.
- Export the snapshot. Deliver as ZIP + a share link.
- Set up monitoring on the first 100 leads. You’ll find at least 2 things to tune.
Hand-off checklist
- Loom walkthrough (≤ 20 minutes)
- One-page runbook (where things live, how to edit, who to call)
- Snapshot ZIP + share link
- 30-day Slack/email support window agreed in writing
- First-week monitoring scheduled (Day 7 and Day 14 review calls)
Builds that ship this checklist on time tend to convert about [demo: 12%] better at the opt-in step and [demo: 8%] better at booking. [placeholder — replace with verified internal numbers]
If you’d like us to ship one of these for your team, book a call.