agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/automation-pricing-and-close/SKILL.md

automation-pricing-and-close

Skill12 starsChanged 4 months agoMITView on GitHub

Price a scoped automation pilot or setup-plus-retainer service and draft a clear closing conversation. Use when a qualified opportunity is ready for commercial terms, pricing feels arbitrary, or another approver is needed.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use this sequence in the buyer's language:

    line 38
  2. Distinctive:

    Ask for a decision or surface the unresolved condition.

    line 42
  3. Distinctive:

    If another approver is needed, identify who, their criteria, and a dated joint next step.

    line 43

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

Automation Pricing and Close

Turn a qualified problem into a sustainable price and an explicit decision. Treat all proposed terms as drafts. A first sale should not create unlimited delivery obligations.

Establish scope and economics

Use the buyer's confirmed problem and success metric, included workflow/integrations, delivery effort, subcontractor and platform costs, support load, buyer dependencies, proof, alternatives, and preferred currency. Ask for missing cost assumptions that materially change the price. If no qualified opportunity exists, give provisional pricing with the discovery gaps.

Separate setup work from recurring work. A one-time workflow with no ongoing service does not justify a retainer by itself. Name monitoring, maintenance, usage, reporting, and support inclusions only when the seller will deliver them. Identify overages and change requests.

Calculate, using supplied or explicitly labeled scenario inputs:

  • Delivery cost = labor hours x loaded hourly cost + direct costs + stated contingency.
  • Setup floor at target gross margin = setup cost / (1 - margin).
  • Monthly floor at target gross margin = recurring cost / (1 - margin).

Specify currency, margin as a fraction below 1, and assumptions. Do not confuse margin with markup: a hypothetical cost of $600 at 50% gross margin implies a $1,200 floor, not $900. A floor is not proof of willingness to pay.

Compare the floor with credible buyer value and alternatives. Use buyer-provided baselines for time or cost savings and show the calculation. Treat uncertain savings as a range. Do not price from fabricated ROI or claim that a particular multiple is universally correct.

Recommend a simple price ladder

Present one recommended paid pilot or setup plus retainer, with an optional alternative only if the tradeoff is meaningful. Explain the deliverables, duration, setup fee, recurring fee if any, billing trigger, customer obligations, scope exclusions, and acceptance process. If the affordable budget is below the delivery floor, reduce scope or decline; do not hide losses in an uncapped guarantee.

Draft risk reversal around something the seller can control. Define the failure condition, measurement period, remedy, and maximum exposure. No invented deadlines, discounts, testimonials, or guaranteed business results.

Write the closing conversation

Use this sequence in the buyer's language:

  1. Confirm the problem, desired outcome, and agreed scope.
  2. State the price and what it covers without apology.
  3. Ask for a decision or surface the unresolved condition.
  4. If another approver is needed, identify who, their criteria, and a dated joint next step.
  5. Confirm the selected next action, owner, and timing.

A possible decision question: "Does this scope and price work for you, or is there something we still need to resolve?" Allow a real no. If timing is wrong, agree a relevant future trigger rather than creating pressure.

Deliver

  • Scope and economics worksheet, with assumptions and margin calculation.
  • Recommended price and explanation of cost floor versus buyer value.
  • Draft commercial terms, exclusions, and bounded risk reversal.
  • Closing script and approver-path response.
  • Deal status: proposed, agreed verbally, signed, or paid, based only on evidence. Name the next unconfirmed step.

For an internal operator, replace external fees with requested resources, implementation effort, sponsor decision, and measurable pilot value. Keep the same discipline about cost and approval evidence.

Working agreement

Use context already supplied. Ask only for missing facts that change the next decision, preferably in one short batch, then make a useful first draft. Label assumptions and distinguish buyer evidence from your interpretation. Never invent interviews, prospect facts, results, testimonials, budget, or meetings. A target date is a planning goal, not a promised commercial outcome. Use plain sentences and normal hyphens in generated copy.

Create drafts and plans within the requested scope. Sending messages, booking meetings, publishing, changing a CRM, or committing the user to commercial terms requires authorization for that action. A request for advice alone does not authorize execution. Work from pasted notes if tools are unavailable; identify what remains unverified.

Source

Agent J Sales 101 curriculum-deck.pdf, page 11; week2-offer-deck.pdf, pages 6-9. The decks credit Hormozi for value-based packaging and risk reversal. Cost calculations and commercial worksheets are this skill's adaptations. These are practical adaptations by John Peslar AI, not endorsements by the referenced educators. The skill is self-contained; the original decks are not required at runtime.

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.