agentleFS
HaroonArshad-53HaroonArshad-53/skills-for-everyone/skills/pricing-calculator/SKILL.md

pricing-calculator

Skill1 starsChanged 32 days agoMITView on GitHub

Calculate a fair freelance project price or hourly rate from hours, experience level, platform fees, rush deadlines, and revision rounds, and present a low, recommended, and high quote with the reasoning. Use when a user asks how much should I charge, price this project, is this budget fair, or wants to convert a monthly salary goal into an hourly rate. If Python is available, run the bundled scripts/pricing.py for exact numbers instead of estimating.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the client stated budget is below the Low number, say that plainly and suggest either a reduced scope that fits the budget, or declining.

    line 18
  2. Very specific:

    Never do the fee maths in your head if the script is available - run scripts/pricing.py.

    line 21
  3. Distinctive:

    If the client says it is too much - the reduced scope that honestly fits their budget

    line 30
  4. Very specific:

    Good output (excerpt): Run pricing.py: base 300, rush 1.25x = 375, extra revision round +10 percent = 412.50, grossed up for the Upwork 10 …

    line 35

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Pricing Calculator

When to use this skill

  • Quoting a fixed-price project
  • Deciding if a client budget is worth it
  • Converting a monthly income goal into an hourly or project rate

Workflow

  1. Collect the inputs that change the price: estimated hours (use the project-scope-planner output if it exists), experience level (beginner, intermediate, expert), platform fee percent (Upwork 10, Fiverr 20, direct 0 by default - confirm with the user), deadline rush (normal, under 7 days, under 48 hours), revision rounds included.
  2. If scripts/pricing.py is available in this skill folder, run it with these inputs and use its exact output. Otherwise calculate: base = hours x hourly rate; rush multiplier 1.25x for under 7 days, 1.5x for under 48 hours; each revision round beyond 2 adds 10 percent; then gross up so the user still receives the target after the platform fee: quote = target / (1 - fee).
  3. Present three numbers: Low (win the job, thin margin - state the risk), Recommended (fair for both sides), High (premium positioning, faster or richer scope).
  4. Show what the user actually keeps after the platform fee for each number. The take-home number is the truth, not the quote.
  5. If the client stated budget is below the Low number, say that plainly and suggest either a reduced scope that fits the budget, or declining. Never just lower the price to match.

Rules - never break these

  • Never do the fee maths in your head if the script is available - run scripts/pricing.py.
  • State every assumption (hours, rate, fee percent) next to the quote so the user can correct one number and recalculate.
  • A quote is hours x value, not a guess. If hours are unknown, price a paid discovery or pilot milestone instead of guessing the whole project.
  • Currency: use the user currency and, for international platforms, also show the USD figure if they gave a USD rate.

Output format

  • Inputs used - hours, rate, level, fee percent, rush, revisions
  • Low / Recommended / High quotes - with take-home after fees for each
  • Why - 2-3 lines of reasoning
  • If the client says it is too much - the reduced scope that honestly fits their budget

Example

User: How much should I charge for a 20-hour logo and brand kit project on Upwork? I am intermediate, my rate is 15 dollars per hour, client wants it in 5 days, 3 revision rounds.

Good output (excerpt): Run pricing.py: base 300, rush 1.25x = 375, extra revision round +10 percent = 412.50, grossed up for the Upwork 10 percent fee = 458 quote to keep 412. Recommended quote: 460. Take-home shown for all three tiers.

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.