How to Set Fees
post # 330 — March 14, 2007 — a Client Relations post
A reader asks:
In light of some things you teach, ideas from Rob Nixon, and the VeraSage institute; it seems a very bad idea to bill by the hour, especially if you are a new consultant just beginning your practice. Yet, most smaller clients one would probably start with would think in terms of hours. Ultimately, you would want to find some way for them to pay you according to value added, right? But how is this done?
The best I can come up with is offer a free consultation (a few hours or whatever) just long enough to show them you are worth your fees and long enough to find out if you want to work with them). Have in mind what your time is worth to you. Estimate with them the length of the project. Come up with a (fixed price) estimate. If they feel like the price is worth it to them, then you are essentially measuring the value added (maybe lower than value added). Then if it takes longer or shorter, it was based on their value and not your hours. And in the future, as you get more efficient, you still bill the same for the project.
Is this the right approach for a beginning consultant?
***
So, what does everyone think? This seems to be toay’s conventional wisdom on pricing, but would anyone else provide different advice?
Michael said:
We do this all the time at my firm (a small IT consultancy). Or rather, we think about it all the time. We think about offering the potential new customer some “free” work, to demonstrate our value. Sometimes we get to the point where we believe the customer trusts us enough to actually make the offer. And sometimes they accept.
My perspective on this is that the free work has a far better risk/reward outcome than doing cold-call business development. And much more likely to lead to a solid, long-term relationship.
Said differently, if we have a choice between spending, say $30K over the course of a year to try to get in with a new customer, or doing $30K of free work with a customer already-identified, that’s a no-brainer.
posted on March 14, 2007