Answer the question
In order to leave comments, you need to log in
How to give the exact price to the customer with a large amount of work?
Hello!
1) Name the exact price, even if there are a lot of nuances and you have to work at a loss?
2) Name the range of prices from and to? As a rule, the customer has unnecessary questions (such as: why such a spread in prices? Can't you name the exact price (doubt about qualifications)? Etc.). Not the best option in general
3) Charge the hourly rate and say the approximate time. It's possible, but this option is not far removed from option 2.
4) My own version of
ps: my case is the layout of 15 pages, with a bunch of forms, validations, scripts, sliders, etc., etc. Typical project in general.
Answer the question
In order to leave comments, you need to log in
You count your hours +/-, multiply by the usual "error factor", and name the exact price. Take the error rate for at least 5 completed projects, this is the ratio of the initial estimate of your hours and actual labor costs. For IT projects, this ratio is usually 1.25 - 2.0.
Let's have three prices, a good script, a bad script and an average script, and three prices.
break the work into stages with payment for each.
write and sign with the customer TK. everything that is past the TK is considered as a feature request and is paid separately
Discuss with the customer in as much detail as possible the TOR for the project. Estimate how long it will take you to complete the project. Choose the cost of one hour of work based on your inner conviction "N bucks per hour will be fine." Multiply the number of working hours by the cost per hour. Tell the price to the customer :-)
As for "how to sign" - conduct all negotiations of this kind by mail. General points can be in the chat, but the draft TK and the cost can only be discussed by mail. So that in the correspondence it always remains - who, when, what he wrote, why he wrote, and so on.
If this is a typical project for you, then you roughly know your cost. The experience of past projects helps a lot when you write down how much time it took you to complete any task. For example, you have made 5 projects for which you have a plate with working hours. Main page 55 hours, feedback form 72 hours, contact page 19 hours, catalog 35 hours (conditional numbers, don't throw stones :) ). With such a sign, it is very easy to give more precise dates for the following projects.
And there is another option, you indicate to the customer your hourly rate, indicate the approximate time frame for the development of the project, divide the project into parts and record the time spent for each completed part. Payment is made for completed and approved milestones.
If the customer believes that this approach is wrong or dishonest, then indicate the approximate period of work on the project and fully invest in the deadlines, unfortunately to the detriment of the quality of work...
The customer is in the USA, the hourly estimate will be clear to him. For a small project, fork in hours inside and out.
If the customer needs a fixed price, absolutely no fork, and at the same time he is not ready to pay by the hour, there is a reason to refuse. This is a signal that there will be a sea of unpaid rework, which kind of refers to the "quality" of your work.
Is there a TK?
If there is and everything is written in it, then what nuances can there be?
Look through the technical specifications, if something is not clear, it is better to discuss it right away and then say the "exact" price, and all corrections from the technical specifications are additional payment.
Alternatively, take an hourly rate.
It looks like a big project. Therefore, this will be the most appropriate option.
The customer, as always, will ask to change something, redo it or something else, and until there is an ideal option for him, he will be reluctant to pay.
You say that if a miracle happens and everything goes like clockwork without sudden wishes and changes, then the minimum time is N. Then you say that most likely K * N can go to the project without any problems, and if a lot of things go not according to plan and there will be a lot of sudden Wishlist/cuts, then you can expect K*N*9000+. I don't know of a more truthful/realistic presentation.
No way. Work part by part. Divide as little as possible. Plus, prepare a detailed price list with prices for each sneeze. To this you estimate the estimated time and cost.
The usual misunderstanding of the task or someone's nervousness in coordination can bury the project at any stage. It's more about the ability to negotiate and find compromises.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question