I recently wrote down a simple product observation that I find myself coming back to:

A lot of early platform products look unfinished because they do not yet have enough features.

No payments. No reviews. No proper booking flow. No dashboard. No deeper workflow layer.

But I do not think that is always the most important question.

In many early products, the harder problem comes earlier: the platform has not yet built enough depth for discovery to feel genuinely useful.

That usually shows up through things like supply density, quality, trust, and onboarding friction — the parts that make a platform feel real enough to search through, compare, and rely on.

why some early products have a depth problem, not just a feature gap

why discovery value often needs to form before the next product layer really matters

why supply density, quality, trust, and onboarding friction can matter more than feature expansion at an early stage

why a product starts becoming a workflow problem once it moves from listing into user actions

For early-stage platform products, the deeper question is often not:

It is:

If discovery still feels thin, the next feature layer often stays weaker than it looks on paper.

I’m interested in backend and platform problems where workflows, integrations, and operational reliability need to hold together cleanly.

This kind of product thinking matters because once a platform starts supporting real user actions, it quickly stops being just a page or interface problem. It becomes a structure, flow, trust, and reliability problem.

I tend to look at early products through:

stage and priority

platform depth and discovery value

workflow implications once user actions become real

trust, structure, and operational reliability

Full note on Medium: