Re^2: Consulting firm, job-based consultant, or hourly contractor?

[punch_card_don]

OK, so one vote for the hourly programmer thing. I can see the logic - quoting is always a delicate area. Guess so far I've been lucky at finding projects that can be farily clearly defined - but it's true that I am always careful to be very explicit about the scope of a quote and upfront about ex-scope work being extra.

[smithers]

And another.

I prefer maintaining relationships with a few good consulting firms so that hourly programmers and technicians can be brought in as needed. Ideally, the contract should allow right-to-hire but that may not be in your interests (but the loss can be mitigated by charging finder's fees).

It's obviously also in your best interest to engage with good clients with proper expectations and experience with consulting resources. For example: once a consultant has established him/herself with us we give them leeway such as flexible working hours and dress code. Although none has ever reached the pinnacle of working in their underwear :)

We are also accustom to having contract resources working with our teams so once the resource is established, they tend to integrate well into the team and the lines between contract and employee resources fade away.