Comments on: Value Billing for Software Projects http://jonathanstark.com/blog/2009/11/16/value-billing-for-software-projects/ Mobile application strategy, design, and development. Tue, 13 Jul 2010 06:18:50 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Kevin Mullins http://jonathanstark.com/blog/2009/11/16/value-billing-for-software-projects/#comment-714 Kevin Mullins Tue, 17 Nov 2009 07:13:08 +0000 http://jonathanstark.com/blog/?p=368#comment-714 I look forward to the future posts about the subject. Something about this approach feels right, but it isn't something I would be able to say why I think it feels right. It will be nice to get further information so that I can make that determination. I look forward to the future posts about the subject. Something about this approach feels right, but it isn’t something I would be able to say why I think it feels right. It will be nice to get further information so that I can make that determination.

]]> By: Tim http://jonathanstark.com/blog/2009/11/16/value-billing-for-software-projects/#comment-671 Tim Mon, 16 Nov 2009 17:37:06 +0000 http://jonathanstark.com/blog/?p=368#comment-671 In conversations with other developers about value-based billing, I've heard (and share) concerns that you can potentially get yourself into a bad situation if scope creep enters a project. If you're committing to a fixed price for a project, then you've got be very sure that the expectations of the client are very clearly defined. I'm wondering if you agree with that or not. I'm also wondering if you build into your proposal the time that will be involved in determining what the scope of work really is? Are your proposals extremely detailed? (I'm suspecting that they're not, and wonder how you manage to pull that off!) And finally, what do you do in situations where, after a project has landed, you realize that your expectations are quite different from those of the client? Thanks for sharing your thoughts, ideas, and experience regarding value-based billing. You've certainly giving us something to think about! -- Tim In conversations with other developers about value-based billing, I’ve heard (and share) concerns that you can potentially get yourself into a bad situation if scope creep enters a project. If you’re committing to a fixed price for a project, then you’ve got be very sure that the expectations of the client are very clearly defined. I’m wondering if you agree with that or not.

I’m also wondering if you build into your proposal the time that will be involved in determining what the scope of work really is? Are your proposals extremely detailed? (I’m suspecting that they’re not, and wonder how you manage to pull that off!)

And finally, what do you do in situations where, after a project has landed, you realize that your expectations are quite different from those of the client?

Thanks for sharing your thoughts, ideas, and experience regarding value-based billing. You’ve certainly giving us something to think about!

– Tim

]]>