Preparing a web quote (or, in general, a quote for any task that is not perfectly defined and in which unforeseen events may arise) is hard work (for some it is an art). On top of that, the quote is supposed to be fair to both parties. Of the many options and theories we have read over the years, there is one that has seemed especially fair to us, although perhaps difficult to put into practice. The main idea was discussed in a hangout about quotes in agile methodology, on the tacande blog. Here is the approach we put to you based on what was said there:
\nAbsolute honesty is assumed on both sides.
\n1. The provider (in this case, the team building the website) works for x weeks. And assesses its cost (materials, hours, profit percentage). Let's suppose the provider has worked for three weeks and that this cost is assessed at 5,000 euros.
\n2. The client estimates the value of the product produced in that time. Let's suppose that, for the client, the product developed provides value of 8,000 euros. Or 3,000 euros, to give both examples.
\n3. And here our doubts come in, along with the question we put to you. How much should the client pay the provider? Should we charge for our work or for the value of what we deliver? What happens if we develop a technology that allows us to deliver something of great value with very little work on our part? We leave it open; we look forward to your opinions.
\n- \n
- Agile quotes in web development: what nobody tells you! (on tacande.net) \n