Pricing Your Work When Money Talk Is Hard

The work itself rarely feels hard to defend. Explaining why it costs what it costs, that's the part that makes people go quiet, hedge, or blurt out a lower number than they meant to the moment a client's face changes. Money talk feels personal in a way the actual deliverable never does.

Why does the generic pricing advice fail?

"Charge what you're worth" is the most common pricing advice given and the least actionable. It doesn't say how to calculate worth, how to communicate it, or what to do when a client simply says no to the number. "Just be confident" has the same problem: confidence isn't a pricing strategy, it's a tone, and a confidently delivered number with no value case behind it collapses the moment a client asks a real question about it.

Generic AI prompting repeats the same gap. Ask an assistant "how much should I charge for this project" and, lacking any knowledge of your market, your skill level, or the client's actual stakes, it will either refuse to answer or produce a generic range pulled from nowhere in particular. The number isn't the hard part. The case for the number is, and that case has to be built from specifics only you have.

The discomfort compounds because most people only think about pricing in the moment a client asks, which is the worst possible time to build a rationale from scratch. A value case built under pressure, in real time, on a call, tends to come out thin and apologetic even when the underlying work genuinely justifies the fee. The fix isn't a better script for that moment; it's doing the value-case work before the moment arrives.

Which documented approaches actually work here?

Blair Enns: price the value delivered, not the hours spent

Enns's Pricing Creativity: A Guide to Profit Beyond the Billable Hour (2017) argues that time-based pricing structurally caps what expertise can earn, since it ties the fee to effort rather than outcome. Value-based pricing instead starts from what the result is worth to the client and works backward to a number.

Applied: Before quoting, ask what this project is actually worth if it succeeds, a product launch that lands, a hire that doesn't leave in six months, a positioning shift that lets the client raise their own prices. Price relative to that outcome, not to the hours the work will take you. A project that takes ten hours but prevents a six-figure mistake is not a ten-hour-rate project.

The hardest part of applying this isn't the math, it's resisting the pull to mention hours at all once the outcome value is on the table. Enns's own observation is that most people who understand value-based pricing in theory still default to justifying a number by effort the moment a client pushes back, because effort feels like safer, more defensible ground than an estimate of value.

Alan Weiss: separate fee conversations from scope conversations entirely

Weiss's Value-Based Fees (2002) makes a structural case that fee should be proposed once, early, and tied to outcomes agreed with the client before any scope-of-hours discussion happens. Mixing the two, discussing hours and discussing fee in the same breath, drags the conversation back toward billable-hour logic even when the stated pricing model is value-based.

Applied: In a proposal conversation, get explicit agreement on what success looks like and what it's worth to the client first. Only once that's settled do you introduce a fee, framed against the agreed outcome rather than against a breakdown of hours or tasks. If a client asks "how many hours is that," the honest answer is that the question is a sign the value conversation hasn't fully landed yet.

Weiss is explicit that the sequence matters more than the words used at each step. Agreeing on outcomes and then stating a fee, in that order, produces a fundamentally different conversation than stating a fee and then being asked to justify it against hours after the fact. Once the hours question is on the table, the conversation has already shifted onto the buyer's preferred ground.

Alex Hormozi: make the offer so clearly valuable the price becomes secondary

Hormozi's offer-creation framework, documented across his published work on value maximization, argues that the price objection usually isn't really about the number, it's about an unclear or underbuilt offer. Stack enough concrete value, guarantees, scope clarity, named outcomes, against a price and the comparison shifts in your favor.

Applied: Before a pricing conversation, write out everything included in the offer as specifically as possible: what's delivered, by when, with what guarantee if it falls short. A vague offer at a lower price often loses to a precisely scoped offer at a higher one, because the buyer can actually see what they're getting in the second case.

This is a useful check even for people who already believe in value-based pricing, because an unclear offer undermines the value case regardless of how well the value itself was argued. A client who can't picture exactly what they're buying will anchor on price because price is the only concrete number in front of them.

How do the three stack up against each other?

What's worth running today?

Why it works: anchoring the price conversation to the outcome's value, not your time, is the entire mechanism behind value-based pricing, and most people never actually write the outcome's value down before quoting.

Why it works: a skeptical-buyer review surfaces the gaps in your offer before a real client finds them mid-negotiation, when it's much harder to add value without looking reactive.

Why it works: having a ready redirect prevents the conversation from sliding back into billable-hour logic in the moment, which is when it's hardest to resist doing so.

What's the honest limit of all three?

These frameworks build a stronger case for a given number. None of them tells you what that number actually is for your specific market, skill level, and this specific client's budget. That judgment, informed by real comparable deals and real knowledge of what this buyer can pay, still has to come from you. A perfectly argued value case attached to a number that's simply outside what this client can pay will still fail, and no framework can see that ceiling from the outside.

All three frameworks live in the Consultant & Advisor category alongside David Maister and David C. Baker, the fuller bench for pricing and positioning work. For running the actual math against your target margin before you quote, Pricing Decision is a $99 tool built for exactly that calculation.

All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.