5 reasons to refuse the client
I tried to make a list of reasons for the immediate refusal of the client to provide the service in order to save time and nerves: her own and her employees. I work for a company that has been developing websites and multimedia projects for many years. Over the years, she has come across various types of clients. Most often, of course, in the middle of working on a project, almost friendly relations are formed. But there are exceptions to any rule. "Complex" customers are called inadequate. I tried to highlight the characteristics of an inadequate client.
So,
1. The client believes that in the subject area, the specialists whom he turned for help understands more than them. In such cases, he gives advice on technology development, very often speculates that the manager called the exaggerated deadlines, the designer should use a particular brush, etc. This is an occasion to think about how many comments will have to endure, like: “I know, it's simple. Why so long / expensive?
2. The client believes that he has paid much more than what it is worth. This, too, is usually reflected in the nervous system of the manager. In this case, the client will never be happy with the result.
3. The client denies all offers and cannot offer anything in return. As a rule, this is accompanied by sharp remarks towards the developers: their talents and experience. It is unpleasant to anyone and not worth it.
4. The customer says "Do something, and then if I like it, I will pay." Most likely, such a client will not like anything.
5. The client does not want to discuss the proposed implementation of the project, citing the lack of time. This raises the question of how interested he is in the project. It threatens with large alterations justified by excessive autonomy of the company-developer. There are moments that really does not make sense to discuss with the client. These are technical details. But, for example, the structure of the site should still be discussed, of course, based on the ease of use of the site by representatives of the target audience, and not the son of a director.
So,
1. The client believes that in the subject area, the specialists whom he turned for help understands more than them. In such cases, he gives advice on technology development, very often speculates that the manager called the exaggerated deadlines, the designer should use a particular brush, etc. This is an occasion to think about how many comments will have to endure, like: “I know, it's simple. Why so long / expensive?
2. The client believes that he has paid much more than what it is worth. This, too, is usually reflected in the nervous system of the manager. In this case, the client will never be happy with the result.
3. The client denies all offers and cannot offer anything in return. As a rule, this is accompanied by sharp remarks towards the developers: their talents and experience. It is unpleasant to anyone and not worth it.
4. The customer says "Do something, and then if I like it, I will pay." Most likely, such a client will not like anything.
5. The client does not want to discuss the proposed implementation of the project, citing the lack of time. This raises the question of how interested he is in the project. It threatens with large alterations justified by excessive autonomy of the company-developer. There are moments that really does not make sense to discuss with the client. These are technical details. But, for example, the structure of the site should still be discussed, of course, based on the ease of use of the site by representatives of the target audience, and not the son of a director.
')
Source: https://habr.com/ru/post/43712/
All Articles