I’m running into a bottleneck that I think others might be dealing with too. Our ops team has legitimate automation ideas, but getting from “wouldn’t it be great if we could automate X” to an actual ROI estimate takes forever. It usually goes like this: idea gets written down, someone finds a business analyst, BA scopes it out, finds an engineer, engineer builds a prototype, and somewhere in month two we finally have something to measure.
So we’re kind of stuck. Good ideas rot because the approval process itself kills momentum. And by the time we have a prototype, the business context has already shifted.
I’ve been reading about no-code builders with AI-assisted workflow generation, where you can supposedly describe what you want in plain language and get something runnable back in days instead of weeks. The theory is that non-technical people can prototype faster, get quicker ROI estimates, and actually validate whether an automation is worth doing before we sink serious engineering time into it.
But I need to know if this is actually real or marketing. Has anyone actually used their ops staff to build ROI prototypes without months of technical handoff? When they do, how much of the prototype actually survives contact with engineering review, or do you end up rebuilding most of it anyway? And what does the timeline actually look like from “idea” to “we have numbers”?