DDeep Dive with Ali Abdaal
← All frameworks
InnovationJulian Hearn Founder Of Huel

Unsolicited Demand Signal Loop

Difficulty
Advanced
Time to result
~months to results
Steps
6
Confidence

Guide product development by listening for needs customers express naturally rather than relying mainly on prompted surveys or competitor imitation. Monitor comments from existing customers and from people explaining why they rejected the product. Treat isolated requests cautiously, but act when the same underlying need appears repeatedly across ads, forums, and customer conversations. Convert the pattern into explicit product constraints, then prototype possible solutions. Because feasibility, cost, taste, and manufacturing can invalidate an attractive concept, pursue multiple projects far enough to uncover their limitations and kill weak options. The approach keeps development grounded in real friction while preserving judgment: customers reveal the problem, but the company still decides how to solve it without cluttering the range.

Origin

Extracted from Deep Dive with Ali Abdaal

How to run it

  1. 1

    Listen to Customers, Not Competitors

    Prioritize the needs of the people buying or considering your product instead of copying another company's audience.

    Pro tip Direct-to-consumer channels provide a continuous stream of first-hand reactions.

    Watch out A competitor's successful feature may not suit your own customers.

  2. 2

    Monitor Buyers and Rejecters

    Collect natural comments from current customers and from prospects explaining why they have not purchased.

    Pro tip Read comments beneath advertisements as well as messages in customer forums.

    Watch out Only listening to satisfied customers hides barriers that prevent conversion.

  3. 3

    Wait for Repetition

    Look for the same underlying request appearing often enough to indicate a durable demand signal.

    Pro tip Group differently worded comments by the problem they are trying to solve.

    Watch out Trying to satisfy every individual request creates an unfocused and cluttered product range.

  4. 4

    Translate Needs Into Constraints

    Turn the recurring demand into concrete requirements such as more protein, fewer carbohydrates, a natural sweetener, heat, or chewable texture.

    Pro tip Define what the new product must accomplish before deciding its exact format.

    Watch out Do not mistake a customer's suggested feature for the only possible solution.

  5. 5

    Prototype Multiple Paths

    Develop and test several possible products far enough to expose cost, manufacturing, taste, and feasibility issues.

    Pro tip Mock up or sample the idea before committing to a full commercial launch.

    Watch out Rejecting every unconventional idea from the desk prevents useful learning.

  6. 6

    Kill or Launch

    Stop projects that reach a genuine dead end and launch the solutions that satisfy both the customer signal and commercial constraints.

    Pro tip Keep the total live range focused even if the development pipeline contains many experiments.

    Watch out Sunk effort is not a reason to release an expensive, infeasible, or unwanted product.

In the wild

Huel Black Edition

Huel repeatedly heard customers ask for more protein, fewer carbohydrates, and a natural sweetener. The team converted those recurring requests into Black Edition rather than simply copying a competitor's formulation.

Black Edition became Huel's number-one product.

Hot and Savoury

Customers asked for food that was hot, savoury, more chewable, and closer to a traditional meal while retaining Huel's nutritional proposition. Huel responded with its Hot and Savoury range.

The request pattern led to a distinct product category within Huel's focused range.

Common mistakes

Asking Leading Survey Questions

Prompted respondents may provide what they think the company wants to hear rather than reveal their strongest natural concern.

Building Every Requested Feature

Serving each comment independently produces unnecessary complexity and weakens product focus.

Rejecting Before Testing

Some feasibility questions can only be answered after the team begins prototyping and follows the idea far enough.

From the transcript

i don't believe in surveys i don't believe going out asking people i think it needs to be given to you without them you asking…

Julian Hearn · 1:15:00

people for a long time said i want more protein i want less carbs and i want a a natural sweetener so we created black…

Julian Hearn · 1:15:30

you got started before you find out the answer you can't just think of idea reject it straight i want to try it first

Julian Hearn · 1:16:30

From the episode

How I Built a $72,000,000 Business In 5 Years - Julian Hearn Founder Of Huel

Julian Hearn Founder Of Huel