you are not your customer

There is a version of market research that founders do constantly and never acknowledge. They ask themselves what they would want. They test a price point in their own head. They read the landing page and think "this makes sense to me." They watch a demo, see something slightly confusing, explain it to themselves, and move on.

The product ends up shaped by a person who looks nothing like the customer.

This isn't arrogance, necessarily. It's a more structural problem born out of human nature. Founders are deep experts in the problem domain they're building in. They've thought about it for months or years. They have context a typical new user will never have. When they navigate the product, they don't get confused, because they built it and knew what every screen was for before it existed.

A new user doesn't have that context. A new user arrives with a different vocabulary, different assumptions about how software works, and genuine skepticism about whether this will actually help them. They will get stuck somewhere you never anticipated, because the thing you found obvious wasn't obvious. The thing you considered self-explanatory requires explanation.

The gap between your experience of the product and a new user's experience is enormous, and it grows with every day you spend inside the product. By the time you ship, you've lost the ability to be confused by your own software. That's a serious liability.

The gap shows up most consistently in three places.

Onboarding. Founders skip steps because they know what comes next and intermediate steps feel redundant. For new users, those intermediate steps are load-bearing. The moment you remove the thing that felt obvious to you, you've created a cliff that users fall off of silently. Nobody emails to say they left. The data shows a drop in activation and you're left guessing.

Pricing. Founders anchor on what feels like a fair exchange for value they deeply understand. But customers don't price from value in the abstract. They price from budget, from comparison, from what they've paid for similar things, from what their manager can approve without a conversation. A founder who decides $99 per month is clearly reasonable for a product that saves ten hours per week is doing mental math the customer isn't doing. The customer is comparing to the last subscription they cut, not to the hours they'll save.

Messaging. Founders write about the solution. Customers search for the problem. The founder knows the mechanism and finds it elegant. The customer doesn't care about the mechanism. They care about whether the pain goes away. These are different conversations, and founders almost always lead with the wrong one because the mechanism is what they've been living inside.

The fix isn't complicated, but it requires discipline and ongoing proximity to real customers, specifically new ones who don't yet know what you know.

Watch someone use the product for the first time without explaining anything. Resist every instinct to clarify. The moment they get confused is where the product needs work. Documentation is the explanation you give when the product failed to explain itself.

Have pricing conversations before you set prices. Ask customers what they're currently paying to solve this problem, including the cost of not solving it. Ask what would make them say no. The answers will almost never match what you expected.

Audit your messaging by finding someone who fits your customer profile and hasn't heard of you. Ask them to read your landing page and tell you in their own words what the product does. The gap between what they say and what you intended is your conversion problem.

In What You're Actually Building, the Kanga story demonstrates this at company level: the founders built what matched their clean pitch, and the market revealed something different. That's the macro version. The pattern here is more granular, operating meeting to meeting and screen to screen, but it runs on the same logic. The map you carry of your customer's experience is not your customer's experience.

The most useful thing you can do, on a regular cadence, is sit in your own product as a stranger. Try to cancel. Try to change your defaults. Try to find the information a new user would need to make a real decision about whether to stay. If what you find doesn't match the product you believe you're building, you've drifted, and good intentions won't close that gap. Only looking honestly will.

You built it, which means you can no longer see it fresh. Find the people who can, and let what they show you change the product.