NYCPHP Meetup

[ophir prusak]

Personally, I'd go the route of a fixed price for a WELL defined site
upgrade, and then $X an hour for changes / upgrades.

It it's more than 1 (or 2) hours work to create a specficiation document,
charge something small just for that. (so they won't get your document
with the nescasasy changes and then get a cheaper bid elsewhere and leave
you with nothing).

In this day and age, most places need to control costs, so a fixed price
can give them some peace of mind. Also - it's easier to give a "discount"
on a fixed price for the WHOLE project.

Also - see if you can get from them what their budget is and try to work
something out accordingly.

If you do go with fixed price, make sure to include a clause where they'll
pay you for hours worked if for some reason they want to break the contract.

Ultimiately, you need to figure out how much it's worth it to you to
get this project.

hope that helps.
ophir

----
Ophir Prusak
Internet developer 
prutwo at onebox.com | http://www.prusak.com/ 



---- "Kenneth Schwartz" <kenschwartz at nyc.rr.com> wrote:
> I know this question is hard to answer due to the many factors that
> could be involved.   But I'm just looking for very general input. 
> I'm wondering if anyone can give me ballpark idea of appropriate rates/project
> price for a fairly 'normal' upgrade from a static HTML site to one
> with some PHP enabled dynamic components.  By 'normal' I mean nothing
> crazy in the data model or code expected.  I need to give a client
> a project price and I've been working completely inside a corporate
> environment for the past 3 years so I really don't know what the freelance
> market will bear.  Anyone wish to enlighten me?
> 
> Thanks and best regards,
> Kenneth Schwartz
> 
>