THE QUICK READ

Who is Yashish Dahiya?

Yashish Dahiya cofounded Policybazaar in 2008. The venture addressed how people discover and compare insurance. His story is useful for studying a product in which presenting more choices is only part of the problem: users also need to understand what the choices mean.

Founder profiled
Yashish Dahiya
Company or institution
Policybazaar
Reading lens
Fintech

Source starting point: Policybazaar: founding purpose and company history ↗. Full sources and context appear below.

A comparison is useful only when the person reading it understands what is being compared. Policybazaar’s company history dates its beginning to 2008 and describes a mission to improve transparency around insurance. Cofounder Yashish Dahiya brought experience from consulting and businesses including eBookers to the venture.

Information is part of the experience

The company’s own account emphasises simplifying information about plans. That points to a product challenge beyond displaying a set of prices. A customer also needs to understand differences in what is covered, how a product works and which questions remain unanswered before choosing.

Clarity does not remove judgement

A marketplace can organise information, but an individual decision still depends on circumstances and the actual policy terms. Treating every option as interchangeable would undermine the purpose of comparison. A thoughtful interface should make meaningful differences easier to inspect instead of hiding them behind a single ranking.

The founder lens

Our interpretation of Dahiya’s story is to examine categories where the difficulty is understanding a choice, not finding an option. A company can make a complex market more approachable by explaining its structure. This is a profile of that business idea, not an insurance recommendation or an assessment of any particular plan.

A comparison needs a shared basis

Two options can appear comparable on a screen while differing in ways the reader does not understand. A founder building a comparison service should ask what each label means to a first-time user and which details materially change the interpretation. The design task is to make uncertainty visible rather than compress every choice into a headline price. Observe the questions people ask after viewing a comparison. Those questions can reveal missing context, unfamiliar terminology or a need for a different kind of assistance. The founder lesson is that clearer information is itself product work. It requires ongoing attention to the relationship between the interface and the underlying material.

The decision and its trade-offs

Comparison requires a common frame. Prices can be placed side by side more easily than exclusions, responsibilities and differences in coverage. A founder working in a complex category needs to decide which information must be understood before a user can make a meaningful choice, and how the service handles uncertainty after the initial purchase.

How to investigate the operating model

Observe a comparison task without assuming that a completed form means understanding. Ask the user to explain the differences they consider important and where they would seek clarification. Separate the role of discovery from the roles of advice, underwriting and claims. Clear boundaries help a product explain what it does and where another institution is responsible.

Evidence and context

This founder profile does not recommend insurance or evaluate individual policies. Coverage, eligibility and claims processes depend on current policy documents and the relevant provider.

YOUR WORKING NOTES

Put the idea to work

Use these questions to investigate the idea in your own context.

  1. Identify the assumptions behind each comparison field.
  2. Ask a new user to explain the differences in their own words.
  3. Make the route to fuller product information easy to find.

A closer look

What makes an insurance comparison understandable?

A reader needs to understand the basis of the comparison and the differences that matter, rather than see prices without context. The Policybazaar profile explores that product-design question and the role of clear explanations in a complex purchasing decision.

What should a founder investigate in the Policybazaar story?

Examine comprehension, unresolved questions and the path to post-purchase support alongside conversion. A faster purchase is not automatically a better understood decision.

Sources & editorial note

This profile draws on the public sources below. Company and founder accounts describe their own perspective. Our analysis, questions and takeaway are editorial interpretation. This is not an original interview or a sponsored feature.

See our editorial standards or request a correction. For a useful comparison, read Deep Kalra: the MakeMyTrip founder story. Explore the founder topic guides for connected reading paths.