How should a founder interpret initial customer enthusiasm followed by hesitation when shown an early product prototype?

Question

Accepted Answer

So I'll start by saying that the smartest thing you're doing is not quitting your job yet. It's absolutly right to wait for a better signal.

As for the 180 degree shift in customer reaction, you got the reaction you were supposed to get.

The first response was to the problem. The second was to your solution. People love nodding at pain; they get stingy when asked to change behavior.

That is not a signal to pivot. It is a signal to get more precise.

My advice: stop “building the product” and start running a series of tiny experiments. Pick one trade, one use case, one narrow quoting workflow. Then ask: will someone use this on a real job, this week, even if it’s clunky?

You showed them a prototype and they refussed to use it. Why? What was missing? What were they scared of? Are they concerned about estimating errors (which would be much more painful to them than the efficiency of a quote would benefit them)? Are they concerned about upsetting a regular customer with something that looks half-assed?

In other words, don’t optimize for compliments. Optimize for behavior. Find someone whose pain is so great that they will pay you to solve it for them even if the solution is half-assed.

If they say, “Make it more usable,” great — that’s not rejection, that’s direction. But don’t disappear for 3 months to polish. Sit beside them, watch them quote, and solve the ugliest 10 minutes of the process first.

And 20 interviews across different trades? Useful, but noisy. Useful because you will find out which one of them hurts the most (and will be most desperate for your solutoin). But decorators, plumbers, electricians all behave differently, so if you're geting all that feedback to build a product that works for everyone, you are going to be too generic. Narrow the beachhead and solve one problem for one customer type really really well.

So my vote is option 3: neither keep building blindly nor pivot blindly. Shrink the scope, test with real jobs, and let usage—not enthusiasm—tell you what to do next.