News for hackers. Stuff that matters.
Re:The Definitive Guide to Project Billing by lifeisstillgood on Tuesday July 30, 2013 @05:20PM (#6130139)
I'm trying bill by feature - that way the client can adjust what they have next, very much like agile stories, but with two advantages - I am not promising to work a 40 hour week but to deliver a feature. Takes me 4 hours I'm quids in, takes me 40 hours my estimate was perfect, more than that - c'est la vie.

Secondly I get to focus on a business metric. Delivering software is boring. Delivering a report showing how much their kPI went up is fun.

Re:The Definitive Guide to Project Billing by jmduke on Tuesday July 30, 2013 @06:04PM (#6130353)
This has the advantage of shifting clients from asking the question "how much will this person cost me?" to "how much will this person make me?", too.
Re:The Definitive Guide to Project Billing by lifeisstillgood on Tuesday July 30, 2013 @06:41PM (#6130602)
Yes, but you have to keep banging on about measurable KPIs - the obvious ones (visits, revenue) cannot be shoehorned into everything. Time to create new campaign, speed of data entry, lead generation, speed of response, all things you can measure. But the client has to be excited about them.
Re:The Definitive Guide to Project Billing by jmduke on Tuesday July 30, 2013 @06:57PM (#6130680)
Time to create new campaign

Do you mind expanding on this a little? What sort of orgs are you working with for which this is a KPI?