This has come up in various ways before but I think Amanda explained it in a very good way:
|
Quote:
|
State your assumptions on how you will receive the information. For example, if you quote $x to prepare a mass mailing you want to be clear that the price reflects that you'll get the information in a usable format that has already been reviewed for completeness and duplication, requiring minimal effort on your part. Also state the number of letters, etc.
Throw in a "projects not meeting the above specifications could result in a higher price, to be discussed prior to work commencing" statement and you should be ok.
Personally I think it's better to quote a not to exceed (NTE) amount as a flat fee with a check-in at the 50% and 80% completion mark.
For example, for the same mailing you could do a "The project is expected to require the following in time/materials (insert your estimate) and should not exceed (use this as your buffer). If, at the 50% and 80% review points it is found that the NTE estimate is insufficient to cover the cost/time of the project (as a result of scope changes or delays through no fault of the VA) a revised quote will be submitted for client approval before work can continue."
You should be tracking your time anyway so it shouldn't be a problem. But this way the client gets a semi-fixed price and you get some protection from a crazy client that changes the letter 500 times.
|
Per project pricing is still based on an hourly rate and you tell your client that the price of the project changes only when the scope of the project changes, that way you don't get stuck with a bunch more hours of work when they want to make changes that weren't included in your original quote. A more difficult project would probably take more hours so you would invariably end up charging more for it in the long.
Per Project Pricing is beneficial in other ways too. For example, what may take you three hours to do now, may only take you 1 1/2 hours once you've done it a hundred times, if you price that as a project then you aren't penalized for simply being for being more efficient.
There's also a good article
here followed by some great comments about why you working by project.