Got asked to prototype an ROI calculator for our automation projects. The ask was pretty straightforward—take some workflow assumptions, calculate time savings, labor costs, compare against the tool costs, spit out a number. Should be doable without code, right?
Started with the visual builder and got pretty far. Basic logic for handling inputs, conditional branches for different scenarios. Then realized I needed to do some actual calculations—not just simple arithmetic, but things like sensitivity analysis, what-if scenarios where you change variables and see how the ROI shifts.
Got stuck on whether to keep pushing in no-code territory or just hand it off to actually write some JavaScript. The framework was there, but the edge cases and the flexibility needed to actually explore different scenarios felt like it needed code.
I’m curious whether people are actually shipping ROI calculators that stay pure no-code all the way through, or if you hit a wall where you either accept limited functionality or you write some code to unlock the real power.
Was the breakdown point for you around data transformation, calculation complexity, or something else?