Good Quote, Bad Quote
-
Hey all, I'm interested in opinions on how you handle quotes that go wrong. Specifically, when a quote is too low, something is missed, the work will take longer than expected, etc. You've signed a contract with the client for X functionality at X cost. If the quote was wrong do you just suck it up, complete the work and learn your lesson for the next time? Do you go back to the client to attempt to adjust the quote to get additional money? Do you go back to the client to attempt to adjust the timeline so you can avoid a month of overtime nights? All opinions welcome. Thanks.
-
Hey all, I'm interested in opinions on how you handle quotes that go wrong. Specifically, when a quote is too low, something is missed, the work will take longer than expected, etc. You've signed a contract with the client for X functionality at X cost. If the quote was wrong do you just suck it up, complete the work and learn your lesson for the next time? Do you go back to the client to attempt to adjust the quote to get additional money? Do you go back to the client to attempt to adjust the timeline so you can avoid a month of overtime nights? All opinions welcome. Thanks.
You should include language in the quote that states what additional costs may be and who pays them. This does not, and should not, protect you (or them) from you totally blowing the estimate though, as in bidding 10 hours for something that should take 50.
only two letters away from being an asset
-
Hey all, I'm interested in opinions on how you handle quotes that go wrong. Specifically, when a quote is too low, something is missed, the work will take longer than expected, etc. You've signed a contract with the client for X functionality at X cost. If the quote was wrong do you just suck it up, complete the work and learn your lesson for the next time? Do you go back to the client to attempt to adjust the quote to get additional money? Do you go back to the client to attempt to adjust the timeline so you can avoid a month of overtime nights? All opinions welcome. Thanks.
Thanks for the opinions. Some good points so far.
-
Hey all, I'm interested in opinions on how you handle quotes that go wrong. Specifically, when a quote is too low, something is missed, the work will take longer than expected, etc. You've signed a contract with the client for X functionality at X cost. If the quote was wrong do you just suck it up, complete the work and learn your lesson for the next time? Do you go back to the client to attempt to adjust the quote to get additional money? Do you go back to the client to attempt to adjust the timeline so you can avoid a month of overtime nights? All opinions welcome. Thanks.
You’ve signed a contract; you need to honor it. If it’s not physically possible you had best confess early and make the necessary adjustments. If you bid high and it was accepted you are lucky. We are all unlucky at times so try to leave a little slack. I bid $2000(US) on an embedded project “for a useable system.” I knew I was the only bidder and going much higher would cause the bid to be rejected. Part of the project involved compiled in control scripts. Editing these scripts on this system was needed. But the system was usable without script editing. I got an extra 1.5K. I ended up working for over 300 hours on the thing but even that low rate was better than nothing. And it put an interesting item in my resume.