first-customers
Create a strategy for selling to your first 100 customers using the minimalist entrepreneur playbook. Use when someone has a product and needs to find customers, or is struggling with early sales.
What this skill does
You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user sell to their first 100 customers. ## Core Principle **Skip the launch. Focus on selling.** "Viral success" is a myth. There is no such thing. Every seemingly overnight success is built on months or years of hard work. Your job is to sell one by one, learn from each interaction, and build momentum. ## The Concentric Circles of Sales Sell outward from the people who care most about you to the people who care least: ### Circle 1: Friends and Family - Start here. Yes, it's uncomfortable. Do it anyway. - Pitch them on being your first customers, not investors - They trust you more than anyone else. If they won't buy, who will? - Ask for their honest feedback, not social media posts - Kickstarter says: "Support always begins with people you know" ### Circle 2: Your Community - The community you identified and have been contributing to - These are subject matter experts who understand the problem - Three steps: 1. **Make a list of everyone** who has written or shared anything about a similar business 2. **Contact them all personally** — walk them through your product, offer a free meal, do it hundreds of times 3. **Ask for candid feedback** — not reviews or social posts, just honest feedback ### Circle 3: Strangers (Cold Outreach) - Cold emails, calls, messages — this works. It's how Gumroad grew. - Sahil literally scoured the web for people who could benefit from Gumroad and emailed them personally, thousands of times - Example cold email: > "Hi John, I saw you're selling a PDF on your website using PayPal, and manually emailing everyone who buys the PDF. I built a service called Gumroad which basically automates all of this. I'd love to show it to you, or you can check it out yourself: gumroad.com. Also happy to just share any learnings we see from creators in a little PDF we have. Let me know! Best, Sahil" - Don't copy/paste. Each email refines your ability to write better ones - Use each rejection as a learning opportunity ## Sales is Not a Dirty Word Reframe how you think about sales: - You're not convincing anyone. You're helping people. - You already have a relationship with your community - You're selling a product that adds value to their life - Turn every failed conversion into an insight — either wrong person, or product needs work - Sales is an education process: your customers get to know you, you get to know what's working ## Pricing (Charge Something!) - There is a massive difference between free and $1 (the "zero price effect") - Two ways to charge: - **Cost-based**: Your costs + a margin (e.g., 20-50%) - **Value-based**: What it's worth to the customer, regardless of your costs - Start low and raise prices over time as your product improves - Pricing is iterative, just like everything else. It's not permanent. - Goal: eventually move to tiered pricing as you build brand and value ## Key Metrics - **Manual sales = 99% of early growth.** Word of mouth = 99% of later growth. - You need far fewer customers than you think. Slack's IPO: 575 customers = 40% of revenue. - If your product costs $10/month, you need 200 customers for $2,000/month. At one customer per business day, that's less than a year. - **Product-market fit** = repeat customers who sign up and use your product on their own ## When to "Launch" Don't launch until you have 100 paying customers. Then launch as a celebration of your community's support, not as a customer acquisition strategy. Throw a party. Thank your customers. Invite them. ## Output Help the user create: 1. A list of 10 friends/family to pitch this week 2. A list of 10 community members to reach out to 3. A cold outreach template (personalized, not copy-paste) 4. Their initial pricing strategy 5. A weekly sales goal and tracking method
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.