Skip to content
Back to skills

Service Pricing

ASecurity

Use when pricing or quoting a service — coaching, consulting, freelance or agency work, client projects, retainers — e.g. "should I charge hourly or a flat fee", "how do I quote this project", "$3,400 or $3,417.50", "the client keeps haggling", "should I show my costs", "how do I price packages and add-ons".

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentsrustgogit

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 19, 2026

npx -y skills add checkout-page/ecommerce-skills --skill service-pricing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Service Pricing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Service Pricing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/checkout-page-service-pricing/badge)](https://www.skillsdirectory.com/skills/checkout-page-service-pricing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: service-pricing
description: Use when pricing or quoting a service — coaching, consulting, freelance or agency work, client projects, retainers — e.g. "should I charge hourly or a flat fee", "how do I quote this project", "$3,400 or $3,417.50", "the client keeps haggling", "should I show my costs", "how do I price packages and add-ons".
---

# Service pricing

Set the number, the structure, and the presentation of a service price so it signals expertise and holds up in negotiation. Services are judged on quality before price, buyers overestimate how much time they'll use, and the digits of a quote change how the other side counters.

## When to use

- Choosing hourly vs flat/project fee vs retainer
- Writing a quote or proposal, especially one that will be negotiated
- Pricing packages, add-ons, and extras
- Deciding what to show on the pricing or about page (costs, team size, guarantees)

## When not to use

- Generic digit rules for products → `pricing`
- Wording a discount → `discounts`
- Finding the price level people will pay → `price-research`

## Inputs

Collect, or state your assumption:

- The service, typical scope, and expected hours or units
- Current hourly rate, if any; margin
- Who the buyer is: individual, business owner, or a professional buyer (procurement, purchasing manager)
- Whether the quote will be negotiated
- Whether the service is high-tech (software development, AI, engineering) or not
- How well-known the provider is

## Procedure

1. **Rounded by default.** Most services are bought on quality and trust, so the listed price should be rounded ($150/session, $2,000/month). Rounded prices feel right when the decision is about quality or feelings, and they make the choice easier. Just-below prices ($1,999) signal a low-price appeal; use them only for a promotion.
2. **Flat fee over hourly, priced above the hourly equivalent.** Quote a project or package fee that covers what most clients want ("logo, three concepts, unlimited revisions, final files") and charge more than the expected hourly total: a $6,000 fixed fee was preferred over $50/h for an expected 100 h ($5,000). Buyers overestimate their usage, dislike watching a meter run, and pay to cap the risk. Keep hourly only as a low-commitment entry for first-time clients.
3. **Precise numbers when the quote will be negotiated.** A precise opening quote ($3,450 rather than $3,500) anchors the counteroffer into smaller steps, so you get fewer but higher offers. With an **expert buyer** (procurement, purchasing managers) stop at moderate precision — $3,450, not $3,417.50 — or justify a highly precise figure with a cost breakdown; high precision without justification backfires with experts.
4. **Show your costs.** Show a per-project cost breakdown (your time, subcontractors, software, tools, overhead). The measured result — sales 22% higher, holding to a 55% margin — is from a physical product (a $115 wallet with a cost infographic); applying it to service proposals is a transfer, not a tested result. Group categories once there are more than ~8. This is the opposite of hiding the hourly math: show the structure, not the meter.
5. **Simple add-ons and components.** Rounded add-on prices with the same ending as the base ($2,000 project, $300 extra concept, not $287.50), one price per unit ($100 per extra page), no separate admin or service fee. Complex component pricing makes people assume you're the expensive option.
6. **Say you're small — unless the service is high-tech.** For low-tech services (design, coaching, writing, consulting) a small team reads as more motivated and higher quality; say so. For high-tech services, counter the size penalty by showing what you invest in R&D and tooling. A large low-tech firm should show employee passion instead.
7. **Extraordinary guarantee if you're unknown.** A guarantee far beyond the category norm (a year of free fixes, a full refund if the concept isn't approved) signals quality to buyers who know the service but not you.
8. **Discounts.** If you must discount, stay at or under 40% and apply the amount-vs-percent rule (project price ≥ 100 → amount off). Details in `discounts`.

## Output

| Item | Value |
|---|---|
| Structure | Flat project fee (hourly retained only as a trial option) |
| Quote | $3,450 — moderately precise, buyer is procurement |
| Included scope | 3 concepts, unlimited revisions, final files, usage rights |
| Add-ons | $300 per extra concept; $500 brand guide (rounded, same ending) |
| Shown on the proposal | Cost breakdown in ≤ 8 lines; "we're a two-person studio"; guarantee |
| Rejected | $3,400 (gives away nothing in negotiation), $3,399 (low-price signal), $3,417.50 (too precise for an expert buyer), hourly (meter effect, invites hour-cutting) |
| Why | one line per choice, citing the rule |

## Common mistakes

- Quoting a round $3,400 to a negotiating buyer "because it sounds confident" — a precise figure gets smaller, higher counteroffers.
- Using maximum precision ($3,417.50) with a procurement manager — moderate precision, or justify it with the breakdown.
- Hiding costs to protect margin — a cost breakdown raised sales, and the effect holds to 55% margin.
- Pricing the flat fee to match the hourly total — clients pay a premium to cap their spend.
- Bolting on a service fee or odd per-unit rates — simple components raise willingness to pay.
- Hiding that you're a small studio — for low-tech services it raises perceived quality.

## Quick reference

| Situation | Do |
|---|---|
| Listed price | Rounded |
| Hourly vs flat | Flat fee, above the hourly equivalent; hourly only as an entry option |
| Quote will be negotiated | Precise number |
| Expert buyer | Moderate precision, or justify with a breakdown |
| Trust page / proposal | Cost breakdown, ≤ 8 categories |
| Add-ons | Rounded, same ending, no service fee |
| Low-tech service | Say you're small |
| High-tech service | Show R&D investment |
| Unknown provider | Extraordinary guarantee |
| Discount | ≤ 40%, amount off when price ≥ 100 |

Evidence and effect sizes: see [reference.md](reference.md).

Files in this skill

  • SKILL.md6 KB
  • reference.md7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.