find-first-customers
Skill2 starsChanged 5 months agoApache-2.0View on GitHub
Use when a founder needs their first paying customers and there's no inbound, no audience, and no growth engine yet - when they say "how do I get my first customers", "nobody's signing up", "how do I do outbound", "I hate selling", "how do I get to 10 customers", or are waiting for customers to magically appear. Produces a target list from the ICP, one outbound channel, a non-spammy outreach message, a conversation-to-ask script, and a simple pipeline to track it. Pair with positioning-and-gtm and launch-plan.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/founderos.mdcCursor rule
- apply-mental-modelsSkill
- brand-and-namingSkill
- capture-learningSkill
- cofounder-and-equitySkill
- consumer-product-testingSkill
- customer-interviewsSkill
- first-hireSkill
- founderos-prompt-scaffoldSkill
- investor-pipelineSkill
- landing-page-copySkill
- launch-planSkill
- legal-and-incorporationSkill
- north-star-metricsSkill
- pitch-deckSkill
- pivot-decisionSkill
- positioning-and-gtmSkill
- pricing-strategySkill
- runway-and-unit-economicsSkill
- scope-mvpSkill
- sensory-testingSkill
- start-hereSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
Do things that don't scale on purpose - hand-built lists and personal messages, not automation, at this stage.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Find Your First Customers
The first ~10 paying customers don't come from a funnel - they come from a founder doing things that don't scale: a hand-built list, personal messages, real conversations, and a direct ask for money. First-timers stall here because selling feels uncomfortable, so they hide behind building features and waiting for inbound that never arrives. This skill gives you a concrete, repeatable motion to go get them by hand - and learn from every "no."
The method
Built on the Founder OS scaffold (High tier). Full templates in references/early-sales.md.
Step 1 - Build a target list from the ICP
You can't sell to "everyone." Translate [ICP] into a list of named, reachable people - 30-50
to start - who plausibly have [PROBLEM] right now. Use the sourcing tactics in references
(communities, search, your network's network, competitor reviews). Each row is a real human, not a
segment. Research enough to know why this person, before you write a word - generic blasts get
generic silence.
Step 2 - Pick ONE outbound channel
Choose the single [CHANNEL] where you can actually reach this list and they'll actually read it:
cold email, LinkedIn/DM, a warm intro, or a community post. One channel, done well and measured,
beats five done half-heartedly. Match the channel to where [ICP] already pays attention.
Step 3 - Write a short, non-spammy message
Good early outreach is short, specific, and about them, not your product. Reference why you're
reaching this person, name the [PROBLEM] in their words, and make a small, low-friction ask
(usually a 15-minute conversation - not "buy now"). Use the good/bad examples in references.
A draft is not a sent message - write three, pick the tightest, then send. Personalize the opening
line; templated flattery reads as spam.
Step 4 - Run the conversation to a clear ask
The call has a job: confirm the problem, see if you're a fit, and make one explicit ask - a trial, a pilot, or a purchase. Use the qualifying questions in references to disqualify fast (your time is the scarce resource). Don't pitch into a vacuum; ask, listen, then ask for the close. If they're a fit, name the next step and a date. Vague "let's stay in touch" is a polite no.
Step 5 - Handle the "no," then close and learn
Most early answers are "no" or an objection - that's data, not rejection. Use the objection table
in references to respond honestly (not to manipulate), and log why each person passed. Patterns
in the no's tell you whether to fix the message, the [ICP], the price, or the product. Track
everything in the simple pipeline so you can see your real conversion [METRIC] and improve it.
Batch a cohort of outreach, then decide what to change - don't rewrite the script after every reply.
Output
- Target list of 30-50 named, reachable people matching
[ICP], with a one-line "why them." - One channel chosen, with the reason it fits where
[ICP]already is. - Outreach message (≤5 sentences) with a personalized opener and a low-friction ask.
- Conversation script: qualifying questions → the one explicit ask → the named next step.
- Pipeline table (contacted → replied → call → trial → paid) with the conversion
[METRIC]and the top reasons for "no."
Constraints
- Do things that don't scale on purpose - hand-built lists and personal messages, not automation, at this stage.
- The first ask is usually a conversation, not a sale. Earn the right to ask for money.
- A "no" is data - log the reason; don't argue the prospect out of it.
- One channel at a time. Measure the
[METRIC]before adding a second. - Stay theme-agnostic; the founder supplies the domain, you supply the motion.
Copy-paste version
Act as a hands-on early-sales coach for a first-time founder who hates selling.
My product: [ONE_LINER]. Who it's for: [ICP]. The problem it solves: [PROBLEM]. My constraints: [CONSTRAINT].
Help me get my first ~10 paying customers by hand:
1. Turn my [ICP] into a way to build a list of 30-50 NAMED, reachable people who likely have [PROBLEM] now - tell me exactly where to find them.
2. Pick ONE outbound channel (cold email / LinkedIn DM / warm intro / community) that fits where they already are.
3. Write me a short (≤5 sentence) outreach message that's about THEM, names the problem in their words, and asks for a 15-minute conversation - plus a bad example so I see what to avoid.
4. Give me a conversation script: qualifying questions to disqualify fast, then ONE clear ask (trial/pilot/purchase) and a named next step.
5. Give me an objection-handling table and a simple pipeline (contacted → replied → call → trial → paid) so I can track my conversion and learn from every "no."
Don't let me automate this yet, don't let me pitch before I listen, and treat every "no" as data to log.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

