Solo developers and small bootstrapped teams often arrive at small business owners as their first paying customers. The reasoning is sound. Small businesses have problems that software can solve, the buyer is the owner, the sales cycle is short, and the price point can be set at a level the founder is comfortable charging. The reality of the conversation is harder than the reasoning suggests. We work with small business owners on getting better at the technology side of their operations, and we hear about a lot of these conversations from the buyer's side. Most of them do not lead to a purchase, and the reasons are mostly the same.
The first reason is that the founder leads with the technology. The owner does not care that the product uses a particular language, framework, or AI capability. The owner cares whether the product will reduce a recognizable cost or make a recognizable amount of money. A pitch that opens with the technology and arrives at the business case after several minutes has lost the owner before the case is made. The pitch that opens with the business outcome and uses the technology only to support the case does much better. Founders who have built the product themselves, and are proud of how it works, often have to suppress that pride during the sales conversation. The product's quality will sell itself once the business case is established.
The second reason is that the founder's pricing does not match the owner's mental model of the cost. Owners price things by comparing them to other things they buy. Software is priced relative to the staff cost it would replace, the revenue it would produce, or the existing software the owner is already paying for. A new tool that costs four hundred dollars a month is fine if it sits in a recognizable category. The same tool at the same price is hard to evaluate if it does not. Founders often price by comparing to what other software companies charge, which is not a frame the owner uses. Anchoring the price to a recognizable comparison is more important than the absolute number.
The third reason is that the founder underestimates the cost of switching. The product may be objectively better than the spreadsheet the owner is using, but the owner's whole staff knows how to use the spreadsheet. Switching costs days of training, weeks of mistakes, and months of small frictions that the owner did not anticipate. The founder who acknowledges these costs and presents a switching plan that addresses them is in a much better position than the founder who treats the switch as obvious. The owner often agrees that the new tool is better and still does not buy, because the cost of switching is being borne entirely by the owner and the new tool's value is uncertain enough to make the trade unappealing.
The fourth reason is that the founder is selling to the wrong person. Many small business owners are very good at delegating decisions about specific operational areas to the staff who run those areas. The shop manager makes the shop tooling decisions. The bookkeeper picks the accounting tool. The owner's role is to ensure that the budget is reasonable and the relationships are sound. A founder pitching the owner directly, when the relevant operational person has not been consulted, often produces a meeting in which the owner says they will think about it, then never moves forward, because the operational person was not part of the conversation. The founder should ask, early, who else needs to be in the room.
The fifth reason is that the trust transfer is missing. Small business owners trust other small business owners, and they trust vendors who have been recommended by people they trust. They do not, by default, trust an unknown founder pitching them software. The founder who arrives with a few specific references, ideally other businesses similar to the owner's that are using the product, has a much shorter path. The founder who arrives with no references, or with references from much larger companies, has to build the trust during the conversation. The conversation is rarely long enough for the trust to fully form.
The sixth reason is the founder's communication style. Owners read a sales conversation closely. They notice when the founder is reading from a script, when the founder is dodging questions, and when the founder is overpromising. They reward founders who answer plainly, who acknowledge limitations, and who do not pretend to be larger than they are. The founder who is honest about being a small team often does better than the founder who tries to project a more polished face. The owner has been a small team themselves and is comfortable buying from one, as long as the team is straightforward about it.
For a technical founder approaching small business owners as buyers, the working pattern is to lead with the business case, anchor the price to a comparison the owner already uses, address switching costs explicitly, ask who else should be involved, arrive with relevant references, and communicate plainly. None of this is exotic, and most of it is opposite to the instincts a founder develops in technical environments. The founders who make the adjustment tend to close. The founders who do not tend to spend a year wondering why the meetings keep going nowhere.
This is a guest post from the team at Biz Little, who write plain-English guides on running and growing a small business across the topics that owners actually have to deal with day to day.