[tptacek]

So provide a conservative estimate billed in week-long increments. You come in way under the wire, they get a week or two deducted from the final cost of the project. Customer dicks around with requirements, you get to say "I am happy to do whatever you'd like and make whatever changes you'd like but I need to remind you that we have a fixed schedule for this project".

All this stuff about "what's best for the customer" tends to be an elaborate justification for complicated pricing schemes that alienate customers while ironically undercharging them for the services you provide.

Avoid customers for whom a week's worth of your time is a make- or- break- the- business decision.

[medinism]

Good point. the way I was thinking about it was more like this 1- you provide an overall estimate on where you think you could come in at. you do this to give all clarity on how you are thinking about the problem, anchors your estimate and the functionality you are about to build, and allows the owner to get a sense of price 2- only commit to a week or 2 at the time. this allows the client to tweak things, see quick progress, and add or subtract features as you make progress. Or even stop, test features on customers - and pause.

thoughts?

[tptacek]

The customer wants you to commit. When you say "let's do a week at a time", the customer does a mental calculation of what one week of your time is worth if the project doesn't complete, arrives at the number $0, and responds accordingly.

That doesn't mean you work a fixed-price gig. It does mean that you give serious thought to a conservative estimate of the whole gig and then confidently offer that as your price for the engagement.