Poll: How much do you average per freelancing gig?
In my personal freelancing experience, I need a certain amount of money before I feel it's worth using my spare time to work for someone else. I'm curious as to what that level is for HNers. How much do you bring in on an average freelance job?
166 comments
[ 4.8 ms ] story [ 148 ms ] threadOver time, I have become less and less interested in these kinds of side-projects as I have become more focused on owning the upside of my own products. But, its occasionally nice to get paid for my late-night coding adventures.
The concepts for the things I am building now were distilled from several other failed ventures. The choices were based on the projected market sizes.
EDIT: Oh and when you start out, if you're estimating time, double it.
Also, start out on hourly gigs - and then always stay with hourly gigs (time & materials). If you fixed price work you end up having to piss off clients with anal scope management (or you take a bath).
If I find the project very interesting and I can fall in love with building it, the client is going to get a good deal. Boring or otherwise tedious projects engender some stone-cold, take-it-or-leave-it negotiation. I mean, this is my free time.
Edit: Nevermind that extra bit, however true. :)
That's how I go about it and have found it to be the best/only way to ensure I don't overwork myself.
It's a good summary on a several techniques, how to apply them, and how to pick how in depth of a one to do, as well as how to talk with people who try to negotiate with them.
One of my customers, which I greatly admire, is very old guard and don't buy nothing of agile, extreme, scrum, etc. He only accept strict a to b estimates. Working with him, while hard, has made me much better at making estimates.
Another benefit of a requirements doc is if the client later says he expects some additional feature, you can refer to the requirement doc and say that it'll cost extra since it's not listed in there and your original quote didn't include it (or let them know that you're going out of scope for free because you want to help them out which will make them love you [only do this if you're ahead of schedule]).
Also back when I was doing freelance stuff I usually wouldn't even take a gig if I didn't think I would make > $5,000 from it.
What I want to start doing with projects that aren't clearly defined, is to simply do an initial contract to nail down some of these details. Build a prototype, do some tests and write a detailed spec - and then the next contract will be building it for real. (Maybe with some inexpensive outsourcing.)
Prototypes aren't as useful as you would think. Clients see them and are like "hey that's a nice mock up, now make what I want", then you build the actual application and they say "well where's feature X, Y and Z?!?! when you say it wasn't in the prototype they just say "well I thought it wasn't there because it was just a mock up"
Ideally though, you want to charge them for the requirements doc (and get paid for it) before you start the actual project. You can usually tell the client this and tell them they can use the requirements doc to shop around with other developers so they can get the best deal. Clients are usually happy with this and usually don't bother shopping around.
"... nearly 90% of all legally distributed pornographic films made in the United States are either filmed in or produced by studios based in the San Fernando Valley"
Since this all side stuff, after my 9-5 job, I'm very picky on what I take in, since I like to work on products that I have 'real' input in.
http://twitter.com/eekfuh
http://www.deliciousmorsel.com/
Need to charge more!
There's a limit on that school of thought, but if have the option of 2 freelancing contacts at X, or 1 at 2x, I prefer to focus on one client at a higher price point.
I figured out my starting freelance rate by taking my per-hour salary from my day job and doubling it. Then, whenever I had too many clients at that price level (generally 2+ back-to-back) I increased my rate by 50% to 100%.
This has worked great for me through multiple iterations. As my portfolio, contacts, and experience grows, so does my rate. I'm left earning a good amount for my freelance work, and have the luxury of turning down work that isn't paying enough or is too much of a hassle to coordinate.
I always advice people to go the hard science way if they like computer science, because there is a really big big lack of people being good at both. I should write about it.
I've thought about going into a hard science industry but never did anything about it because 1) I'm not really qualified in the science side, my skills/experience/qualifications are in computer science and 2) I don't really know how to get started.
Please do.
Just off the top of my head you'd need to think about winning each contract, paying taxes, holidays, health cover, professional indemnity, sick leave, misc business expendables (like office, phone, ISP), the list goes on.
Don't get me wrong. It is still good money I'm sure.
its also an amazing learning opportunity (and play. but never take close up photos of your phone. you'll become OCD about clean pretty fast)
Off-topic: what books do you recommend on chemical engineering? What's the equivalent of The Art of Electronics for analog electronics, or HDL Chip Design for digital chip design, or Code Complete or Algorithms in C or CLRS or The Pragmatic Programmer or SICP or TAOCP for software?
1) Perry's Handbook for Chemical Engineers (Perry)
2) Conceptual Design of Chemical Processes (Douglas)
Perry's is the end all be all for technical reference.
Conceptual Design is incredibly useful for learning how to quickly and accurately design an entire process. If anything, it'll teach you the best methods to go about "back of the hand" calculations for sanity checks.
I did a lot of operations-research type programming in grad school, and I thought it would set me apart, but I've found that the jobs that want programming and OR skills don't seem to pay any better than other types of programming. This is jobs, not consulting gigs, though, and I'm only basing this on a few data points.
- I mean, I'm not from a developed country. Is that still possible that I can take advantage of mastering both skills? I'm currently a Medicine student with good programming skills. -
The last few projects I've gotten average to about $7k each and are about 1-2 months in duration. The highest I've gotten is $10k for a 2 month design and development gig, working very casually over that time (enough time to work on other projects freely). I'm now learning that people are willing to pay for high quality work and consistent/reliable communication.
I think many people get hung up on skill though. Clients pay for many, many things. Skill is only one of those things, and it doesn't dominate, either. Clients can also pay for:
Of these, if you could only have one, I'd probably go with the ability to give clients the warm fuzzy feeling. You will never go hungry if clients get the warm fuzzy feeling from working with you.Hat tip to tptacek, who taught me the importance of some of the above.
- make your clients look good to their stakeholders
- make someone look good to their manager
- make an exec look good to their board
- make the firm subcontracting to you look good to the end-client
- make your teammates/collaborators look good (and help them save face when they screw up)
We've had trouble finding great infographic designers that don't take a lot of time to manage, and I'm wondering if we should be paying more.
If interested in that or doing UI/UX stuff, check us out http://feefighters.com and drop me a note
EDIT - looks like people are interested! job posting for fulltime UI/UX here : http://feefighters.com/jobs/ui-designer-developer/
and Freelance infographic posting here: http://www.genuinejobs.com/jobs_detail.php?id=5606 (but just drop an email to josh@feefighters.com instead of responding to this one)
For those curious about the workflow, I use:
* Google Docs to create a spreadsheet with all project research/notes that is shared with client
* MockFlow to handle wireframe mockups, as it also allows me to easily share them with the client AND is cheap (I think $70 per year?)
* Photoshop and Illustrator to create the main mockups for each of the major pages/sections of the site
I also tend to shy away from logo design, as for me it is not worth the time and effort for the pay - instead I suggest to my clients that they use a service like 99Designs or Brandstack.
It does not matter one bit what I or others charge. What matters is WHO IS YOUR IDEAL CLIENT?
If you know that, you know what VALUE you bring to them and you can charge whatever you want to solve a real problem.
Otherwise you are trading time for money. AKA - Job.
Does Rolls Royce consult Honda as to what to charge for their products? No. Two different markets with two different clients and two very different ways of solving a clients/customer's problems.