← ClaudeAtlas

pricing-advisorlisted

Suggest how to price a specific gig, bid, or hourly rate based on the job's scope, the client's budget signals, and the platform's norms. Triggers on "how much should I charge", "price this job", "is this budget fair", "what should my hourly rate be". Not for writing the pitch itself (use proposal-writer).
SidSharma010/freelance-gig-skills · ★ 1 · DevOps & Infrastructure · score 69
Install: claude install-skill SidSharma010/freelance-gig-skills
# Pricing Advisor Freelancers usually either underprice out of fear of losing the bid, or guess a round number with no reasoning behind it. This skill reasons through a specific price from the actual scope, then explains the reasoning — not just a number, so the user can defend it if a client pushes back. ## When to use - User pastes a job post and asks what to charge or bid - User asks whether a stated client budget is reasonable for the scope - User wants help setting a base hourly or project rate for their profile ## Input - The job post or scope description - Platform (Upwork hourly vs. fixed, Fiverr package tiers, Freelancer.com bid) - The user's experience level and existing rate, if any (don't assume — ask, since a fair rate depends heavily on where they already are) - Their target market if known (e.g. US/EU clients vs. price-sensitive markets — this materially changes what's a reasonable ask) ## Steps 1. **Break the scope into real units of work.** Vague scopes ("build me a website") hide the actual hours; ask what's really included if unclear (pages, revisions, content written or supplied, ongoing support). 2. **Estimate effort honestly**, not optimistically — first-time scope estimates from freelancers are almost always too low; flag this explicitly rather than reinforcing an underestimate. 3. **Reason in a range, not a single number.** Give a floor (what covers the time at a fair rate) and a target (what a confident, in-demand freelanc