10 Nov 09 Freelance PHP Programmer – Managing Estimates

Dealing on larger projects and mediating between my PHP development team and the Client is often a far simpler task than acting as a sole freelancer. Having a very good and reliable team of 12 long term offshore PHP programmers, means that I now have sufficient confidence that I could theoretically just pass their overall estimates straight on to the Client without issue. Even still, I add at least 10% to the PHP developer’s estimates as well as subtracting at least 10% from the Client’s final delivery date. If we’re all happy and can agree on those deadlines, great. This allows for a comfort period for us, as well as the ability to iron out bugs and perform good QA on anything delivered.
When it comes to freelancing as an individual, managing Clients expectations can often be difficult, as well as quoting appropriately on projects. Clients being clients and having budgets to manage, want fixed quotes on projects. Per hour is always my preferred method, because after a brief discussion on what we expect to be able to achieve, and within what periods, we can just get the job done. As the project evolves, we can spec things up in terms of hours estimated, and the client has the option of going ahead on a particular feature or perhaps not at that time.

Offering any kind of intangible job, development or otherwise on a fixed price, means meticulous and thorough specifications, which are of course a good thing in themselves, but can drag out and become unnecessary at times. Of course, with Client satisfaction as a top priority, turning round and pointing out that the a particular simple addition or quirk is not in spec and therefore can not be done is not an option. With that in mind, I’ll generally have to spec up the project as tightly as possible, and then take my genuine best hourly estimate and add beween 15 and 20% to it to cover all eventualities. This will more often than not mean that although the Client will ultimately get the project he wants, but could actually be paying more in the long term, and perhaps for a less feature-rich final product.

On that basis, I always recommend going ahead on a per-hour basis with any developer if you’re confident with the development process as a whole. If you’re not familiar with the developer’s work, then take each hour or two as it comes, and if you’re not happy with what’s been done in the given time, halt the project and re-evaluate.

Tags: freelance php programmer, PHP, php programmer

Leave a Comment

You must be logged in to post a comment.