Is it worth using little-known technologies in development to "bind" the customer to yourself?

Question

Freelance

Actually, subject. Suppose the development is using a little-known framework written in a not very common language. In this case, it will be difficult for the customer to find another person to support the project in the future, and therefore, most likely, he will have to work with me. Which is guaranteed to provide me with work with regular customers. What do you think about this issue? What are the pros and cons of this approach?
UPD: Thanks guys! I realized that this approach is wrong)

Answer 1

It is necessary to bind the customer to yourself not by using specific technologies, but by quality and service.
From experience, the cost of developing projects of this kind is much less than the cost of their annual support. Accordingly, if they want to get rid of you, they will find a person who will quickly rewrite everything from scratch.
In addition, there is the question of reputation. A satisfied customer tells 1-2 people. Dissatisfied - 10.
This applies to any gray methods in general. You can also encrypt the source code, which is too embarrassing.

Answer 2

The main disadvantage that will stop many from using the approach is an adequate customer, who will not work with you at least a little "in the subject". Gain inadequate and will suffer with them happily ever after. At work, but...

Answer 3

Another disadvantage - working according to your scheme - customers who cannot refuse the contractor, you will eventually begin to slide into laziness, boredom, unreasonably high needs with complete unwillingness to strain for them. Since there is a client, he will not go anywhere, which means that you can afford anything.
In the end, the client runs out of money or a project, and you are left with your ambitions, without knowledge of languages ​​that are relevant on the market, with experience in an environment / language that no one needs, and most importantly, you are already used to being given everything for beautiful eyes. As a result, they only framed themselves.

Answer 4

If you have a good relationship with the customer, then it will be extremely difficult for you to get rid of him. And sooner or later the project can get bored. And this is IMHO the main problem of the approach. And you can tie it in this way, I saw a couple of tied ones myself. Strange as it may seem, people were proud of being attached.

Answer 5

Плюс для вас - уже описали. Вы будете окружены неадекватами.
Минус для вас тот же.
Плюс для заказчиков, что вдруг им этот пост попадется на глаза и они заказывать у вас не будут никогда и ничего.

Answer 6

Если вы пишете огромное приложение пусть даже на php (по которому специалистов разного уровня более чем дофига), то никто просто так менять человека на поддержке не будет, ибо даже чтобы въехать в проект нужно время, да и нюансов новый человек знать не будет.
Если вы пишете небольшое приложение, то его накрайняк перепишут с нуля, какую бы вы технологию не использовали.

Answer 7

Начнём с того что если вы захотите избавится от заказчика то сделать это так же не сможете. Если просто пошлёте его то карма у вас будет плохая. И вообще не считайте себя умнее других ))

Answer 8

Плюсы и минусы тут идиотизм.