Why We Should Build More Ambitious Software

The Comfort Trap of Incrementalism

In the current tech landscape, we have become incredibly efficient at building the status quo. With robust frameworks like Next.js, powerful AI coding assistants, and cloud infrastructure that scales automatically, shipping code has never been easier. Yet, if you look at the landscape of new applications, many feel like minor variations of what existed five years ago. We are optimizing the delivery of products, but are we optimizing for impact?

There is a palpable trend toward safe bets. For founders, this means building another CRUD app with a slightly better UI or a niche SaaS tool that automates one specific workflow. For developers, this often translates to focusing on maintenance, refactoring, and 'developer experience' tools that make us faster at doing the same things we were already doing. While this is great for business stability, it creates a stagnant environment for true engineering innovation.

Redefining Ambition in the Age of AI

Ambition in software does not necessarily mean 'building the next big platform.' Instead, it is about shifting focus from the 'how' to the 'what.' Too many of us get obsessed with the latest architectural patterns—micro-frontends, serverless optimizations, or vector database tuning—without asking if the end product fundamentally changes the user's life or capabilities.

As an AI product engineer, I see this regularly. We have the capability to build agents that reason, tools that synthesize knowledge, and systems that act autonomously. Yet, most implementations are merely wrapper UIs for existing APIs. Being ambitious today means moving past the 'wrapper' mindset. It means building systems that have high agency, that integrate deeply with real-world constraints, and that solve complex problems that were previously deemed 'too hard' to automate.

• Move from wrapper applications to agentic workflows.
• Focus on domain-specific complexity rather than generalist tools.
• Prioritize long-term architectural stability over quick-fix libraries.
• Question whether your current project actually advances the state of the art.

Why Developers Often Shy Away From Big Projects

Why are we choosing the path of least resistance? It largely comes down to risk. Big, ambitious software projects fail often. They require deep domain knowledge, significant R&D, and the patience to survive the 'trough of disillusionment.' When you build a simple SaaS tool, you can get a feedback loop in weeks. When you attempt to build a new way to process local-first data or a novel way to manage LLM context, the feedback loop is measured in months.

There is also a fear of 'over-engineering.' In the agile era, we were taught to release early and iterate. This is excellent advice for product-market fit, but it has been weaponized against ambition. We treat the 'MVP' mindset as an excuse to avoid building core, transformative features that require heavy lifting on the backend or novel algorithms.

Practical Steps for Founders and Engineers

If you want to move toward more ambitious software, you must start by changing your personal allocation of 'innovation time.' If you are a developer, dedicate 20 percent of your time to projects that scare you—the ones where you do not know the solution on day one.

For founders, this means looking at your roadmap and asking: Is this feature actually increasing the value of my product, or am I just adding 'bells and whistles' to keep users engaged? True ambition often comes from removing friction that people thought was inevitable. If your software makes a hard process easy, you have achieved something valuable.

Do not be afraid to build 'deep tech.' We need more engineers willing to dive into the low-level constraints—compilers, networking protocols, local-first data syncing, and efficient model hosting. These are the foundations upon which the next generation of ambitious software will be built.

The Long-Term Dividend of Ambition

The market rewards audacity. While the 'safe' route might lead to a stable job or a small, self-sustaining business, the most impactful software in history was built by those who didn't care about the immediate, incremental path. They were focused on the 'what if' scenario.

For my fellow developers in India and globally, we have the unique advantage of a massive talent pool and the best tools in history. Let us use that not just to build more clones, but to tackle the hard problems in education, climate tech, local-first connectivity, and healthcare. The software we build is our legacy. Make it something that forces the world to change, even if just a little.

Frequently asked questions

Sources & further reading

• We should be more ambitious with the software we build