agentleFS
anotbanotb/management-consulting-plugin/skills/engagement-pricing/SKILL.md

engagement-pricing

Skill62 starsChanged 12 days agoMITView on GitHub

Price consulting engagements and evaluate delivery economics. Use for fee models, rate cards, margin floors, realization, retainers, discounts, payment schedules, and the commercial section of a proposal or SOW.

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

    Use commercial structures and negotiation for payment, retainer, outcome, and concession detail.

    line 39

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

Engagement Pricing

Develop a commercially credible price that fits the scope, delivery cost, value to the client, and available alternatives. Start with the user's requested pricing decision; preserve an agreed model or terms unless a material problem needs to be raised.

Use the supplied scope, cost basis, capacity, rate card, target margins, budget, and procurement context. Continue a draft with explicit unknowns when inputs are missing; ask only for information that prevents a defensible calculation or recommendation. Do not substitute generic rate or margin benchmarks for firm data.

Select the commercial model

Assess scope certainty, duration, deliverables, dependence on client actions, outcome measurability, attribution, and payment risk. Fixed fees fit bounded deliverables when delivery risk can be estimated. T&M fits evolving work; caps need an explicit scope or effort boundary. Retainers fit continuing access or delivery with defined capacity and service expectations, including a new client when that arrangement is suitable.

Distinguish pricing based on value from payment contingent on outcomes. A fixed value-based fee need not depend on measuring realized results; an outcome-linked fee needs a defensible baseline, measurement rules, attribution, timing, and treatment of external factors. Hybrid structures can share uncertainty without leaving all costs at risk.

Model the economics

Define what each cost includes before adding it. If personnel cost already includes benefits and allocated overhead, do not allocate that overhead again. Separate direct delivery costs, incremental external costs, allocated overhead, and risk contingency. Make the allocation basis explicit. Do not use billing rates as personnel costs.

Calculate the relevant measures with available tools and state their definitions:

  • Delivery margin amount = fee minus defined direct delivery cost; percentage = that amount divided by fee.
  • Profit after allocations = fee minus all included costs, counted once; percentage = profit divided by fee.
  • Minimum fee for target margin m on that cost basis = included cost / (1-m), for m < 1.
  • Realization = actual fee / rate-card value of actual delivery effort. Explain write-offs, discounts, and scope growth.
  • Effective daily rate = fee / total person-days. Confirm the workday length and distinguish headcount from effort.

Show the effect of overrun, scope change, discount, and payment timing where they change the decision. A contingency is a disclosed allowance derived from risks, not an automatic percentage added to an already risk-adjusted estimate.

Propose terms and trade-offs

Use commercial structures and negotiation for payment, retainer, outcome, and concession detail. Respect supplied contract terms and the firm's approval authority. Present proposed terms as proposals, not universal legal requirements or commitments already made.

Tie payment timing to the delivery cost curve, exposure to delayed acceptance, and procurement constraints. Quantify financing costs where material instead of imposing a universal Net 30 or final-payment cap. Make scope, client dependencies, change control, acceptance, and exit terms specific to the engagement.

For the client's value case, distinguish benefit-cost multiple (benefits / costs) from net ROI ((benefits-costs)/costs). Include relevant client implementation and operating costs, not only the consulting fee. Explain whether benefits are cash savings, released capacity, incremental contribution, or risk reduction. Claim attribution only where supported.

Deliver

Present the recommended fee and structure, included scope, assumptions, cost and margin basis, downside exposure, payment schedule, and decisions needed. Offer alternative tiers only when they represent useful scope or risk choices. Keep numerical tables compact and put the rationale beside the choice. Producing a quote does not authorize submitting it or agreeing concessions with a client.

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.