Discovery phase in software development: a practical guide

The discovery phase is the first stage of a software project, where a team turns a raw idea into a clear, estimable development plan. Instead of jumping straight into code, you define what you are building, who it is for, which features come first, and what it will cost. It answers the most expensive question up front: is this product worth building the way you imagine it?

Skipping this step is where budgets break. McKinsey studied more than 5,400 large IT projects and found they run, on average, 45% over budget and 7% over time, while delivering 56% less value than predicted (McKinsey, 2012). A discovery phase is the cheapest way to move those odds in your favor before development spending starts.

Why the discovery phase matters

The discovery phase exists to remove uncertainty before it becomes expensive. During it, a business analyst clarifies your goals, defines the product's users, and maps out how the software should work. By the end, you know the scope, the cost, and the order in which features will be built.

The discovery phase gives you four concrete things:

• A tested idea. You learn whether the product is feasible and worth building before you commit a development budget to it.
• A predictable budget. A prioritized feature list and estimate make spending predictable, so you are less likely to need an emergency top-up mid-project.
• A shared vision. User stories and journey maps let everyone (founders, investors, designers, and developers) work from the same understanding of the product.
• Measurable goals. Success metrics defined early (for example, how many users convert to a paid plan) give the product something to aim at after launch.

At Ronas IT, we call this stage the analysis phase, and a business analyst leads it rather than a single developer, so the plan reflects both business logic and technical reality. Beyond mapping the product, the analyst looks for ways to make the build cheaper: unifying overlapping flows, covering the same goal with fewer user stories, and cutting the number of components you have to build and maintain later. If you are outsourcing, having the analyst and the engineering team under one roof means the estimate you receive is the one the same team will build against.

What happens during the discovery phase

A discovery phase moves from understanding the idea to producing a plan a team can build from. Below are the five artifacts we create most often, in the order we usually create them.

1. Mind map. We start by mapping user roles and the product's modules on a single diagram. This shows the scope at a glance and sets the boundaries of the project: what is in the first version and what is not.

   

2. Customer journey map. For each user role, we map the steps a person takes to reach their goal. For a tutoring platform, a student's journey ends with a booked and completed lesson; mapping it reveals every screen and decision needed to get there.

   

3. User flow. We turn journeys into a schematic of screens and the transitions between them. This diagram shows exactly how a user moves through the product to complete a task, and it becomes the skeleton designers work from.

   

4. User stories. We describe what each feature does for each role in plain language. If a feature does not solve a real task, it usually does not belong in the first version. User stories make it easy to prioritize and to explain the product to stakeholders and investors.

   

5. Wireframes. For the most complex screens, we sketch a low-fidelity layout. Wireframes are optional in discovery, but they help you demonstrate the idea to investors and gather early feedback before design starts.

   

Alongside these, the analyst writes business rules that cover how the system should handle payments, refunds, cancellations, and disputes, then recommends a tech stack and integrations. Choosing proven tools early (a payment provider, a video SDK, a support chat) removes technical risk and keeps the estimate honest. For a deeper look at how we write requirements, see our guides on writing user stories and writing an IT project description.

A real discovery phase: a personalized tutoring platform

The owner of a tutoring agency came to us with a Canva mockup of a dashboard and an idea: a platform that connects students with tutors for personalized video lessons. The mockup explained the idea, but it was not enough to start design or development. Our task was to turn it into a plan.

Working with the agency owner, our business analyst ran the discovery in a few steps:

• Defined three user roles (student, tutor, and admin) and built a journey map for each one.
• Broke the product into features and grouped them into release versions, first version first.
• Wrote business rules for holding funds, refunds, cancellations, and dispute resolution.
• Studied similar platforms to shape the features that mattered most, such as personalized tutor matching and a trial-lesson flow.
• Recommended web interfaces for all roles, with a responsive student view instead of a separate mobile app.

For the first version, we kept only the features that delivered the platform's core value, personalization: students describing their needs, admins assigning the right tutor, and tutors managing a schedule and trial lessons. Everything else moved to a later release.

“A rough estimate is free, so that is not what you pay for in an analysis phase. You pay us to work through the fuzzy parts with you and hand you a plan you own. After that, the budget you commit goes to a first version you can build and afford, not a wishlist you cannot finish.”

Roman Surikov, CEO at Ronas IT

The numbers: this discovery phase cost $1,300 and took two weeks. It was an earlier, tightly scoped engagement; today the analysis phase starts at $2,000. The client ended up with a prioritized feature list, journey maps for every role, a set of business rules, a recommended stack (React, Laravel, and Laravel Nova with Stripe, Zoom, and Intercom integrations), and a cost-and-timeline estimate. The plan was hers to keep: a portable document she could build from with us or hand to any team. You can read the full story in our tutoring platform discovery case.

How much does a discovery phase cost, and how long does it take?

A discovery phase (the analysis phase in our pricing) is a small share of the total project cost, and it usually pays for itself by preventing rework. Here is a rough guide based on our pricing.

The right level depends on your risk. If the main question is “what exactly should we build and what will it cost?”, an analysis phase answers it. If the risk is technical (can this integration or algorithm even work?), a proof of concept is the better first step. Discovery leads naturally into MVP development, where the plan becomes a working product.

When you can skip the discovery phase

A full discovery phase is not always the right call, and we will say so. If a product has a single obvious flow and one user role, a short scoping call can be enough to start. We once built a subscription web app for a client after a 15-minute call, because the scope was that simple. The discovery phase earns its cost when a product has several user roles, handles money, or depends on third-party integrations. That is where unclear requirements turn into expensive changes later. Either way, you can start with a free rough estimate: tell us about the idea and we will scope it and give you a ballpark before any paid work. The analysis phase is the deeper, paid step you add when the product has enough roles, money, or integrations that a rough number is not solid enough to build against.

What to do next

Before you start building, make sure you can answer these questions in writing:

• Who are the users, and what is each one trying to accomplish?
• Which features belong in the first version, and which can wait?
• How does the product handle money, edge cases, and errors?
• What is the scope, and what will the first release cost and take?

If you cannot answer all four yet, a discovery phase is the fastest way to get there. A week or two of analysis up front keeps the budget you commit next tied to a plan you can actually build.

Ready to scope your idea? Tell us what you want to build, and our team will turn it into a prioritized plan with a cost and timeline you can rely on.

Get a project estimate