Guides founders in acquiring first 100 customers via prospect lists from LinkedIn/Reddit, personalized cold outreach, and sales closing strategies.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersThis skill uses the workspace's default tool permissions.
Your first 100 customers won't come from inbound. You have to go get them. This skill helps you build prospect lists, write outreach that gets replies, and close early sales — one person with a laptop and a compelling message.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Your first 100 customers won't come from inbound. You have to go get them. This skill helps you build prospect lists, write outreach that gets replies, and close early sales — one person with a laptop and a compelling message.
If
ABOUT-ME.mdand/orMY-ICP.mdexist in the project root, read them before writing outreach. Lead with founder credibility from ABOUT-ME.md (Domain Expertise, Key Stories). Frame the message around ICP pain from MY-ICP.md (Their Pain, Their Language). If the founder has a strong network (ABOUT-ME.md Network & Distribution), prioritize warm channels over cold outreach.
LinkedIn (best for B2B SaaS):
Communities:
Review sites:
Job boards:
Existing networks:
Build a spreadsheet:
| Name | Title | Company | Company Size | Source | Email | LinkedIn | Pain Signal | Status | Last Contact | Response | Notes |
Pain signal is the most important column. It's the specific reason you believe THIS person has the problem you solve:
Minimum viable list: 100 prospects before you start sending.
[1-2 sentences showing you know THEM and THEIR problem]
[1 sentence connecting to your experience with that problem]
[1 sentence introducing your solution — what it does, not what it is]
[1 sentence with a specific, low-commitment ask]
Subject: [Specific to their situation — NOT your product name]
Hi [First name],
I noticed [specific observation about them — their company, a post they
wrote, a job listing, a review they left]. [One sentence about why that
caught your attention, connecting it to a problem you understand.]
I ran into the same issue when I was [your relevant experience]. That's
why I built [Product] — it [one sentence on the specific outcome, not
features].
[Concrete proof point: "We've helped X companies reduce Y by Z%" or
"Here's a 2-minute demo: [link]"]
Would a quick 15-minute call make sense to see if this fits your situation?
[Your name]
[Product — one-line description]
Cold email:
Subject: re: your [specific pain signal]
Hi Sarah,
I saw your G2 review of [Competitor] — sounds like the reporting
limitations are costing your team real time. I heard the same thing
from 3 other marketing ops leads this month.
I built [Product] specifically to solve that gap — it [specific
outcome]. [Company X] cut their reporting time from 4 hours to 20
minutes.
Worth a 15-minute look? I can show you exactly how it'd work for
your setup.
— [Name]
LinkedIn DM:
Hi [Name] — I noticed you're leading [function] at [Company].
Curious: are you still using [current tool/process] for [task]?
I've been building something specifically for teams your size
and would love your take. No pitch — genuinely looking for feedback
from people doing this work daily.
Community reply (Reddit, HN, Discord):
I dealt with exactly this. [Share your genuine experience with the
problem — 2-3 sentences of value.] I actually ended up building a
tool to fix it for myself: [link]. Happy to answer questions if
you're exploring options.
Morning (30-45 minutes):
1. Send 10 new outreach messages (personalized).
2. Send follow-ups to previous messages (per sequence rules).
3. Reply to any responses from yesterday.
4. Log everything in your spreadsheet.
End of week (15 minutes):
1. Review response rate: Target 10-20% reply rate.
2. Review objections: What are people saying?
3. Refine message based on what's working.
Day 0: Initial message (the full problem-first message)
Day 3: Follow-up #1 — Short, add new value
"Hi [Name], following up on my note about [problem].
I just published [relevant resource] that might be useful
regardless — [link]. Still happy to chat if it makes sense."
Day 8: Follow-up #2 — Even shorter, different angle
"Hi [Name], one more thought — [different proof point or
angle]. If the timing isn't right, no worries at all."
Day 15: Follow-up #3 (final) — Breakup email
"Hi [Name], I'll assume this isn't a fit right now.
If [problem] comes back up, I'm at [email]. Good luck
with [something specific about their work]."
Positive reply ("Sure, let's chat"):
Objection reply:
No reply (most common):
Apply the same systematic approach:
| Directory | URL | Category | Submitted | Status | Backlink? | Traffic? |
Batch this work: dedicate 2-3 focused sessions to submit to 100+ directories. Write 3 variations of your product description (short, medium, long) and reuse across submissions.
Priority directories: Product Hunt, BetaList, DevHunt, Uneed, MicroLaunch, AlternativeTo, SaaSHub, GetApp, G2 (free listing), Capterra (free listing).
Weekly outreach metrics:
Messages sent: ___
Reply rate: ___% (target: 10-20%)
Positive reply rate: ___% (target: 3-8%)
Calls booked: ___
Demos given: ___
Conversions: ___
Objection frequency:
[Objection 1]: ___ times
[Objection 2]: ___ times
[Objection 3]: ___ times