question for web developers - sample quotes?

[bluesea]

I am about to prepare a quote for an intranet site for a local company. They didn't provide a detailed spec, I had to speak to them to find out all the requirements.

The site will need admin section for adding editing users, etc, forms for adding details to database, reports section, document store etc. The site will be hosted internally on their server.


I have never done a paid wed development job before however I am confident I can do the job as I have developed some databases before in php/mysql.

My question is, how would you supply the quote.
Should I provide just a quote with a price for development, support, etc or should it go into detail about the design spec, languages used, sample screen layouts, etc?

Thanks

[Dwebs-Ltd]

My question is, how would you supply the quote.
Should I provide just a quote with a price for development, support, etc or should it go into detail about the design spec, languages used, sample screen layouts, etc?

Thanks

Don't do what I did on my first network quote, I spent 4hrs detailing exactly what would be done and purchased. The company then went to another more experienced IT company and gave them the documents I created and gave the job to them. Then after the other company implemented the system they asked if I would support it. You can guess the answer!

Simple, give them a figure and what they get i.e. basics no detail. Then if they are happy with your quote and decide to proceed you create a detailed document with exact specs and make them sign it to confirm their requirements and what they are getting.

[NextPoint]

You also need to take into account that clients nearly always 'add in extras'. Be careful how you word your specification agreement - ambiguous wording leaves you at risk of being exploited of providing ABCDEF when the original deal was to provide ABC - this can happen whether the client has either good or bad intentions. When specifying your agreement/proposal, always define a feature like "The system will have X feature, specifically allow the user to achieve ABC - should further requirements for features like, but not limited to, DEF, an additional agreement can be drawn between each parties for the required additional maintenance...".

[matt.chatterley]

Simple, give them a figure and what they get i.e. basics no detail. Then if they are happy with your quote and decide to proceed you create a detailed document with exact specs and make them sign it to confirm their requirements and what they are getting.

And as/when you DO prepare detailed documentation, make sure you've allowed for this time (and time spent making revisions based on feedback) within your quote.

Although a good spec will save you a lot of work (and tears) later on, it's still work, nonetheless - if you quote "two days" for a project, but the spec takes 4 hours.. well.. you've lost out quite a bit there!

[bdw]

Be careful how you word your specification agreement - ambiguous wording leaves you at risk of being exploited of providing ABCDEF when the original deal was to provide ABC

Absolutely, there's a discussion about "scope creep" here, http://www.ukbusinessforums.co.uk/forums/showthread.php?t=105749&page=2

[Peter Bowen]

You might also want to specify what is outside the scope of the contract.

[Place of design]

I am about to prepare a quote for an intranet site for a local company. They didn't provide a detailed spec, I had to speak to them to find out all the requirements.

The site will need admin section for adding editing users, etc, forms for adding details to database, reports section, document store etc. The site will be hosted internally on their server.


I have never done a paid wed development job before however I am confident I can do the job as I have developed some databases before in php/mysql.

My question is, how would you supply the quote.
Should I provide just a quote with a price for development, support, etc or should it go into detail about the design spec, languages used, sample screen layouts, etc?

Thanks

I would provide an "Estimate" not a quotation. Cite the estimate is based on your limited discussions so far. If in principle they broadly accept the estimate, then you will shedule in a more detailed meeting, and provide a more detailed quotation down the line

In this way, you dont do a pile of "thinking" now which is then handed to the next company to undercut you with

It is good practice in web development to produce a roadmap. Indicate that this will be the next stage, once they have you onboard. if thier requests then pull you away form the original estimate, then supply them a new quotation for the additional requests

The roadmap principle is sweet. They see you are managing things and "on track" and you know what you need to do next

If you integrate this with "phased payments".. complete and sign off phase 1 of the map, you get paid for phase 1 etc. In this way you are further minimising your exposure to job creep and not being paid for a lot of work

[ayqazi]

In terms of 'scope creep', I would probably encourage this as long as the work being added is balanced by work being taken out!

This is what agile development methodologies were invented for - encouraging scope change during development, because we can't all predict the future. http://www.coactivate.org/projects/agile-contracts/money-for-nothing-change-for-free (http://%5bb/)

Since I'm just starting out, I quite frankly don't mind if I give someone a detailed quote, and then they go to another IT company to implement what I told them. They wouldn't have used me anyway, I end up getting some requirements gathering experience letting me quote future customers faster, and at least I got my name in the door. Hopefully the other IT company will mess up and they'll come running back to me, or at least pass my name onto their friends.