Advanced Funnel Builder (Like Advanced Workflows, But For Funnels)
J
Justin Padron
Image if the Advanced Workflow Builder & Funnels had a baby... An Advanced Funnel Builder inside HighLevel that combines the visual look, technical functionality, and conditional logic of the Advanced Workflow Builder with the structure and monetization of funnels. Right now, funnels are linear and page-based, while workflows are dynamic and visual. The opportunity is to merge those two worlds. Imagine building funnels on a visual canvas where every page is a node, every decision creates a visible branch, and every step shows live analytics. Instead of a long vertical list of pages that implies everything goes in order, we would see the actual journey, including where it starts, where it branches out, where there are split tests for individual steps, and where it connects. This would turn funnels from static step sequences into fully dynamic customer journey engines, giving advanced users the control, visibility, and optimization tools they need to build sophisticated revenue systems inside HighLevel... And it will look cool...
P.S. I'll add more details in the comments �
Log In
J
Justin Padron
Here are some ideas that I vibecoded to give an example of what could be built:
J
Justin Padron
(4/4) CONTINUED:
- Native Upsell / Downsell / Cross-Sell Architecture
Current State:
Upsells exist but remain structurally linear.
Hard to visualize complex offer trees.
What We Could Have:
A true offer tree structure:
~ Decline → Downsell branch.
~ Purchase → Specific Upsell #2.
~ Multi-offer stacking clearly visible.
What This Solves:
~ Enables complex revenue architecture.
~ Makes monetization strategy visible.
~ Encourages structured scaling.
~ Improves clarity in multi-offer funnels.
- AI Optimization Layer (Optional Enhancement):
Current State:
~ All optimization is manual.
~ No proactive insights inside funnels.
What We Could Have:
An optional AI insights layer that can:
~ Identify device performance gaps.
~ Highlight high drop-off nodes.
~ Recommend split testing.
~ Flag redundant offer exposure.
~ Suggest routing improvements.
What This Solves:
~ Accelerates optimization.
~ Reduces blind spots.
~ Supports advanced marketers.
~ Adds intelligent guidance without forcing automation.
Final Summary:
~ Funnels today are linear.
~ Workflows are dynamic.
We’re requesting the evolution that merges them.
The Advanced Funnel Builder would include:
~ Visual funnel architecture
~ Native conditional branching
~ Embedded performance analytics
~ Advanced filtering by dates, source, device, etc
~ Contact-level execution logs
~ Workflow-style routing checks
~ Structured offer trees
~ Optional AI optimization insights
This is not about adding complexity for its own sake.
It is about clarity, control, and strategic depth.
By merging workflow intelligence with funnel monetization, HighLevel can transform funnels from static page sequences into fully adaptive revenue systems.
Feel free to build on this & add to the conversation... I'd love to help make this a reality!
J
Justin Padron
(3/4) CONTINUED:
- Execution Log (Contact-Level Funnel Journey)
Current State:
Workflow execution logs exist.
No equivalent visual execution log for funnels.
What We Could Have:
An Execution Log tab inside each funnel (For any contact):
~ Click the contact.
~ See a visual replay of their journey.
~ View pages visited.
~ See which branch they followed.
~ Track offers accepted or declined.
~ Identify exact drop-off point.
~ Track popup interactions.
~ Displayed visually on the same funnel map.
What This Solves:
~ Deep debugging capability.
~ Removes guesswork about user behavior.
~ Enables granular performance analysis.
~ Improves support and troubleshooting.
~ Mirrors the transparency of workflows.
- Workflow-Style Conditions and Checks Inside Funnel Nodes
Current State:
~ Routing is limited to simple button actions.
~ Advanced logic requires external automation.
What We Could Have:
~ Allow conditional checks inside funnel nodes:
Examples:
~ If tag exists
~ If custom field equals value
~ If purchase history contains product
~ If appointment booked
~ If form completed
~ If cart abandoned
~ If lead score exceeds threshold
All checks should visually route to different funnel pages.
What This Solves:
~ Eliminates fragmentation between workflows and funnels.
~ Enables intelligent dynamic routing.
~ Makes funnels adaptive to user data.
~ Simplifies advanced segmentation.
J
Justin Padron
(2/4) CONTINUED:
- Embedded Analytics Directly on the Funnel Map
Current State:
Analytics are viewed separately.
No visual performance indicators on the funnel itself.
Difficult to quickly identify bottlenecks.
What We Could Have:
Analytics embedded into each funnel node (Each page node should display):
~ Total views
~ Unique visitors
~ Conversion rate
~ Revenue generated
~ Split test breakdown
~ Drop-off percentage
Optional enhancements:
~ Red highlight for high drop-off.
~ Green highlight for strong conversion.
~ Warning indicators for sudden performance changes.
What This Solves:
~ Immediate identification of weak points.
~ Faster optimization cycles.
~ Data-driven decisions without switching screens.
~ Performance visibility directly tied to structure.
- Advanced Filtering (Source, Device, Segmentation)
Current State:
Limited filtering at the funnel level.
No clear device-based breakdown on funnel map.
Hard to analyze performance by traffic segment.
What We Could Have:
Advanced filtering built directly into the funnel builder (Filter by):
~ Traffic source (Facebook, YouTube, Google, Organic, etc.)
~ UTM parameters
~ Campaign
~ Device (Mobile / Desktop / Tablet)
~ First-time vs Returning visitors
~ Tag-based segmentation
~ Buyer vs Non-buyer
Why Device Filtering Is Critical (If):
Desktop converts at 12%
Mobile converts at 2%
~ We need to instantly see that discrepancy to make adjustments.
What This Solves:
~ Diagnoses mobile-specific conversion issues.
~ Enables source-level optimization.
~ Prevents hidden performance problems.
~ Encourages channel-specific strategy refinement.
J
Justin Padron
(1/4) Here is the initial detailed idea (that we can build off of):
By comparing the current state vs. The Advanced Funnel Builder Vision
- Visual Funnel Architecture (Workflow-Style Canvas)
Current State:
~ Funnel pages are displayed in one long vertical list.
~ The layout implies pages run strictly in order.
~ You cannot visually see how pages branch or connect.
~ Complex funnels become difficult to understand at a glance.
What We Could Have:
~ A visual canvas similar to the Advanced Workflow Builder:
~ Every funnel page displayed as a node.
~ A clearly defined starting page.
~ Visible branches that split based on actions.
~ Lines that show exactly which page connects to which.
~ Drag-and-drop positioning.
~ Zoom in / zoom out functionality.
~ A clean map-style interface.
What This Solves:
~ Eliminates confusion in complex funnels.
~ Removes the illusion that everything must be linear.
~ Allows advanced strategy planning visually.
~ Makes multi-offer funnels manageable.
~ Gives instant clarity on overall funnel architecture.
- True Conditional Funnel Logic (If / Else Inside Funnels)
Current State:
~ Basic A/B split testing per step.
~ No native if/else routing inside funnels.
~ Advanced routing requires separate workflows.
~ What We’re Requesting
~ Workflow-level conditional logic embedded directly into the funnel builder:
Examples:
~ If user clicks “Yes” → send to Upsell A.
~ If user clicks “No” → send to Downsell B.
~ If user already purchased Product X → skip that offer.
~ If contact has specific tag → route to custom version.
~ If returning visitor → change path.
All routing should be visually represented as branching paths on the funnel canvas.
What This Solves:
~ Native personalization at the funnel level.
~ Reduces dependency on external workflows.
~ Enables intelligent offer sequencing.
~ Prevents showing irrelevant offers.
~ Turns funnels into adaptive systems instead of static pages.