Product Discovery: How to turn an idea into an application that customers REALLY want in 5 steps? [case study]

2025-11-20 | Joanna Iwanków Maison

As a software house with many years of experience, we have seen hundreds of startup ideas. Innovative, creative, sometimes revolutionary. But when working with investors, we treat their budget with enormous respect.

 

That’s why my favorite question to ask a client is, “What do you need this for?” (Someday I’ll write an article with the best answers…🙂)

 

This question can be shocking, but it is crucial. The brutal truth is that most startups don’t fail because of bad technology. They fail because they build something nobody needs.

 

Investing resources, time, and hundreds of thousands of zlotys into an application based solely on a “hunch” is not a strategy. It’s burning money.

 

What if I told you there is a process that acts a bit like an insurance policy for your idea? A process that separates brilliant ideas from those that just SOUND brilliant?

 

It’s called Product Discovery. It is the absolute foundation that determines whether your project will succeed or get lost in the jungle of other applications. I will show you what this process looks like in practice, leading to the creation of the Kidzoom application.

 

 

 

What exactly is Product Discovery? (It’s more than “market research”)

Many entrepreneurs confuse Product Discovery with simple competitor analysis. They think, “I’ve checked other apps, mine will be better.” That’s a trap.

 

Product Discovery is an intensive, structured process aimed at deeply understanding and validating the problem you are trying to solve, even before you write the first line of code.

 

It’s the transition from “I think people need this” to “I know who my customer is, what problem they have, and what feature they need enough to pay for it.”

 

 

 

“But I already know what customers want” – The most expensive mistake in business

 

 

The biggest risk in any digital project is not the technical risk (can we build it?), but the market risk (will anyone want to use it?).

 

Product Discovery minimizes the latter. Instead of spending 6 months and 200,000 PLN on building a complex application, you spend 1-2 weeks on workshops and research to confirm you are heading in the right direction. It’s a process that protects you from your own enthusiasm and assumptions that are not based in reality.

 

 

Case study: Budget under control… or how the KidZoom app was created?

 

Nothing explains this better than a real-life example. Our collaboration on the Kidzoom app began with… a completely different idea. The client came to us with a vision for an application for the education sector. The market? Extremely competitive, full of mature solutions, and difficult to break into.

 

Problem: The idea was interesting, but entering such an industry would require gigantic outlays on programming, testing, and marketing just to get noticed.

 

Solution: We proposed intensive, two-day Product Discovery workshops. The client was somewhat surprised by the vision of two days of “meetings” about a product he had already invented. But he trusted the process.

 

The result: Those two days turned out to be the best investment in the entire project. During the workshops, we jointly discovered that the real, burning, and unaddressed problem lay elsewhere. Every parent faces a dilemma: how to effectively organize their child’s time outside of school? How to find interesting, developmental activities, events, or places, tailored to their age and interests?

 

Pivot! Instead of committing resources to a competitive industry, we identified a niche. This is how Kidzoom was born – a mobile application that makes parents’ lives easier by organizing free time.

The workshops allowed us not only to define a new goal but also to identify key users and initial monetization strategies.

 

 

Product Discovery: How to turn an idea into an application that customers REALLY want in 5 steps? [case study]

 

Fig. Screenshot from the KidZoom mobile application created by Devqube

 

 

 

Our 5-step Product Discovery process based on the KidZoom example

So what does the process that leads to such breakthrough moments look like?

At Devqube, we simplified it down to 5 key, logical steps, which we implemented together with the client.

 

 

 

Step 1: Defining the goal and the problem

We started with the fundamental “why.” As I mentioned, it’s my favorite question.

  • What problem are we really solving?
  • For whom are we solving it?
  • How will we know we’ve succeeded?

 

On the Kidizoom example: The goal was not “to create an app,” but “to save parents time and provide them with inspiration for quality moments with their children.”

 

All attractions in one place, without time-consuming internet searches.

 

Your child,

Your time,

Your moments

 

 

 

Step 2: Competitor and market analysis

But not to copy, rather to find gaps.

  • How are others trying to solve this problem?
  • What are they doing well, and where are they failing?
  • Is there a “blue ocean” – a niche that no one has capitalized on?

 

In Kidzoom’s case, our analysis showed that there was no single place that aggregates all these activities in an intuitive, personalized way.

 

This was our opportunity. This is usually part of a UX Designer’s job. And since we have no competition in this project… they didn’t have an easy task. 🙂 

 

 

 

Step 3: Identifying and understanding users

When we know “why,” we must understand “for whom.” This is where we build so-called personas, or detailed profiles of our ideal users.

This isn’t just demographics. We need to step into their shoes and learn their motivations, frustrations, and needs.

 

In Kidzoom’s case, we identified 3 key user groups:

  • Parents/Guardians of children aged 0-15 (Looking for inspiration and easy organization).
  • Partners (Venues and services that want to reach parents).
  • Event Organizers (Want to promote their events).

 

Understanding that we have 3 different groups was crucial for the application’s strategy and architecture.

 

This is a job for a marketing strategist and involves building so-called buyer personas for each user group.

 

 

 

Step 4: Monetization strategy and action plan

In other words, the specifics. How is the app supposed to make money?

 

Entrepreneurs often postpone this, which is a mistake. The business model must be part of the project from the very beginning.

 

For Kidzoom, we developed strategies based on subscriptions for Partners and promoting Organizers’ events.

 

 

 

Step 5: Defining key functionalities (MVP)

With all this knowledge, we can start talking about features. But here too lies a trap: “feature creep,” or the endless addition of “cool” extras.

 

That’s why we focus on the MVP (Minimum Viable Product) – the absolute minimum required to solve the user’s main problem.

 

  • What is absolutely crucial for the Parent? (Attraction search, age filters, interest categories, map).
  • What is crucial for the Partner? (The ability to easily add an offer, reach the customer group).

Everything else (loyalty systems, gamification, advanced AI) goes on the “for later” list. This allows the product to get to market faster and cheaper.

 

 

 

The result?

The outcome of this workshop is a complete action plan: we know WHAT we are building, FOR WHOM, and WHY.

 

We moved away from the original concept. Instead of committing resources to the competitive education app industry, full of more or less mature digital solutions, we identified a niche in serving the market for children’s services outside of school, preschool, or nursery. We developed a common product vision and a description of its most important functionalities. This was the basis for work on the product’s MVP, which has been released to the wider market today.

 

 

And what does the Client think about all this?

 

 

Product Discovery: How to turn an idea into an application that customers REALLY want in 5 steps? [case study]

 

 

 

 

Frequently Asked Questions (FAQ)

💡 How long do Product Discovery workshops last?

In Kidzoom’s case, it was 2 intensive days. Usually, this process, depending on the project’s complexity, is completed within 1-2 weeks, including analysis and documentation preparation.

 

 

💡 Is Product Discovery only for new applications?

No. It is also a powerful tool for existing products. If your application has conversion problems, users are churning, or you want to enter a new market – Product Discovery will help diagnose the problem and find a solution (a so-called pivot).

 

 

💡 What is the difference between Product Discovery and MVP?

Product Discovery is the “thinking” phase – it answers the question: WHAT and WHY should we build?

MVP is the “building” phase – it is the FIRST VERSION of the product, created based on the conclusions from Product Discovery.

 

 

💡 What specifically do Product Discovery workshops provide?

Product Discovery workshops are not a “casual chat.” It’s an investment that pays for itself immediately, giving you three priceless assets:

  • A concrete plan. Instead of a vague vision, you receive a concrete action plan, the scope of the MVP, and a common product vision understood by the entire team.
  • Budget savings: The most important benefit. The certainty that you won’t spend hundreds of thousands on features that no one will use. It is better to invest 5% of the budget in validation than to lose 100% on a failure.
  • Faster time-to-market. By focusing on the MVP, you radically shorten the time needed to build the first, valuable version of the product and can start gathering feedback from real users sooner.

Start with….

 

If you have an app idea and you’re serious about it, don’t start by looking for developers. Start with validation. Let’s talk about your idea. Schedule a free consultation. We’ll ask you a few questions and together we’ll check the potential hidden in your vision.

 

product discovery - contact devqube

 

Joanna Iwanków Maison
Ostatnio opublikowane przez Joanna Iwanków Maison (zobacz wszystkie)