First customers for a small software product come one at a time
- 1 day ago
- 3 min read
Updated: 18 hours ago
Introduction
Early software marketing goes wrong in a predictable way. The founder builds something, launches it, sets up advertising, and waits. Nothing much happens, so the conclusion drawn is that more marketing is needed — when the actual problem is that nobody has yet established who the product is for or what they would call the problem it solves.
The first ten or twenty customers are almost always found by hand: individually, through conversations, in places where the specific problem is being discussed. That is slow, unscalable and correct. Every scalable channel depends on knowing what this phase teaches you.
Scalable acquisition only works once you know exactly who converts and why, and that knowledge comes from the manual phase.
First customers for a small software product come from doing unscalable things
The early phase is sales, not marketing.
Go where the problem is discussed. Forums, communities, industry groups, local associations. Not to promote, but to understand how people describe the difficulty. Write down their exact phrases.
Approach people individually. A short, specific message about their situation converts at a rate no campaign will match at this stage. Send twenty, not two thousand.
Do demos yourself. The founder doing demonstrations learns what confuses people, which is worth more early on than the revenue. Watch where they hesitate and fix that.
Set it up for them. Manual onboarding for the first customers removes the largest barrier to adoption and teaches you what to automate. Do it for the first twenty and no more.
Solve one problem for one type of buyer
Breadth is the commonest early mistake.
Name the buyer precisely. Not small businesses — the specific role in the specific sector who feels this problem weekly. If you cannot name them, you are not ready to advertise.
Use their vocabulary. Buyers search for their problem in their own words, which are rarely the words a technical founder would choose. Copy the phrases from your own notes.
Say no to the wrong customers. An early customer who needs something different will pull the product sideways for a year. Refer them somewhere else.
Charge from the beginning
Free users teach you very little.
Get somebody to pay early. Willingness to pay is the only reliable evidence that the problem is real. Free signups measure curiosity. Ask for money in the first conversation.
Do not build a free tier yet. Support costs are real and free users at this stage consume the time you need for selling. Add one later, deliberately.
Talk to anybody who declines. The reason somebody would not pay is the most valuable information available. Ask what would have changed their mind.
Build the routes that scale later
Once you know who converts, some things become worth doing.
Answer the questions your buyers search. Written properly, aimed at the specific problem. This compounds slowly and keeps working. Twenty good answers beats two hundred thin ones.
Ask early customers for introductions. In a narrow sector everybody knows everybody, and a referral carries real weight. Ask for one name at a time.
Consider partnerships with adjacent tools. Anybody serving the same buyer with something different is a route to their audience.
Conclusion
Do the unscalable things first: go where your buyers already discuss the problem, approach people individually, run the demonstrations yourself, and set the product up manually for your first customers.
Narrow to one buyer and one problem, described in their vocabulary rather than yours, and be willing to decline customers who would pull the product sideways. Charge from the start, because willingness to pay is the only real evidence and free signups measure curiosity, and talk to everybody who declines. Only once you know precisely who converts and why should you build the things that scale — written answers to the questions they search, introductions from existing customers, and partnerships with tools serving the same buyer.
.png)



Comments