How to quickly and reliably close tasks on the site without hiring a programmer?

Question

Project management

Stable, once a month there are 2-3 small tasks on the site. (Bitrix, wordpress, tilda) A total of 30-40 hours. The budget is also 30-40 tr. (like average)

- It's not smart to hire a programmer for them, I won't be able to load it in full time
- Every time I'm tired of looking for a freelancer. The task is being completed, but you can no longer count on the completion of the next task in a couple of months. Busy, unresponsive, or able to pick up in a couple of weeks.
- Signing contracts with companies and then procrastinating each task is also a proven stage, it's difficult.

How do you deal with this if you find yourself in such a situation? Am I the only one suffering like this?

Answer 1

I am writing as a programmer. I have a number of old clients who sometimes wake up and ask to finish something. I try to find time for them and help.
The ideal solution for you would be to find a stable developer who understands everything well and is ready to periodically take on a part-time job.
There is one point - it is usually easy for a developer to take a part-time job 5-10 hours a week. But you should not expect that a person will give up everything and will have full-time sausages for your tasks all week. If you want to make a large volume quickly, then you have to hire a new one every time. And if you can break the volume into small parts that can be done without breaking away from the main work, then you should be able to hire such a person.

Answer 2

Могу ответить с точки зрения фрилансера:
Если через пару месяцев сложно рассчитывать на работу, значит у вас есть какие-то проблемы в организации работы. Например, с вами психологически тяжело общаться в процессе или вы не спешите оплачивать работу, задерживаете оплату и т.п. Если человеку стало некомфортно с вами работать, он обычно доделывает текущую работу, но дальше с вами работать никогда не будет — будет только придумывать отмазки, что сейчас завален работой или тому подобное. Напрямую такие вещи высказываются очень редко.
Вот несколько советов, которые помогут улучшить «возвращаемость» фрилансеров:

• Most often, a freelancer is ready to do the job right away (especially when working with you for the first time), he shows zeal and does everything very quickly. It is expected of you that you can pay for the work instantly after everything is done and checked by both the freelancer and you. If you tell a freelancer that you need some time to get to an ATM and top up your account because you can’t pay right now, this will spoil the impression very much, and most likely the person will not show his mind, calmly wait without psychos when you tell him pay, but next time they won't work with you anymore. A freelancer is ready to work right away, which means you should be ready to pay right away.
  
• If you have low technical background, and apart from the code itself, the freelancer has to communicate with you a lot about what exactly needs to be done, the desire to work further also disappears. The less discussions and phone calls are required in the messenger, the more likely it is that the freelancer will continue to work with you. Freelancers usually do not consider correspondence as part of paid work and, accordingly, the longer the correspondence takes, the less will be the desire to continue working. A freelancer usually wants to do the work right away and not be distracted by any free chatter.
  
• If a freelancer needs to deal with the administration of your server in addition, and this was not discussed in advance, this can also spoil the impression. Often, customers write that they need to fix the menu on the site, and this eventually turns into editing the menu, and then uploading the code to the site, setting up and restarting the server, and some other similar work that was not in the task at all. And, most likely, you take for granted that a freelancer should be able to do this, and you think that this is a normal practice if he does this in addition to coding. Additionally, if these moments are not yet paid, the chances that people will want to work with you further decrease even more.
  
• Some customers like to show their authority. Remember that for a freelancer you are not a boss, but an equal partner, and he expects an appropriate level of communication from you. If you pretend to be the boss, people will come up with all kinds of excuses, but they will not work again.
  

These are the main factors that affect how a freelancer will respond to you the next time you need help and decide that you can turn to someone you have worked with before.

Answer 3

Well, this is a market, everyone wants to eat, a freelancer will not wait half a year for what may or may not arrive from you, an order for 40 hours.
Therefore, the whole world has long been divided into "subscribers" and "designers".
If you need periodic work, then you conclude an agreement under which the contractor reserves for you +/- a certain amount of time that you can choose within a month, or, by analogy with the Labor Code, pay the employee a downtime.
If you need a one-time job, then roll out the TK and wait for one of the "designers" to freely respond in order to fully immerse yourself in your task.
Therefore, analyze the market and consider what is more profitable: split tasks to fit in +/- 10 hours per month and have a permanent person who has these 10 hours on the schedule and who, already knowing the architecture and state of your project, will quickly do everything. Or, for each one-time task, hire a new specialist and pay extra each time 5-10 hours for "injection into the project", because, yes, the "project manager" is now sitting on a 40-hour work similar to yours and has already agreed another 40-hour work next week, and yours, respectively, will be able to take it only at the end of the month, if it doesn’t turn up more profitable.

Answer 4

You yourself answered your own question in the question, there are no more options, full-time, freelancer, the company of the
Second and Third can be taken for fixes to support the project so that they have time

Answer 5

most often, you need to keep in touch with the developer. so that he, when necessary, rules.
to look for a new one every time, it is time-consuming and the effectiveness is in question.

Answer 6

Conclude a contract with a 1C company for maintenance.

Answer 7

It is difficult to find a person who is ready to immediately allocate 30-40 hours, at your first request. Yes, at least 10, so only novice freelancers are ready to work.
The closest solution is Kwork. Split better tasks for a quick start, sooner or later you will find a person who will be ready to work in this mode.

Answer 8

I can see why you won't succeed. Tilda, VP, Bitrix - this is cocoa with tea.
And if the tilde is in the VP database, although there are still much fewer specialists in block design than we would like, then Bitrix is ​​a separate completely fucked-up universe of 1SSovtsev. It is impossible to find specialists who understand how the same simple, at first glance, feature is made both on one and on the other system. In order for such tasks to be solved within limited budgets, it is first necessary to standardize the infrastructure as much as possible and get rid of everything except the necessary minimum.
Next, you need to realize the minimum pipeline, because it still won’t work to load both the layout and the front and back on one artist. You need to at least understand which specialist is needed for which task. Further, it’s already realistic to try to find a person who understands the stack of technologies used, and only then, after some time, he will remember how your projects are arranged. Separately, you will have to try so that at the same time he is not a narcissistic asshole. Recently, problems have come from just this area.

Answer 9

The biggest part of the problem lies in the fact that specialists are needed for each site and for each task are different. I understand that one person cannot be a Jedi in everything. At the very least, he will do something very badly.