|
>1. The word "between. I largely agree with this article and even this point in particular, but I think you will often end up in a situation where stating a range can move things along quickly. If you qualify it properly, it can be a useful way to turn the tables. For example, if you are discussing rate you could say well, from the other people I've been talking to it looks like positions like this one pay between $45 and $65 an hour, depending on various factors, but of course more detail is required to pin the number down exactly and it varies for each individual, so what kind of budgetary, time and code quality constraints are on this project? I think this is a nice way of turning the tables, it would be socially weird for them to just ignore the question and be like, "so what EXACTLY were you looking for?" Of course, they may end up offering you at 45 to start, but you can just kind of scoff at that (if you want) and be like well this seems more complex/difficult because... there's nothing wrong with continually edging away from the question until they get frustrated. |
I've made this mistake before, and find that people always zoom in on the lower number and think that's your actual offer. And then it's quite awkward to say "Well, I didn't really mean $45, I won't do it for that little."
I've found that offering a range works much better when I make the lower number of the range quite a bit higher than what I actually want. That gives me room to come down, so that even once they've talked you down from that lower range, it's still higher than what you wanted.