4 ms·

I have done this both ways. The most success I have had with per project pricing is having a discovery phase to actually scope out the work. There is a decent

I have done this both ways. The most success I have had with per project pricing is having a discovery phase to actually scope out the work. There is a decent amount of up-front work, but it really ensures everyone is on the same page. This is usually a series of 4 meetings, anywhere from 30 minutes to an hour. From there, I can write a spec/contract, I present that, which is another meeting (I don’t just email it). Then once they agree, 50% up front, and 50% upon completion. There is language in the contract that any changes to spec/feature, they require an additional contract and do not change existing work/agreement. The pain comes from vague specs and everybody has a different interpretation, and the feat of not getting paid until satisfying the vague expectations. So, just don’t do that. :)

Silhouette 6y ago
The most success I have had with per project pricing is having a discovery phase to actually scope out the work. I concur. Also, the discovery phase itself can be flexible on time allotted and billed in time increments, even if the main project won't be. You might well not know up-front whether you need a day, a week or a month to pin down the spec and all the other details, so a self-contained "getting to know you" phase before anyone makes big commitments has a lot of upsides for all parties. Also, regarding the problem of vague requirements and differing interpretations, getting a complete set of acceptance tests agreed early-on has a lot of upsides for both parties too.