The Illusion of Progress in AI-Driven Development: Speed Is Cheap, Insight Is Rare (feat. Rob Wright)
AI tools boost speed, but real advantage comes from solving meaningful problems, validating demand, and using AI intentionally—not blindly.
In this in-depth interview, Rob Wright, Co-founder of Waffl, a West Point graduate and former special operations leader turned tech founder, shares insights on AI adoption, building software, and navigating the rapidly changing tech landscape. Discover practical advice on leveraging AI for small businesses, the importance of trust in client relationships, and how large corporations approach innovation.
For software developers, the current AI wave feels like a cheat code. Tools can scaffold APIs, generate documentation, write tests, and even suggest architectural decisions. What once took days can now be done in hours, sometimes minutes. On the surface, this looks like undeniable progress. But beneath that speed lies a subtle trap: doing more is not the same as creating value.
As one insight from the conversation captures, “AI adoption is easy depending on your size…you can just log into tools and get efficiencies out of it.” That accessibility is precisely the problem. When something is this easy to adopt, it becomes just as easy to misuse.
Developers are increasingly surrounded by tools that promise leverage, yet many teams end up layering AI onto workflows without questioning whether it meaningfully improves outcomes. The result is often noise disguised as productivity.
Podcast
AI Adoption Is Easy. Creating Advantage Is Not. — on Apple and Spotify.
From West Point to Waffle: The Unlikely Entrepreneur
Rob Wright didn’t set out to be an entrepreneur. He grew up in East Tennessee, graduated from West Point in 2014, and spent the better part of a decade in the military. But even before high school, his mind worked a certain way.
“When I walk into a Tropical Smoothie Cafe,” he explains, “my mind starts going — this is how many people are on the assembly line, this is how much they’re getting paid, the rent is this much, this is how many orders they have to do to break even.” That instinct to see the business inside every business eventually led him to co-found Waffle, an AI-powered platform designed to help small businesses build real competitive advantage — not just bolt on AI for the sake of it.
When Tools Start Driving the Process
A common anti-pattern emerging across engineering teams is the force-fitting of AI into workflows. Instead of starting with a problem and identifying where AI fits, teams start with the tool and look for ways to use it.
Consider something as simple as requirements gathering. Traditionally, ideas might evolve through informal notes, discussions, or quick iterations. Introducing AI into that process can seem like a natural upgrade—convert voice notes into structured documents, generate detailed specs, and standardize outputs.
But what actually happens?
The output becomes bloated. A single idea expands into pages of over-structured documentation. Signal gets buried under verbosity. What once enabled clarity now introduces friction.
This is the paradox: AI can make processes more “complete” while making them less useful.
Efficiency vs. Advantage
There is a fundamental distinction developers must internalize: efficiency is not advantage.
Efficiency means doing the same things faster. Advantage means doing things others cannot easily replicate.
Most AI usage today falls into the first category. Generating code snippets faster, automating documentation, or improving internal workflows—these are valuable, but they are not defensible. If everyone has access to the same tools, then efficiency gains are quickly commoditized.
As discussed in the conversation, “If it is not replacing something that you do or generating something that you already don’t do, it’s not giving you a competitive advantage.”
This is the crux. Developers are not competing on how fast they can write boilerplate anymore. They are competing on how effectively they can solve meaningful problems.
The FOMO Trap in Developer Ecosystems
There is also a psychological dimension at play. The developer ecosystem is heavily influenced by trends, and AI has amplified this effect. Every new tool claims to replace entire workflows. Every announcement suggests that not adopting it immediately puts you at risk.
This creates a constant sense of urgency—an artificial pressure to integrate tools before understanding their value.
But chasing tools is not the same as building systems.
The more disciplined teams are doing the opposite. They are slowing down, identifying bottlenecks, and selectively introducing AI where it creates measurable impact. They are not asking, “How do we use this tool?” but rather, “Where does this tool actually matter?”
Why Small Teams Struggle More
Interestingly, smaller teams and startups often struggle more with AI adoption than larger organizations—not because they lack capability, but because they lack structure.
Large companies assign ownership. They define metrics. They evaluate outcomes. Even if their processes are slower, they are deliberate. There is accountability tied to adoption.
Small teams, on the other hand, operate with fluid roles. The same developer might be building features, handling infrastructure, and experimenting with AI tools—all at once. In such environments, AI becomes an unstructured layer added on top of already complex systems.
The result is fragmentation. Tools get adopted inconsistently. Workflows become harder to reason about. And ironically, productivity can decline.
Building vs. Selling: The Hard Truth
Another hard lesson for developers is that building something impressive does not guarantee that anyone will pay for it.
AI has lowered the barrier to building software. More people can create products now than ever before. But this has also increased competition dramatically. The real challenge is no longer building—it is validating demand.
As highlighted in the discussion, a product can receive strong positive feedback and still fail commercially because no one is willing to pay for it.
This forces a shift in mindset. Developers must think beyond implementation and consider distribution, user behavior, and willingness to pay. AI can accelerate development, but it cannot create demand.
Letting Go of the Wrong Things
One of the most difficult skills for developers and founders alike is knowing when to stop.
There is a natural tendency to persist, especially after investing significant time and effort. But persistence without validation leads to sunk cost fallacy—continuing a path simply because of past investment.
The more effective approach is iterative validation. Build small, test quickly, and measure real-world outcomes. If the signal is weak, pivot. Not because the idea is bad, but because the market is indifferent.
AI makes iteration faster, which should make decision-making faster as well. But that only works if teams are willing to act on feedback.
Rethinking What It Means to Build Software
The role of a software developer is evolving. It is no longer just about writing code—it is about orchestrating systems, making judgment calls, and understanding where automation fits.
AI is not replacing developers. It is exposing gaps in how developers think.
Those who rely solely on tools will produce more output, but not necessarily better outcomes. Those who focus on problem clarity, system design, and user value will use AI as leverage rather than a crutch.
Closing Thoughts: Evaluate Before You Implement
Rob’s closing comment distills everything into a single sharp principle:
“Really evaluate what you’re doing. Because AI doesn’t fix what’s already broken.”
Before implementing any tool — AI or otherwise — ask whether it replaces something you do or generates something you couldn’t do before. If it does neither, you don’t have an AI problem. You might have a process problem. And the solution to a process problem is building a better process, not stacking more technology on top of broken foundations.
The businesses that will win with AI aren’t the ones who adopt the most tools. They’re the ones who adopt the right tools, in the right places, at the right time — and build the kind of trust and judgment that no tool can replicate.
Rob Wright is the co-founder of Waffle, an AI platform for small and medium businesses. You can learn more at gowaffl.com.