When asked for a ballpark #, I always shoot to the high side. As you've learned here, people are more shocked when you come in over estimate than if you'd have came in under. If you'd come in $200 below the low end of your estimate, you'd have had no grief from the client.It was not a hard estimate that I gave him. He asked if I had an idea what the cost would be and I said "Anywhere from $1,500 to $2,000 but I will have to run the numbers to know for sure. The actual amount came out to around $2,200. Would you have eaten a couple hundred dollars based on that answer in that scenario? I would not have thought that anyone would hold me exactly within those parameters but maybe that is something I should take into account next time.
So he's an employee releasing confidential information?Intellectual Property. If something happens like an employee takes files with them and goes to a competitor, and you claim the information is confidential, you better not have released that type of information without at least a confidentiality notice, otherwise there's an argument that the whole class of information is not confidential, due to your established practices.
The implications go way beyond sending a few numbers to a client.
The IP involved in programming is but a tiny slice. I should have made a broader statement, since trade secrets, customer lists, contracts, etc are broader than IP. The may or may not be covered by IP laws, but they are covered by additional laws as well.So he's an employee releasing confidential information?
I do enough programming that I'm quite familiar with intellectual property.
If it's his company he can disclose all he wants no?The IP involved in programming is but a tiny slice. I should have made a broader statement, since trade secrets, customer lists, contracts, etc are broader than IP. The may or may not be covered by IP laws, but they are covered by additional laws as well.
Ive had to explain to people that I don't get the materials for free, that I wish I did, and I would give them a hell of a price if I did. They think because you're a contractor you get the materials for less than half the cost. It's funny.I wont do itemizations. once in awhile ill break the labor and materials down, but I have gotten away from that as well.
People seem to think that I pull up to the back door at Home Depot and the store restocks my truck for free.
remember, your a contracotr / small business owner. you are a rip off, your rich, and are out to screw over everybody.
wierd.. everyone bitches about the hacks, no one ever mentions that ******* customers we have to deal with
I'll do the same. Saves me some time. I try to go high though and I explain that I can't be held to it because it's off the cuff. Eliminates some lookey Lous that have no idea. Nothing worse than giving someone a bid for 12k and the customer telling you they thought it'd be like 5k. What a waste of time. That 5k might cover the materials, but I don't work for free unless your immediate family.I give rough estimates fairly regularly to weed out people who can't afford me but it's safer to say something will cost "at least XX" and only provide a minimum. Never limit your price before you've done the math.
Also, I agree that you shouldn't have apologized. If this happens again, address the overrun in your proposal so they don't need to ask you about it.
The United States of America is clueless about IP. My favorite part of every movie is the Copyright notification at the beginning. :no::no::no:I see you're clueless about IP law.
Why?I still do not agree that I should have been held to the top of the $2,000 mark .
The way I read it is that Joseph gave them an on-site guesstimate, then came back with a final quote later, before doing any work, before any commitment was made. That's not the same as doing the work based on an estimate, then charging more than estimated.Why?
If you give an estimate telling the potential customer that the project's cost could be as low as $1,500 or as high as $2,000, why do you think it's ok to go past that amount - WITHOUT - FIRST - NOTIFYING THEM OF UNFORESEEN CIRCUMSTANCES.
What if they simply didn't have the extra money?
I know it's so difficult to give accurate estimates, especially when we're referring to things sight-unseen. But, I usually explain that prior to.
I am about to replace some leaking windows tomorrow, water damage, etc. I explained that the price could be higher depending on what I find once I open the wall. I explained that to the customer during our initial meeting and I'll reiterate it again tomorrow prior to starting. I also explained that I will keep them informed throughout to avoid surprises.
I have given a customer an invoice which was higher than my estimate - without warning or prior authorization. But, I felt as if it was wrong. I wouldn't like it done to me.
I understood it the same way.The way I read it is that Joseph gave them an on-site guesstimate, then came back with a final quote later, before doing any work, before any commitment was made. That's not the same as doing the work based on an estimate, then charging more than estimated.