The riskiest thing is still building before you really learn.
Editorial insight
Something has been shifting quietly in product work.
We could say a few years ago, but honestly, just a few months ago, most conversations started with a brief, a deck or just an idea. Now, more and more teams show up with something that already looks functional. A demo stitched together from different tools. An internal prototype someone built on a weekend.
On the surface, this should make things easier. In practice, it changes what comes next. Even the role of a partner team shifts: are they here to build, to validate, to fix, or all of the above?
At the same time, many teams are hesitant to invest in “discovery work” that does not end in something concrete. Some teams want a real piece they can put in front of early customers, sponsors or investors. Others need something real enough to bring into a decision meeting.
Getting to “something on screen” faster is powerful, but it also hides risk. When it is this easy to produce a demo, it is just as easy to skip the hard questions: what are we actually validating with this, for whom, and what will we decide differently if it goes well?
What this period is really testing is not how fast teams can produce prototypes, but how they choose to reduce risk: through big, hopeful builds or through smaller, more honest experiments.
This edition is about that choice.
Value piece
How to take low-risk paths and bring bold ideas to life
When “not sure yet” is the honest answer for “How sure are you before you build?”, most teams end up choosing between two unhelpful extremes: staying stuck in abstract discovery, or jumping into a big build that is still, in practice, an expensive guess.
There is a middle path we see more and more teams looking for: a short discovery cycle that already ends with a focused prototype. Not a full product. A small, representative slice of the idea, built to answer one simple question: “If it worked like this, would it still be worth betting on?”
The value shows up in three ways:
Less risk, because customers and stakeholders can use something, not just hear about it in theory.
More speed, because within a few weeks, there is already something real to observe, adjust, or even discard.
Better thinking, because a small product + design + tech team works together from day one instead of in hand-offs.
In some contexts, that prototype is a simple click-through used in early conversations with customers, sponsors, or investors. In others, it is a critical journey mapped clearly enough to bring into a decision meeting without overpromising or pretending it is more finished than it is.
When an idea is too important to ignore and too early for a full build, this kind of small bet gives you what is usually missing: a concrete way to learn before you commit serious time and budget.
Untile Picks & Trends Radar
Another month, another newsletter, and a few picks from our team that feel especially close to this edition’s theme:
If you are weighing how big your next move should be, this piece on small bets vs big bets is a good reminder of why many low-risk experiments often beat a single all-in project over time.
For a take on our prototype first, commit later idea, this HBS article on rapid prototyping shows how teams use early prototypes to reduce risk and get to market faster, without full builds
This LinkedIn post on “the two AIs” is a sharp take on speed vs control. A good metaphor for using AI to explore many ideas without lowering your standards.
And since we are all experimenting with tools anyway, the comic above is here as a tiny “this escalated quickly” break between meetings.
When “just a small prototype” quietly turns into a full build.
Use Cases & Case Studies
Entering a crowded market without a blind bet
Popcasts entered a crowded market by making one clear product bet
Popcasts, a podcast brand from Grupo Renascença Multimedia, wanted to move from a web-only hub to a dedicated mobile app in an already crowded podcast market, without an “infinite budget” or copying every existing player.
We used a focused discovery track to understand what heavy listeners actually cared about, instead of starting from a long feature wishlist.
That led to a clear bet: a simplified, personalised listening experience, not a bloated “me too” app.
Only then did we move into hybrid app development, keeping scope tight and collaboration close between teams.
Result: Popcasts entered a mature market with a focused app that felt distinctive, not overloaded, and started learning from real users without a big, blind build upfront.
Inside Untile
Keeping standards high while everything moves faster.
February was a short month, but a lot happened on our side. Here are a few highlights:
“From the ‘garage’ to the digital revolution.” We turned 17 last month and took a moment to celebrate with the team over lunch and an All Hands. You can check a bit of that moment here.
Open Days Women’s Edition is here. This time with case confessions from three women leading products and companies. If you want to join us in Viana, you can save your spot here.
How our culture supports collaboration and innovation. Our COO, Elisabete, just published a new article on our blog about our team and culture. Curious? You can read it here.
Global App Economy Conference. Ricardo was in Brussels meeting with policymakers about the reality of small tech in Europe. His recap is totally worth a look here.
Do we have a Product Manager here? We’re still on the lookout for a Product Manager. If you think you could be the one, apply here.
From the team
“I am very demanding by nature, and that did not change. What changed is that today’s tools let us explore ideas much faster without lowering the bar. It makes me excited about what we'll build next!”
Till next month!
Across early-stage teams and large organisations, we keep seeing the same pattern. Ideas get stuck between “too early for a full build” and “too important to ignore”.
This is exactly the space where a short discovery track can make the next step clearer. A small, focused bet, with a team that is used to turning fuzzy ideas into something concrete enough to test with customers and stakeholders.
If you are sitting on an idea like that, you do not need a big project to get started. A short, low-risk validation track is often enough to see whether it is worth going further.
Maybe this is your sign to put a few things on the right path for this next chapter.