Pitfalls in jumping ship to a client company?

Perspective context: Am CTO who has converted consultants to staff before.

There is nothing stopping you personally from changing roles like everyone says and non competes are not enforceable in California.

However B2B contracts usually don't have any such limitations, so there might be a liability for damages between the client and your current company. This is the main reason you need to raise this up to people who has insight into the contracts between client and your current company ON THE CLIENT SIDE FIRST.

Then, and ONLY then imo should you bring it up with your current employer to try to do it in a way that steps on no toes. You need to make sure that the client is allowed to do it based on the contract frameworks AND that they want you before you open that can of worms. It might also be beneficial to have the client be the one to approach your current employer in a gentlemans approach, especially if your client has access to higher up decision makers than you naturally have in your current job.

Then it's up to your current employer how much hell they wanna raise and your political manouvering internally and how you break the news will probably be integral to that. However as long as there are no regulation of this between client and current employer the only thing you might be doing is burn a reference bridge.

I haven't been in this situation, but I observed these situations where I worked at.

Make sure there are no clauses in your contract stipulating what they can hold you accountable for, if in doubt, consult somebody with a legal background. Consider that the relationship with the old company might be tarnished no matter how well you handle this.

In general, I would:

- Ask the client company directly, not by applying via posting, but by approaching somebody high-up who knows that you're consulting for them

- Disregard any HR rules or promises, the only things that bind you are the contract (where enforceable) and law (can't comment here)

- Make sure that the fact that you were a consultant (implied temporary relationship), doesn't put you to a bad start with the new company (ie. "we don't need this guy full time, he's only taking responsibility over something small")

- Carefully plan how and when are you quitting

I work for a consultancy in the UK. Occasionally someone leaves us to join a client. Our contracts with our clients prevent "solicitation" i.e. trying to encourage some to leave us to join them.

In practice we never use those clauses - it's almost always better to maintain good relationships and reputation with clients. Plus it's legal for our employees to move jobs to them, it's just the solicitation bit that's not allowed.

There was a case at my previous company (that happened before I was there) where a client that wasn't paying for work done, also tried to get the entire project team to leave and join them. They did this by emailing their work email address thereby handing us incontrovertible evidence of breach of contract. This was used as additional legal ammunition to force them to actually pay us. It never made it to court or anything.

Hey, I did this ~5 years ago! I was working as a consultant in client company's office (4 days a week) and they opened a position similar to mine there.

I contacted our legal team to ask about the no-compete cause but they told me that the client is not a competitor to my employer so no problem there. No mention about recruiting from supplier either.

Luckily all went well and the client company negotiated things with my employer. I have no idea what kind of compensatory deals they made behind my back as my employer was asking for an yearly fee for my service.

Getting the employers to negotiate about transferring a specialist worked for me, hope you find a solution too.

I've been really happy working for a client, handling multiple different clients was stressing me out.

In the old days accounting firms used to love it when their staff went to a client, they saw it as reinforcing the long-term relationship. I dont know if any of these terms have meaning in the modern era.

You're correct in your intuition that this will affect the business relationship. Would your potential new employer prefer you over the business relationship with your current employer? If no, this is a risk for you which could potentially lose you both job opportunities. In any case you need to discuss this with your potential new employer as soon as you apply.

Some managers are empathic if you are open and honest and you might try disclosing your plans to your current employer somewhat early during the hiring process. This might it less likely for the business relationship with the client (your potential new employer) to sour. Of course, there is the possibility it backfires. Depends on the relationship between you and them.

I have seen this done a few times without consequences BUT always after a pretty strong informal expression of client's interest.

You will need support from client company anyway, so I would start with an informal conversation with your team there. If that team wants you they can cut most of the interview process, too.

But there may be pitfalls: they may be contractually restricted from hiring you (not legally prohibited, but enough to make it a pain not worth it), etc. An informal conversation can explore options without your intent to jump ship leaking to your current employer.

The main thing to think about here is that your application is going to be back channelled to whoever manages the client account at your current firm. How will they react to this?

Other than the points already raised around the client's contract with your employer possibly containing clauses saying they can't hire you away without discussing it with your employer I would be worried about any NDAs you've signed.

You're going to be entering an environment where you're still talking about the project you were working on day to day, but now you'll be doing so with a client. If you can make it an amicable move by ensuring both sides are involved in the discussion you're probably fine, but if your current employer doesn't want you going I could see them making use of NDAs to severely restrict what you're able to do, even if just by forcing you to make sure everything you discuss in the new job is meticulously documented in order to cover yourself in the case of future legal actions.

As others have also said, get a lawyer (your lawyer - anyone hired by either your current or future employer isn't your lawyer, they are the employer's lawyer) to review everything before making a leap.

It is common for consulting or professional services contracts to include non-solicitation clauses. In other words, the client company may have already committed to your employer that they would not hire any of its employees for the duration of the contract and for some time after.

If you were not involved in the negotiation and signing of the engagement agreement, then you probably don't have any way to find out if the contract contains a clause like this. If it does—and even if it doesn't—the leadership of the team at that company may feel an obligation to tell your employer that you have applied for a job with them.

I worked at a small company where a vendor poached the team member that worked closely with the vendor.

The company was pretty bitter about it and switched vendors, and the CEO would often bad-mouth the vendor at speaking events with other small company teams.

Nobody was really nasty to the former colleague, although there was some light shade thrown their way as well.

You don't mention company size but if these are boutique shops or startups with sub 20 employees, and you aren't a role they regularly hire for, expect reputational damage to your new employer, you, or both in whatever sphere of influence your former employer has.

Consider whether you can do this move with everything above board. These two companies (and more importantly, the people working in them) have a business relationship to maintain. You want to be a positive part of that story, not the one creating problems for everyone.

Ideally, you'd want to be able to discuss this move openly with both the target company and your current employer and get everyone's blessing. If not, there's a risk that if the relationship between the two companies sours because of your attempt to move, you'll be the one thrown under the bus.

Your client may have a contract with your employer which would stop them from hiring you. I would ask around. In any case, you could always apply and they say no. Nothing ventured...nothing gained.

Depends on your reasons to be loyal to your current employer. Is it because they're really a great place to work at? Is it just to maintain some kind of arbitrary integrity? Is it the people, and if so, are they truly worth it and would they also choose to stay with you if presented with an attractive job offer? I think you might have encountered a pitfall already by believing you owe something to your employer.

While there may not be a clause in your employment contract there may certainly be a clause in the contract between your employer and the client that could possibly be more hassle than it's worth for the client.

The only way to know is to go through the process with the client, declare the possible conflict early on and let them research it on their side to see if it's worth going through with. Best of luck.

The only one who can answer this reliable is yourself, but you do need to ask the right people, which in this case, is not us. Just ask around. Nothing wrong with letting people know you have eyes open for other opportunities. It's only healthy.

If both teams are very involved, the word will get out anyway, so just be open about it from the get-go.

Rule of life: always ask.

I’ve always said no is the second best answer and in most cases the sooner you get a definitive answer the better.

Legal or not, it's possible current employer raises enough hell that the client says "not worth it." Now you've lost the new job and your current employer knows you're unhappy and less loyal than expected.

Maybe it doesn't go that sideways? But if it does, don't be surprised. Be prepared.

I did this and it was the best thing I ever did for my career. The contracting company was kinda neglecting the contract and the company I moved over was fed up. The company ended up agreeing to end the contract in exchange for my non-compete to be nullified.

I jumped ships to customer company and it proved great. That being said my non compete agreement didn't apply because there was 2 proxies in between so no direct competition. Better work agreement, also meant I could move countries, didn't regret it.

Contact a lawyer and / or the client company and ask about things. You - and the client company - can either just yolo and chance a lawsuit, or the client company can come to an agreement with your current employer and buy you out.

>> a role within that team which I would be absolutely ideal for

is the dual of that sentence true: is the position ideal for you?

Something I have not seen mentioned - just beware you might end up "stuck" at the new company doing nothing other than working with/on that very same piece of software you're currently working on.

They may never want to promote you or let you move to another team if you're "The Expert"(TM).

Were the people you know there in a position to recruit you?

If so, why didn’t they?

That’s where the footguns rest.