You Just Bought a One-Way Ticket. Now What?
AI has unlocked a gold rush of software development inside your business. Before you celebrate, answer four questions.
THE DAM JUST BROKE
For twenty years, your company did the smart thing. Every time a leader walked in with a problem that needed a software solution, the conversation went roughly the same way. How much will it cost? How long will it take? Who maintains it? The answers were always: more than you want to spend, longer than you want to wait, and somebody we probably have to hire. So you put the problem on the shelf and moved on.
That shelf got very full. Marc Andreessen, co-founder of Andreessen Horowitz, has argued publicly that the world had far more demand for software than anyone ever realized. The reason we did not see it was simple: the friction of building software had trained everyone to stop asking. Leaders are smart people. They learned to skip the question before it became a headache.1
Then AI showed up and changed the math completely.
Today, over 26 percent of all production code is being written by AI, up from 22 percent just one quarter ago.2 What used to take a development team three months now takes an afternoon. What used to require a programmer now requires someone willing to describe a problem in plain English. The shelf is being cleared out at a pace nobody predicted.
“We did not go from walking to driving. We went straight from walking to flying.”
Two terms have emerged to describe this new reality. Low code refers to development platforms that reduce manual programming through visual tools and templates. Vibe coding, a term coined by AI researcher Andrej Karpathy in February 2025, takes it further: you describe what you want, and the AI builds it. You are not programming. You are directing. The technical barrier, the one that kept that shelf full for twenty years, is gone.
THIS IS THE BEST NEWS IN BUSINESS. MOSTLY.
At REDEGADES.AI, we watch this transformation play out inside our clients every week. Problems that sat unsolved for years are getting fixed in days. Workflows that required three humans and a spreadsheet are being automated. The productivity unlock is real, and we encourage every company we work with to move fast. Build aggressively. The companies that do are pulling ahead of the ones that are still waiting for a pricing page.3
But here is the part of the story that does not get enough airtime, and I am going to give it some, because I think ignoring it is going to be expensive for a lot of companies in the next two years.
Flying somewhere on a one-way ticket is great. Right up until you need to come back.
A significant portion of the software being built right now with AI tools is exactly that: a one-way ticket. It solves the problem in front of you today. It does what you need it to do right now. And then it lands somewhere, and the question of what happens next has not been fully answered. According to a recent survey of technology leaders, 75 percent expect moderate to severe technical debt by 2026 as a direct result of rapid AI-assisted development.4 That debt is already accumulating. The question is whether you see it before it comes due.
THE FOUR QUESTIONS YOUR IT TEAM IS HOPING YOU WON’T ASK
Here is the honest version of where most companies are right now. They are building fast, deploying aggressively, and solving problems they could not touch two years ago. All of that is good. What is not good is that four critical questions are going unanswered. Most leaders do not ask them because they feel like IT questions. They are not. They are business continuity questions.
The first question is: where does this software actually live?
A tool built inside a chat interface, a link shared with the team, a deployment dropped into a temporary environment: none of those are infrastructure. They are convenient right now. Licensing terms change. Platforms evolve. The tool your sales team relies on every morning may not exist in the same form twelve months from now, and if nobody owns it, nobody will fix it when it breaks.
The second question is: is it secure?
AI can write functional code very quickly. What it does not automatically produce is hardened, production-grade code. Research from Veracode found that between 40 and 45 percent of AI-generated code contains vulnerabilities mapping to the OWASP Top 10, the industry’s standard list of critical security risks.5 AI-generated code has a 2.7 times higher vulnerability density than human-written code. And 58 percent of developers admit they trust AI output without testing it. That is not a developer problem. That is a leadership problem.
The third question is: who maintains it?
Software built to solve a problem today will eventually run into a change, whether that change comes from inside your business or from a shift in the underlying technology powering the build. When that happens, who fixes it? This is not rhetorical. It needs a real owner, a real answer, and a real plan, before the break happens, not after.
The fourth question is: who troubleshoots it when something goes wrong?
This still requires a human in the loop with enough context to know what they are looking at. If everyone who understood what the tool was supposed to do has moved on to the next project, that context is gone. Gone, as in, the tool sits broken while someone tries to re-explain its entire purpose to an AI, hoping to reconstruct something that should have been documented from the start.
“75 percent of tech leaders expect moderate to severe technical debt by 2026. The clock is already running.”
THE GOOD NEWS: THIS IS FIXABLE RIGHT NOW
None of these questions are reasons to slow down. Let me be clear about that. The era of being able to build software fast, at low cost, without a team of developers, is one of the most significant competitive advantages in the history of business. The companies that lean into it are going to look very different from the ones that wait. I am not here to pump the brakes.
I am here to say: build fast, and build with a plan.
That means deploying every tool you build into a real environment you own or control. It means running a basic security review before anything touches your data or your customers. It means assigning an owner, not just a builder. And it means documenting what the thing is supposed to do while someone still knows.
This does not require a large IT team. It does not require a budget overhaul. It requires a checklist and the discipline to use it. At REDEGADES.AI, we help companies build that infrastructure around their AI development so the velocity stays high and the debt does not pile up quietly in the background.
THE RETURN FLIGHT IS PART OF THE TRIP
I thought about Y2K when I was putting this together. We spent years worrying about what would happen when the calendar rolled over to the year 2000, and when it did, the lights stayed on. This could be a Y2K situation. Maybe AI tools improve fast enough that maintenance and troubleshooting become trivially easy and the four questions answer themselves. That is possible.
But the cautionary part of a cautionary tale is not that the outcome is certain. It is that the outcome is avoidable. Build fast. Solve every problem on that shelf. Clear it out. Just make sure someone has thought about the return flight before the plane takes off.
The shelf is empty. The plane is in the air. Book the return.
____________________________________________________________
CITATIONS
1 Marc Andreessen, The Joe Rogan Experience, Episode #2234, November 26, 2024, https://open.spotify.com/episode/2JDW5u8BlKHM5C5wInOT4u. See also: Marc Andreessen, “Why AI Will Save the World,” Andreessen Horowitz, June 6, 2023, https://a16z.com/ai-will-save-the-world/.
2 “AI Coding Assistant Statistics & Trends [2025],” Second Talent, https://www.secondtalent.com/resources/ai-coding-assistant-statistics/. AI-authored code share figure as of mid-2025.
3 REDEGADES.AI client observation.
4 “Vibe Coding Hit 84% Adoption. 45% Has Vulnerabilities,” Pixelmojo, https://www.pixelmojo.io/blogs/vibe-coding-technical-debt-crisis-2026-2027. Technical debt projection figure drawn from survey of technology leaders, 2025-2026.
5 Veracode, “AI-Generated Code Security Risks: What Developers Must Know,” https://www.veracode.com/blog/ai-generated-code-security-risks/. OWASP Top 10 vulnerability mapping figure and 2.7x vulnerability density comparison. Developer trust figure: Faros AI, “The AI Productivity Paradox Research Report,” https://www.faros.ai/blog/ai-software-engineering.









