Many small business owners have had at least one conversation with a technical founder who built a product, was confident the product would help, and somehow did not close the deal even though the owner was open to buying. The founder went away frustrated. The owner moved on without thinking much more about it. The pattern repeats often enough that we want to describe what is going on inside the founder's experience, in case it helps owners understand the conversations they are likely to keep having.
Most technical founders we work with have built their first product alone or with one or two collaborators. They have spent more time on the building than on selling, by a meaningful margin. The product, by the time they are pitching it to a small business owner, has been polished long past the point at which it could have started generating revenue. The founder is not bringing a half-formed prototype to the conversation. They are bringing something that has been overworked, in technical detail that the owner is not equipped to evaluate.
The founder's pitch usually has more product detail than the owner needs. This is the most common pattern. The founder has spent months thinking about the product and has internalized which features are valuable. The owner has spent ten minutes on it, and the features that are obvious to the founder are abstract to the owner. A pitch that lists features performs much worse than a pitch that walks the owner through a specific scenario the owner already recognizes. The founder often resists the scenario approach because it feels like leaving features on the table. The owner does not care about the features that did not appear in the scenario.
The founder's pricing is usually wrong, in one of two predictable directions. They have either priced it too low, because they are anxious about asking, or too high in a way that does not match anything the owner is used to paying. The right price for a small business product is almost always one that the owner has a comparison for. If the product is replacing a piece of software the owner already uses, the price should be in conversation with the existing tool's price. If the product is replacing staff time, the price should be in conversation with the cost of the staff time it replaces. The founder who has not done either of these comparisons usually arrives with a price that the owner has no way to evaluate, and the absence of evaluation often becomes a no.
The founder usually underestimates how much risk the owner is taking. Switching to a new tool, even a good one, is risky for the owner. The staff has to learn it. The data has to migrate. The existing process has to be unwound. The owner is taking weeks of small business hours and putting them at risk for a benefit that is theoretical until proven. The founder, who built the product and is confident it works, does not naturally see this risk because they have already taken it themselves. The founder who acknowledges the risk and offers a structured way to reduce it, often through a short trial or a pilot, gives the owner a path that does not require the owner to take all of the risk in advance.
The founder's communication style is often calibrated to other technical people. Other founders, other engineers. The owner is not a member of either group, and the language that worked in those contexts misses with the owner. The founder who can talk plainly, in the owner's vocabulary, has a meaningful advantage. The founder who tries to use technical credibility to anchor the conversation often loses the owner in the first few minutes.
The founder's reference profile is often weak. The owner trusts other owners. A founder with three small business references, ideally similar in size and category, is a different conversation than a founder with no references or references from companies that are not comparable. Small business owners are not impressed by Fortune 500 logos in the way that founders sometimes assume. They want to know whether the product has worked for someone like them.
The founder's understanding of who decides is often wrong. The owner often is not the buyer for the specific area the product addresses. The bookkeeper, the shop manager, the office manager, or another delegated person is. The founder who pitches the owner directly without involving the operational person often produces a meeting that ends in "I'll think about it" because the owner does not actually have the operational context to evaluate the product on their own.
For owners on the receiving end of these conversations, none of this is your problem to solve. It is useful, though, to recognize the pattern when it appears. The founder who is overworking the technology, mispricing the product, ignoring switching cost, talking past you, lacking comparable references, and pitching the wrong person is exhibiting an identifiable mode that almost all technical founders pass through on the way to learning how to sell. Many of them do learn. Some of them learn quickly enough to deserve a small piece of business if you are inclined to give them one. The signal that they are learning is usually that they are listening more than they are talking, and that the questions they are asking are about your business rather than about their product.
This is a guest post from the team at Tiny Revenue Stream, who run an advisory service for solo developers and small bootstrapped teams working toward their first paying customer.