The first time I had to quote a real project, I stared at a blank email for the better part of an hour. I knew what the work involved. I knew roughly how long it would take. What I had no idea about was what number to put in the email — and there was nowhere obvious to look, because competitors don't publish their rates, the ranges online are enormous and contextless, and asking someone directly felt like admitting I didn't know what I was doing. So I picked a number that felt safe, which meant low, sent it before I could second-guess it, and got an immediate yes that felt like relief and was actually a signal I'd underpriced.
Pricing is one of the genuinely hard parts of running a service business, and it's made harder by how little practical guidance exists. Most advice is either an abstract principle ("charge what you're worth") or a demand for information you don't have ("know your value to the client"), neither of which helps when there's an empty quote field in front of you. What's missing is the practical middle: how to actually construct a number, what the main pricing models are and when each fits, how to handle the awkwardness of saying the number out loud, and what to do when the client says it's too much.
Two things worth saying up front. First, there's no single correct price for your work — pricing is a judgment made with incomplete information, and anyone claiming there's a formula that produces the right answer is selling something. What you can do is build a defensible number from a sensible process, which is achievable and enormously better than guessing. Second, the most common error by a wide margin is charging too little, and it's an error that compounds: low prices anchor future pricing, attract worse clients, and force the volume that prevents you doing good work. If you're uncertain in either direction, the odds strongly favour the higher number.
This article is the practical companion to that: how to arrive at a price you can stand behind, which model to use, and how to present it. Here's how to price your services.
Key Takeaways
- There's no formula, but there is a process. You can't calculate the "correct" price, but you can build a defensible one from your costs, your time, the market, and the value delivered.
- Know your floor before you quote anything. Work out what you actually need to earn per hour or per project to be sustainable — that's the number you never go below.
- Project pricing usually beats hourly. Hourly punishes you for getting faster and better, caps your income, and makes clients watch the clock instead of the outcome.
- Price the value, not just the hours. What the work is worth to the client often has little to do with how long it takes you — expertise means doing it faster, not earning less.
- State the number plainly. Hedging, apologising, or burying the price signals you don't believe in it, which invites the negotiation you were trying to avoid.
Start With Your Floor
Before thinking about what a client might pay, work out what you actually need — because that number is your floor, and knowing it turns pricing from pure anxiety into a decision with at least one solid edge. Start with what you need to earn over a year to run the business and live: your costs, your taxes, your equipment and software, and your actual income requirement. Then divide by the amount of work you can realistically do.
That last part is where most people go badly wrong. If you assume you'll bill forty hours a week, fifty weeks a year, your floor comes out far too low, because nobody bills anywhere near all their working hours. A large share of your time goes to things nobody pays for directly: finding clients, writing proposals, admin, invoicing, email, learning, and the gaps between projects. Realistic billable time is a fraction of working time, and if your rate assumes otherwise, you've built underpricing into your foundation. Be honest about how many hours you'll actually charge for, and divide by that smaller number.
The result is your floor: the rate below which the work isn't sustainable, no matter how much you want the project. This doesn't tell you what to charge — it tells you what not to go under, which is genuinely useful when a client pushes back or when a project feels exciting enough to talk yourself into a bad number. Anything below the floor isn't a discount; it's paying for the privilege of working, and knowing exactly where that line sits makes it much easier to hold.
Choose the Right Pricing Model
There are three main ways to price service work, and choosing well matters more than most people realise. Hourly charges for time spent. It's simple, easy to explain, and it's what most people default to — and it has a serious structural flaw: it punishes you for being good. As you get faster and more skilled, the same work takes less time, so you earn less for the same result, which means your growing expertise actively reduces your income. It also caps you at the number of hours you can physically work, and it focuses the client's attention on how long things take rather than what they get, which invites scrutiny of your speed instead of your outcomes.
Project pricing charges a fixed amount for a defined piece of work, and for most service businesses it's the better default. It decouples your income from your hours, so getting faster increases your effective rate instead of shrinking your invoice. It gives the client certainty about cost, which they generally prefer. And it moves the conversation to what's being delivered rather than how long it takes, which is where you want it. The trade-off is that you carry the risk of the work taking longer than expected, which makes accurate scoping essential — an unclear project price is how you end up doing three times the work for one price. [BACKLINK PLACEHOLDER → suggestion: internal link to article #47, the truth about agency retainers / clear scope is what makes fixed pricing work]
Retainers charge a recurring fee for ongoing work or availability. They're valuable for predictable income and deeper client relationships, and they work well when the ongoing need is genuine and the scope is clearly defined. They go wrong when the scope is vague, because "available for whatever comes up" quietly expands into unlimited work for a fixed fee. For most people the sensible progression is to price projects by the project, and move to retainers where there's a real, continuing, well-defined need — not as a way to lock in revenue by leaving the boundaries fuzzy.
Price the Value, Not Just the Time
Your floor tells you the minimum; the value tells you where the ceiling might be. The important insight is that what a piece of work is worth to a client often has very little to do with how long it takes you. A short, expert intervention that solves an expensive problem is worth a great deal regardless of the hours involved, and a long, laborious task that changes little is worth less regardless of the effort. Time is a cost input, not a measure of value, and pricing purely on time means systematically undercharging for exactly the work where your expertise is most valuable.
So when you're quoting, think about what the outcome is worth in the client's terms — what problem it solves, what it enables, what it saves them, what happens if they don't do it. You usually can't calculate this precisely, and you don't need to; you need enough of a sense of the stakes to know whether this is a small job or a significant one for them, and to price accordingly. The same work can legitimately carry different prices for different clients, because it's genuinely worth different amounts in different contexts.
This is also the answer to the guilt that comes with charging well for work that felt easy. The years behind a fast, confident solution are part of what the client is buying, and expertise expressed as speed shouldn't be penalised with a lower price — that's precisely the trap hourly billing creates. What clients are actually paying for is the outcome and the judgment that produced it, not the duration. [BACKLINK PLACEHOLDER → suggestion: internal link to article #29, what clients are actually buying from agencies / paying for judgment and outcomes, not hours]
How to Quote and What to Include
A quote is more than a number — it's the number plus enough context to make it make sense. Present the price alongside what's included: the specific deliverables, the timeline, what's covered and what isn't, and, where useful, a brief connection back to the outcome the client is after. A bare figure invites the question "why that much?", while a figure attached to a clear description of what they're getting answers it before it's asked.
Be specific about scope, because that's where fixed prices survive or collapse. Say what's included and, where relevant, what isn't — how many rounds of revisions, what happens if requirements change, what falls outside this price. This feels awkward when you're trying to win the work, and it's exactly what prevents the scope creep that turns a well-priced project into an underpaid one. Clarity here also signals professionalism: a provider who's precise about what they're delivering reads as someone who's done this before.
Then state the number plainly. Don't bury it at the end of a long document, don't hedge it with apologies, don't pre-emptively offer discounts nobody asked for. Hedging language — "this might seem like a lot, but..." — tells the client you're not confident in your own price, which is an invitation to negotiate. Present it as a straightforward fact, the way you'd state any other detail of the work. Confidence in the number is itself part of the argument for it, and the quote as a whole is part of the argument you're making that you understand their problem and can solve it. [BACKLINK PLACEHOLDER → suggestion: internal link to article #81, how to write a proposal that wins the client / stating price clearly within a clear argument]
🎬 Embed a short walkthrough of building a quote — floor, model, value, scope — and presenting the number plainly without hedging.
Handling "That's Too Expensive"
Price pushback is normal and doesn't mean your price was wrong. The most useful thing to understand is that "too expensive" is usually a statement about perceived value rather than about affordability — it typically means "I'm not sure this is worth that to me," which is a value problem, not a price problem. So the first response isn't to drop the number; it's to make the value clearer, or to find out what's actually behind the objection.
If the value genuinely isn't there for that client, you have two honest options: reduce the scope so the price matches what they can justify, or let the project go. What you should avoid is simply cutting the price while keeping the same scope, because that teaches the client your prices are negotiable fiction, sets a low anchor for everything that follows, and means doing the same work for less — which is the underpricing trap arriving through the back door. Reducing scope alongside price is honest; discounting alone is a concession that costs you more than the project is worth. [BACKLINK PLACEHOLDER → suggestion: internal link to article #59, why you're probably undercharging / what discounting actually costs you]
It also helps to remember that some price objections are simply clients who aren't a fit, and that's fine. If everyone says yes immediately, your prices are almost certainly too low — a healthy price gets occasional pushback, because it sits at a level where not everyone can justify it. Losing some projects on price is a normal feature of pricing properly, not evidence that you've made a mistake.
