What Changed My Mind About Problem Interviews (Non-Technical Founders)

I used to skip problem interviews. I was non-technical, I had energy, I had no-code tools, I could just build. Talking to strangers about their week sounded slow and faintly humiliating. Several wasted contractor invoices later, I changed my mind. Here is what actually did it.

It Was Not the Failed Launches

Failed launches did not change my mind. I rationalized them. The marketing was wrong, the timing was off, the audience was distracted. There was always a story that did not require interrogating the underlying premise.

If you have only shipped one thing that flopped, you can probably explain it the same way. The denial is comfortable and works for a while.

It Was Not the Books

I read the books. I knew the arguments. None of it changed my behavior, because reading about a discipline is not the same as adopting it. I treated the books as theoretically true and personally optional.

What Actually Did It

An invoice. Specifically, an invoice for $4,200 from a contractor for two months of work on a feature that nobody used.

I had hired the contractor based on what felt like a strong intuition about the audience. I had not interviewed anyone. I had read about problem interviews and concluded I was the exception - I knew this market, I had been in it for years, I did not need to validate.

The product launched. The feature got crickets. I rationalized it as a marketing failure for a few weeks. Then I started doing what I should have done first: I called ten people who fit the audience and asked them about their week.

The Specific Realization

By the third call, the pattern was clear. The audience had a related but different problem. The feature I had paid for solved a problem that existed in my head, not in their workflow. They would have told me this in week one if I had asked.

The lesson was specific: the $4,200 was a test of my intuition. The intuition failed the test. Ten thirty-minute conversations would have caught the same failure for free.

The Cheaper Version of That Realization

I should have engineered ten of those conversations on purpose, before signing the contractor agreement. That is, exactly, problem interviews. Engineered conversations with people who plausibly have the problem, run before the build.

The realization that changed my mind was not that interviews are good. It was that the conversations that would have saved my $4,200 were reproducible on demand, and I had been refusing to reproduce them.

Why This Hits Non-Technical Founders Harder

Technical founders also pay for being wrong. They pay in their own time. Non-technical founders pay in cash, which is harder to recover. Every wrong assumption that survives into a contractor brief becomes an invoice. The interview round is the cheapest insurance available against that specific cost.

What I Did Differently After

Every project since: at least ten interviews before signing any contractor or agency agreement. Some have killed the idea. Some have rearranged it. A few have confirmed it. None have been wasted, even when the conclusion was "do not build this." Especially when the conclusion was "do not build this" - that conclusion saved the most money.

I am not better at interviews than I used to be. I am just willing to do them now. The willingness is the entire skill, and it shows up only after you have paid the cost of not having it.

What This Means for You

If you are a first-time non-technical founder reading this, you do not yet have the scar. The arguments above will not move you the way the scar would. I am not going to tell you they should. I will tell you the scar arrives, sooner or later, and it is much cheaper to take the lesson on faith now than to pay the tuition.

One conversation. With one person. Before you sign the next contractor agreement. That is the threshold of trying.