4 ms·
> Why not bill on a daily/weekly/monthly rate? I would need explanation on this. It's not that I disagree, just that I don't understand the reason of this reco
by me_bx 12y ago
> Why not bill on a daily/weekly/monthly rate?
I would need explanation on this. It's not that I disagree, just that I don't understand the reason of this recommendation.
I've read the other comments going in the same direction as you, and already saw it in the past written in tptacek's profile [1].
Do you mean that you always dedicate full days to a customer, and will always invoice them full days, even if you don't work all the time? If not, how do you do when you work, say 4 hours for one client?
How is billing daily/weekly/monthly more simple? Thanks for enlighting me.
[1]https://news.ycombinator.com/user?id=tptacek https://news.ycombinator.com/user?id=tptacek
- gk1 12y agoPersonally I work with monthly billing, and infrequently with weekly billing, so my experience is mostly with those two formats. > Do you mean that you always dedicate full days to a customer, and will always invoice them full days, even if you don't work all the time? When I'm on a monthly contract, it means "I will spend time this month doing X and Y to help your company achieve goal Z." There is no mention at all about hours. Nor does the actual time spent doing X and Y affect the rate. In any given month I am helping multiple companies reach various goals. Some may wonder: "So how in the world does the client know you're actually doing anything?" Well, if after a month or two we're not any closer to goal Z, then I'd be out of work. Not only does this turn the conversation toward ROI and real business value instead of counting hours, but it also gives both the consultant and company predictability: The company knows how much it needs to budget each month towards goal Z, and I can plan expenses ahead of time instead of living paycheck-to-paycheck.
- me_bx 12y agoThanks, things are much clear now :)