Most freelancers price a project by thinking about the main work: the hours they will spend doing the thing the client asked for, multiplied by a rate that feels about right. Then the project starts, and the real costs show up one by one. The calls. The revisions. The file the client sends late. The tool you have to buy for this one job. The subcontractor you need for a small part you cannot do yourself. The afternoon you spend fixing something that was never in the brief. By the end, you have done far more work than you priced for, and the project that looked profitable has quietly paid you less than your normal rate — or less than nothing, once your time is counted properly.
The true cost of delivering a project is not the headline hours. It is everything the project consumes: your time, other people’s time, tools, licences, admin, communication, corrections and the running costs of your business while you do it. If you do not count all of it, you are not pricing a project. You are guessing, and the guess is usually too low.
Start with the price you charge, and the cost you pay — they are not the same thing
The price is what the client pays you. The cost is what delivering the work takes out of you and your business. The difference between them is what is left for your pay, your tax, and anything you want to keep for slow months. If you confuse the two, you will keep accepting work that feels busy and looks successful while your bank balance stays flat.
Count your own time — all of it, not just the skilled part
This is where most under-pricing starts. When you estimate a project, you usually count the core work: the design, the writing, the editing, the coding. That is the visible part. But a project also takes time that does not look like the core work, and it all comes out of your working week.
Count the time to understand the brief and ask questions. Count the calls and messages. Count the time to set up files, organise material the client sends, and chase material the client has not sent. Count the time to review your own work before you send it, and the time to fix the things you find. Count the delivery itself — preparing files, uploading them, writing the handover note. Count the time to invoice, follow up on payment, and keep records.
A useful way to catch this is to time one real project from start to finish, including everything, and compare the total hours with the hours you estimated at the start. Most freelancers find the real total is noticeably higher than the estimate. That gap is not a personal failure. It is information. Use it the next time you quote, by adding a realistic allowance for the work around the work.
Count subcontractors and bought-in help properly
Sometimes a project needs a skill you do not have, or more hands than you have. A subcontractor, a proofreader, a voice artist, a developer for one small part — whatever it is, their cost is part of your project cost, and it needs to be counted in full.
That means the fee they charge you, plus the time you spend briefing them, reviewing their work, and fixing anything that comes back wrong. Subcontracted work is rarely free of your time. You still have to manage it, and that management time is yours, not theirs.
Agree the subcontractor’s price and scope in writing before the work starts, and agree what happens if the client changes the brief halfway through. If the client change means the subcontractor has to redo work, someone has to pay for that redo. Decide in advance who that is — in your quote to the client, or in your agreement with the subcontractor — instead of discovering the answer when the invoice arrives.
Tools, licences, assets and one-off purchases add up
Every project uses tools. Some you already pay for every month. Some you have to buy, rent or licence for this project alone. Both count, but in different ways.
For a tool you already pay for monthly, the project uses a share of it. You do not need to charge the client the full monthly subscription for one small job. But you do need to remember that the subscription exists, and that your prices across all your projects together have to cover it. This is why a single project can look profitable on its own while the business as a whole struggles — each project ignores the shared costs, and nobody picks them up.
For a one-off purchase — a stock asset, a font licence, a plugin, a template, a piece of software you need for this client only — the cost belongs to this project, and it should be in the quote or agreed with the client before you buy it. Do not buy it first and hope the client agrees to pay for it later. Ask first, in writing, and get the answer before you spend the money.
Check licences carefully. A licence that covers your own use may not cover a client’s commercial use, and a licence for one project may not cover the next one. If the licence does not cover what the client needs, you need a different licence or a different asset. Sorting that out after delivery is far more expensive than sorting it out before you buy.
Admin, communication and revisions are real work
Nobody likes counting admin time, because it feels like it should be free. It is not free. It is time you could have spent on paid work, and it is time the project required.
Communication is the biggest hidden cost. A client who sends ten short messages a day is not sending you ten small requests — they are interrupting your work ten times, and each interruption costs you focus as well as minutes. A client who needs a weekly call, a written update, and a meeting to discuss the update is asking for three pieces of work, not one. None of this is unreasonable. Clients are allowed to ask questions and expect updates. But it is work, and work belongs in the cost.
Revisions are the same. A revision round is not a small favour at the end. It is reading feedback, deciding what it means, changing the work, checking the change, and sending it back. If your quote includes two revision rounds, that is two rounds of real work. If the client asks for a third, a fourth, or a change that rewrites the brief, that is new scope, and it should be priced as new scope. Put the number of included revision rounds in writing before you start, and say plainly what counts as a new scope. That one paragraph in your quote saves more arguments than any other.
Do not forget overheads, tax and your own pay
Overheads are the costs that keep your business running whether or not you have a project this week: your software subscriptions, your internet, your phone, your hosting, your bank charges, the time you spend looking for work. No single project pays all of them, but every project has to carry its share. If you price projects as if overheads do not exist, you will earn money on every project and still struggle to cover the month.
Tax works the same way: set the tax share aside when the money arrives, based on professional advice for your situation, not when the bill arrives.
And finally, your own pay. If the project leaves nothing for you after costs and tax, you have not run a business. You have donated your time. Price so that your pay is in the number, not an afterthought you hope will be left over.
A worked example: the same project, counted two ways (illustration)
This is a made-up example with simple round numbers, purely to show the shape of the problem — not a real project and not a recommended price.
Imagine a small project you estimate at 10 hours of core work, at a rate of 50 units an hour. The simple count says the cost is 500 units, so you quote 500 and feel good about it.
Now count it properly. The core work is still 10 hours. But there are also 2 hours of calls and messages, 1 hour of setup and file handling, 1 hour of review and fixes, and 1 hour of delivery, invoicing and admin. That is 15 hours, not 10. At the same rate, your time alone is 750 units. Then add a subcontractor for one small part at 100 units, a stock asset licence at 50 units, and a share of your monthly overheads at, say, 50 units for this project. The true cost is 950 units — nearly double the first count.
Nothing changed about the project. Only the counting changed. If you had quoted 500, you would have done 950 units’ worth of cost for 500 units of income. If you had counted first, you would have quoted differently, or agreed a smaller scope, or walked away. That is what the calculation is for. It does not make you expensive. It makes you honest with yourself.
Use the true cost to set the price — and to say no
Once you have the true cost, the pricing decision is simple, even if it is not easy. The price has to cover the true cost, leave something for tax, and leave you a fair margin for your time and the risk you take. If it does not, you have three options: raise the price, reduce the scope, or decline the project. Doing the project at a loss and hoping it leads to better work later is not a fourth option — it is the same as the loss, with a hope attached.
A project that pays well is not the one with the biggest price. It is the one where the price covers the true cost and leaves you fairly paid for every hour it actually took. Count the cost first, quote second, and you will take fewer projects that quietly lose you money.
Quick checklist before you quote
- I have listed every kind of time the project will take, not just the core work.
- I have counted subcontractors, licences, assets and one-off purchases in full.
- I have added a share of overheads, and I have thought about tax separately.
- I have put the number of revision rounds and the definition of new scope in writing.
- The price covers the true cost, tax and a fair margin — or I have a plan to change the price, the scope, or my answer.
