Watching the “vibe coding” wave hitting the enterprise is moving the previous bottleneck and creating new predicaments. Sales ops is building little tools to automate quoting. RevOps is stitching together workflows. Finance is prototyping dashboards and approvals. Support is hacking together internal apps to reduce ticket time. And then the same script rolls: Someone on a nontechnical team, an employee with SME type knowledge about their workflow, shows off a prototype in a weekly standup. It works, and the team starts relying on it. Then an alarm goes off when it hits the enterprise wall, if it even got that far. Not because anyone hates innovation, but because the obvious questions show up fast: - What systems does this touch (Salesforce, pricing, customer data)? - Where did the data go while it was being built? - Did any code or prompts leave the environment? - Who owns this when it breaks at 9pm on quarter-end? - How do we audit decisions, permissions, and changes? - Is this now an unmaintainable pile of tech debt? From the builder’s perspective: “I solved a real problem. Why is engineering slowing me down?” From IT’s perspective: “We just inherited a production system with no provenance, no controls, and no rollback plan.” This is the enterprise reality: bottom-up building is happening whether policy is ready or not. The organizations that win will not be the ones that ban everything. They will be the ones that create a safe lane: encourage rapid prototyping, but require clear guardrails (data flow, admin controls, audit trail, ownership, and operational readiness) before anything becomes mission critical.