You have the call. The client likes you, the scope is clear, and there is a genuine silence on the other end of the line. Then they ask the question that breaks more freelance negotiations than price objections do: “So, what would you charge for this?”
If you have ever answered that question with a number that felt like a guess — and then spent the next six weeks quietly resenting yourself for it — this guide is for you. Pricing a project when you genuinely have no idea what it is worth is not a talent you are born with. It is a procedure. This is the procedure.
By the end you will have a repeatable way to build a price from scratch, in about ninety minutes, without needing to know the “market rate” in advance. It works for a design sprint, a website rebuild, an SEO engagement, a bookkeeping close, a podcast edit — anything where the deliverable is a mix of judgment and hours.
Why “What’s the market rate?” is the wrong first question
The most common pricing mistake is researching competitors before you have defined the work. It feels responsible. It is actually backwards.
Rates quoted by other people tell you what their scope, their overhead, their skill mix, and their risk appetite are worth. None of those are yours. A freelancer quoting $1,800 for a website might be delivering a template install with three weeks of time sitting idle behind it. Another quoting $9,000 might be building something custom with a two-round revision cap and a legal review of the terms. The number is meaningless without the shape of the work attached.
There is also a survivorship problem. The rates you can see publicly are the ones confident people publish. The freelancer who underpriced, burned out, and left the market is not posting a rate card. You are sampling from a biased set and then letting it set your ceiling.
Start with the work. The number falls out of the work. Market data becomes a sanity check at the end, not an input at the beginning.
Step 1: Write the deliverable inventory before you write any number
Before a single figure enters the conversation, list everything the client is actually getting. Not the category of work — the objects.
For a website project that inventory looks like: a sitemap, eight page designs, a responsive build, content migration of 40 pages, a contact form, analytics installation, one training call, and a written handoff document. That is nine distinct deliverables. Vague scope says “a website.” A priceable scope says nine things.
Then add the invisible deliverables — the ones clients never think to ask for but which consume your week:
- Discovery calls and async questions. Count them. A client who sends twelve Slack messages a day is a different project from one who sends a weekly email.
- Revision cycles. Decide the number now: two rounds? Three? Unlimited is not a deliverable, it is an open-ended liability.
- Stakeholder count. One decision-maker is one set of opinions. Five stakeholders means five vetoes and triangulation. Charge for the meetings.
- Access and dependency risk. If you are waiting on their copywriter, their brand assets, or their legal team, your calendar is being held hostage by someone who is not paying you for the waiting.
Write this list down and send it to the client as part of the proposal. Half the value of the inventory is that it reveals scope disputes before they become invoices.
Step 2: Estimate hours in ranges, then take the pessimistic end
You do not need precise estimates. You need defensible estimates. There is a difference.
For each deliverable, write a range: best case and realistic case. Not worst case — you are not building a scarecrow. Then multiply the guess by a small honesty factor. The classic advice is to double your estimate, and the classic advice is only half right: doubling compensates for optimism bias, but it does not compensate for interruption, rework, or the unbilled hour spent re-reading the brief at 11pm.
A better rule for freelancers with fewer than three years of comparable projects: take your midpoint estimate and add 35 percent. If this is your first project of this exact type, add 60 percent. If you have done this twenty times, add 15 percent.
You are not padding. You are correcting for a known, measurable error that almost every independent worker makes in the same direction. Better to come in slightly over and be remembered as reliable than slightly under and be remembered as slow.
One more thing about estimates: they are internal. The client sees deliverables and price. If you show a client an hour estimate, you have just invited a negotiation about how long your work should take, which is not a negotiation you want to be in.
Step 3: Work backwards to find your floor from your own finances
Here is the step almost everyone skips, and it is the reason people undercharge even when they “know” their rate.
Start with the number you need to take home per year. Add self-employment tax, health insurance, retirement contribution, and a buffer for the months the pipeline goes dry. Add business costs: software subscriptions, hardware amortization, accounting, a portion of your rent or electricity if you work from home. Divide by the number of billable hours you can realistically sell.
Most freelancers can bill roughly 60 percent of their working hours. The rest goes to sales, admin, learning, and client communication. If you assume you can bill 40 hours a week at your target rate, you will systematically undercharge, because that math only works if nothing else exists in your life.
Run the numbers once and write the result down as a floor. Your floor is not a negotiating position. It is the line below which you earn less than unemployment plus freedom, which means the project is a slow way to lose money.
Now compare the floor against Step 2. If your estimated hours times your floor rate already exceeds what you would feel comfortable quoting, the project is too big for your current pricing, and the right answer is scope reduction, not discounting.
Step 4: Decide whether you are pricing hours or outcomes
The two are not interchangeable, and choosing the wrong one for the situation costs you money in both directions.
Price by hours (or day rate) when the work is uncertain, the client is exploratory, or the scope is likely to change. You are selling capacity. The client is buying access to your time, and scope changes are expected and billable.
Price by outcome (fixed fee) when the deliverables are countable, the client is decisive, and you have done this exact thing before. Fixed fee protects the client from surprise and protects you from a low hourly rate on the days you happen to be fast.
A third option worth knowing: value-based pricing, where you price against the money the work makes or saves the client. It is powerful and frequently misapplied. It only works if you can credibly link your work to a financial result and the client already believes that link. Do not attempt it on your second project with a client. Attempt it when you have a case study that says “this changed the number.”
For most freelancers pricing an unknown project for the first time, fixed fee with a narrow, written scope is the safest structure. You know the client’s number up front, and you control the risk through scope discipline rather than through hope.
Step 5: Price the risk separately instead of hiding it in the rate
Every project has risk, and the usual response is to inflate the estimate by some unspoken percentage that the client never sees and you can never defend. That is bad for everyone. Say the risk out loud.
Build a short risk table before quoting. For each risk, write the probability, the cost, and who bears it.
- Scope ambiguity. If the brief is vague, the risk is yours. Price it or fix the brief.
- Payment terms. Net 60 with a client who has a history of late payments is a financing cost. Either raise the price or take a deposit.
- Ghost assets. No logo files, no brand guide, no access to the CMS. Add a line item for production work you did not want to do.
- Third-party dependencies. Platform changes, API limits, a plugin that breaks on update. State who pays when the thing you do not control breaks.
Then include the risk terms in the proposal. A client who understands “two revision rounds, then $X per additional round” is a client who self-manages their feedback. A client who reads “unlimited revisions” is a client who will test that word.
Step 6: Build the price, then do an integrity check
Now you have numbers. Turn them into a single figure or a three-tier ladder, and run four questions against it.
Is it above my floor? If not, do not proceed. No amount of interesting work compensates for a project that loses money.
Does the number match my recorded effort? Multiply estimated hours by your effective rate. If the effective rate is dramatically below what you earn on your best project, be honest about why. Sometimes the answer is fine — strategic client, portfolio piece, referral source. Write the reason down so you do not repeat the discount without a reason.
Would I still do this at 80 percent of the price and feel okay? If the answer is no, the padding is not padding, it is a signal that you do not want the project. Push the price up until you would feel fine. This is how professionals repel bad clients without ever saying no.
Can I explain the number in two sentences without apologizing? Price is stated flatly, tied to deliverables, and then you stop talking. “It is $6,400: eight pages, the migration, and two revision rounds, delivered in six weeks.” That is a complete sentence. There is no need to justify it further.
Step 7: Write the quote so the scope is the story
The proposal is not a receipt. It is the document that determines whether the project goes well for both of you.
Put deliverables first, in plain language, in countable form. Put price second. Put terms third: payment schedule, revision limits, what triggers a change order, response times, and what happens if the project pauses.
Then state what is explicitly excluded. Exclusions are not hostile. They are the boundary that makes a fixed price possible. Clients who respect you read them and are relieved; clients who planned to expand the scope into your fee read them and negotiate, which is exactly the conversation you want to have now rather than in month two.
If you have never written one, a scope of work is the right companion document — it is where the deliverables and exclusions live so the price does not have to carry the ambiguity on its own.
Step 8: Handle the counter-offer without breaking the price
Expect a counter. Most clients will test the number, and testing is not an insult — it is what buyers do when they have a budget they are trying to fit.
The response that preserves both the price and the relationship is a three-part move:
- Do not discount the same scope. Say the number is tied to the deliverables. A lower number means fewer deliverables.
- Offer a smaller scope at a lower price. Remove the migration. Remove one of the design rounds. Remove the training call. Now the lower number is honest and your margin is intact.
- Offer a payment plan, not a price cut. If cash flow is the real objection, split the fee into three installments. You lose nothing and they get what they need.
If the client still wants the whole thing for less, the answer is no, and saying no here is what makes every future yes worth something. A project sold below your floor is not a project you won. It is a scheduling problem you bought for cash.
Step 9: Review your estimate after delivery and adjust the model
Most freelancers never learn their real error rate because they never measure it. You will, once, and it changes everything.
At project close, record four numbers: estimated hours, actual hours, final invoice, and number of change orders. That is it. Four numbers per project, in a spreadsheet.
After five projects you will know your personal estimation bias. Almost everybody runs over — commonly by 20 to 40 percent on projects that are “done” and by 60 percent or more on projects that go sideways. Once you know your own number, you can set your pricing factor from evidence instead of from a rule of thumb someone wrote on the internet.
This is the difference between a freelancer who prices by feel for a decade and one whose margin improves every six months. The data is not hard to collect. It just requires deciding, once, that you will collect it.
The ninety-minute procedure, end to end
Here is the whole thing compressed into one sequence you can run before your next quote.
- Minutes 0–15: Inventory. List every deliverable, visible and invisible. Count them.
- Minutes 15–35: Estimate. Range each deliverable, take the midpoint, apply your correction factor (35 percent baseline, 60 percent for a first of type).
- Minutes 35–50: Floor. Run your annual number through the billable-hours calculation once. Note your floor rate.
- Minutes 50–65: Structure. Choose hours or fixed fee. Write the revision limit and the payment schedule.
- Minutes 65–75: Risk. Name the three biggest risks and who bears each one.
- Minutes 75–85: Integrity check. Above floor? Matches effort? Fine at 80 percent? Explainable in two sentences?
- Minutes 85–90: Write. Deliverables, price, terms, exclusions. Send it flat, without apology.
Ninety minutes is not a lot of time for the highest-leverage decision in the project. Most freelancers spend more time choosing a font than choosing a price, and then spend six weeks living inside the consequences.
How to price when the client will not tell you their budget
Clients often refuse to share a budget, and the refusal is usually strategic rather than malicious. They are afraid that naming a number first anchors them high, or that telling you they have $20,000 will make a $6,000 project cost $20,000. Both fears are reasonable.
You do not need their budget to price correctly. But you do need a range, or you risk spending an hour preparing a proposal for a project you cannot afford to take.
The move that works is a scoping question rather than a pricing question. Instead of “What is your budget?” ask:
“To make sure I scope this to fit, are we talking about a small engagement, a mid-size build, or a flagship project?”
That gives you a tier, not a number, and a tier is enough to decide whether to invest in the proposal. It also reads as helpful rather than as an attempt to extract a ceiling you can price up to.
If the client still refuses after a direct question, that is information. Either they genuinely do not know, which means the scope will move, or they are planning to shop the number against competitors. Both cases call for a smaller first engagement, not a bigger proposal. Start with a paid discovery phase of a few days. It is easier to sell, it de-risks your estimate, and it converts a speculative bid into an informed quote.
When to raise your price, and what to say
Most freelancers raise prices reactively: they get busy, they feel resentful, they raise the price and lose the client. There is a less painful version.
Raise prices on a schedule, not on a feeling. Twice a year is enough. Announce the change to existing clients with notice and let them lock in the old rate for one more project. Most will accept; the ones who leave were the ones buying the discount rather than the work.
The wording matters less than the consistency. “My rates are going up in January. I wanted to give you the first chance to book at the current rate.” That sentence does three things at once: it informs, it rewards loyalty, and it creates mild urgency without pressure.
What to avoid is apologizing for the increase or explaining it away with your own costs. Your rent is not the client’s problem, and leading with it invites a negotiation about your expenses rather than about the value of the work.
Keeping the price you quoted
The final discipline is the hardest: once the number is sent, do not reopen it in your own head.
Freelancers lose enormous amounts of energy replaying quotes. Was it too high? Should I have said $5,800 instead? Will they think I am greedy? That loop has no useful output. The number was built from an inventory, an estimate, a floor, and a set of stated terms. It is defensible. Replaying it does not make it more correct, it only makes you flinch during the follow-up call.
If the client says yes, the answer is a short confirmation and a start date. If they say nothing, the answer is one polite follow-up after a week, then silence. If they say no, the answer is curiosity rather than a discount: what would have made this work? Sometimes the answer is scope, sometimes it is timing, and sometimes it is simply that you were not the right fit. All three are useful, and none of them require you to have priced differently.
The freelancers who hold their prices well are not the ones who are confident by temperament. They are the ones who did the work before the call, once, in writing. That is the entire difference.
Three common traps and how to step out of them
The anchoring trap. You quote $5,000, the client says another freelancer quoted $2,800, and suddenly your number feels wrong. It is not wrong, it is different — different scope, different person, different risk. Ask what the other quote included. Usually the answer reveals a smaller project, and you can say so without aggression.
The deposit-free trap. Fixed fee plus no deposit plus net 45 is not a project, it is an interest-free loan you are making to a business you have never audited. Standard practice is 30 to 50 percent up front. If a client refuses any deposit, that is information about how they will treat the final invoice, not information about your price.
The “I’ll know the number when I see the work” trap. Clients who want to finalize price after delivery are asking you to work without a contract. Convert it into a fixed fee with a written revision cap, or convert it into an hourly engagement with a stated cap. Never work open-endedly on the promise of a good number later.
What this looks like in practice
Consider a hypothetical: a small e-commerce brand asks for “a full SEO overhaul.” Vague scope, no inventory, no number.
Run the procedure. Inventory yields: technical audit of 60 pages, keyword mapping for 18 product categories, rewrite of 12 category descriptions, schema markup on product templates, a redirect map, and a 90-day reporting dashboard. Six deliverables plus an unbilled invisible one: weekly reporting calls.
Estimation: audit 12h, mapping 10h, rewrites 14h, schema 6h, redirects 5h, dashboard 8h, calls 8h — 63 hours midpoint. Apply 35 percent: 85 hours. If your floor rate is $85 an hour, the cost-based number is roughly $7,200. But you have done this exact engagement three times and you know your process is tighter than a fresh estimate suggests, so you price the fixed fee at $6,900 with a two-round revision cap and a stated exclusions list.
The client counters at $5,000. You offer to remove the 12 category rewrites and the weekly calls: $5,400. They accept the smaller scope. You lost no margin, and the project starts with a written definition of what it is.
None of that required knowing what anyone else charges. It required an inventory, an estimate, a floor, and a willingness to state the number once and stop talking.
The uncomfortable part
The real blocker for most independent workers is not arithmetic. It is that saying a large number out loud feels like overreaching, and the instinct is to soften it, discount it preemptively, or explain it apologies-first: “I was thinking maybe around $6,400 or so, but I am flexible.”
That sentence costs money. It signals that the number was invented, and invented numbers are negotiable by definition.
The fix is rehearsal. Say the sentence out loud — to a wall, to a recording, to someone who will not be polite about it — until you can say it flatly. Not aggressively. Just flatly. “It is $6,400. That covers eight pages, the migration, and two rounds of revisions.” Then be quiet.
You are not asking for permission to be paid well. You are telling a client what your work costs, the way a contractor tells a homeowner what a roof costs. The silence after the number is not a rejection; it is usually the client doing arithmetic.
Price your work as though it is a decision you have already made. Because after ninety minutes with an inventory, an estimate, a floor, and an integrity check, it is.
If you are still tightening the paperwork on the client side, the companion pieces are how to write a scope of work that stops scope creep and how to follow up on a proposal without sounding desperate.
