Introduction: The Challenge of Relevance in Software Development
Developing an application is one thing; creating one that users actually want to use is another. The difference lies in the depth of your understanding of the pains, desires, and unmet needs of your target audience. Too often, development begins with a solution looking for a problem.
I recently embarked on a journey to optimize my product discovery process, moving from time-consuming manual methods to an AI-assisted application building workflow. My mission? To build a flow that not only generated ideas but deeply validated them against the real sentiment of the market.
The Flow
1 - The Raw Data Collection (Sources): I focused on a specific topic of interest and fed NotebookLM's source feature with complex data:
- User Pains: Documents extracted from forums (Reddit, communities) to investigate pains unresolved by existing solutions.
- Market Trends: Articles and research on emerging trends (e.g., generative AI integration, specialized niches).
- Competitive Analysis: Detailed reviews and descriptions of competitor applications.
2- Information Cross-Referencing and Analysis: NotebookLM excelled at finding connections. By asking the model to cross-reference data, I could quickly identify patterns of complaints and resource gaps in the market.
3- Generating Strategic Insights (Prompts): I used structured analysis prompts to synthesize the data into actionable insights: "Cross-reference market trends with competitor features and identify a feature that is in high demand, but has low coverage in the market."
4 - The MVP Conception (Final Prompt): The final step was generating a highly refined MVP prompt, ready for development:
"Generate an MVP documentation (including Target Audience, Value Proposition, and 3 Essential Features) that addresses pain X, aligns with trend Y, and offers feature Z (low/non-existent coverage). The goal is for this MVP to be built on Gemini 3.0."
Scaling Discovery with Google Opal
The initial validation phase using NotebookLM was an insightful experiment, but it still required significant manual intervention. Now, it’s time to evolve this workflow into a truly automated engine.
This led me to Google Opal, the platform designed to turn complex logic into visual, multi-step AI Workflows (or mini-apps). While the concept mirrors the functionality of AI Agents - systems that take action autonomously - Opal provides the no-code workflow pipeline for orchestrating these steps reliably.
In Google Opal, the goal is to create a product discovery agent pipeline that operates continuously.
Step 1 - The Search: At external sources (forums, reviews) to filter and feed new pain signals and trends.
Step 2: The Analyst: Analyzes data from phase 1 against competitive data to generate strategic gaps and novel feature ideas.
Step 3: The Strategist: Converts the strategic report into the final assets for development and business.
Here is the step-by-step breakdown of how I configured the three core agents in Google Opal, turning a simple workflow into an autonomous pipeline.
Step 1: The Search (Data Ingestion)
This step is the system's eyes and ears, responsible for ingesting and pre-filtering raw market data.
1 - Topic of Interest: UserInput Initially empty node where the user enters the topic of interest.
2 - Search Users, Trends and Competitors: Generate Nodes for search with specific prompts
3 - Users Opinion, Trends and Competitors: OutPut (Google Docs)
Each output node I specified "Save to Google Docs" and set a name for the file in Advanced Settings.
Step 2: The Analyst (Insight Generation)
This is the brain of the operation, where raw data is turned into strategic intelligence.
1 - Analyze Problems: Generate
2 - Strategic Analysis: Generate
3 - Pain Points: OutPut (Google Docs)
4 - Strategic Analysis: OutPut (Google Docs)
Step 3: The Strategist (MVP & Pitch Generation)
The final takes the distilled strategy and turns it into deliverable assets for developers and stakeholders.
1 - Ideas App Generate
2 - MVP Recommendation Generate
3 - Generate Pitch Generate
The nodes are connected to other OutPut (Google Docs) (Ideas, MVP Recommendation) for creating files in Google Docs and the node Pitch has type OutPut (Google Slides)
And finally, the last step where we add a node to generate the Prompt for Gemini 3, another with an HTML output showing the result of the entire flow execution.
Conclusion: From Idea to MVP in Minutes
1 - Prompt to App: Generate
2 - Prompt for Gemini 3.0: OutPut (Google Docs)
3 - Generate HTML: OutPut (Manual Layout)
It transforms your workflow into an innovation pipeline quickly, ensuring that your next application not only meets a market need but is designed to address a real problem the market is actively complaining about.
By leveraging the power of agents and workdflows, we can move from market insight to a complete, validated, and ready-to-code MVP specification in minutes, significantly de-risking the development process.
To create the MVP, simply use the generated prompt and run it in the Build tab of ai.dev, letting Gemini build it for you.
Want to put it into production? Use the icon in the upper corner of the built app screen to send it directly to Google Cloud.
Top comments (0)