The pain

You're writing the proposal. The work is real. The value is real. You know — somewhere underneath — what it should cost.

Then a small, quiet voice says "$3,500 might scare them off."

You drop it to $2,500. The client accepts in four minutes. The speed of the yes lands in your chest like a small, second pain — the pain of having known.

Solo operators do this every month. Over a year, tens of thousands of dollars get left on the table. Paid for by your weekends. Filed under "I just want this one to close."

Who has it

Service freelancers. Consultants. Coaches. Fractional execs.

Particularly anyone more than eighteen months in who has quietly stopped raising prices — not because they ran the numbers and concluded no, but because they ran the feeling and concluded not yet.

The fix

A pricing partner trained on your delivery economics and your last ten deals. You run every proposal past it before sending.

It is the only person in your business who has read every contract you've ever signed and is incapable of being conflict-averse on your behalf.

Setup (30 min, once)

  • Build a Claude Project called "Pricing partner." Drop in:
    • - Your delivery cost per engagement type (honest hours × your minimum hourly rate) - Last ten deals: scope, price, hours actually spent, whether you'd take it again - Market range for your work (three competitors' published prices, if any exist) - Your stated annual revenue goal
  • Write the prompt:
    • > You are my pricing partner. I'll describe a proposal I'm about to send. Tell me: (1) Is this priced inside my market band? (2) Given the scope, what's the implied hourly rate if I'm honest about hours? Compare to my minimum hourly rate. (3) Compared to my past ten deals, what's the closest analogue and what did I learn? (4) Is this a price I'd be proud of, or one I'm setting from anxiety? End with a recommended number, not a range.

    The "not a range" is doing a lot of work in that prompt. Ranges let you keep flinching. A number forces a decision.

    Running it (5 min, before any proposal)

    Type the proposal in plain English: scope, deliverables, timeline, what you're about to charge. The partner replies. You either send the original — or you revise.

    What it looks like running

    You propose: "Help a SaaS founder set up a customer chatbot — 2 weeks, 3 calls, build + deploy + handoff. Charging $1,500."

    Partner replies:

    (1) Market band: custom RAG bots for solo SaaS run $1.5k–$4k. You're at the floor.
    >
    (2) Honest hours: setup ~6h, build ~10h, deployment + handoff ~6h, support buffer ~4h = 26h. At $1,500, that's $58/hr. Your stated minimum is $150/hr.
    >
    (3) Closest past analogue: the Q4 chatbot build for [client]. You charged $1,200, ended up at 31 hours, said you'd never do that price again.
    >
    (4) This is an anxiety price. The buyer is a funded SaaS, not a starving freelancer.
    >
    Recommended: $3,200. If they push back, $2,800 is the floor — not lower.

    You read that. Take a breath. Send at $3,200. They accept in two days with one small scope question.

    Why this works

    This is Partner-tier — AI as Thinking Partner — because the trust ask is the heaviest in the whole stack: "Tell me when I'm wrong about something I have a strong feeling about."

    The leverage is the honest-hours math plus your past deal history. Most pricing advice is theoretical. This isn't. It's anchored in what you actually do and how long it actually takes.

    The compounding effect isn't a sudden price hike. It's the unconscious discount you stop giving. You don't tell existing clients anything. You stop the next three quotes from coming in 30% under what the work actually takes.

    Maybe that's the real return. Not the money — though the money is real. The thing you get back is the small, daily, unmetered cost of pretending you're worth less than you are.