I used to think the basic logic of doing business should be simple: find a real problem, build a product that can solve it, then find people who have that problem. Sales would follow naturally.
After repeated setbacks in trying to make that work, I gradually rebuilt my approach to marketing.
You may already have promoted your business, contacted potential customers, changed how you explain what you offer, and listened carefully to feedback. Yet the market still hasn’t responded as you hoped. At that point, hearing “Even a good product needs good marketing” is of limited help. What you need to understand is why you still haven’t made a sale, even though you have a product that can solve a problem and have found people who might need it.
The developer of Voloshow said on Hacker News that their AI image and video generation website had been live for nearly a month without attracting any users. One person who tried it described their experience in detail: they entered a prompt and were asked to sign in; after signing in with Google, they had to choose a different prompt, had trouble browsing on their phone, and were finally told they had no credits. They then opened Gemini, entered the prompt again, and tried to generate an image for free. Another commenter ran into an error while signing up.
A few days later, the developer replied that they had fixed the login issue and added credits for trial users. Looking back at that attempt, the user wanted to generate an image, yet had already spent time completing several steps without even getting to use the site’s generation capabilities. Another option was right there. To keep trying this unfamiliar website, they would have to be willing to put in more time.
For the provider, signing in, setting things up, and submitting information may just be preparation for use. For the customer, those steps are already their experience of the product or service. They begin judging it here and may not wait to see what it can do later.
Before any of that, a customer also needs a reason to give it a try.
Acknowledging a problem only means that someone is dissatisfied with the way things are. Whether that problem is worth dealing with now is a separate judgment. Some work may be inefficient, but it can still be done manually. Some losses are real, but addressing them may not rank among the top few priorities right now. They may also have bought another solution that they aren’t entirely happy with, but at least they know where it will go wrong.
When they encounter your product, they compare it with these existing ways of doing things. They have to weigh what they’d gain by switching to your solution against what they’d have to put into it.
Price is only one part of that. Organizing information, migrating data, learning how to use it, and persuading colleagues all take work. A service that promises to save time may first require the customer to spend several hours explaining their situation, preparing materials, and coordinating with the people involved. What you see as preparation also takes up their time.
Even if they believe the solution works, they still have to ask: Will it work in my circumstances? Can I make good use of it? If something goes wrong, who will handle it? When a business makes a purchase, the people using the product, approving the budget, and handling implementation may each have their own concerns.
So a smooth demo or a sincere compliment is still a long way from a purchase. While watching a demo, customers can temporarily accept the scenario you’ve set up. To actually adopt it, they have to commit their own time and budget and make room for it in their work.
And you still need a practical way to reach these people.
“Small businesses have this problem” describes a group of potential customers, but it doesn’t tell you when they’d start looking for help, whether you can be there at that moment, or why they’d be willing to stop and listen to you. Even if you can reach them, you still need to consider how much money and time it takes and whether you can keep doing it.
You also need to look at what actually happened when you promoted it. A message that never reaches a decision-maker is one situation; a decision-maker understanding it and still having no interest is another. They call for different next steps. Yet both can be recorded as “Sent it. No results.” Knowing only which channels you’ve tried doesn’t tell you how far those attempts got toward a sale.
That original way of thinking leaves out many of the conditions that determine whether someone buys. It also carries a deeper assumption: you’ve already settled what the product is and who the customer is. All that remains is to connect the two.
Once a product is built, you can open it, use it, and show it. The result is right there in front of you. This can sometimes make it feel as though most of the work of building the business is done, with finding customers and making sales just the finishing touches. But a finished product doesn’t mean you’ve figured out who will buy, why they’ll buy, or what help customers need to start using it. Those questions may still be unanswered.
Steve Blank described this gap when looking back on one of his entrepreneurship courses. By the first class, students had already used AI to build products that previously might not have been finished until the end of the semester. The teaching team was excited at first. Later, though, they found that some teams still hadn’t worked out whether those products met customers’ needs and solved their problems. AI had helped them build products, but it hadn’t done the work of understanding customers for them.
The way established companies’ products look today can also distort our picture of what starting out involves. Their websites, products, pricing, and ways to buy are all there to see. The work they put in early on to get a few customers actually using the product is much harder to see.
In discussing early work that doesn’t scale, Paul Graham noted how founders’ experience as customers can skew their frame of reference for service. They mostly deal with large companies and are used to the service those companies provide, so they may not realize they can give early users attention that large companies would struggle to offer.
Words such as “product,” “customer,” and “market” also make things seem more settled than they really are. “Sell the product to the customer” sounds straightforward, but says nothing about the customer’s circumstances or what exactly you need to provide for them to adopt it.
Graham described how the Viaweb team approached merchants in its early days. They asked merchants whether they wanted to use the software to build online stores. Some didn’t want to do it themselves but were willing to let the team do it for them. So the team built the stores themselves, selling luggage, pens, and men’s shirts on the merchants’ behalf.
Sometimes, while building a merchant’s site, Graham would find that the software lacked a feature he needed. He would spend several hours adding it, then go back to building the site.
Through that work, the team gradually learned what merchants were willing to accept, what help they needed to use the software, and what the software was still missing. They put in extra work to get customers using it, and that same work exposed real shortcomings in a product that had initially seemed “finished.”
Service businesses can be like this too. You might think a customer needs an analysis, then discover when you talk to them that they lack the basic information needed to make a judgment. You might think the job ends when you deliver the report, yet they may still need someone to help them explain it to others within the organization. Otherwise, the conclusions can’t be put into practice.
These discoveries lead you to reconsider your original assumptions. Should you include this help in the service? Can you make the scope clear, will customers pay for it, and are you in a position to keep providing it? What you actually sell may change as a result.
The range of customers you serve changes along with it.
If one customer needs extensive explanation, setup, and coordination from you, the time you spend on them is time you cannot also spend reaching more people. If every customer needs individual customization, your product and service will gradually take on a different form. Some customers who seem to have a strong need for what you offer may require more than your team can currently handle. Some smaller customers whose circumstances are more alike may be a better fit at this stage.
So it’s hard to settle “what to sell,” “who to sell to,” and “how to sell it” once and for all, in that order. You reach a customer and discover they don’t have the reason to buy you assumed they had. You help them adopt the product and see what it’s missing. You complete the delivery and discover that the scope you originally promised exceeds what you can handle. This feedback changes the product and how you sell it, as well as the kinds of customers it makes sense to look for next.
At Direction Reset Review, we believe that building a product is not enough to prove a business is viable. A lack of sales doesn’t justify a hasty conclusion that the direction is unworkable, either. What actually stands between a product and its customers only becomes clear when you consider real customer responses and the conditions under which the business operates.
Between “it can solve the problem” and “they will buy it,” what gets left out is how customers make choices in their own circumstances, and whether the business owner is in a position to do the work needed to make the sale, deliver, and get it into use. Making contact, understanding, comparing, trying, paying, and putting it to use: each step involves real people and asks something of them.
Top comments (0)