Free tool · no signup
How many nodes would you have to draw?
A visual flow builder makes you hand-draw every path a conversation can take — and that node count grows with every product, question and language. Drag the sliders to see the size of the flowchart you'd be maintaining, versus an agent you just describe your business to.
A rough estimate to make a point about how flows scale — see why you shouldn’t have to choose.
Your conversation
Sizing, shipping, returns, availability, discounts, order status… count the separate questions.
Average back-and-forth to answer a single question — messages, buttons, conditions.
How many products the answers branch on. Each one is another path to draw in a flow builder.
Each language is a parallel copy of the whole flow to build and maintain.
Every path scripted
53
nodes to build & maintain (~69 connections)
With an AI Step
0
nodes for the conversation — draw only what must not vary
And it keeps growing
In a flow builder, every new product adds about 4 nodes to redraw, and every new question you want handled adds about 4 more. Hand that turn to an AI Step and a new product syncs from your catalog, a new question is just answered — and the flow you drew stays the size you drew it.
The honest part
This is a rough estimate — real flows vary, and a simple keyword auto-reply is genuinely fine as a few nodes. The point isn't the exact number; it's the slope. Canvases are predictable and controllable, and for a giveaway or a launch that's exactly what you want — we ship one for that reason. What doesn't scale is scripting open-ended conversation. So don't: drop an AI Step into the flow and let the agent take that turn.
Estimates only. Node counts are a rough model of a typical visual flow builder (one trigger plus a few nodes per question, extra branches per product, a parallel copy per language); your real build depends on the tool and how much logic you script. This tool doesn't represent any specific product's editor.