On this page
Sell one clearly scoped outcome to one customer segment, and track the next action rather than the size of your contact list.
Define a customer you can recognise
Describe the company type, relevant role, recurring problem and situation that makes the problem urgent. 'All SMEs in Estonia' does not help you prioritise. 'Independent agencies that reconcile supplier invoices manually before month-end' gives you an observable workflow and a likely person to contact. Use interviews to confirm that the problem matters before building a large prospect list.
Write down why the customer would change from their current approach. A faster interface may not compensate for migration work or perceived risk. Identify both the daily user and the person who approves spending. In a small firm these may be the same person; in a larger organisation they may involve several separate conversations.
Build a small, relevant prospect list
Start with a researchable batch, such as twenty companies, rather than buying a large database. For each company, record the reason for fit, the appropriate contact route and the source of your information. Use introductions with permission and respect the recipient's preferences. Avoid scraped personal contact lists and do not assume every public email address welcomes promotional messages.
At an EESTISTARTUP meetup, explain the customer profile you are trying to reach and ask whether someone knows a relevant person. An event is an opportunity for a conversation, not permission to add every attendee to an outreach campaign. Check applicable privacy and electronic-marketing rules before organising outreach at scale.
- Company and evidence of the relevant workflow.
- User, buyer and any additional approver.
- Permitted contact route and date of last contact.
- Current stage, next action and action owner.
Make the first conversation about the job
A short introduction should describe the customer problem, the outcome you are exploring and why this particular company seems relevant. Avoid opening with a catalogue of features. Ask how the work is handled today, what a failed outcome costs and whether a change is currently a priority. A buyer who has no reason to act this quarter is not necessarily a poor long-term fit.
Illustrative message for a warm introduction: 'We are testing a way for independent agencies to reconcile supplier invoices with less manual checking. Could we discuss how your team handles this today?' Only mention results or customers you can substantiate. Y Combinator's public Startup School collection includes a first-customers talk for further learning about founder-led selling.
Offer a bounded pilot
Write a pilot brief before the customer starts: workflow, inputs, deliverable, responsibilities, price, duration and success measure. A pilot should let both parties decide whether a longer relationship makes sense. State which work is manual and which integrations are not included. If the pilot is free, explain the limits and when a commercial decision will be discussed.
Fictional example: help one agency check a month's supplier invoices and agree to review time spent and unresolved discrepancies afterwards. Before receiving live data, clarify access, retention and the customer's requirements. Do not promise enterprise security capabilities or service levels that your team cannot support. Bring in qualified advice for contractual or sensitive-data questions.
Measure movement through the buying process
Use a simple pipeline with explicit stages: contacted, discovery completed, pilot agreed, pilot delivered and paid contract signed. Define what counts as entering each stage. A demo invitation is not a paying customer, and an unsigned proposal is not committed revenue. Record why an opportunity stalls instead of quietly moving it into an optimistic forecast.
Review the pipeline weekly. Ask which conversation produced useful evidence, which customer needs help and which next action is overdue. In a small early sample, raw counts and short explanations can be clearer than conversion percentages. If pilots start but do not become paid contracts, investigate outcomes and buying constraints before increasing the volume of outreach.
Earn a reference, then test repetition
After delivering the agreed result, ask the customer whether you may describe the work publicly. Get approval for the exact quote, company name and any figures. A confidential customer can still help you learn; do not invent an anonymous success story that suggests results you cannot evidence. Ask for introductions only when the relationship supports that request.
Repeat the offer with another company in the same segment and compare delivery effort, sales cycle and objections. Then test the assumptions that may change abroad: language, procurement, integrations and local alternatives. The useful outcome of the first sales cycle is not just revenue, but a clearer explanation of who buys, why they buy and what it costs to serve them.
Sources and review
Official sources checked on 6 October 2026. Programme terms and schedules can change. Check the provider's website before acting. Worked examples are illustrative, not client results.



