Team StartupsMap · 30 Oct 2026 · 28 min read
You don't need a big audience, an expensive marketing team, or thousands of leads to find your first SaaS customers. Sometimes, a well-researched email to the right person is enough to start a business relationship.
There is something interesting about building a SaaS product.
You can spend weeks writing code, designing the interface, fixing bugs, and adding features. You finally launch, share your product on X, post in a few communities, and wait for users to arrive.
A few people visit your website. Some create accounts. Someone might even say, "Looks interesting!"
But nobody is paying.
That's when you realise that building the product was only half the job. You still need to find people who have the problem your product solves and convince them to give it a try.
For early-stage founders, this is often the hardest part.
You probably don't have a marketing budget. You may not have an audience. You might not even have a sales team. What you do have is a product, some time, and the ability to talk directly to potential customers.
This is where cold email can help.
I've seen founders spend hours trying to make a product go viral when they could have spent that time talking to 20 people who actually needed it.
Cold email is not a magic growth hack. It won't automatically get you customers. But when done thoughtfully, it can help you find early users, understand your market, book product demos, and sometimes land your first paying customer.
Let's talk about how to do it properly.
Most people don't enjoy receiving promotional emails. And honestly, who can blame them?
Open your inbox and you'll probably find messages like:
"Dear Sir/Madam,"
"We are a leading provider of innovative AI-powered solutions..."
"We would love to schedule a quick 15-minute call to explore synergies."
Most of these emails are deleted without being read.
But here's the interesting part: people still respond to emails that are relevant to what they're doing.
Imagine you're running a small SaaS company and spending several hours every week manually handling customer support tickets.
One morning, you receive an email from a founder who has built a tool that helps small teams automate repetitive support tasks.
The email is short. It explains why they contacted you, what problem the product solves, and asks whether you'd be interested in seeing it.
You might actually reply.
That's the difference between cold email and spam.
Cold email is about starting a relevant conversation with someone who doesn't know you yet. Spam is about sending the same promotional message to as many people as possible.
For early-stage SaaS companies, this distinction matters.
You don't need 10,000 random email addresses. You need a small list of people who are likely to benefit from what you're building.
Before writing templates, let's look at some published examples and research. The useful lessons are not just about reply rates. They are about how founders approach potential customers.
Outboundy, a cold email software company, published a case study explaining how it used its own platform to grow its business.
According to its report, over eight months the company:
Sent 310,000 emails.
Received 34,800 replies.
Reported an 11.2% reply rate.
Generated 3,600 free trials.
Acquired 1,000 paying customers.
The company targeted sales leaders, agency founders, and startup CEOs. It also reported that the campaigns used individual prospect research rather than relying entirely on generic templates.
There are two things worth taking away from this.
First, the company understood exactly who it wanted to reach.
Second, it connected outreach to a clear next step: getting someone to try the product.
A reply is useful, but a reply that leads to a product experience is much more valuable.
Read the case study: How Outboundy Found Its First 1,000 Paying Customers.
These are company-reported results and should not be treated as typical performance benchmarks.
Zaap is a SaaS product for creators. In a published case study, its outreach campaign reported a 22% reply rate and a 28% meeting-booking rate.
The interesting part wasn't simply the numbers.
The campaign focused on reaching creators with messages that felt relevant to their businesses rather than sending generic software pitches.
Creators are frequently approached by brands, agencies, and software companies. A generic sales email is easy to ignore.
A message that understands how a creator works, what they are trying to achieve, and why a particular product could help is much more likely to start a conversation.
The lesson for founders:
Don't write an email that could be sent to 500 different people without changing anything.
Read the case study: How Zaap Made Cold Email Work in the Creator Economy.
This is also a vendor-published case study, so treat the results as an example rather than an independently verified benchmark.
One of the more useful resources for understanding cold email is Hunter's 2025 State of Cold Email report.
The report surveyed 217 decision-makers and analysed 11 million emails.
Some of its findings:
61% of surveyed decision-makers said they preferred receiving cold emails as an outreach channel.
The average campaign reply rate reported was 4.1%.
71% said a lack of relevance was a major reason they didn't respond.
43% identified impersonality as a reason for ignoring messages.
The takeaway is quite simple.
People aren't necessarily against receiving emails from someone they don't know. They are against receiving emails that have nothing to do with them.
Read the report: Hunter's State of Cold Email 2025.
They point towards a few consistent principles:
Know exactly who you're trying to reach.
Understand the problem before writing the email.
Explain the value in plain language.
Make the next step easy.
Measure actual customer outcomes, not just replies.
This is where most early-stage founders should spend their time.
This is probably the most important step in the entire process.
Let's say you've built an AI-powered customer support tool.
Who should you contact?
You could email:
Startup founders.
Customer support managers.
E-commerce business owners.
Marketing agencies.
SaaS companies.
Freelancers.
All of these groups might find your product useful, but they don't necessarily have the same problems or buying motivations.
If you try to sell to everyone, your message becomes generic.
Instead, narrow your audience.
For example:
Product: AI-powered customer support automation.
Ideal customer: E-commerce businesses with small support teams handling a high volume of customer queries.
Likely decision-maker: Founder, Head of Customer Support, or Operations Manager.
Problem: Too much time spent answering repetitive questions about orders, refunds, and deliveries.
Potential outcome: Reduce manual support work and help the team respond faster.
Now you have something specific to talk about.
Here's another example.
Product: AI resume screening software.
Ideal customer: Recruitment agencies and companies hiring frequently.
Decision-maker: Recruitment Head, HR Manager, or Talent Acquisition Lead.
Problem: Recruiters spend too much time manually reviewing applications.
Potential outcome: Help recruiters organise and review candidates more efficiently.
Notice how much easier it becomes to write an email when you know exactly who you're contacting.
Before starting outreach, write down these details:
AttributeExampleIndustryE-commerceCompany size10 to 100 employeesTarget roleFounder / Operations ManagerProblemRepetitive customer support queriesCurrent solutionManual support or basic helpdeskBuying signalGrowing support team or hiring customer service staffProduct valueReduce repetitive support work
You don't need a complicated sales strategy document.
A simple Google Sheet is enough to start.
Now comes the practical part.
You know who your customers are. Where do you find them?
Here are some methods that work well for early-stage founders.
LinkedIn is one of the easiest places to start building a prospect list.
Search for job titles relevant to your product.
For example, if you're selling a recruitment SaaS, search for:
Talent Acquisition Manager
Head of Recruitment
HR Manager
Recruitment Agency Founder
People Operations Manager
You can also narrow your search by:
Industry.
Company size.
Location.
Job title.
Company name.
Once you find a relevant person, look at their profile and company website.
Try to understand:
What the company does.
Who its customers are.
Whether it is hiring.
What tools or workflows it might use.
Whether your product solves a relevant problem.
Don't just collect names. Collect context.
A list of 50 relevant people with useful information is often a better starting point than a list of 5,000 unqualified contacts.
Startup directories can help you discover companies that match your ideal customer profile.
For example, if you've built software for early-stage SaaS companies, you can search for startups in relevant categories.
Some places to explore:
Look for:
Recently launched startups.
Companies hiring for relevant roles.
Startups expanding into new markets.
Founders discussing operational challenges.
Businesses that might be experiencing the problem your product solves.
For example, if you sell onboarding software, a startup hiring several customer success employees might be worth researching.
That doesn't automatically mean they need your product. It gives you a reason to investigate further.
Job postings can reveal what a company is currently investing in.
Imagine you've built a SaaS product that automates repetitive data-entry work.
You find a company hiring five operations executives whose job descriptions include manual data processing.
That might be a useful signal.
You can approach the company with a message explaining how your product could potentially reduce repetitive work.
Other examples:
Your productHiring signal to look forCustomer support automationCustomer support executivesRecruitment automationRecruiters and talent acquisition teamsSales automationSDRs and sales development teamsAnalytics softwareData analysts and business analystsSocial media managementSocial media managersDeveloper productivity toolsEngineering teams and developers
Be careful not to assume that hiring automatically means a company needs your software. Treat it as a reason to research the business.
This is another useful approach.
Find companies offering products similar to yours.
Explore their:
Customer stories.
Public testimonials.
Case studies.
Integration directories.
Public customer showcases.
If a competitor is solving a problem for a particular type of business, those businesses may also be relevant prospects for your product.
But don't send an email saying:
"I saw you're using our competitor. Switch to us."
That's not a compelling reason to respond.
Instead, identify what your product does differently.
Maybe you offer:
A simpler workflow.
Better integration.
Lower costs for a particular use case.
A feature the customer needs.
A solution tailored to a specific industry.
Lead with that difference.
Some of the best leads are people who are already talking about a problem.
Explore:
Search for phrases like:
"Looking for an alternative to..."
"Any recommendations for..."
"How do you manage..."
"Is there a tool that..."
"Struggling with..."
"Need help automating..."
When someone publicly discusses a problem your product solves, you have a reason to investigate whether they're a suitable prospect.
You can respond publicly first or reach out through an appropriate channel.
Don't turn someone's question into an excuse for an irrelevant sales pitch.
This is where you can make a big difference.
Let's say you find a startup founder on LinkedIn.
You could immediately send:
"Hey, we have built an AI tool that helps startups grow. Would you like to try it?"
But why would that person care?
Instead, spend a few minutes researching the company.
Look at:
Its website.
Its product and target audience.
Recent company announcements.
Open job positions.
Recent product launches.
The founder's public posts.
Any specific problem your product might solve.
You don't need to spend 30 minutes researching every prospect.
You just need enough context to understand why the email is relevant.
For example:
You discover that a startup recently launched a product and is onboarding its first customers.
Your SaaS helps automate customer onboarding.
Now you have a relevant reason to reach out.
Your opening could be:
"Hey Sarah, noticed your team recently launched [Product]. I was curious how you're currently handling customer onboarding as new users come in."
That feels more natural than starting with a pitch.
Before emailing someone, ask:
Is this person actually relevant to my product?
Does their company fit my target audience?
Is there a real problem I can help solve?
Can I explain why I'm contacting this person?
Is there a useful and truthful reason to start a conversation?
If you cannot answer these questions, don't send the email yet.
Now let's write the email.
One mistake founders make is treating cold email like a company brochure.
They introduce the company, explain every feature, mention their experience, share multiple links, and finally ask for a meeting.
The prospect doesn't need all of that.
Your first email has one job:
Give the recipient a good reason to respond.
A useful cold email generally has five parts.
Don't overthink it.
Some examples:
Quick question about [Company]
Question about your onboarding
Idea for your support workflow
[Company] and customer support
Reducing manual work at [Company]
Avoid fake urgency, misleading subjects, and clickbait.
Explain why you're contacting them.
For example:
"Noticed your team is expanding its customer support operations."
Or:
"Saw that you've recently launched your new product."
Don't pretend you know someone personally if you don't.
Show that you understand the problem they might be facing.
For example:
"Teams at this stage often end up handling repetitive customer queries manually."
Use language that reflects what you've actually learned from customers or industry research.
Explain what your product does in one or two sentences.
For example:
"We're building a support automation tool that helps small teams handle repetitive queries without increasing their support workload."
Avoid listing every feature.
Don't immediately demand a 30-minute meeting.
Try:
"Would this be relevant to your team?"
Or:
"Would you be open to taking a quick look?"
A low-friction question makes it easier to reply.
Here are templates you can adapt to your product and target audience.
Don't copy and paste them blindly. Replace the examples with genuine information about the person you're contacting.
Subject: Quick question about [Company]
Hi [Name],
I came across [Company] while researching startups working in [industry].
I'm building [Product Name], a tool that helps [target audience] solve [specific problem].
We're currently speaking with founders who experience this challenge and would love to understand how you're handling it today.
Would you be open to sharing a little about your current process?
Thanks,
[Your Name]
Why this works: You're starting with a conversation rather than immediately asking someone to purchase your product.
Subject: Question about [specific workflow]
Hi [Name],
I noticed that your team works in [industry / area].
I'm curious how you're currently handling [specific problem].
We built [Product Name] to help [target audience] reduce [specific pain point] through [brief explanation].
Thought it might be relevant to your team.
Would you be interested in taking a look?
Best,
[Your Name]
Why this works: It connects your product to a specific workflow instead of making a broad claim.
Subject: Quick idea for [Startup Name]
Hi [Name],
Congratulations on the recent launch of [Product / Company].
I'm also building in the startup ecosystem and came across your company while exploring [relevant category].
We built [Product Name], which helps startups with [specific outcome].
I thought it might be useful as your team grows.
Would you be open to trying it and sharing your feedback?
Best,
[Your Name]
Why this works: It uses a real company event as the reason for contacting someone.
Only mention a launch if it actually happened.
Subject: Could I get your perspective?
Hi [Name],
I'm working on a product for [target audience] that helps with [specific problem].
Before we invest further in building it, I'm trying to understand how people currently solve this problem.
Given your experience in [industry / role], I'd really value your perspective.
Would you be open to a short conversation?
Thanks,
[Your Name]
Why this works: It is particularly useful when you are still validating your product or looking for early design partners.
Subject: Thought this might be useful for [Company]
Hi [Name],
I came across [Company] and noticed that your team works on [relevant activity].
We've built [Product Name], which helps companies like yours [specific outcome].
I recorded a short demo showing how it works:
[Demo Link]
Would you be interested in trying it?
Best,
[Your Name]
Why this works: A short demonstration can make an unfamiliar product easier to understand.
Only send a recording that is genuinely relevant to the recipient.
Subject: A different approach to [problem]
Hi [Name],
I noticed your team uses [existing tool / workflow] for [specific activity].
We're building [Product Name], which approaches this problem differently by [specific differentiator].
I thought it might be worth comparing if you're looking to improve [specific outcome].
Would you be open to exploring it?
Best,
[Your Name]
Why this works: It introduces a reason to consider your product without insulting a competitor or assuming the recipient is unhappy.
Subject: Early access to [Product Name]
Hi [Name],
We're opening early access to [Product Name], built for [target audience].
It helps with [specific problem] by [short explanation].
We're looking for a small group of early users who can try the product and share honest feedback.
Would you be interested in joining?
Here's the link: [Product URL]
Thanks,
[Your Name]
Why this works: It gives the recipient a clear next step without pretending the product is more mature than it is.
Subject: [Specific business outcome] at [Company]
Hi [Name],
I noticed that you're responsible for [department / function] at [Company].
We work with [type of company] to help them [specific business outcome].
I thought this could be relevant because [genuine reason based on public information or prior research].
Would it be useful if I shared a short overview?
Best,
[Your Name]
Why this works: It speaks to the recipient's role and business priorities rather than trying to sell to everyone in the organisation.
Here's something important.
Not receiving a reply doesn't always mean someone isn't interested.
People are busy. Emails get buried. Someone might read your message and forget to respond.
A polite follow-up can help.
But don't send five emails every two days.
For a small founder-led campaign, start with one or two thoughtful follow-ups and stop if the recipient declines or asks you not to contact them.
Subject: Re: [Original subject]
Hi [Name],
Just bringing this back to the top of your inbox.
I reached out because I thought [Product Name] might be relevant to [specific problem at their company].
Happy to share a short demo if useful.
Best,
[Your Name]
Subject: Re: [Original subject]
Hi [Name],
One additional thought that might be useful.
[Share one relevant insight, short resource, or example related to their problem.]
This is the kind of workflow we're trying to improve with [Product Name].
If it's relevant to your team, happy to show you how it works.
Best,
[Your Name]
Subject: Should I close this out?
Hi [Name],
I don't want to keep filling your inbox, so I'll close the loop here.
If [specific problem] becomes a priority in the future, happy to reconnect.
Wishing you and the team all the best.
[Your Name]
This final message is not a trick to force a reply. It is a respectful way to end the conversation.
When you're just starting, I would not recommend sending thousands of emails.
You don't yet know:
Which customer segment responds.
Which problem matters most.
Whether your offer is compelling.
Whether your pricing makes sense.
Whether your product actually solves the problem.
Sending more emails before understanding these things only creates more noise.
Start with a small experiment.
ActivityTargetResearch relevant companies50Identify suitable decision-makers30Send personalised emails30Conduct customer conversations5Offer product trials or demos3 to 5
These are suggested activity targets, not expected conversion rates.
After sending your first batch, review the responses.
If nobody replies, don't immediately increase volume.
Ask:
Did I contact the right people?
Was the problem relevant?
Was my opening specific?
Did I explain the product clearly?
Was the next step too demanding?
Was the email actually delivered?
Change one thing at a time and run another small test.
This is where many founders make another mistake.
They get excited when someone replies and immediately send a long product pitch.
Don't do that.
Read what the person actually said.
There are different types of replies, and each deserves a different response.
Don't send a five-page presentation.
Try:
"Thanks for getting back!
In short, [Product Name] helps [target audience] solve [specific problem].
The easiest way to understand it is through a short demo. Would you prefer a quick video or a live walkthrough?"
This is a buying signal.
Be direct:
"Absolutely.
Our current plans start at [$X] per month, depending on usage and features.
Here's the pricing page: [Link]
Happy to help you figure out which plan would fit your requirements."
Don't hide your pricing unnecessarily.
Don't immediately attack the competitor.
Try:
"That makes sense. Out of curiosity, is there anything you wish your current solution handled better?
We're trying to understand where existing tools fall short, so that feedback would be genuinely useful."
If they are happy with their current solution, respect that.
Keep it simple:
"Thanks for letting me know. Appreciate your time. Won't follow up further."
And actually stop contacting them.
Try:
"Understood. Is there a better time for me to reconnect, or would you prefer that I leave it with you?"
If they don't invite another follow-up, don't keep chasing them.
You don't need an expensive CRM to start.
A simple spreadsheet is enough.
Create these columns:
FieldPurposeCompanyCompany nameContactPerson's nameJob titleTheir roleWebsiteCompany websiteEmailRelevant business contactSourceWhere you found the contactReason for outreachWhy they are a potential fitDate contactedFirst email dateFollow-up datePlanned follow-upStatusSent, replied, interested, not interestedNotesImportant conversation details
You can manage this using Google Sheets, Notion, or a CRM.
Useful tools include:
HubSpot CRM: Manage contacts, deals, and sales conversations.
Google Sheets: Build a simple prospect tracker.
Notion: Organise research and follow-ups.
Hunter: Find and verify professional email addresses.
Apollo: Research business contacts and company information.
Clay: Enrich prospect information and build research workflows.
Check each provider's current plans, data sources, and usage limits before choosing a tool.
Don't focus only on open rates.
Track:
Delivery rate: How many emails were successfully delivered?
Bounce rate: How many emails could not be delivered?
Reply rate: How many recipients responded?
Positive reply rate: How many replies showed genuine interest?
Meeting rate: How many recipients agreed to a conversation or demo?
Trial conversion: How many interested people actually tried your product?
Customer conversion: How many became paying customers?
For a SaaS founder, the most important outcome is not how many people opened your email.
It's whether the right people started using your product and eventually paid for it.
I've seen many early-stage founders make these mistakes because they want customers quickly.
A message written for a startup founder might not work for a Head of Engineering.
Understand the recipient before writing.
Your prospect doesn't need your entire company history.
Explain what you do in a couple of sentences.
Avoid statements like:
"We will increase your revenue by 300%."
Unless you have reliable evidence, don't make promises you cannot support.
For someone who has never heard of you, that is a significant commitment.
Start with a smaller request.
Mentioning someone's LinkedIn post without understanding it is not meaningful personalisation.
Don't pretend you have researched someone when you haven't.
Repeated messages can damage your reputation and annoy potential customers.
A follow-up should add context or value, not pressure.
Large lists are not necessarily useful lists.
Purchased or scraped contact databases can contain inaccurate information, personal addresses, and people who have not agreed to receive marketing.
Build relevant prospect lists and verify that your outreach complies with the applicable rules.
A small sample doesn't tell you much.
You might have selected the wrong audience, chosen the wrong problem, or written an unclear offer.
Use a structured experiment rather than judging the entire channel from a handful of messages.
You can write the best cold email in the world, but it won't matter if it never reaches the recipient's inbox.
Before starting outreach, pay attention to your sending setup.
A few practical things:
Use a professional business email address.
Avoid sending business outreach from a random personal account.
Configure SPF, DKIM, and DMARC.
These email authentication mechanisms help receiving mail systems verify your sending domain.
Keep your contact list clean.
Remove invalid addresses and avoid repeatedly sending to bounced contacts.
Avoid misleading subject lines.
Your subject should accurately describe the email.
Make opting out easy.
If someone doesn't want further messages, respect that immediately and maintain a suppression list.
Monitor your domain reputation.
Poor sending practices can damage the ability to reach even people who genuinely want to hear from you.
Google's official documentation is a useful starting point:
Google Email Sender Guidelines
Don't assume that sending a low volume automatically makes every outreach practice safe. Authentication, consent, relevance, and applicable marketing laws all matter.
Cold email rules depend on where you and your recipients are located.
There isn't one universal rule that makes every unsolicited business email legal.
For example:
United States: The CAN-SPAM Act applies to commercial email, including business-to-business messages. It includes requirements around accurate sender information, non-deceptive subject lines, a valid postal address, and a functioning opt-out process.
Official resource: FTC CAN-SPAM Compliance Guide.
United Kingdom: PECR and UK GDPR apply to electronic marketing and personal data. Rules differ between corporate subscribers and individuals, including sole traders. Publicly available contact details do not automatically remove your compliance obligations.
Official resource: ICO Business-to-Business Marketing Guidance.
Other countries: Check the relevant privacy and electronic marketing laws before sending campaigns. This includes rules that may apply in the EU, Canada, India, and other markets.
A few good practices regardless of location:
Identify yourself and your company honestly.
Contact people for a genuine and relevant business reason.
Use appropriate business contact information.
Explain how recipients can stop receiving marketing messages.
Respect objections and unsubscribe requests.
Don't use deceptive sender identities or subject lines.
Don't assume a publicly visible email address means someone has agreed to marketing.
If you're planning a larger campaign, get advice on the laws that apply to your target markets.
Let's put everything together.
If I were launching a SaaS product today with no marketing budget, this is how I would approach the first 30 days.
Don't start with email templates.
Start with research.
Choose one customer segment.
Identify one specific problem.
Find 30 to 50 relevant companies.
Research the people responsible for that problem.
Speak to a few potential customers if possible.
Write down the language they use to describe the problem.
Goal: Know exactly who you are contacting and why.
Build a list of 30 qualified contacts.
Verify relevant business email addresses.
Write two versions of your email.
Create a short product demo.
Set up a basic tracking sheet.
Check your sending domain authentication and compliance requirements.
Goal: Have a small, relevant outreach campaign ready.
Send a small batch of personalised emails.
Review replies.
Follow up politely where appropriate.
Ask interested people about their current workflow.
Offer a product demo or early access.
Record objections and questions.
Goal: Start real conversations with potential customers.
Identify which audience responded.
Review which message created interest.
Talk to people who tried the product.
Understand why some people didn't convert.
Improve your positioning.
Ask qualified prospects whether they are ready to pay.
Goal: Get closer to product-market fit and, ideally, your first paying customer.
Don't judge the entire experiment by whether you close a customer within 30 days. The conversations and feedback can be valuable even when someone isn't ready to purchase.
Cold email works better when people can verify that you're a real person building a real product.
Imagine receiving an email from a founder.
You search their name on LinkedIn or X.
You find:
Their product updates.
Conversations with other founders.
Customer feedback.
Product demonstrations.
Lessons from building the company.
You now have more context about the person behind the email.
This is why I like combining direct outreach with building in public.
You don't need to become an influencer.
Just share what you're learning.
For example:
What you shipped this week.
A problem your customers mentioned.
A feature you improved.
A mistake you made.
A product experiment that failed.
A small customer win.
When someone receives your email and looks you up, your public presence can help establish trust.
It also creates another opportunity: people who discover your posts may become customers without receiving a cold email at all.
One challenge that almost every early-stage founder faces is distribution.
You can build a useful product, but getting it discovered is a different problem.
You need to find communities, reach relevant users, connect with other founders, and make people aware of what you're building.
That's one of the reasons I started working on StartupsMap.
StartupsMap is a platform where people can discover startups, founders, and products being built across different cities and industries.
The idea is straightforward: there are thousands of interesting startups that people simply don't know about.
Some are building AI products. Others are working on developer tools, SaaS platforms, fintech, healthcare, productivity, and much more.
We want to make those companies easier to discover.
If you're building a SaaS, AI product, or any startup, you can add your company to StartupsMap.
Why list your startup?
Give your company another place to be discovered.
Help people understand what you're building.
Make your startup visible alongside other emerging companies.
Increase opportunities for discovery and connections.
Become part of a growing startup ecosystem.
We're also building a community around founders and early-stage SaaS companies where people can share what they're working on, ask questions, and learn from each other.
If you're building something, we'd love to have you on the map.
Add your startup: https://startupsmap.co.in/map
Explore startups: https://startupsmap.co.in/
When you're building your first SaaS, it's easy to believe that growth starts with a viral launch, a large audience, or an expensive marketing campaign.
But sometimes it starts with a much smaller action.
You find a company that has the problem you're solving.
You understand how they currently handle it.
You write a short email explaining why you reached out.
They reply.
You have a conversation.
They try your product.
And eventually, they become your first customer.
That's how founder-led sales often begins.
Don't obsess over sending hundreds of emails every day. Don't spend hours trying to create the perfect subject line.
Spend more time understanding your customers.
Talk to them. Learn how they work. Understand what they are already paying for. Find out what frustrates them.
Then write an email that makes sense for that particular person.
Your first 10 customers won't necessarily come from a sophisticated sales system.
They might come from 10 thoughtful conversations.
And that's a pretty good place to start.
About the author / StartupsMap
StartupsMap is a platform built to help people discover startups, founders, and products being built across the startup ecosystem.
If you're a founder building something interesting, get your startup listed and become part of the growing community.
Website: https://startupsmap.co.in/