Building with AI · · 4 min · Updated

Validate the product, not yourself

Testing demand before you build is good discipline. Needing the yes is something else. A field note on how to gather the data without letting it decide what you are worth.

In short

Testing a product and needing a yes look the same from the outside: same screen, same refresh, same waiting. Inside they are two different jobs. One is research, gathering facts to make a good call. The other is a vote on you, where a yes means you are worth something and a no means the whole thing was made up. The move that separates them is the quiet claim you make while you check: this number does not get to say who I am. Not detachment. Not a rule about checking less. Just a different owner in the driver's seat while the data lands. The grab for the phone is the tell that the claim broke, and it breaks earlier, at the moment you stopped feeling settled and the work started having to prove something about its builder. The vote will attach to any object on hand (a message, a signup, a comment), which is why fixing it at the object level never holds. The usable test: can you look at zero responses this morning and still feel settled that the thing is real and worth building? If yes, the research is just research. If no, the real work of the morning sits upstream of the dashboard.

Product validation and needing validation are two different jobs running on identical inputs. Product validation is research: gather demand facts against a live offer (signups, replies, booked calls, ad-click-through) to inform a build decision, and hold both possible answers with equal weight. Needing validation is a subconscious vote on the operator’s self-worth using the same metrics as the input. A yes means the operator is worth something; a no means the work was made up. The surface behavior is identical: same dashboard, same refresh, same 6:00 a.m. reach for the phone. The internal states diverge on one question, which is what the operator is asking the number to prove. Research asks whether a specific offer matches a specific audience on a specific channel. Validation-need asks whether the person who built it is worth something. The move that separates them is not checking less. It is a claim held while checking: this number does not decide what I am worth. The reach for the phone is the tell that the claim broke, and the break is upstream of the reach.

The problem is the tightness while you check. The small drop in your chest when the count says zero. The way the morning starts to feel like a verdict.

Two kinds of validation

Testing a product and needing a yes look the same from the outside. Same screen, same refresh.

Inside, they are two different jobs. One is research. I am gathering facts so I can make a good call, and I can live with either answer. The other is a vote on me. A yes means I am worth something. A no means the whole thing was made up.

You can run the same process from either place. The numbers do not change. What changes is what you need the numbers to prove about you.

What stance turns checking from verdict into research?

The move that makes checking research instead of a verdict has nothing to do with how often you look. It is a quiet claim you make while you look. This number does not get to say who I am.

You do not kill the want. You want the yes fully, and at the same time you refuse to let its arrival or its absence decide what you are worth. Both at once. This is not detachment. Detachment is checking less. This is checking with a different owner in the driver’s seat.

The grab for the phone is the tell that the claim broke. And here is the part I keep relearning. It does not break when the hand reaches. It breaks earlier. Somewhere before the thumb moves, I stop feeling settled that the work is real, and I start needing the world to confirm it. The reach is just that break showing up at the surface.

The vote will attach to anything

The pattern does not care what the object is. A message, a signup, a booked call, a comment from a stranger. Whatever is on hand becomes the vote on whether you are enough.

That is why fixing it at the object level never holds. Mute the app and the vote moves to email. Stop checking email and it moves to the next talk with a client. The object was never the engine. I wrote about the engine in image pursuit dressed as ambition: the same loop, one level down, where the work exists to prove something about the person who built it.

There is a cost past the anxious morning. I wrote a few weeks ago about the vessel, an old word for how much good you can take in and hold. Needing the yes makes that container smaller. The work now has to carry your worth on top of its own weight, and nothing lands well while you are gripping it.

A test you can run

Here is the check I use, most mornings, while the count is still at zero.

Can I look at zero and still feel settled that the thing is real and worth building?

If yes, the research is just research. Keep gathering it.

If no, the vote is running, and more checking will not fix it. Less checking will not fix it either. The work sits upstream of the screen: sit with the part of you that needs the yes before you touch the dashboard again.

The data stays useful either way. What the test protects is the person reading it.

Still in it

I am still in this. I shipped something last week and watched my hand go to the phone before I had decided anything. Some mornings zero lands clean and I go do the work. Some mornings it lands like a verdict, and that is the real work of the morning, before any number means what it says.

Validate the product. Keep the discipline. Watch what you ask the data to prove.

Written by Martin Ronquillo, founder of Genuai. He reads every reply.

Send me Sunday's note

A short note · every Sunday

The Sunday Alignment

For the Sunday night when the week already feels heavy. One short note before Monday: three minutes, one thing to do. By Thursday you have done it once.

One email a week. Free. Unsubscribe in one click.

Alignment is the meta-skill of infinite intelligence.

Open the free app

The Sunday Alignment

For the Sunday night when the week already feels heavy. One short note before Monday: three minutes, one thing to do. By Thursday you have done it once.

Sunday · 3 min · 1 thing to do · not a reading

Send me Sunday's note

One email a week. Free. Unsubscribe in one click.