4 ms·
Another item to consider is what a fair rate is. Let's suppose that a full-time developer is paid $120K/year. (There are developers who get more, a lot who ge
by btilly 14y ago
Another item to consider is what a fair rate is.
Let's suppose that a full-time developer is paid $120K/year. (There are developers who get more, a lot who get less, but this gives us a nice round number to work with.)
When you add up benefits, taxes, office space, etc, the average employee costs 2x their salary. So that developer probably costs $240K/year.
You tend to work about 50 weeks per year, so that's about $4,800/week.
You work 5 days/week so that's $960/week.
After you get rid of lunch, discussing the weather, HN, etc, you're probably only putting in 6 hours of actual work per day, so that's $160/hour.
Therefore an employee who makes $120k/year is likely costing the employer $160/hour. As a contractor you have to bear those costs that employees do not. Plus you have to bear costs such as not getting paid for the time it takes to find more work.
Most people who contract do not charge enough. Perhaps after running through these sample numbers, you'll do the calculation for yourself and ask for a more realistic rate for what it costs for you to be a contractor.
- vanni 14y agoThank you for your analysis. Just a typo: $960 per day not per week.
- DeepDuh 14y agoI've worked as a Software consultant for a small company known for quality work and I can confirm your numbers. I've been billed for up to 230$/h, however this is Switzerland - on US price levels it should add up with your calculation pretty well.
- ww520 14y agoThat's a healthy rate. I guess the company takes a cut as well.
- ww520 14y agoYeah, most people don't bill enough to cover the cost. Remember you are paying your own medical, social security (both employee and employer portions), insurances (professional, worker comp, life), retirement, office, utility, etc. A rough rule of thumb is to charge 2X of what you would be paid as an employee.
- Silhouette 14y agoA rough rule of thumb is to charge 2X of what you would be paid as an employee. That's a common rule of thumb, but I suggest that it's not a good mindset if you're interested in making what you're really worth as a freelancer. One of the most fundamental differences when you're negotiating with a client as another business rather than as a prospective employee is that your arrangement will be a business to business one. Like any other such arrangement, it pays to price based on what your contribution is worth to the client, which will ideally be much more than what it costs you to provide it.
- mseebach 14y agoIt shouldn't be your target price, but it's useful to keep in mind as your "cost" level. Below this, you're actively loosing money (over a regular job) and at that price point, there's no financial upside to compensate you for the downsides (risk, uncertainly, stress) of consulting.
- flgb 14y agoAs someone who has run a consultancy and employed consulting staff my rough rule of thumb is 3x total employment cost: one third for the employee, one third for the company, and one third for profits.
- daeken 14y agoI believe the reason people bill at a significantly lower rate than they should is that they're worried that the difference will mean less work; I know that fear drove my prices down when I was doing freelance stuff heavily a few years back. At this point I know what my time is actually worth and bill at that rate, but it's taken me years to feel comfortable doing that. Channeling patio11 here: you should be charging more.
- patio11 14y agoIt is valuable to consider the you-centric position on why you need to charge a lot, but also keep in mind why your client gets more valuable out of you, in such a fashion that they don't mind you charging much more than a FTE over the same interval: + They can keep you for exactly as long as they need you, and then let you go, with no hard feelings. + You don't require a 3 ~ 6 week spin-up period as you get used to e.g. how your new employer uses source control, the procedure for running acceptance tests, or the proper way to fill out requisition forms. + The search to find you took days, not months. + The interview(s) to bring you in takes one person minutes/hours rather than several people days. + The paperwork to bring you in takes minutes, not days. + There are some specialties where FTEs for that specialty are either a) extraordinarily expensive or b) unavailable for hire at essentially any price. The business might not be able to justify keeping one of them around for the year, if for no other reason than their salary would upset the apple cart with other employees, but might still get value out of tactical engagements. + Employers and employees have an expectation that employees will occasionally have issues which temporarily impair productivity and that this is just the nature of the beast. ("Dad is in-and-out of the hospital and I'm mentally checked out.", "Off to JavaOne this week.", "I'm pregnant, cya in a few months.", "We sprinted hard for the last six weeks and I'm in cooldown mode.", etc) Consultants sometimes have impaired productivity, too -- but employers don't have to pay for it, since consultants will typically attempt to avoid scheduling engagements during them. * Consultants put up with a lot of things by charter which are socially awkward to ask of employees, for example, "We need you in Berlin the day after tomorrow."
- bdunn 14y agoTo reiterate what patio11 just said, focus less on reverse engineering your former salary into an equivalent "rate" - figure out the business value you're delivering to your clients and price accordingly.
- tptacek 14y agoThe rate structure 'btilly outlined --- the cost-based price for your services --- is very important to know, even though it's rarely the rate you want to be quoting clients. He's right: lots of contractors, maybe even more than half of them! are delivering below their true cost, and are losing money compared to a full-time job.
- btilly 14y agoExactly. Your cost is a floor, not a ceiling.
- devs1010 14y agoIn my opinion, the concept of paying per hour is one of the biggest fallacies in software development. I am salaried but I don't get paid based on hours worked, I have deliverables that I meet, its irrelevant how much time is spent on meeting those and is impossible to quantify because often the hardest problems are solved in my head when doing something else, could be when stepping out of the office to go for a walk or while on the commute home, etc. We are paid to use our brains and this does not correlate directly with the traditional concept of billing for time. Also,things I do outside of work often positively benefit me, such as working on a side project or reading a book about new programming styles / concepts, however this would never be considered to be "billable hours". Its my goal to one day work on a per-project basis, I haven't quite figured out how to make a go of this yet, however I really think this is how most software should be done for anyone with a few years experience under their belt. Working software is valuable and if you can commit to something and deliver, the concept of time should be immaterial (outside of meeting a deadline)... its all about value delivered. By tying ourselves to hourly billing rates, I think software development as a profession is held back and part of the reason it may not be as well respected as it should be by "business" people. It takes standing up and proclaiming the value that you bring every now and then to make people realize this isn't an assembly line type of job and never will be.
- ErrantX 14y agoI've recently been experimenting with this; it can be dangerous for you (read on) but if well managed it can be more flexible for both you and the client. For a long time I've been playing around with how I charge; a few weeks ago we had a discussion r.e. hourly vs. daily rates (I prefer the former, as it works best for me). But in the last ~2 months I've been working on ways to charge on a target basis. Or to put it another way; I agree a schedule with my client, and they pay as I reach each milestone. This takes time almost entirely out of the negotiation. It has other benefits too; for example it forces the client to work on a formal specification (as an engineer, this is crucial!) for a project. I have flexibility on how I reach the goals we agree - I might give a deadline estimate (two weeks for milestone 1, a further week for milestone 2). Whether I do the work on a Monday, or part of Weds and Fri, is irrelevant to them. And so I have the flexibility to schedule all of my work as is convenient. Internally I am figuring out that it requires X hours work for each milestone - but the client never sees this, they just see my quoted figure and the delivery date. But I have found that this way I can up my rates significantly - I suspect because clients are measuring cost in terms of deliverables, rather than hourly or daily rate. I spent a lot of time working up my rate from £40/hr (three years ago) to £100/hr through various mechanisms. But I have struggled to breach that barrier for a while now. My ultimate aim is £200/hr (which, as a full-stack engineer with years of experience & happy clients, is what I think my time is worth). This new method is currently "testing" at around £120/hr and I am slowly increasing it, without issue so far. This also helps for existing clients too; if you start working with someone at £40/hr it's hard to build your rate up significantly without putting them off [I lost a very solid client on the jump from £60 - £100]. But if clients don't know your rates, upping them by £10/hr will be much less visible, and they only have to judge whether the total cost is worth the outcome. So, I think I would be happy in saying - your theory is sound, and seems to be working out for me in practice :)
- bambax 14y agoYou should not bill per hour but, at the minimum, per day. Better yet, you should give quotes for the whole project, regardless of time spent. If you spend less time than anticipated, good for you; if you spend more time than anticipated, you bear the cost. But here's the thing: most clients have NO IDEA how much work goes into a specific task. If you bill by the hour, they will want their money's worth of your time. If however your quotes are for the whole project, the only relevant metric becomes "is the project done?" For this to work, the project has to be specified with a reasonable amount of precision that allows one to check at the end whether it's done or not; but this extra work of specification pays off big time -- even, I might add, if you have to do it yourself for free, as part of the sales process.
- peteretep 14y agoThis is why it's worth contracting (ie: onsite with the client, paid by the day) rather than freelancing.