Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: Getting your first 100 customers is a manual, gritty, founder-led process — not a marketing funnel problem. The playbook: build a pre-launch waitlist with a tight value proposition, do direct outreach (50–100 messages/day), embed yourself in 2–3 communities before you sell anything, launch on Product Hunt and Hacker News in the same week, and close every single deal yourself. Do not hire a salesperson. Do not run ads. Do not wait for SEO. The first 100 customers come from relentless, personal effort — and that's exactly what makes them so valuable.
I've built and shipped multiple products. The number I come back to every time is 100. Not 1,000. Not 10,000. One hundred.
Getting your first 100 customers is categorically different from every other growth phase you'll go through. At 1,000 customers, you have social proof. At 10,000, you have data. At 100,000, you have brand. But at zero? You have nothing. No testimonials. No case studies. No Google rankings. No one to quote when a prospect asks "who else uses this?" You are invisible.
That invisibility is the core challenge. Modern customers are skeptical, attention-fragmented, and drowning in options. They default to established names. They Google you and find nothing. They ask for customer references and you have none. They want to see reviews on G2 or Capterra, and your listing is blank. Every instinct they have tells them to wait, to try the thing everyone else is already using.
And yet — those first 100 customers are the most important 100 you'll ever acquire.
Here's why.
They shape your product. Every feature you build in the first six months will be informed by what these 100 people tell you, or more accurately, what they show you through their behavior. The bugs they surface, the workflows they invent that you never anticipated, the integrations they ask for — this feedback loop is worth more than any market research report. Your first 100 customers are your co-designers.
They give you proof. Once you have 10 customers who are genuinely getting value, you have testimonials. Once you have 25, you have case studies. Once you have 100, you have a real pattern — industries, use cases, personas — that tells a story to the next 900. The social proof you earn from these 100 people becomes the foundation of every marketing asset you build for years.
They become evangelists. The customers who find you before you're famous often feel a sense of ownership over your product. They were early. They took a chance. If you treat them well, they'll refer colleagues, write tweets, mention you in Slack communities, and become unpaid salespeople who reach audiences you never could. This organic referral engine is worth far more than any affiliate program.
They validate your pricing. You learn whether people will actually pay for this thing, and how much. Early price discovery is brutal but necessary. The data you collect from these first 100 — conversion rates, churn, LTV — tells you whether the business model works before you pour money into acquisition.
So yes, getting the first 100 is hard. But that's what makes them matter.
Let's talk about how to actually get them.
Most founders think of "launch" as the moment they go public. I think of it as the last step in a 60–90 day pre-launch process that, when done right, means your launch day starts with momentum instead of silence.
A waitlist is not a vanity metric. It's a pre-qualified lead list of people who have expressed enough interest to give you their email address before the product exists. Done right, your waitlist should convert at 20–40% to paid or trial users. Done wrong, it's a collection of people who clicked something once and forgot about you.
The difference comes down to three things:
1. A specific, painful problem statement in the headline. Not "the future of project management." Not "build faster." Something like: "The CRM built for agencies that hate CRMs — tracks client communication automatically, no manual entry." Specific. Painful. Clear on who it's for.
2. A lead magnet that attracts the right people. The best waitlist lead magnets are things your target customer would genuinely find useful even if you didn't exist. An agency owner might download "The Agency Profitability Calculator" or "The Client Onboarding Checklist" without caring about your CRM. Once they're on the list, you nurture them toward your product. A generic "Get early access" CTA converts at 2–5%. A specific, valuable lead magnet converts at 15–25%.
3. A nurture sequence that sells before you launch. Build a 5–7 email sequence that starts immediately after signup. Email 1: deliver the lead magnet + intro. Email 2: the problem you're solving (be specific, be honest). Email 3: how you're solving it differently. Email 4: social proof from your beta users (even if it's just 3 quotes from people in your network who tried a prototype). Email 5: the launch announcement with early-bird pricing. Email 6: final reminder. Email 7: cart close.
For the landing page itself, stick to a simple structure: headline, subheadline, 3–5 key benefits (not features), one clear CTA, and optionally a screenshot or demo video. If you're pre-product, use a mockup. Figma frames are enough. People aren't buying the screenshot — they're buying the promise.
Conversion benchmarks to track:
Tools I'd recommend: Typedream or Carrd for fast landing pages. ConvertKit or Loops for email sequences. Tally for intake forms.
One underused tactic: differentiate between your waitlist and your early access program. The waitlist is passive — they're watching. The early access program is active — they're participating.
To get into the early access program, require a 15-minute onboarding call. This does two things: it pre-qualifies people who are serious enough to book time, and it gives you a guaranteed customer interview before they've even used the product. You learn their context, their current solution, their frustrations. You can personalize their onboarding. And that call itself often converts fence-sitters into believers.
Offer early access members something tangible: a permanent discount (lifetime deals work well here — AppSumo is worth considering for this), priority support, or a credit. Make the value of being early explicit.
Cold outreach has a terrible reputation because most people do it terribly. They send generic, self-promotional messages that open with "I hope this email finds you well" and immediately pivot to "I'd love to show you our product." Nobody responds to those. They're deleted in under three seconds.
But when you do outreach right — hyper-personalized, clearly researched, leading with value — you can hit 15–30% reply rates. I've done it. I know founders who consistently hit 35%+. It requires volume and precision simultaneously, which sounds contradictory, but I'll explain how it works.
R — Research. Before writing a single message, spend 2–3 minutes on the recipient. What do they post about? What's their title? What company are they at? What problem does that company have that you can solve? This is not optional. It's the entire reason the message works.
A — Acknowledge. Open with something specific about them or their company that shows you did the research. Not "I saw your post" — something that couldn't be faked. "I noticed your company recently expanded into enterprise accounts — congrats on the Series A" or "Your thread on LinkedIn about onboarding friction was exactly right." Specificity is the signal.
C — Connect the dots. Bridge what you acknowledged to the problem you solve. "The onboarding friction problem you described is exactly what [Product] tackles..."
E — Evidence. One sentence of credibility. "We're helping [similar company] reduce onboarding drop-off by 40%." Early on, this might be a beta user result or your own experience. It doesn't need to be a Fortune 500 logo.
R — Request. Ask for one specific, small thing. Not "Would love to jump on a call." Instead: "Would you be open to a 15-minute Zoom this week? I'll show you exactly how it works for a team your size." Or even smaller: "Would it be useful if I sent you a quick walkthrough video?"
Subject: [Company name] + [Your product name] — quick idea
Hi [First name],
I came across your post about [specific topic] — you were spot on about [specific insight].
Quick context: I'm building [Product name], which [one-sentence description of what it does and for whom].
I noticed [Company name] is [specific observation — growing, hiring, recently pivoted, etc.]. That's usually when [problem you solve] starts to become a real drain on [their team / revenue / time].
We're in early access, and [brief result — e.g., "the last 5 teams we onboarded cut their [X] time by half in the first two weeks"].
Would a 20-minute demo this week be worth your time? I can show you how it'd work specifically for your setup.
Either way — great work on [specific thing].
[Your name]
[Title] at [Product name]
[Website]What makes this work: it's under 150 words, references something real, doesn't oversell, and ends with a low-friction ask. The subject line uses brackets to suggest a connection without being clickbait.
Hey [First name] — saw your comment on [post/thread] about [topic]. Really good point on [specific angle].
I'm building [Product name] for [target persona] and think it might be relevant to what you're doing at [Company].
Not trying to pitch you — would love to hear your take on [problem you solve]. 10 minutes?The LinkedIn DM works because it's conversational, leads with listening rather than selling, and positions a call as getting their opinion rather than a sales demo. People's egos will often close the call for you.
[First name] — your thread on [topic] was exactly right.
I'm building something in that space. Would genuinely value your feedback — not pitching, just curious if the problem I'm solving resonates with what you described.
Mind if I DM more context?Always ask permission before sending a long DM on Twitter. The "mind if I DM more context?" converts at a surprisingly high rate because it's respectful of their attention.
The math is simple: at a 20% reply rate and a 30% booking rate from replies, you need to send 50 messages to book 3 calls. To book 10 calls a week, you need to send ~170 messages. That's 25–35 messages per day.
That sounds like a lot. It is a lot. But in the first month, this is your job. More than coding. More than design. More than anything else.
Tools that help: Apollo.io for B2B lead lists, Hunter.io for email finding, Lemlist or Instantly for sequenced email outreach. For LinkedIn, Sales Navigator is worth the subscription if your target market is on there.
One rule: personalize the opening of every single message. The rest can be templated. But that first line — the one that proves you paid attention — must be custom. This is the line that separates a 5% reply rate from a 25% one.
"Community" gets a bad reputation in startup circles because most founders approach it wrong. They join a Slack group, post "Hey everyone, check out my new product!", get ignored or banned, and conclude that community doesn't work.
Community works. But it requires a fundamentally different mindset: you are there to give, not to get.
Week 1: Listen and map. Join 3–5 communities where your target customers spend time. Subreddits, Discord servers, Slack groups, industry forums, LinkedIn groups. Do not post anything. Read everything. Map the recurring questions, the common frustrations, the debates people keep having. These are your content and outreach opportunities.
For a B2B SaaS targeting marketing agencies, this might be: r/PPC, r/digital_marketing, the Traffic Think Tank Slack, the Agency Founders Discord, and a few LinkedIn marketing groups.
Week 2: Add value without any self-promotion. Answer questions. Write detailed replies. Share resources. Ask thoughtful follow-up questions. Your goal is to post 2–3 genuinely helpful things per day across your communities. No mention of your product. Not even a link to your website. Just help.
Week 3: Build relationships. DM the people whose questions you answered. Not to pitch — to follow up. "Hey, did that approach work for you? Curious how it went." This starts real conversations. Some of these will naturally evolve into product conversations when they ask what you do.
Week 4: Soft introduce. By now, you're a known contributor. When relevant, you can mention what you're building — but only in context. "I've been working on something that tries to solve exactly this — happy to share early access if you're interested." The key phrase: "only in context." If someone posts about a problem your product solves, that's context. If there's no connection, don't force it.
Reddit requires extra care because it's highly sensitive to self-promotion. Subreddits like r/SaaS, r/startups, r/entrepreneur, and r/indiehackers are actually quite welcoming of founders sharing genuine progress — they just need to see authenticity.
The format that works on Reddit: the transparent progress post. "We launched [Product] 3 months ago. Here's everything we tried, what worked, and what flopped." Be specific. Include numbers. Don't hide the failures. Reddit rewards honesty and punishes polish.
For your specific industry subreddits (not the generic startup ones), the bar for self-promotion is higher. Build a karma history first. Your account should have 50+ upvotes from genuine contributions before you mention your product.
These communities tend to be smaller and higher-trust than Reddit. They're also more tolerant of direct product discussion — especially if you've been a good member.
Strategy for Slack/Discord:
Two communities I'd specifically recommend for early-stage B2B founders: Indie Hackers (excellent for peer support and launch visibility) and Lenny's Community (high-quality PM and growth practitioners if that's your audience).
Product Hunt is still worth your time in 2026, but with two important caveats: (1) the upvotes-to-traffic correlation is weaker than it was in 2018, and (2) the community you build in the process matters more than the ranking.
Preparation (4 weeks before launch):
Launch day:
What to expect: A top-10 product on launch day generates 500–2,000 clicks. Conversion to signups depends on your landing page. A #1 product can drive 1,000+ signups. Even a #5–10 finish typically drives 200–500 signups. For your first 100 customers, this is meaningful.
Hacker News's "Show HN" (submit at news.ycombinator.com/submit) is one of the highest-quality traffic sources available for developer or technical tools. It's more hit-or-miss than Product Hunt because HN is more opinion-driven, but when it hits, the traffic is extraordinary.
Show HN best practices:
Show HN traffic is often 1,000–10,000+ visits on a good day. For developer tools, it can be life-changing. For consumer products, it's less predictable.
r/SaaS, r/startups, and r/entrepreneur all allow genuine launch posts. The key is to frame it as a "what I built and why" rather than a product announcement.
Good title format: "I built [X] for [Y] — here's how I did it and what I learned"
Include: the problem you solved, the technical or business decisions you made, early results, and an honest admission of what you still need to figure out. Then, at the bottom: "If you're dealing with [problem], I'd love feedback — here's the link."
Reddit launches can drive 200–1,000 visits depending on the subreddit and timing. More importantly, the comments often contain extremely high-quality feedback from your exact target persona.
Indie Hackers is a must-use platform if you're building a bootstrapped or early-stage SaaS. The audience is specifically founders and solo builders — people who love discovering and trying new tools, and who talk to each other constantly.
Post a product page on Indie Hackers (free). Then post regular milestones — "Hit $1k MRR," "First 10 paying customers," "Launched on Product Hunt." The community celebrates progress and the posts drive ongoing discovery.
The Indie Hackers interview (once you have some traction) is one of the best organic marketing assets you can create. Past interviews have driven thousands of signups for products that nobody had ever heard of.
BetaList is specifically designed for pre-launch or newly launched startups. The audience is early adopters who actively look for new products to try. Expect 100–500 signups from a BetaList feature.
Submit your product 2–4 weeks before your launch date. BetaList has a queue, so early submission gives you control over timing. The paid option ($99) lets you skip the queue and choose your launch week.
One of the fastest ways to get your first 100 customers is to remove the barrier to trying your product entirely — then earn the payment by delivering real value.
Build something genuinely useful that your target customer would use independently of your main product. A calculator, a grading tool, an analysis report, a generator. Make it free. Make it excellent. This is not a "freemium" tease — it's a complete, standalone valuable thing.
Why this works: free tools rank well in search, get shared in communities, and position you as the expert on the problem before anyone knows you have a paid product. When someone uses your free tool and then discovers you have a full product that goes deeper, the conversion is warm.
Examples that have worked:
For your first 100 customers, a free tool strategy takes 2–3 months to compound. Pair it with direct outreach for faster results.
If your product has a freemium tier, the conversion rate depends entirely on how you design the limit.
Bad limits: time-based trials (people forget, then churn). Feature-gating obscure features that most users never find. Limits so generous that nobody ever needs to upgrade.
Good limits: usage-based limits at the exact point where a user has gotten value and wants more. Seat limits for collaboration features. Data or storage caps. API call limits for developers.
The moment-of-upgrade trigger should be when the user has just experienced success with your product and wants to do more of it. Design for that. The free tier should get them to their first "aha moment" — the point where they genuinely see the value — and then the limit hits just after that moment.
In-app upgrade prompts that convert:
If you're in developer tools, open-sourcing a component of your stack can be a powerful acquisition strategy. You get GitHub stars, community contributions, and inbound interest from developers who discover you through the open-source repository. When those developers need more than the open-source version offers, they upgrade.
Similarly, templates and frameworks that help people do their job better — spreadsheets, Notion templates, Figma files, Airtable bases — can drive thousands of signups when distributed through the right communities. Template marketplaces, Gumroad, and Notion's template gallery are all distribution channels worth exploring.
The fastest way to get access to someone else's audience is to become useful to their existing customers.
If your product integrates with established platforms, their marketplace is a distribution channel you should treat as seriously as Product Hunt. Salesforce AppExchange, HubSpot App Marketplace, Shopify App Store, Zapier Integration Directory — these are places where people with a specific need actively search for solutions.
The key insight: people searching in an app marketplace are already in buying mode. They're not browsing. They have a problem and they're looking for a solution right now. Conversion rates from marketplace traffic are typically 3–5x higher than general web traffic.
Getting listed requires integration work upfront, but the payoff is compounding. A well-reviewed listing in a relevant marketplace can be a top-5 acquisition source for years.
For Zapier specifically: even a single-direction integration (your product as a "trigger" or an "action") makes you discoverable to millions of Zapier users. The setup is 2–4 weeks of work and the listing is free.
Here's the honest reality: nobody wants to co-market with a startup they've never heard of. So you don't lead with "let's co-market." You lead with value.
Step 1: Identify the right partner. You want a company that serves your target customer but doesn't compete with you. If you're building a proposal tool for agencies, your partners might be project management tools, CRMs, or accounting software that agencies already use.
Step 2: Find the angle. Every partnership needs a clear "what's in it for them." Early on, the best angles are: (a) you do the work, they get credit — write a guest post, create a resource, build a free integration, all co-branded; (b) you offer their customers a discount or exclusive access; (c) you bring an audience they want — even a small, highly targeted list of 500 ideal customers can be appealing.
Step 3: Cold pitch the partnership. Email the Head of Partnerships, Marketing, or a founder directly. Keep it short:
Subject: Partnership idea — [Your Product] x [Their Product]
Hi [Name],
I'm building [Your Product], which helps [their target customer] do [specific thing].
We have about [X] customers who also use [Their Product], and I think there's a simple integration + co-promotion angle that'd be valuable for both audiences.
Happy to do all the heavy lifting — I just think the combination is strong. Worth a 20-minute call?
[Your name]"I'll do all the heavy lifting" removes the biggest objection (we don't have time). For a small startup, this is your biggest advantage — you have more flexibility and urgency than they do.
A simple referral program — "give a friend 1 month free, get 1 month free yourself" — can generate a meaningful portion of your early growth if your customers genuinely get value from your product. The condition is critical: referral programs only work when your product delivers clear, shareable results.
The mechanics are simple. Use ReferralHero or Viral Loops to implement the tracking. The key design decisions are: (a) make the reward immediately relevant to the user's goals — free usage is usually better than cash for SaaS; (b) make sharing dead simple — a single link they can paste anywhere; (c) acknowledge the referral quickly, ideally with a thank-you email that tells them their friend signed up.
This section is non-negotiable. If you're a technical founder, you might want to skip it. Don't.
You need to sell the first 100 customers yourself. Not your cofounder. Not a hired sales rep. Not a freelancer. You.
Here's why: every sales conversation with a prospect is a product research session. You learn what words they use to describe their problem, which benefits resonate, which objections keep coming up, which competitor they're currently using. This information is too valuable to delegate. A sales rep will convert some of those calls into customers. You will convert some AND come away with 20 product insights per week.
The founders who hire salespeople at customer #10 almost always regret it. They end up building a product for a sales rep's interpretation of customer needs, not the customer's actual words.
Selling is not about convincing people. That's manipulation. Real selling is about finding the people who already have the problem your product solves, helping them understand that your product is the solution, and removing the barriers to them using it.
Framework: SPIN Selling (simplified)
S — Situation. Understand their current setup. "How are you currently handling [problem]?" Listen. Take notes. Don't pitch yet.
P — Problem. Identify the pain. "How much time does that take each week?" or "What happens when [problem] goes wrong?" You're helping them articulate what they already feel.
I — Implication. Expand the impact. "So that's roughly 5 hours a week — at your billing rate, that's [cost]?" or "And what happens to client relationships when that breaks down?" You're not inventing pain — you're helping them see it clearly.
N — Need-payoff. Let them conclude. "If you could get that time back, what would you do with it?" When they describe the outcome they want, that's your cue to show them how your product delivers it.
This is not manipulation. It's structured listening. Most technical founders skip the S, P, and I, and go straight to the demo. That's why their demos don't convert.
Open with a situation question. Before you share your screen, spend 5 minutes on their context. "Tell me what you're working on — what does your day look like around [problem]?" This tells you which features to emphasize.
Show the before and after. Don't walk through every feature. Show the workflow that solves their specific problem, and contrast it with how they described doing it currently. "Right now you told me you're doing X manually — here's what that looks like in [Product]."
Let them drive. Hand over the keyboard (or the Figma prototype). People commit more when they're doing, not watching.
End with a clear next step. Not "think it over." Ask: "Does this solve the problem you described?" If yes: "What would need to be true for you to start this week?" If there's an objection, you now know what it is.
"It's too expensive." Price objection is almost always a value objection. They don't see enough value to justify the cost. Go back to the implication step: "What's the cost of not solving this?" If you can quantify it (time saved, revenue generated, mistakes avoided), the math usually works in your favor.
"We'll think about it." Asking for time is asking to lose momentum. The prospect will forget. Competitors will swoop in. Respond with: "Of course — what specifically are you weighing? Sometimes I can help clarify." This gets the real objection out.
"We're happy with [Competitor]." Don't trash the competitor. Ask: "What's working well with them? And is there anything you wish was different?" This reveals the wedge — the specific frustration that created the opening for you.
"We don't have budget right now." Ask: "When does your budget cycle reset? And if you had the budget, is this something you'd want to move forward on?" This separates "we can't buy now" from "we don't want to buy."
My strong advice: charge from day one. Even if it's low. Even if it's embarrassingly low by future standards.
There are three reasons:
That said, your pricing for the first 100 can and should be lower than your eventual pricing. Founding member pricing is real. The exchange is clear: lower price now, in return for being a reference customer, participating in product interviews, and dealing with the rough edges of early software.
You can't improve what you don't measure. But the trap most early-stage founders fall into is measuring vanity metrics — signups, page views, trial starts — instead of behavioral metrics that actually predict retention and revenue.
Activation rate. The percentage of signups who reach your "aha moment" — the action that correlates with long-term retention. This is product-specific. For a project management tool, it might be "created their first project and invited a teammate." For an email tool, it might be "sent their first campaign." Identify your activation event, instrument it, and track it weekly. Target 40%+ activation from trial start.
Day-7 retention. What percentage of users who signed up 7 days ago are still active today? This is your north star for early product-market fit. Under 20%: serious problem. 20–40%: typical early-stage. 40%+: strong signal.
Day-30 retention. Same, but 30 days out. This is your true retention signal. For B2B SaaS, you should target 60%+ day-30 retention among paying customers.
Trial-to-paid conversion rate. What percentage of free trial users convert to paid? Healthy range for B2B SaaS: 15–30%. Below 10%: pricing, onboarding, or product problem. Above 30%: you might be underpricing.
NPS (Net Promoter Score). Ask every customer after their first 30 days: "On a scale of 0–10, how likely are you to recommend [Product] to a colleague?" NPS above 40 is excellent for early-stage. The more important data, though, is the qualitative follow-up: "What's the one thing that would make this a 10?"
Feature usage heatmap. Which features are being used? Which are being ignored? This tells you where your product's actual value lives vs. where you assumed it lived. Mixpanel or Amplitude for SaaS. FullStory or Hotjar if you want session recordings.
Customer interviews are your most valuable research tool — and most founders either don't do them or do them wrong.
Who to interview: your happiest customers (understand what's working), your churned users (understand what broke), and people who tried but never converted (understand the gap).
Frequency: at least 3 interviews per week in your first 6 months. This sounds like a lot. It's not. Each interview is 30 minutes and gives you data worth 10 hours of assumption-making.
Format: semi-structured. Have 5 questions prepared, but let the conversation go where it naturally goes. Record it (with permission) so you can review and share.
The 5 Questions That Matter:
Question 5 is gold. The alternative they name is your real competitor. The pain they describe at the thought of losing your product tells you exactly what value you're delivering.
How to use the data: create a simple Google Sheet. Each row is a quote or insight. Columns: customer name, segment, quote, category (onboarding, pricing, feature X, etc.). After 10 interviews, patterns emerge. After 20, you have a clear picture of what your best customers care about and why they stay.
The most important discipline in the first 100 customers is closing the loop between what you hear and what you build. This is deceptively hard. You'll hear from 20 customers that they want feature X, and you'll build it. Then you'll hear from 5 customers who want feature Y, which contradicts your feature X decision. Then a prospect on a sales call mentions feature Z that nobody else has asked for.
The way to not lose your mind: segment by customer type. Early adopter feedback is different from mainstream customer feedback. Power user requests are different from average user requests. Sort by who's telling you what, and weight accordingly.
A simple rule: features requested by your 10 most-retained, highest-value customers get priority over features requested by everyone else. These customers are closest to product-market fit. Their feedback is most directionally correct.
Write a weekly "what we heard, what we're doing about it" note to your customers. Even if it's three sentences. It demonstrates that you listen, which is itself a retention mechanism.
Q: Should I do paid ads to get my first 100 customers?
Generally, no. Paid ads require a proven funnel — you need to know your conversion rates, customer acquisition cost, and LTV before you can make the math work. Before 100 customers, you don't have enough data. More importantly, ads won't give you the relationship-level insights that come from direct outreach and community. The exception: highly targeted LinkedIn ads for B2B can work if you have a very specific ICP (ideal customer profile) and your landing page converts well. Even then, treat it as an experiment with a hard budget cap, not a primary channel.
Q: How long should it take to get 100 customers?
For B2B SaaS with a focused ICP and active founder outreach: 3–6 months from launch. If you're moving slower than that, the bottleneck is usually one of: (1) too narrow an ICP, (2) insufficient outreach volume, (3) product doesn't deliver on its promise, or (4) pricing is too high for the value delivered. Consumer products can move faster with a viral loop or slower without one — the range is much wider.
Q: What if my product requires a long sales cycle?
For enterprise products with 3–6 month sales cycles, your first 100 customers metric may take 18–24 months. In that case, track pipeline velocity instead: number of active opportunities, stage conversion rates, and average deal size. The same tactics apply — direct outreach, community, partnerships — but your timeline assumptions need to adjust.
Q: Should I focus on one channel or diversify?
Focus first, then diversify. Pick the one channel where your customers are most concentrated and do it at maximum effort for 30 days. If it works, scale it. If it doesn't, pivot to the next. Diversifying too early spreads your attention thin and makes it impossible to determine what's actually working. The sequencing: direct outreach first (fastest feedback), community second (compounding), launch platforms third (one-time boost), free tools fourth (long-term organic).
Q: What if I'm getting signups but no one is converting to paid?
The most common causes: (1) the free tier is too generous — people don't need to upgrade; (2) the upgrade moment is too early — people haven't experienced value yet; (3) pricing is disconnected from perceived value — the jump from free to paid feels too large; (4) there's a trust gap — they like the product but don't trust you enough to put a credit card in. Fix each systematically. Run a qualitative interview specifically with trial users who didn't convert. Ask them directly: "What would have needed to be different for you to upgrade?"
Q: Is it okay to give away equity to get early customers?
Generally no, but advisor arrangements can work. The common early-stage pattern: offer an advisor agreement (0.1–0.25% vested over 2 years) to 2–3 industry experts in exchange for introductions to their network, product feedback, and social proof. This is different from giving equity to customers — you're paying for access and credibility, not for a purchase. Do this selectively with people who have genuine networks in your target market and who you'd want on your cap table.
Q: What's the most underrated tactic for getting the first 100 customers?
Handwritten onboarding. When a new customer signs up, email them personally. Not a Mailchimp template — a genuine email from your personal address. "Hey [Name], I saw you just signed up — I'm Udit, the founder. What made you decide to try this? And is there anything specific you're hoping it helps with?" This converts a transaction into a conversation. It improves activation because you're now personally invested. It generates feedback. And it shocks people in the best way — they didn't expect the founder to reach out. Most of your first 100 customers will remember that email.
Q: When do I stop doing founder sales and hire?
When you can write down, in explicit enough detail that another person could follow it, a sales playbook that consistently closes deals. This usually happens around customer 80–120. You should have: a clear ICP, a predictable outreach sequence with known conversion rates, a demo framework that reliably gets "yes," a set of objection-handling scripts that work, and a known sales cycle length. Hiring before this is premature. You'll either hire the wrong person or be unable to evaluate their performance. Get to the playbook first. Then hire.
Getting to 100 customers is not about having the best product, the biggest network, or the most funding. It's about doing the uncomfortable, manual, relationship-heavy work that doesn't scale — yet. Every founder who reaches 100 customers and looks back says the same thing: "I wish I'd been more aggressive earlier."
Start tomorrow. Pick one channel. Send 20 messages. Book two calls. Close one customer. Then do it again.
The first 100 are waiting. Go find them.
If you're working on early-stage growth and want to think through your acquisition strategy, I'm occasionally available for founder office hours. Find me on X/Twitter or reach out through udit.co.
Practical strategies to reduce customer acquisition cost for startups — from zero-CAC channels to creative testing frameworks that cut paid acquisition costs by 40%.
Learn how vibe coding with AI tools like Claude Code, Cursor, and v0 lets solo founders build and ship products 10x faster — the complete playbook for AI-augmented development.
Why vertical AI startups have 3x higher retention and can charge 10x more than horizontal tools — the complete playbook for building industry-specific AI products.