“Hi guys, so here is my idea of an app. How much would it cost and how soon can I get it?”
In that form or another, this is a pretty frequent request we get during initial meetings with potential clients. However, software development estimation isn’t as simple.
To answer this properly, we first need to clarify how collaboration with a technology company typically works. At a high level, a technology company usually offers two cooperation models: team extension or a full technology partner. The first option gives you a skilled team that delivers the features you decide to build. The second option is closer to a business-to-business partnership, where the technology partner helps shape the solution so it aligns with your real business needs. Both models have their own aims, and TechVision works effectively with either scenario.
Still, when it comes to software project estimation, we act as a technology partner. Of course, as a technology company, we can build a perfect solution from a technical standpoint and follow every specification, but that alone doesn’t guarantee the product will meet the real needs of your business. In that case, neither side benefits.
That’s why we focus first on understanding the problem you want to solve, the restrictions around possible solutions, and whether the proposed path aligns with the outcomes your business expects. Only then can we recommend the right approach, propose a solution that makes sense, and discuss realistic software project budget estimation and team composition.
From Uncertainty to Clarity
Another typical question is “Why can’t a cost be precise from day one?” The simple answer is uncertainty. Every project begins with assumptions, which turn into concrete facts through Discovery. The graph below illustrates the cone of uncertainty across the three stages we follow to provide clear and reliable estimates.
The Role of Pre-Discovery and Discovery
Why We Start with Pre-Discovery
When we first meet a client, we are still at the wide end of the cone of uncertainty. Initial estimates can swing in both directions, in some cases up to four times above or below the final number. This happens simply because the solution concept may not be fully formed or validated yet. Without enough clarity, there are too many risks, assumptions, and unknowns that can influence the development effort, and we cannot foresee all of them at this early stage.
What Happens During Pre-Discovery
The Pre-Discovery phase is a short but important checkpoint where our team and the client’s team get aligned. We discuss your goals, explore the business context, and assess how prepared the solution idea actually is. This early step allows us to see whether our expertise is the right match and what needs to happen next so that the future solution not only reflects the client’s wishes but also serves the real needs of the business.
Expected Outcomes of Pre-Discovery
By the end of Pre-Discovery, we have the following outcomes:
⚪ Business goals elicitation
⚪ Customer journey mapping
⚪ Market problem research
⚪ Architectural drivers definition
⚪ Competitive analysis
⚪ Problem definition
After this phase, the accuracy of the estimated effort usually improves to a range of 0.5x-2x, meaning we are much closer to understanding the real scope.
When We Move to Discovery
Discovery requires a dedicated team and active involvement from the client’s side. We suggest moving to Discovery when:
⚪ The solution vision is still vague or exists only as an idea
⚪ Requirements are not clearly defined
⚪ The client’s team lacks technical, business analysis, or UX design expertise
⚪ A fast and accurate assessment of the solution is required
What the Discovery Phase Includes
Although the steps inside Discovery might vary depending on how mature the client’s idea is, a typical track includes:
1. Use cases elicitation
2. Requirements specification
3. Quality attributes workshop
4. Architectural design and trade-off analysis
5. Integration and transition requirements
6. Value proposition validation
7. Solution concept
8. Solution scope and prioritization
Deliverables After Discovery
At the end of the Discovery phase, we present a clear plan for moving forward. You receive the proposed team composition, a time frame with best- and worst-case scenarios, and a detailed budget. We provide range estimates because every solution is unique and small changes are inevitable, and we prefer to be transparent about that rather than hiding risks inside the price. By this stage, however, the range becomes much narrower.
