Before any collaboration, we conduct discovery. It's not a formality — it's the moment when we understand if and how we can work together.
It is a dialogue in which we listen to the client, ask questions, and put doubts and hypotheses on the table. It helps us understand where they want to go and whether we are the right people to accompany them on this journey.
This guide explains how we structure discovery, what we ask for, and why every step matters.
What happens during discovery
Define your goals
Let's talk about the concrete objectives of your project. Not abstract visions, but measurable results: what needs to happen for the project to be a success?
Understanding the context
We ask our clients to tell us about their business: value proposition, market, target audience and competitors. Not out of curiosity, but because without context we cannot design anything meaningful.
The questions we ask:
— What does your company do?
— What value does it offer customers?
— Who are your competitors?
— What sets you apart from them?
— Who is your target audience?
Setting clear constraints
We define timelines and budgets. Not later, not ‘we'll see’ — right away. Because a project without clear constraints is a project that never gets off the ground.
The questions we ask:
— What is the available budget?
— Does the project have a clearly defined deadline?
— Are there any technical or organisation constraints?
Prepare the ground
After our initial meeting, we usually send a brief. This is a questionnaire containing specific questions that the client answers. It serves to gather key, detailed information before we begin designing and developing a digital product.
During the discovery phase, if necessary, we revisit that document, analyse it and explore it in depth together, thus making it the starting point for the conversation.
Shared strategy
At the end of the discovery phase, a shared strategy emerges. The client has clearly defined objectives, timelines and budget. We have proposed a path forward, a solution that takes all these elements into account.
The result:
— Clear and measurable objectives
— Defined context and constraints
— Shared strategy on how to proceed
— Alignment between expectations and possibilities
No improvisation. No vague promises. Just a clear direction on which to build.
Why it is essential
Discovery determines everything that comes after. If we start off on the wrong foot, everything else will be an uphill battle. If, on the other hand, we build solid foundations, the project will run more smoothly — for the client and for us.
For the customer: clarity on what to expect. Certainty that we have understood their needs.
For us: understanding whether we are the right people for the project. Avoiding projects without direction.
This is the moment when trust is established. Not with fine words, but with clarity, transparency and honesty. And that is where collaboration begins.
This process is essential because it allows everyone to be on the same page. It prevents discovering halfway through the project that objectives, budgets, or timelines were not aligned. This step cannot be rushed. It is the moment that determines whether the project will be successful or will drag on amid misunderstandings and rework.
If there is a time to invest time at the beginning, it is here.