4 ms·
I've consulted in this manner and I'm surprised this isnt the norm. It reduces risk for both parties. The client is seeing tangible results sooner and you're mi
by AlexDanger 14y ago
I've consulted in this manner and I'm surprised this isnt the norm. It reduces risk for both parties. The client is seeing tangible results sooner and you're minimising potential losses due to non-payment (for whatever reason).
- brandall10 14y agoExactly... at least if you're doing agile development, it seems that you should get paid in an 'agile' way :)
- mikeleeorg 14y agoFor many engagements, we required both an upfront deposit and invoiced payments every two weeks. In addition to the benefits you guys cited, billing often can also help manage scope creep - though I know some agencies thrived off the additional income from change requests. I agree that it's possible to build a roster of clients that always pay you, but when you start casting your net wider (which we did), you encounter a greater variety of clients. We grew to a team of 20+ developers and aimed to keep our pipeline near 100% utilization. With that said, we only had a handful of clients that didn't or couldn't pay. This was early in our existence and we learned quickly how to avoid, and dump, bad clients.