The first customers are rarely found by announcing a broad product and waiting for strangers to understand it. Early sales usually require direct investigation: identifying a specific buyer, describing a relevant outcome, and learning why an offer does or does not fit their situation. The work is part of building the business model, rather than a separate activity that begins after development.
Chapter 3 defined a narrow pilot offer and a learning budget. This chapter develops a practical way to reach appropriate prospects, qualify interest, and agree on a limited engagement. The examples continue our hypothetical reporting-automation service and describe a process Thora Vietnam could use, without implying an existing customer pipeline.
Build a focused prospect definition
Use the segment and problem evidence from the earlier chapters. Describe the circumstances that make a prospect suitable: a recurring reporting workflow, several people contributing inputs, an identifiable owner, and a reason to investigate improvement. Avoid treating every organization with a website as a potential buyer.
Add disqualifying conditions. A firm with no recurring reporting requirement is unlikely to be a useful pilot participant. An organization requiring certifications or integration capabilities the team cannot provide may need a different offer or a later conversation. Honest qualification protects the prospect's time and the team's delivery capacity.
Create a small prospect list with a reason for including each entry. The list should support careful learning, not bulk outreach. Record only necessary business contact information, respect communication preferences, and follow the rules applicable to the channel and location.
Choose an access route you can evaluate
Founder networks, professional communities, referrals, and relevant educational content can each create conversations. Pick a route based on where the intended buyer actually spends attention. A general social post may attract readers while producing little information about a narrowly defined business workflow.
Start with a modest, clearly bounded effort. For example, prepare a useful reporting checklist and invite suitable contacts to discuss how they currently manage the job. The checklist should be valuable on its own, rather than disguising a sales pitch as neutral research.
Track the source of each conversation. A referral from a trusted colleague has a different context from an unfamiliar visitor finding an article. Combining the results can hide whether the offer is understandable without the founder's personal credibility doing most of the work.
Write an invitation that earns a response
Explain why the conversation may be relevant, what you are investigating, and what you are asking for. Keep the request small and avoid pretending to know the prospect's internal problem. “We are exploring how small agencies handle weekly reporting” is more credible than claiming you can solve their operational bottleneck without understanding it.
If you are selling a pilot, say so. If you are conducting discovery, do not quietly turn the call into a purchase demand. Clear expectations make the response easier to interpret and reduce the chance that politeness is mistaken for buying interest.
A hypothetical invitation could ask an operations lead whether combining updates is part of their weekly work and offer a short conversation about the process. It should make declining easy. Never use fabricated customer names or implied results to make an early offer appear established.
Qualify the opportunity through the workflow
Understand the immediate need
Ask what is happening now, what makes it important, and what happens if the situation stays unchanged. A serious recurring problem can still be a poor fit if the prospect has no capacity to change the workflow during your pilot window.
Identify the decision process
Learn who uses the result, who approves spending, and who reviews data access. Ask how a small external engagement would normally be approved. This helps the team avoid building a proposal for someone who cannot evaluate or authorize it.
Check delivery fit
Discuss inputs, access restrictions, review requirements, and timing before committing. If the prospect needs a capability outside the team's scope, acknowledge the gap. A promising conversation is useful evidence even when it does not become an engagement.
Offer a concrete next step
A discovery conversation should end with a clear outcome: no fit, a specific follow-up question, or a defined pilot discussion. Avoid leaving every conversation in a vague “interested” state. Ambiguity makes a pipeline look healthier than it is and creates unnecessary follow-up work.
A pilot proposal should explain the outcome, deliverables, inputs, responsibilities, timing, price, and acceptance conditions. Include how either side can end the experiment and what happens to data or access afterward. Keep the promise within the delivery capability tested so far.
The offer from Chapter 3 provides a starting point. Adapt it to evidence from the prospect rather than expanding scope to answer every request. If the adaptation changes the business hypothesis, record that explicitly.
Keep a pipeline that reflects evidence
Use a few stages with observable entry conditions: identified fit, conversation completed, pilot proposed, decision pending, and agreed or closed. A prospect moves because something happened, not because the founder hopes the conversation is progressing.
Record the next action, its owner, and the agreed date where one exists. Keep a brief reason when a prospect declines. Reasons such as insufficient urgency, price, missing authority, or unsuitable data access lead to different changes in the offer.
A small spreadsheet can be sufficient at this stage. The purpose is reliable follow-up and learning. Introducing a complex sales system before the team understands its own process can consume attention without improving conversations.
Separate acquisition learning from delivery pressure
The first prospect willing to pay may request extensive custom work. That can be a reasonable business choice, but it may test a consulting engagement rather than the repeatable service you intended. Decide consciously whether the opportunity fits the current learning objective and resource limits.
Price the actual scope and count the delivery effort. Do not hide unbounded founder labor behind an appealing pilot price. If a discount is offered for a limited experiment, state the conditions and avoid implying that future work will cost the same.
For Thora Vietnam's proposed process, a weekly review could connect pipeline evidence, available delivery capacity, and the next experiment. Business development should not promise integrations that engineers have not assessed. Engineering should understand which commitments the customer is evaluating.
Learn from a small set of outcomes
Review where suitable prospects stopped and why. If the invitation is ignored, the problem may be relevance, trust, timing, or channel. If conversations happen but pilots do not, investigate the offer and decision process. If pilots begin but do not continue, examine delivered value and operational fit.
Small numbers do not justify broad conversion claims. Use the evidence to choose the next focused change. Revising one element at a time makes it easier to understand whether the change improves the quality of conversations or merely increases activity.
Conclusion: make early sales a disciplined conversation
Finding first customers means connecting a credible offer with people who face the relevant problem and can participate in a decision. Narrow the prospect definition, make honest invitations, qualify the workflow, and agree on a bounded next step. Keep the pipeline tied to observable actions rather than optimism.
Prepare one prospect definition, one invitation, and one pilot proposal before adding more outreach channels. Chapter 5 will examine how to turn useful early engagements into a sustainable operation without scaling delivery problems along with revenue.
