Ask HN: Why will companies hire you, but not buy code from you?
I run a little consulting business that makes bespoke software. I also get headhunted a lot. When I tell the recruiter that I am not interested in working for them, but I would be happy to sell them the same deliverable I would make for them as an employee, they are not open to this. Why do companies operate this way? Why do they want to pay you 10X (or whatever multiple it is) what that deliverable would cost in salary, rather than just paying you X for the thing itself? This makes no sense to me.
8 comments
[ 1.8 ms ] story [ 31.3 ms ] threadYou are anyway talking to the "wrong" people.
A recruiter is generally an external consultant that has nothing to do with the actual company, he/she is tasked to find candidates for a role (and nothing else, and they are paid for providing these candidates only).
And they won't give you a contact to the company, let alone to the people inside the company that can overrule a taken decision "let's hire someone to do this" with an alternative.
If you manage to get to know the company they are recruiting for AND you manage to speak to its CTO (or whomever takes this kind of decisions) then you might have a chance to propose the alternative of just buying the code.
I believe that the decision process - generally speaking - is not "let's think how to solve this problem":
1) let's see if anyone already invented a solution and is willing to sell it to us
then if above doesn't produce results:
2) let's hire someone to solve this problem
It is directly "let's hire someone to solve this problem" or directly "let's see if a recruiter can find someone to hire that can solve the problem".
For their IP, companies like "clean" assets -- stuff developed by employees on company systems. This is also true from an operational standpoint (if they want to customize or integrate with other in-house systems), they'd rather be able to do that in-house.
I worked in-house for a company that would literally spend waaayyy more time/money on building tools than licensing or buying them from somewhere else just because they didn't want to deal with the risk/headache.
If your bread and butter is implementing projects for dishonest cs students, that would make a lot more sense.
Ok, I'll be honest, I never thought of that. Thank you.