The task meter section is the one I would move to the front, because the number people check is the wrong one. Volume is what gets quoted and billed steps per run is what sets the invoice. A twelve-step workflow at 300 runs a month costs more than a three-step one at 2,000, and the second one feels ten times busier to everyone in the building.

That also changes which two workflows to move. The ones worth rebuilding are rarely the loudest, they are the ones that fan out into loops and filters, where each added branch multiplies against every run. Counting steps per run across the account usually names a different pair than asking the team which Zap annoys them most.

On the 65% figure, the fact that OutSystems published it is a fair catch, and it is worth saying what it does not claim: that a project eventually needed custom code somewhere, not that starting low-code was the mistake.