Your first ten customers are a research project
Early sales should reveal which problem is worth building a company around. Start with the buyer’s last difficult day.
A founder can leave a meeting with warm feedback and no useful evidence. The prospect likes the idea, agrees the market is interesting and says they would try a finished product. Nobody has explained what they do today, what the problem costs or what would make them change.
The first ten customers should help answer those questions. Treat early selling as a series of small experiments in which payment matters, but the explanation behind the payment matters too. You are looking for a problem that repeats across a recognisable group of buyers.
Ask about the last time
Begin with an event rather than a hypothetical. Ask the buyer to walk through the last time the problem happened. Who noticed? Which tools were involved? What did they try? Where did the process stop? A specific account gives you something to examine.
Listen for workarounds. A spreadsheet maintained by a manager, a recurring manual export or a weekly reconciliation meeting can reveal more than a list of requested features. The workaround shows that somebody already spends resources on the problem. Understand whether your product would improve that trade-off.
Sell a bounded result
The early offer should describe an outcome you can deliver and a scope you can control. A paid pilot with a clear end date is easier to evaluate than an open-ended promise to transform a business. Specify the input the customer provides, the output they receive and the decision both sides make at the end.
Record objections in the buyer’s words. A pricing objection may conceal a trust problem, a missing integration or a lack of buying authority. Lowering the price will not solve every one of those problems. A question about the approval process may be more valuable than another discount.
Find a repeatable pattern
After each conversation, record the buyer, the trigger, the workaround, the budget owner and the reason the sale moved or stalled. Compare those accounts. If every buyer needs a different product, you may have a consulting opportunity rather than a repeatable software offer. Either can work, but they require different plans.
Keep observations separate from decisions. Several observations may support one product change; one enthusiastic request rarely should. The purpose of a small customer set is to sharpen judgement, rather than turn a roadmap into individual promises.
Keep the next step small
The useful output is a clearer commercial hypothesis: this buyer, facing this trigger, will pay for this result through this buying process. Next, test whether that pattern survives outside your personal network. A modest product with a repeatable reason to buy is a stronger starting point than a broad platform supported by polite interest.
Choose one acquisition channel and a short evaluation period. Record how many suitable buyers you reach, how many agree to a conversation and what happens next. That gives the business a way to learn without confusing a growing feature list with progress towards demand.