Discovery call - what is it, and when does it take place?

Let's begin with a definition and a timeline.

  • Our cooperation with you starts with the initial call. It consists of introductions, some essential information exchange and acts as the first checkpoint for both parties. It serves us to determine if the project is doable - from a big picture perspective. The initial call is also meant to tell you if our software house is a good fit for the job you need to get done. If yes, then we can sign our NDAs and go further.
  • Before we meet again, we spend some time working on mutual understanding. We learn more about you and your project from the documents and white papers you provide. It is also time for you to prepare a coherent vision and requirements for your project, which you share in the next stage, which is…
  • …the discovery call - this is where we stop today. It is a crucial stage that is to help us understand your idea as well as you do.
  • Based on the knowledge acquired during the discovery call, we have grounds to prepare a workshop.

To sum up, the discovery call is an exchange of information between technical teams or persons from our and your side. Together, we are to find out what exactly is to be done. During the conversation, the entire vision is often verified on an ongoing basis - if it turns out that something in our opinion is missing or pointlessimpossible, and we see it on the spot, we can comment on it immediately.

We come out of the discovery call with a fairly complete understanding of the project, as well as with specific challenges to think about. This allows us to appoint a team of experts to meet you at the workshop, which is followed by the offer on our part.

What is the most important in the discovery phase?

For the discovery call to run smoothly and effectively, both your and our preparation is crucial.

Key elements of the discovery call

After our initial call and collecting materialsfrom you, our CTO prepares a list of questions about your project. We use the discovery call to discuss everything that is not yet clear to our team - potential risks and challenges or tech choices. For the conversation to be mutually beneficial, it is vital that you:

  1. provide a person responsible for the technicalities - only such a person will be able to share the information we need,
  2. have a well-thought-out vision of the project and are ready to answer detailed questions - perhaps it is worth having the documentation at hand.

The key to us is to deliver value to our customers, so the more thoroughly we understand the project assumptions, and the more information we get, the better.

General and specific questions - examples

First things first. What must we know from the very start? Our three basic questions are:

  1. What is to be created as a result of this project?
  2. What change or value will it bring to the persona/market/world/people?
  3. How will it function - can you describe its basic features?

We already know the general answers to these questions at the initial call stage. During the discovery phase, we clarify them and consider how to achieve the goals defined in the process.

At the discovery call stage, we refine the business vision with technical details. We want to know what exactly is to be built and in which part you need our support. Do you have your team, or are we responsible for the project from A to Z? What technologies would you like to use? What is the project's timeframe - is there a specific deadline for go-to-market?

The purpose of this stage is to set goals, the implementation plan of which we will develop together in the workshop. However, it is crucial that we leave this meeting with a sense of mutual understanding and a clear vision of what is still vague and needs working on during the workshop.

What follows a discovery call?

The discovery call lasts up to one hour. However, during this time it is not possible to estimate a large project that will take months or years.

That's why we want to meet you. After the discovery call, you will receive a quote from us for the workshop we organize to:

  • enable our client to get to know us better,
  • deliver quick wins, so some easy-to-carry-out tasks are already checked off the list,
  • prepare a valuation based on dialogue and maximally precise estimation of what is to be done.

The workshop is dedicated to you and your project - we plan it based on your needs, which we define together at the discovery stage.

We come to the workshop prepared, with supplemented knowledge, research done, and lots of energy to work together.

Getting to know each other better is especially important - thanks to this you can understand better what we have to offer and how we work. In addition, you will meet the developers, project managers, and other people who are to be personally involved in the project. In this way, we can create a relationship from the first stages of cooperation and thus work more effectively and in a pleasant atmosphere.

After such a workshop you can be sure that your project is on course. The next step is an offer with a complete estimate and then we can take off.

It is worth mentioning, that workshop is not always needed. If you are after something basic, a quick fix, or a team extension, we go from discovery call straight to the offer.

Let’s wrap it up! A checklist for you

Summing up, after the initial call, when getting ready for the discovery stage, you should remember to:

  • have a clear concept of your project - best if it's specified in the documentation,
  • be able to tell what is to be the project's outcome - an app, software, or something else,
  • have a quite detailed vision of how the product is going to work,
  • know the estimated date when the project needs to be ready to conquer the market,
  • have a budget bracket well thought through,
  • specify your needs - what kind of engagement do you need from us. Should it be complex support in creating the product from A to Z, or maybe just some assistance?

If both parties approach the discovery call with commitment and clearly defined requirements, the cooperation will quickly prove fruitful.

There is no single scheme for a discovery call

Every project is different. That's why we don't really have a scheme for a perfect discovery call. Instead, we approach each cooperation with open minds and readiness to put everything upside down. All we need is your engagement and willingness to share information. As soon as we have that flow, we will be ready to immerse ourselves in your idea. But only if we get these first stages done thoroughly will we be able to deliver a robust working product to you.

It's called discovery call for a reason. It is supposed to provide total exposure - we throw questions at each other to come up with a plan to get your vision to see the light of the day. And if we believe it's worth it, we will undoubtedly get there.