The Freelancer Pricing Conundrum
November 3, 2008 by Taiyab
Filed under Freelance Advice, Marketing Resources
Whether you’re looking to get into freelancing, or in the thick of it, there always exists the topic of rates a freelancer should charge for his/her work. People adopt various methods of pricing their service, from hourly rates to one-time project fees. But how do you price yourself just right so you’re not too expensive and you’re not too cheap? Should you undercut the current market and work in bulk, or should you charge a little higher and take on less projects? After all, two of the great successes in retail are ASDA (for you Americans, it’s owned by Walmart) which is a supermarket which aims to keep the lowest prices possible, and Selfridges & Co, one of the much more expensive luxury stores in the UK. Well, let’s dig a little deeper into the topic and see what we can uncover.
The Client’s Psychology
Clients are people, and we as a people are very prejudgemental in our everyday lives, whether that be subconsciously prejudging the mindset of a person from their outward appearance, or prejudging the quality of a piece of clothing from its price tag. There are a lot of external factors that have no real effect on the issues that matter to us, but are considered subconsciously by the mind without us even knowing it. As a freelancer, you could use this to your advantage (in a non-malicious kind of way!)
Usually when a person asseses the price for a service when attempting to put a value on it, they will attempt to associate it with the “quality” of the work/product/service in their eyes. For example, if they feel that the end product(s) from your portfolio are better than the competitions’, then they are more willing to pay a premium for the service in mind. If however, they feel the end product is not of a high enough quality they will be less willing to pay a premium for it. This however, also works in reverse when it comes to the prejudgemental nature of us human beings.
Subconsciously, if we see a product or service with a high price tag, or “better” outward appearance (in terms of branding), we usually think it is because that product is of a very high “quality” (and I’m deliberately using speech marks here). This is rather deliberately triggered in our heads with all the subliminal marketing campaigns that go on in society on a daily basis. Therefore, it may well be a good idea to price yourself higher, in order to portray yourself in a better light. Pricing has a lot to do with establishing a quality brand.
So putting this all into the perspective of a freelancer, you could well be charging higher than the competition, establishing yourself as “quality” and therefore reap the benefits in terms of being able to charge more for your work.
If we further explore this mindset, you do come to realize though that your pricing also should rely heavily upon whom the client is – and not for discriminatory purposes. If you’re pitching to a business owner, then they’re inevitably going to be price-savvy and be looking for the best deal possible for work of a good standard (and that’s not to say the tactic won’t work at all); however, target the common individual and you could leverage this psychology and charge more for your work in order to increase your income and establish yourself as a quality brand.
You could also take the opposite direction, charge less, and in turn by my predictions attract a lot more business clients rather than what I’ve referred to as the “common individual”.
The Economics of Pricing
The economics of pricing is very important in the freelance-industry. Immediately, I hear you crying “but I didn’t pay attention in Economics classes!” – well, maybe you should have.
It’s a very basic concept which shows that there is a inversely linear relationship between price and amounts sold or in this case, number of pitches accepted. This means that as price increases, the number of pitches your clients are likely to accept are lower and vice versa. Simple – but again in such an industry this can be manipulated using the techniques described previously. It’s just something to generally think about when pricing as a general rule with a “bog-standard” product/service when quality of work is not taken into consideration.
I would put up a nice little graph to illustrate this point, but what the heck, it’s not hard to understand.
Hourly Rates
What I’ve covered so far has mainly affected the actual price you want to charge for your freelance services, but, how will you structure these charges? Well, hourly rates are a very good way to go about it. Why? Simply because it gives you a solid price structuring that you can always rely on instead of having to come up with a price per project. Again though, this has its disadvantages. In order to obtain a higher income, the only ways to do this would be to increase your hourly rate (which is a difficult step which could have great negative/positive effects) or work for longer periods of time. To me, this really goes against the “freedom” principles of freelancing if you were to take the latter step, as one core advantage of freelancing is being able to earn a good income with less hours of work in comparison to the typical 9 to 5 jobs.
Per Project-based Pricing
A lot of people think that per project-based pricing is something that is decided from midair. No. It is also based on hourly rates, but loosely. A good way of pricing per project is to first estimate how long a project is going to take if worked on at a decent speed (in hours – making sure the estimate is conservative) and multiply that by how much you wish to earn from doing the project per hour. You’d then add on certain premiums such as costs, and other extras.
What’s the difference?
So what’s the difference between per project-based pricing and hourly rates you ask – well, the answer to that is effort. When conducting the hourly rates method, you’ll be paid directly dependent on how long you took to complete the project. On the other hand though, per project is based on a conservative estimate on how long the project would take, and therefore allowing you to reward working more efficiently.
Just take a look at this example:
- John works on a fixed amount per hour.
- Linda works on a per-project basis.
John conducts his work at the rate of $40/hour. The project takes him 10 hours to complete, and therefore he sends an invoice of $400 to the client.
Linda estimates that the project will take 14 hours to complete (remember, it’s a conservative estimate). She wants about $40/hour whilst working on the project. She decides to multiply $40 x 14 = $560, and therefore prices the project at that amount. She then invoices the client at that price. Linda decided to work very efficiently and focus on the project and therefore gets it done within 10 hours.
If we do the maths, effectively Linda was paid $56/hour for the services she rendered, whilst John was only paid $400.
There are obviously a lot of factors which affect each situation that have not been considered in this case, but you get the general jist of things.
Conclusion
So, how do you think pricing should be decided upon? Do you have a particular formula in mind? Let us know your thoughts on the topic via the comments section below.
Also, please subscribe to our RSS feed for more great content.

Follow us on Twitter
Become a Facebook Fan



I’m currently working on the price per-project basis, purely because I think it will get me more work at the moment as I’m just starting out.
I think a client is more likely to say ‘yes’ if they know how much it will cost in definite.
I agree with Paul. The client will feel more safe knowing the total cost before the project is started. Great write-up!
And yes, many people feel much more comfortable when they know the total amount that they are going to spend on a project. I’ve worked as a designer for a couple of years and found myself starting to freelance lately and I try and quote on a per-project basis which is based on hours x hourly rate, and i let the client know that so they know what they are getting for their dollar.
The more direct and hoest you are, the better off you’ll be.
Great article, I tried not to repeat too much, you’re quite right.
Of course, the risk is that Linda is wrong with her estimate, and the work actually takes her 20 hours to complete.
I’m not saying that per-project pricing is a bad idea; in fact, that’s how I do almost all of my projects. But I do think that to be successful at it, you have to be fairly good at estimating.
Also, while I work hard to be as efficient and productive as possible, I also don’t get bothered if occasionally a task takes me longer to accomplish.
Personally, I don’t like the idea of hourly pricing. To me, it isn’t the customer’s fault if something takes me longer to accomplish. They are paying for an end-result, and I promise to deliver that end-result for a flat rate. The notion that they should pay more if I’m slow seems wrong to me. (Of course if the scope changes, that’s a different story entirely.)
Although pricing per project is a safe approach from the client’s point of view, it can also bite you in the behind when you do not get your planning correct or get into trouble with things like scope creep.
Make a detailed list of work you will do in the project and make sure the client signs off on that. You will be okay with that.
I usuall do my pricing on per-project basis. It will also make me work harder as my revenue will go up
I would never quote for a full project, always a daily rate.
The problem is clients very rarely know exactly what they want and exactly what it will entail. Additionally they will often leave you waiting for their own delevirables or decisions.
I tend to agree a daily rate and then agree how many days we think the project should take. It’s generally easier to negotiate extra days due to scope creep or unavoidable delays than it is extra money; even if the two add up to exactly the same thing.
I’m with Paul. I price on a per project basis, but calculate it on my estimate of how long it will take me. I’m also very careful about scope creep and try to ensure that everything is clearly detailed in the contract that the client signs.
My prices are per project. Of course at the beginning your estimations won’t be that good. You get better over time.
Some customers don’t want to know the total, but even what I charge per hour and how many hours I think I will need. It differs a bit. You ca’t really estimate how many hours it will take to get a design done. But if you are to code some modules or something, hours work fine.
If the customer’s needs change whilst in a project or whenever you feel you’re putting way more work in it than you previously thought, you should think about why it happens and maybe talk to your client. If it isn’t fully your fault chances are your client proves he know the worth of your work and agrees to pay you some more.
I do both. I have an hourly rate (and that rate is what I use when computing a per project fee), but I’ll also do per project if the client requests it. If it’s a larger project, I almost always do a project fee — with the understanding that the price can increase if we decide to go in a different direction or if they decide to add on requirements during the course of the process. So $X gets you this, regardless of how long it takes. If you want more, it has to be added to the bill.
Per hour typically works best for quicker or smaller projects, where I can give them an estimate in advance of how long it will take, or if I’m doing IT work, which is just easier to bill hourly.
I used both hourly rates and per project pricing. For me, the second one works best for precisely the reason you mentioned in the article: the estimate is for working at a regular pace, but I usually work much faster. I consider this to be my “premium”, along with the quality of my work.
Another great tip that I recently read about is to use 3 levels of pricing. That way, clients can choose a “plan” based on what their budget and expectations. Clients will never tell you everything and since humans can’t (yet) read minds, it’s best to give him some options right from the start.
We recently published a free e-guide called “The One Piece of Advice You Need to Get the Fees You Deserve” (http://www.raintoday.com/onepiecefees.cfm). It includes 12 articles on pricing from experts in the field of professional services with insights on how to maximize your fees. If you’re interested in learning more about services pricing, it’s a good read.
Hello, I work in both hourly rates and per project pricing (as Adrian). Usually I work per project pricing at the beginning and then charge per hour for updating or for adding new functions.
By the way, working for web as designer or developer is really difficult to find the right solution. It depends on client needs.
(sorry for my little english).