10

We're a client that recently hired a contract programming company for some fairly focused work (essentially writing 'scripts' to extend the functionality of a third-party enterprise application). We're trying to evaluate their performance on and the value of some work they did for us, but we're a little new to using contract programmers and could use some help:

  1. If you were hiring a company as a contractor to do computer program development for you, and the minimum billing time unit was not mentioned in the contract, would you expect to be billed in whole-hour increments (so that a phone call of 5 minutes is billed as 1 hour)?

  2. What is industry standard practice for the minimum billable time unit in contract programming work?

  3. If you hired a contracting company that had two employees, would you expect each person's time to be broken out and rounded up to the minimum billable time unit? Let's say the senior guy worked with the junior guy for 15 minutes, and the junior guy worked 4:15 that day. Would you take exception to a bill for 1 hour (senior guy) plus 5 hours (junior guy), or would you expect a bill for just 5 hours?

You may find my follow-up question about key contract points interesting.

Community
  • 1
ErikE
  • 1,181

3 Answers3

10

First, the obvious point -- whatever you're going to do, put it in writing, and make sure the client is completely aware of how he is going to be charged. A surprising bill is a lot more harmful than a big bill, every time.

Second, the real money for you is in keeping a client over a long period, and making them unafraid to call you when they need you, not in getting as much money as you can each time they do call. Make sure this is reflected in how you're billing them; look at the policy you wrote down for the first part, and see which of these two cases it would look like to you if you were the client.

Now, how would I recommend you actually bill? Here's how: don't try to find an hour here and an hour there. Total the time you spend working for the client up over the whole billing period (usually two weeks or a month, but you'll nail this down with the client in advance), and figure our how many hours this comes to. If you work 45 minutes a day for them for four days, this is three hours, not four hours. If you work ten hours and fifteen minutes a week for them for two weeks, this is twenty-one hours, not twenty-two hours, and so on. In the time I spent contracting, I found that what you lose in nickel-and-dime stuff, you'll make back in a long and productive relationship -- though Your Mileage May Vary.

jimwise
  • 7,668
6

Programmers, even contract ones, are not like lawyers in most cases with billable hours, there is a lot of rounding going on with most bills. Also, its been said in other posts on this site, look at the quality/quantity of work completed and the total cost of the work, and ask yourself did it seem reasonable, trying to breakdown hours to the minute is not going to get the results you want as there is just to much variance in the time it takes programmer between indviduals and situations. Also, I've rarely seen bills broken down in enough detail to even tell what was going on during the hour billed.

I'm a consultant and I'd probably never charge for a 5 minute phone call, the goodwill with the client is worth more than the time spent, though if you call me out to your site, I'm probably billing you at least 8 hours for the work, as you've severely hampered doing any other work for the day (unless it was an agreed upon, scheduled meeting, then it would just be the time). If I'm working at my site, I'm probably billing nearest half an hour.

ben f.
  • 436
1

You have to think about it this way. There is a context switching overhead to the senior guy stopping what he is doing, helping the junior guy and documenting the time for that project and then getting back to what you were doing before the interruption.

Might not be 45 mins but it is there, and it is just a fact of doing business, there is more to developing software than just writing code. If there wasn't people would bill by the line of code and that wouldn't work either.

Personally I only charge in minimum 4 hour increments, anything less isn't worth the overhead of having to keep track of minutia and details. And you can't really get a significant amount of development work done in less time, unless it is tech support, which gets bill differently than development. And that gets billed by the hour, I usually let short things less than 15 slide if they are one off type things, and anything more than 15 mins is rounded up to an hour.