Every meaningful digital product starts with an investment. The interesting question is whether that investment should begin with development.
One of the first questions we hear from founders, business leaders, and product teams is, “How much will it cost to build?” Sometimes the conversation is about a new website, sometimes a mobile application, a SaaS platform, an enterprise system, or increasingly an AI-powered product. The technology changes, the ambition changes, but the question rarely does.
It is a perfectly reasonable question. Every organisation has budgets, timelines, stakeholders, and expectations. Before committing to a project, there needs to be confidence that the investment is justified. Yet over the years, we have realised that very few people are actually asking about development costs. What they are really trying to understand is whether they are investing in the right opportunity.
Those are two very different conversations.
One focuses on the price of building software. The other focuses on reducing uncertainty before software is ever built. The difference may appear subtle, but it often determines whether a digital product creates long-term business value or simply becomes another expensive project that never quite delivers on its original promise.
The reality is that software development has become increasingly accessible. Modern frameworks, cloud infrastructure, AI-assisted development, and low-code platforms have dramatically reduced the barriers to building digital products. What has not become easier is deciding what deserves to be built. That decision still requires careful thinking, market understanding, and an honest assessment of the problem an organisation is trying to solve.
Perhaps the first investment should not be measured in development hours at all.
Perhaps it should be measured in clarity.
Every product begins long before development
There is a common misconception that product development begins when designers open their design tools or engineers begin writing code. In practice, those activities represent the execution of decisions that should already have been made. By the time implementation begins, an organisation should have a reasonable understanding of the business problem, the people it intends to serve, the value it hopes to create, and the outcomes that will define success.
Without that understanding, development becomes an exercise in exploration rather than execution.
This is one of the reasons many digital products become more expensive than originally planned. It is rarely because development teams underestimate complexity. More often, the complexity was already present—it simply had not yet been discovered. New requirements emerge halfway through the project. User expectations differ from initial assumptions. Internal stakeholders interpret the vision differently. Entire workflows require redesign because they were never validated with real users.
None of these problems originate from technology. They originate from uncertainty.
Over the years, we have seen organisations invest considerable resources solving problems that could have been identified much earlier through thoughtful product discovery. We have also seen relatively modest investments in research, workshops, and user validation completely change the direction of a product before development even began. In almost every case, the investment in understanding proved significantly more valuable than rushing towards implementation.
That is why, at Kormoan, our product engagements rarely begin with discussions about technology. They begin with questions.
Who are we building for?
What problem are we solving?
Why does this product deserve to exist?
The answers to these questions shape every decision that follows.
The most expensive feature is usually the one nobody needed
When organisations prepare budgets, they naturally think about visible costs. Design, development, cloud infrastructure, software licences, quality assurance, marketing, and launch activities all find their place within a project plan. These are tangible investments with measurable costs.
What rarely appears on the budget is the cost of building the wrong thing.
A feature that seemed essential during planning but is ignored after launch.
A dashboard that looks impressive but never influences a business decision.
An internal platform that employees avoid because existing processes feel easier.
An AI capability introduced because competitors announced one, rather than because customers genuinely needed it.
These are not engineering failures. They are product decisions that were never sufficiently challenged before implementation began.
Every feature carries an ongoing cost. It must be designed, developed, tested, documented, maintained, secured, and eventually improved. The more unnecessary complexity a product accumulates, the more difficult it becomes to evolve. Teams spend increasing amounts of time maintaining existing functionality instead of creating new value.
One of the most valuable outcomes of product strategy is not identifying what should be built.
It is identifying what should not.
That discipline often determines whether a product remains focused as it grows or gradually becomes overwhelmed by features that contribute little to the overall experience.
Investment should follow uncertainty
One of the reasons businesses struggle to estimate digital product costs is that not every product carries the same level of uncertainty. Building a marketing website for an established business is fundamentally different from creating a SaaS platform for a market that has never been validated. Likewise, developing an internal enterprise application presents very different challenges from designing an AI-powered customer experience.
The investment should therefore reflect the complexity of the questions that still need answers.
If an organisation already understands its users, business processes, competitive landscape, and product direction, development can begin with a relatively high degree of confidence. If those answers remain unclear, investing immediately in engineering often amplifies uncertainty rather than reducing it.
This is precisely where Product Discovery creates value. Discovery is not simply a workshop or a collection of documents. It is a structured process for replacing assumptions with evidence before they become expensive technical decisions. Through research, stakeholder alignment, market evaluation, user journey mapping, and product strategy, organisations gradually build the confidence required to make informed investment decisions.
The objective is not to delay development.
The objective is to ensure that when development begins, the team is solving the right problem in the right way.
Every investment should reduce uncertainty
If product development is about creating certainty, then every investment made before development should answer a question that would otherwise become expensive later.
Unfortunately, many organisations invest in the opposite order. They purchase technology before understanding users. They select development partners before defining the product vision. They compare quotations before understanding whether the proposed solution actually addresses the problem they are trying to solve.
The consequence isn’t always an unsuccessful product. More often, it is a product that takes significantly longer to mature because important decisions are made while the product is already under construction.
We’ve found that successful digital products rarely emerge from having the largest development budget. They emerge from having the clearest understanding of the problem, the customer, and the outcome the organisation is trying to achieve.
This is why the earliest investment should always reduce uncertainty rather than increase capability.
Not every investment belongs in engineering
When people think about digital products, they naturally think about development. Yet engineering represents only one part of the investment.
Before a single line of code is written, organisations should already have confidence in several fundamental areas.
Do we understand our users well enough?
Is there evidence that this problem genuinely exists?
What makes our solution different from existing alternatives?
How will this product create measurable business value?
What should the first version include—and more importantly, what should it deliberately exclude?
These questions rarely have technical answers.
They require product thinking.
Over the years, this has shaped the way we approach every engagement. Product strategy comes before product design. Product design comes before engineering. Engineering creates the solution, but strategy determines whether the solution deserves to exist in the first place.
This philosophy eventually evolved into what we now call the Kormoan Product Framework—Discover → Design → Build → Scale. It isn’t a process created for presentations. It is simply the sequence we’ve found most effective after years of helping organisations transform ideas into digital products.
Artificial intelligence has changed the conversation, not the principles
Artificial Intelligence has undoubtedly changed the way organisations think about technology. Conversations that once focused on websites and mobile applications now include AI assistants, enterprise copilots, intelligent automation, and conversational interfaces.
While the technology has evolved rapidly, the underlying questions remain surprisingly familiar.
Should AI make this decision?
Will users trust the response?
Do we have reliable data?
Does intelligence genuinely improve the experience, or are we adding complexity for the sake of innovation?
These are product decisions before they are technical decisions.
One of the reasons we began investing heavily in Design for AI is because we recognised that traditional UX principles alone were no longer enough. AI introduces uncertainty into interfaces. It changes how users discover information, how they make decisions, and how much control they expect to retain.
Designing these experiences requires organisations to think beyond implementation. They must consider explainability, trust, transparency, responsibility, and long-term adoption alongside technical capability.
In many ways, AI reinforces the very principle this article began with.
Technology should never be the starting point.
Understanding should.
Looking beyond the first release
Another mistake organisations frequently make is treating launch as the finish line.
In reality, launch is simply the beginning of learning.
The first version of any product should answer new questions rather than attempting to answer every possible one. User behaviour reveals opportunities that research alone cannot uncover. Analytics expose friction that no workshop could predict. Customer feedback challenges assumptions that seemed obvious during planning.
The products that continue to evolve are rarely those with the most features. They are the ones designed with enough flexibility to learn from the people using them.
This is why we often encourage businesses to think less about building a perfect product and more about building a product capable of improving continuously.
Whether through product analytics, customer research, search insights, experimentation, or AI-assisted optimisation, every iteration should reduce uncertainty further than the previous one.
Growth is not another phase of development.
It is the continuation of product discovery.
So, how much should you invest?
There isn’t a universal answer because there isn’t a universal product.
The investment required for a corporate website differs significantly from an enterprise platform. A SaaS product serving thousands of customers demands different thinking than an internal operations portal. Likewise, an AI-powered product introduces entirely new considerations around trust, governance, and user adoption.
Rather than asking for a number too early, organisations benefit far more from understanding the level of certainty required before development begins.
Sometimes that certainty can be achieved through a few collaborative workshops.
Sometimes it requires customer interviews, market analysis, technical architecture, prototyping, or AI opportunity assessment.
The objective isn’t to increase the budget.
It’s to increase confidence.
When confidence improves, investment decisions become easier, priorities become clearer, and development becomes significantly more efficient.
Final thoughts
Looking back across hundreds of digital initiatives, one observation has remained remarkably consistent.
We’ve never seen a project fail because an organisation invested too much time understanding the problem.
We have seen many struggle because they invested too little.
Technology will continue to evolve. Development will become faster. Artificial Intelligence will automate more of the implementation process. Building software will become increasingly accessible.
Choosing what deserves to be built will become increasingly valuable.
Perhaps that is the real investment every organisation should make before beginning a digital product.
Not simply in technology.
Not simply in design.
But in clarity.
Because when organisations understand the problem deeply, every decision that follows becomes easier.
And when decisions become easier, products become better.
At Kormoan, that belief continues to shape how we approach every engagement whether we’re helping organisations define a new product strategy, redesign a digital experience, modernise an enterprise platform, or explore the opportunities created by AI.
Great products are rarely the result of building more.
They are the result of understanding better.
Before you ask for a proposal, ask better questions.
If you’re exploring a new website, SaaS platform, enterprise application, or AI initiative, the most valuable outcome of the first conversation shouldn’t be an estimate. It should be a clearer understanding of the opportunity, the challenges, and the decisions ahead.
That’s exactly where we believe every successful digital product begins.
