Start from what already happens
Before designing anything, read twenty recent conversations that closed and twenty that did not. The stages will be obvious, and they are rarely the textbook seven.
Most WhatsApp-led businesses need four or five: something arrived, we replied, we qualified it, we quoted, it closed. Extra stages feel thorough and produce cards that nobody moves.
Every stage needs an exit condition
A stage that cannot be defined in one sentence — 'a quote has been sent' — is not a stage, it is a mood. Ambiguous stages are why two reps put the same deal in different columns.
Make the stages yours, and keep them editable
Your first pipeline will be wrong, which is fine as long as it is changeable. In Waboxa stages are data rather than code: you can rename, recolour, reorder, enable, disable or add them with no cap, and mark which one new leads land in.
Two of them carry meaning beyond presentation — the ones that close a deal as won or lost — because analytics needs to know which outcomes count as revenue.
The rule about deleting a stage
Deleting a stage that still has leads in it should be refused, not silently cascaded. A pipeline reshuffle should never be able to quietly destroy the deals sitting in the column you removed — they have to be reassigned first.
It is a small design decision that becomes very important the first time someone tidies up the pipeline on a Friday afternoon.
Then measure the shape, not just the total
A pipeline report that only shows total leads hides the problem. Leads per stage tells you where deals stall — a pile-up at 'quoted' is a pricing conversation, a pile-up at 'contacted' is a qualification one.