A client sends you a short message — "I need a website for my bakery, what would you charge?" — and suddenly you're doing mental arithmetic you have no basis for. Too high and you assume they'll vanish. Too low and you'll spend six weeks resenting the job. So most beginners split the difference, pick a number that feels survivable, and hit send. That's guessing, and guessing is why so many first projects end up underpaid and overrun.
Here's the takeaway up front: a project quote is an estimate you build, not a number you feel. You get there by turning a vague brief into a specific list of tasks, pricing that list against a rate you've already worked out, adding a buffer for the things that always go wrong, and writing down exactly what the price does and doesn't include. Do that and the number stops being a confession — it becomes something you can explain, defend, and adjust on purpose.
The real mistake isn't the number — it's quoting before you understand the job
Beginners think pricing goes wrong at the moment they name a figure. It usually goes wrong earlier, when they agree to price something they haven't defined. "A website," "some social posts," "a logo" — these aren't jobs, they're categories. Two clients using the same words can want work that differs by a factor of five.
That's what makes a quote feel like a gamble. You're not bad at maths; you're being asked to price an unknown. Every technique below is the same move in different clothes: convert the unknown into something countable before you attach money to it. Once the work is a list of tasks with hours attached, the price is arithmetic — and if the client changes the list later, you have a clear, unemotional reason to change the price too.
Step 1: Interrogate the brief before you touch a calculator
You are allowed to ask questions before quoting. Clients expect it, and the ones who refuse to answer are telling you something useful. Aim for the smallest set of questions that make the work countable:
- What exactly is the deliverable, in units? How many pages, posts, minutes of video, revisions, product photos? "A website" becomes "five pages and a contact form."
- Who provides the raw material? Are they giving you the text, images, brand colours, and logins — or is that your job? Writing the copy for a five-page site can cost more than building it.
- What does 'done' look like? Delivered as files? Live on their server? Working on mobile? Handed over with a walkthrough?
- What's the deadline, and how firm is it? A rushed timeline is a legitimate reason for a higher price, because it displaces other work.
- Who signs off? One owner approving is fast. A committee of four is several extra rounds you should be paid for.
If a client can't answer these, you haven't lost anything — you've discovered the project isn't ready to be priced. It's fine to say so: "I can give you a firm number once we've settled the page count and who's writing the copy."
Step 2: Build the estimate from a task list, not a gut feeling
Now break the deliverable into the actual steps you'll perform. Not "build website" — but discovery call, sitemap, wireframe, build each page, mobile check, form setup, handover. Write down an honest hour estimate next to each one.
Two things make this estimate more accurate than instinct:
Count the invisible work. Beginners price the visible craft and forget everything around it — the kickoff call, the emails, the file wrangling, the round of feedback, the invoice, the handover instructions. On a small project this admin can rival the creative work itself. If it takes your time, it belongs on the list.
Add a buffer, and don't apologise for it. Something will take longer than planned: a client goes quiet for a week, an asset arrives in the wrong format, a "tiny tweak" reopens a finished page. A meaningful buffer isn't padding the bill — it's pricing reality instead of the perfect-run fantasy in your head.
Keep a simple log of estimated hours versus actual hours on your first few projects. After three or four jobs you'll know your personal underestimation habit, and that single number will improve your quoting more than any article can.
Step 3: Turn hours into a project price
Multiply your task-list hours (buffer included) by the rate you charge, then round to a clean figure and quote that total — not the hours, not the rate, not the breakdown of your internal maths.
This assumes you already have a rate you can defend, which is a separate calculation: living costs plus business costs plus tax, divided by the hours you can realistically bill, with a margin on top. Do that before you quote anything — our guide to setting your freelance rate as a beginner walks through the floor-and-target method. Hours are only an estimating tool here; the client should hear one project price.
Why quote the whole project rather than an hourly rate? Hourly pricing punishes you for getting faster, invites the client to audit your speed, and leaves them staring at an open meter. A fixed price gives them certainty about the total and gives you the upside of working efficiently. The trade-off is real, though: with a flat fee, every extra request eats your margin — which is exactly why the next step matters.
Step 4: Write down what the price includes — and what it doesn't
Scope creep isn't usually a client being sneaky. It's two people who never agreed on the boundary, drifting apart. Your quote is where you draw it. Even a short email quote should state:
- The deliverables, in the units you agreed — "five pages," "three concepts," "a 90-second edit."
- The number of revision rounds included. Unlimited revisions is the single most expensive phrase in freelancing. Two rounds is a decision; "we'll see" is a liability.
- What's explicitly excluded. Copywriting, stock photos, hosting fees, ongoing maintenance, printing — name the obvious adjacent things so nobody assumes they're free.
- What you need from them, and by when. Your timeline depends on their assets and feedback; say so.
- What happens if scope changes. One calm sentence does it: "Additional pages or revision rounds beyond those listed are quoted separately before any extra work starts."
That last line is the whole game. It means a mid-project request becomes a normal conversation about a small add-on quote, instead of a resentful decision about whether to work for free.
Step 5: Set payment terms that protect a first-time relationship
You don't know this client yet, and they don't know you. Structure the money so neither side is carrying all the risk.
Ask for a portion up front before you start — for a new client on a first project, that's normal practice, not a sign of distrust. On anything longer than a couple of weeks, split the rest into milestones tied to visible progress rather than one payment at the very end. Where you hand over files or push a site live, arrange final delivery and final payment closely together.
Put the boring details in writing too: the payment window, how they pay you, and whether anything is due if the project is cancelled halfway. Payment terms, contracts, and tax treatment vary a lot by country and client type, so treat this as general guidance and check what applies where you live — it isn't legal or financial advice.
Step 6: Deliver the number, then stop talking
Send the quote as a plain statement of price and scope. No apologies, no long justification, no pre-emptive discount. The silence after a number is uncomfortable and the beginner reflex is to fill it — that reflex has cost more freelancers more money than any competitor ever has.
If the client says the budget is lower, remember you have two dials, not one: the price, or the scope. Reducing scope is almost always the better move — "I can do that budget as three pages instead of five, with the contact form added later." It keeps your rate intact and hands the decision back to them. And if they accept instantly and enthusiastically, note it: not proof you got it wrong, but a signal worth testing with a higher number next time.
A pre-send checklist for your first quote
- [ ] The deliverable is written in countable units, not categories
- [ ] You know who supplies the copy, images, and access
- [ ] Every task, including admin and calls, is on your estimate list
- [ ] You added a buffer for feedback delays and rework
- [ ] The total is built from a rate you can actually live on
- [ ] Revision rounds are capped and stated
- [ ] Exclusions are named explicitly
- [ ] A deposit and payment schedule are agreed before work starts
- [ ] The quote states how changes will be handled
FAQ
How do I price freelance work when I've never done this type of project?
Break it into the smallest tasks you can imagine performing, estimate each one, then add a larger buffer than usual because unfamiliar work has more unknowns. If the uncertainty is genuinely wide, quote a small paid first phase — an audit, a plan, a single sample deliverable — and quote the rest once you know what you're dealing with.
Should I give a quote on the first call?
Better not to. Ask your scoping questions on the call, then send a written quote within a day or two. That gap lets you do the task breakdown properly and prevents a pressured number you'll regret. Saying "let me put this in writing for you" reads as professional, not evasive.
What do I do if the client changes the scope mid-project?
Treat it as a new, small quote rather than a favour. Confirm the change, state what it adds in time and cost, and get a yes before you do the work. This is easy when your original quote already said extra work is quoted separately — which is exactly why that sentence belongs in every quote.
Is it bad to quote a range instead of a fixed price?
A range is useful early, when scope is still fuzzy, as a way to check you're in the same ballpark before either side invests time. But clients tend to hear the bottom of a range as the price, so move to a single fixed number as soon as the deliverables are defined.
How much should I ask for as a deposit?
There's no universal figure, and it depends on your work and local norms. The principle matters more than the percentage: for a new client, a meaningful portion up front, with the balance tied to milestones or delivery, keeps risk shared rather than all on you.
Next step
Pricing a first project stops feeling like a gamble the moment you stop quoting categories and start quoting task lists. Before your next quote goes out, do three things: turn the brief into countable deliverables, estimate every task including the invisible admin, and write down the revision cap and the exclusions. Then name one clean project number and let it sit. For more everyday money and work decisions like this one, browse the related answers at beadvices.net.
