agentleFS
jtmuller5jtmuller5/small-business-skills/skills/sell/SKILL.md

sell

Skill0 starsChanged 2 months agoMITView on GitHub

Set a price that is defensible, run the conversation that closes, and follow up without being annoying. Use when people are interested but not buying, when someone does not know what to charge, when they keep discounting, or when they are afraid to ask for the money.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. AetherCore-Dev/ag402★ 9same name
    2. ychampion/ystack★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Never hourly for anything where getting faster is possible.

    line 44
  2. Distinctive:

    Follow up three times over two weeks, each time with something useful rather than "just checking in".

    line 76
  3. Distinctive:

    Do not discount to close. Change the scope if the price has to move, so the price itself stays true.

    line 89
  4. Distinctive:

    Do not price their time at zero.

    line 91
  5. Distinctive:

    Do not present tiers when one price would do.

    line 92
  6. Distinctive:

    Do not let them avoid saying the number out loud.

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Sell

Two jobs: the number, and the conversation. Most small businesses are wrong on the first and avoid the second.

The number

Work through all four and say the number each one implies, then recommend one:

  1. Cost-plus. Cost to deliver, including their time at a real rate, plus margin. This is the floor, not the price. If they are below it, everything else is moot.
  2. Competitive. What comparable options cost, including the alternative of doing nothing and the alternative of hiring someone.
  3. Value. What the problem costs the customer per month. Price is easiest to defend when it is visibly a fraction of that.
  4. What the market showed. What people actually paid or committed to in validate. This is the only number backed by evidence — weight it heavily.

Then give one recommendation and one sentence of reasoning. Not a range for them to choose from; they came here because choosing is hard.

Bias upward. The most common small-business pricing error by a wide margin is charging too little, and it is nearly unfixable once customers exist. Undercharging also filters for the customers who are hardest to serve, which is the part nobody warns about.

Structure

Say which of these fits and why:

  • One price — simplest, and simplest usually wins.
  • Three tiers — works when the middle one is the one you want sold. If they cannot say which tier they expect most people to buy, they are not ready for tiers.
  • Retainer or subscription — better for both sides when the work recurs. Worth proposing even where it is unusual in the trade.
  • Per project — needs a scope boundary written down, or it becomes hourly work at a fixed price.

Never hourly for anything where getting faster is possible. It prices skill downward.

The conversation

Give them a structure they can hold in their head:

  1. Ask before telling. What are they trying to fix, what have they tried, what happens if they do nothing? Three questions, then listen.
  2. Say it back. Repeat their problem in their words. This does more to close a sale than any description of the product.
  3. Then describe the offer, only in terms of the problem they just described.
  4. Say the price, out loud, and stop talking. The silence after a price is uncomfortable and it belongs to the buyer. Filling it with a discount is the single most expensive habit in small-business selling.
  5. Ask for the decision. "Do you want to go ahead?" Not "let me know if you're interested", which is a way of not asking.

Objections

Prepare answers for the five they will actually hear — too expensive, need to think, not the right time, already have someone, need to ask someone else. For each, write the honest response rather than the clever one.

And distinguish the two versions of "too expensive": I cannot afford it and I do not see why it costs that. The first is a qualification problem, the second is an explanation problem, and treating them the same loses both.

Follow up

Most sales are lost to silence, not to no.

  • Agree the next step during the conversation, with a date.
  • Follow up three times over two weeks, each time with something useful rather than "just checking in".
  • Then stop, and say so plainly: "I'll leave it with you — get in touch when the timing is right." That last message closes a surprising number of them.

What to hand back

pricing.md — the four numbers, the recommendation, the structure, and what to test in three months. sales.md — the conversation structure, the five objections with answers, and the three follow-up messages written out ready to send.

Do not

  • Do not discount to close. Change the scope if the price has to move, so the price itself stays true.
  • Do not price their time at zero.
  • Do not present tiers when one price would do.
  • Do not let them avoid saying the number out loud. Practise it if needed; it is the part that gets easier only by doing.

Next

grow when it works and there is more demand than time.

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.