Discovery Phase

Usually 2 to 4 weeks. It depends mostly on the number of integrations and on how quickly the people we need are available.

A free estimate is based on a short brief, so the team either adds a large safety margin or meets the real scope halfway through the project. Discovery gives the price and the deadline something solid to stand on.

No. The documents are yours and written for any team, so you can compare vendors on the same scope.

A strategic session looks at the whole business and its direction. An MVP review assesses a first version that already exists. Discovery prepares one specific new product for development.

A person who can make decisions, a few hours a week for interviews and reviews, and access to existing materials and systems.

Then you learn it for the price of discovery, not of development. We explain what to change: a smaller first release, a different order of features or an existing tool instead of custom code.

Not always. We treat any specification as a starting point rather than the answer, because it describes someone's current understanding of what should be built, not how the business actually works. If it already covers roles, data, integrations and what is out of scope, MVP development can start from it directly. If it prescribes a technology or a list of features without the reasons behind them, discovery checks those reasons first, and sometimes we send two proposals: one that follows the specification and one that challenges it.

The backlog gives a budget and a timeline for every stage. For most projects we then fix the price for the agreed scope, so you know the total before development begins; large products are split into stages, and each stage gets its own estimate. If the scope changes later, we discuss the change and agree on it before doing the work, not after.

A business analyst writes the requirements, a designer builds the user flows and the prototype, and an architect chooses the structure and the stack. You review their work every week. The founder, Yevhen Borovoi, joins every engagement at the strategic session and can step into any project to review it. Interviews and reviews run by video call in English, Russian or Ukrainian.

No. The prototype shows the key screens and journeys, so that you and future users can walk through the product and find gaps before code is written. There is no database, payment or integration behind it. A first version that real users can sign up for and pay through is built in MVP development, from $20,000, and it starts from the requirements and the prototype that discovery produced.

Yes. The phase is built for new products, internal systems and large sites alike. With an internal system the observation matters even more: we look at how orders, requests or reports actually move today, including the spreadsheets and chats next to the official tools, because those workarounds show what the new system has to handle. Your CRM, ERP or accounting is checked against its documentation, and you receive the same package: requirements, flows, a prototype, an architecture, a risk register and an estimate by stages.