Insights

Idea and Product Validation: Earn the Next Decision

Salim Akil · · 3 min read

Validation is not a certificate you earn once. I want evidence for the decision in front of me: continue, change, invest more or stop. These clips make that distinction across content, logistics and new revenue streams. The right evidence changes when the model changes.

Match the Signal to the Model

In Argaam's first validation discussion, Islam Zween describes a content business watching daily users, time spent, pages viewed and interaction. Those signals help explain whether an audience is finding the content useful. They do not, by themselves, establish that the same people will pay for a subscription.

That is the distinction I would bring into a UAE or KSA venture review. If the model depends on paid renewals, traffic is not enough. If it depends on advertising, audience behaviour matters, but the commercial relationship with advertisers still needs to work.

Test the Old Model's Limits Before Declaring a New One

The second-validation clip describes another attempt to grow an advertising-led model before moving towards subscriptions. Islam discusses expanding the audience through Akhbaar24 and reaching a broader news segment. The point is the sequence of questioning, not a universal traffic target.

I read this as a warning against changing the revenue model simply because the current one is difficult. First understand which assumption is failing. More reach, better monetisation and a different customer segment are separate hypotheses.

Let a Real Customer Expose the Product

The early-product clip recalls Fetchr serving a handful of local clients and learning through deliveries that the team sometimes did themselves. Idriss argues for getting market feedback before building too much. The useful part is not embarrassment as a badge. It is discovering what does not work while the scope is still small.

I would keep an important boundary around that advice: a small test is not permission to ignore safety, security or legal obligations. Reduce scope, not responsibility.

Buy Evidence Before You Buy Scale

In the product-validation clip, Idriss describes reserving a small part of a business's resources for experiments. He wants to see early customer adoption and unit economics before building the larger investment case. His description is deliberately scrappy: small teams and technology built to test rather than to support full scale.

That is different from starting with a market report and using it to justify a major commitment. A market report can guide a question. It cannot tell you that your own product will be adopted at a workable cost.

A New Revenue Stream Needs Its Own Proof

The proof-of-concept clip makes this explicit: an established company still needs a POC for a new service or product. Idriss describes a small team, further customer validation and attempts to get customers to pay before moving ahead.

Paris Norriss gives a complementary example in the business-model-verification clip. Distributing his own shows demonstrated a capability; distributing other people's shows tested it as a service. He links the model to ongoing royalties and a business that is less dependent on his involvement in every task. Those are his stated aims and experience, not a guarantee of company value.

My practical test is to name the next uncertainty and the smallest responsible way to learn about it. Do not carry proof from one product into another without checking what has changed. Validation earns the next decision; it does not remove the need to keep learning.

Bottom Line

Related reading

Put this into practice with Venture OS. Venture OS is BE Venture Partners' step-by-step platform for taking an idea from a problem to a validated business, with AI-powered tools, expert and mentor insight, and real customer testing. Start in Venture OS.

Salim Akil — Venture Building Consultant, BE Venture Partners · Host, B Model Podcast. LinkedIn