Answer the question
In order to leave comments, you need to log in
How to remove the risks of luring a developer to T&M and outstaff?
Hello! For many days I have been struggling with the issue of safe leasing of personnel (T&M or outstaff) in the IT field. Tell me who knows.
We are an IT company and create custom software. Often we are asked not to create software, but simply to rent people on a T&M payment scheme, or in general for outstaff. In this case, the developer has direct contact with the customer and the customer can easily lure him away by offering slightly better conditions. Now we simply refuse such orders and lose leads, but I think how to remove these risks. We have a small team of professionals, and the loss of even 1-2 best developers will hit the company's business hard. We nurture developers ourselves, and give all the conditions that we can - flexible schedule, interesting tasks, technologies, etc., but we cannot pay like top companies.
Tell me who knows:
1. In practice, the customer often lures people to him or does fair play work?
2. What methods exist to remove the risks of poaching?
Answer the question
In order to leave comments, you need to log in
As far as I know, they usually just include a clause in the contract that for a year (for example) the company cannot hire a person directly.
If the developer wants to run away from you, he will do it.
If he's still working with you, then he doesn't want to.
If you don't pay like top companies, then the transition from your firm to a top company is a matter of time, and I would not even say that it is very long.
a chair, a rope... but seriously, the answers are in your question. If everything is so bad, then you need to change something, if not everything is so bad, then there is somewhere even worse, which means you can poach yourself from there? Yes, and top companies sometimes run notably despite high salaries. Do not look at this as something bad, see your benefits from such nomadic specialists
Why does Letual or Lukoil need a Sharepoint developer?
Ask yourself this question. In theory, you should have a "clearing" for your developers. New projects, learning new features. In general, an eternal holiday with a corresponding reward.
Well, do not lose touch with the departed. From experience I can say that you see many long-running projects 2-3-4-6 times.
You know everyone, on occasion you are interested in why they messed up like that.
PS cookies and a young creative project hammer in nails, better with money and go ahead.
No way. Let them pass. These are petty customers. A normal client prefers to work with legal entities.
what CRM do you do? ))
look at MoneyBall, but there is no direct universal solution,
but at least move away from the incubator model
It is possible to probe candidates for the love of permanence more carefully. If a person is even a little inclined towards it, he will leave quickly, but there are those whose hands itch all the time, who want to move from project to project and delve into something new. You will pull the second horseradish. Well, plus remote work, some are ready to lower salaries for the sake of remote work. Our contractors are mostly remote workers now, and if we covet them, we offer a move and a 5/2 office. But they don't want to.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question