4 ms·
It has the difficulty of justifying to clients who reckon they know the standard industry rates, why a feature costs so much. Having a per-feature price doesn't
by porker 13y ago
It has the difficulty of justifying to clients who reckon they know the standard industry rates, why a feature costs so much. Having a per-feature price doesn't get round questions about why this costs so much.
Clients who have a little technical knowledge are the most dangerous. I have one with a large-agency background in the mid-'90s who quibbles every single time over the cost, whether fixed for per-hour. Because he expects it to always be a quick 5 minute/1 hour fix. So even on fixed price, he's sat there going "Well this costs $400, it isn't complex and will only take 2 hours, so they're charging... $200/hr?!!". Cue the same old justification of effort fight again, where "because there are unknowns and it could take 2 hours to debug the network issue" doesn't justify charging for it, because computers are simple, I'm the expert and I should know what I'm charging for...
- lifeisstillgood 13y agoQuite simply we have moved from discussing my hourly rate and onto "you will deliver valuable feature X, that I estimate will improve sales by Y - but you are charging too much for it" Now that is a much easier argument to have - plus if I have many other features I can swap some around, split X into xx and xy and so on. Talking about features for the client is always good
- lifeisstillgood 13y agoI have re-read the comment you made. Ditch the client.