4 ms·
My flow adapted for this question: 1. Why do you need the estimate? Is it to get budget approval, or because you're trying to meet an approved budget? If they
by rrggrr 9y ago
My flow adapted for this question:
1. Why do you need the estimate? Is it to get budget approval, or because you're trying to meet an approved budget?
If they don't have budget approval then I'm going to charge them something to gather requirements and deliver an estimate.
No budget approval = low on priority list.
2. We charge a blended rate of $xxx per hour. If you have a detailed requirements list I can tell you if we can do this within your budget.
If they don't have a detailed requirements list then I'm going to charge them to provide one.
After I have the requirements list completed I'm asking for their budget.
3. Don't want to pay for a requirements list? I understand. Its okay. Something like this typically costs (low bid), but that will likely change if the requirements are different then my assumptions.
- jlj 9y agoCould you elaborate on #3? Do you walk away at that point? A last attempt to show the value of good requirements and get them back to #2, else they are premtively "fired" as a client? Going to hold onto these. Good phrasing/ideas.
- rrggrr 9y agoIn enterprise software, at least the companies I know, they will underbid and return to the well many times for increases. They will blame this on poorly scoped requirements, for which they were not responsible. They will be right, and they count on this for much profit. If you quote virtuously, you will be a victim of your client and competitors who scope/quote less virtiously.