How to Validate a Startup Idea Before Building an MVP
- Pilar del Prado Abril
- Mar 6
- 3 min read
Many products start in the same place.
A clear intuition about a problem worth solving and a common question: how do you actually build this if you are not technical?
That question was the starting point of the conversation between Javier Mateache Calderón, CEO of Nomu Labs, and Fernando López García on the program Éxito sin Edad on Déjate de Historias TV.
The interview focuses on a challenge that appears again and again in early-stage projects: founders with a strong idea but without the technical background to turn it into a product.
Technology today is more accessible than ever.
Artificial intelligence accelerates many processes.
Prototyping tools allow teams to build faster.
What has not changed is the core difficulty in early stages: understanding whether what you are building actually has a market.
The real problem is rarely technical
Many founders assume that the biggest challenge is development.
In practice, most early-stage failures come from a different place.
Teams build the wrong thing.
Highly capable engineers can spend months developing features that users never adopt. Startups with funding can burn significant capital validating the wrong assumptions.
Execution is rarely the limiting factor.
Clarity around what should be built usually is.
During the interview, Javier Mateache explains that this pattern appears repeatedly in projects that come to Nomu Labs. The conversation revolves around questions every team should answer before writing code:
what real problem is being solved
who experiences that problem frequently
what user behavior would confirm that the solution creates value
what signals should be observed before scaling
Without those answers, development simply accelerates uncertainty.
Building without a technical team
Many founders launching digital products are not technical. That is not necessarily a limitation.
The challenge appears when a product is built without a clear validation strategy.
Common patterns start to appear:
an MVP that becomes too complex
long development cycles before talking to users
poorly defined metrics
decisions driven mainly by intuition
The product evolves, but validation does not.
The interview explores practical ways founders can move forward when they want to launch a technology product without building a full technical team from the beginning.
Speed does not equal validation
Access to new tools has dramatically reduced technical barriers.
Building is faster.
Validation is still difficult.
Prototyping something in days can be valuable if the goal is to learn something specific from users. Without a clear learning objective, speed simply produces more noise.
That is why an important part of early product work is transforming an idea into measurable hypotheses.
A good hypothesis includes three elements:
a clearly defined user
a specific problem
an observable signal of value
When those elements are defined, the MVP becomes an experiment rather than a full product.
What happens before the code
At Nomu Labs we work with early-stage startups, corporate innovation teams, and international organizations launching new digital products.
In many cases, the work begins before development.
Before writing code, teams need clarity on decisions that will shape the entire product:
which problem should be addressed first
which feature should be tested
which metric should be tracked
which signal indicates real market demand
This process allows teams to define the right MVP and avoid months of unnecessary development.
Over the years we have supported products ranging from early startups to initiatives with organizations such as FIBA and Samsung, as well as platforms like DiveLife and ViveEspaña.
Across these projects, the same pattern appears consistently.
The teams that move fastest are not the ones building more features. They are the ones making better decisions about what to validate first.
Turning an idea into something measurable
One of the central points in the interview is how founders can transform an idea into something testable.
Ideas usually sound like this:
We want to build a platform for X.
A hypothesis sounds different:
If we offer this solution to this type of user, we expect to observe this behavior.
That behavior becomes the signal that the product creates value.
Until users interact with the product and those signals are measured, it is difficult to understand whether a product truly works.
Watch the full conversation
The full interview with Javier Mateache Calderón on Éxito sin Edad covers several topics relevant to founders and product teams:
how Nomu Labs started
early challenges when launching technology products
the problem of information overload in entrepreneurship
practical advice for founders
how to approach building a startup without a technical background
how to turn ideas into market-validated products
A direct conversation about the decisions that actually determine whether a new product succeeds or fails in its early stages.
For anyone validating an idea or exploring the next step in building a digital product, the discussion offers a practical perspective on how to reduce risk before investing time and capital.
.
Comments