agentleFS
zubair-trabzadazubair-trabzada/ai-proposal-claude/skills/proposal-pricing/SKILL.md

proposal-pricing

Skill39 starsChanged 6 months agoMITView on GitHub

Builds Good-Better-Best pricing with ROI math for a service. Invoked by /proposal pricing <service>. Output: PROPOSAL-PRICING-[Service].md. Works for any service — a web build, automation setup, marketing retainer, consulting, coaching, GEO/SEO, whatever.

The file

Files
SKILL.md

Proposal Pricing — 3-Tier Pricing Builder

Builds Good-Better-Best pricing with ROI math for a service. Invoked by /proposal pricing <service>. Output: PROPOSAL-PRICING-[Service].md.

Works for any service — a web build, automation setup, marketing retainer, consulting, coaching, GEO/SEO, whatever.

Steps

  1. Identify the service and engagement model (one-time project / monthly retainer / value-based / hybrid).
  2. Set the price anchor: use the user's own rates first; else value-based (a fraction of the value created); else a market reference. Fallback AI-adjacent bands: web build $1.5K–10K · automation $2K–15K (or $500–5K/mo) · marketing $1K–5K (or $2K–10K/mo) · GEO/SEO $500–2.5K (or $1.5K–10K/mo) · consulting $1.5K–10K.
  3. Adjust for client size, location (HCOL ×1.05–1.15), urgency, buyer sophistication.
  4. Build 3 tiers with aspirational names:
    • Starter/Launch — foot in the door, smallest viable scope, low end
    • Growth/Core ★ RECOMMENDED — the complete solution, midpoint, the target
    • Scale/Partner — premium anchor, expanded scope, high end
  5. ROI math per tier: investment → expected return → breakeven → 12-mo ROI multiple. Conservative must stay positive.

Rules

Top tier anchors; middle is RECOMMENDED; bottom never too complete. Never a price without ROI context. If an audit score exists, frame price against the point gap in revenue terms.

Output

A pricing comparison table (feature rows across 3 tiers), ROI math block per tier, and a one-line recommendation on which tier to push given the client's budget.

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.