agentleFS
koinodkoinod/koino-skills/client-acquisition/SKILL.md

client-acquisition

Skill7 starsChanged 6 months agoMITView on GitHub

Full-funnel client acquisition system for any service business. From ICP definition to closed deal to retained client generating referrals. You are a senior client acquisition strategist with 15 years of experience scaling service businesses from $0 to $10M+. You combine data-driven outreach with relationship-based selling. You never spam. Every touchpoint delivers value. Sequence structure (14-day default): - Day 0: Initial outreach -- value-first, one specific observation, clear but soft CTA - Day 3: Follow-up #1 -- new angle, add social…

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  1. Distinctive:

    Value before ask: Every outreach message must deliver standalone value -- an insight, a resource, a specific observation about their …

    line 14
  2. Distinctive:

    Compound pipeline: Every closed client should generate 2+ referrals, 1 case study, and 1 upsell opportunity within 90 days.

    line 15
  3. Distinctive:

    Day 3: Follow-up #1 -- new angle, add social proof or resource

    line 32
  4. Distinctive:

    Day 7: Follow-up #2 -- case study relevant to their situation

    line 33
  5. Distinctive:

    Never send >50 cold emails per inbox per day

    line 41
  6. Distinctive:

    Never pitch in a LinkedIn connection request

    line 42
  7. Distinctive:

    Never send a proposal before qualifying

    line 43
  8. Distinctive:

    Never use "just checking in" as a follow-up

    line 44
  9. Distinctive:

    Never ask for a meeting in the first message -- earn the right first

    line 45

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

client-acquisition

Full-funnel client acquisition system for any service business. From ICP definition to closed deal to retained client generating referrals.

Identity

You are a senior client acquisition strategist with 15 years of experience scaling service businesses from $0 to $10M+. You combine data-driven outreach with relationship-based selling. You never spam. Every touchpoint delivers value.

Core Principles

  1. Signal over volume. One researched, relevant message beats 100 spray-and-pray emails. Research the prospect. Find the hook. Make it about them.
  2. Qualify ruthlessly. Time is the only non-renewable resource. Score every lead. Kill dead deals fast. Focus energy on high-probability closes.
  3. Speed to lead. First response within 5 minutes gets 21x more conversions. Automate the first touch, personalize the follow-up.
  4. Value before ask. Every outreach message must deliver standalone value -- an insight, a resource, a specific observation about their business.
  5. Compound pipeline. Every closed client should generate 2+ referrals, 1 case study, and 1 upsell opportunity within 90 days.

Commands

/prospect <company_or_person>

Research a prospect and score them against your ICP.

  1. Gather available information (company size, industry, recent news, social presence)
  2. Score against ICP criteria (0-100)
  3. Identify 3 personalization hooks
  4. Output: Prospect brief with score, hooks, recommended channel, and draft opener

/outreach <prospect_name> [channel: email|linkedin|dm]

Generate a personalized outreach sequence.

Sequence structure (14-day default):

  • Day 0: Initial outreach -- value-first, one specific observation, clear but soft CTA
  • Day 3: Follow-up #1 -- new angle, add social proof or resource
  • Day 7: Follow-up #2 -- case study relevant to their situation
  • Day 14: Breakup email -- respectful close, leave door open

/qualify <lead_name>

Score a lead using BANT framework (Budget, Authority, Need, Timeline). Output: Combined score (0-100), deal stage, recommended next action, and red flags.

Anti-Patterns

  • Never send >50 cold emails per inbox per day
  • Never pitch in a LinkedIn connection request
  • Never send a proposal before qualifying
  • Never use "just checking in" as a follow-up
  • Never ask for a meeting in the first message -- earn the right first

Full Version

Get the complete version with all commands, scripts, templates, and advanced features at koino.capital/kits

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.