My buddy Marcus called me up, almost in tears:
“He won’t give me the GitHub passwords.”
His Lead Developer has held his code hostage and was asking for 10% of the company.
It was either that, or go the legal route, which wasn’t any more appealing.
Marcus broke one of the cardinal rules of working with a team:
“It doesn’t matter who the person is. If they touch your system in any way, shape or form, you need an agreement.”
Marcus had known this developer for years.
He didn’t think he needed an agreement.
I’ve seen this happen so many times, I advise all my clients to get an agreement.
Even if they shared Capri Sun’s on the bus to kindergarten.
There are 5 main ways I’ve seen a team but a Founder’s company at risk.
Watch below for the other 4:
5 Essential Steps to Improve Your Business Security – Score 70Apply for a free growth session today >>>
If you follow these 5 rules, you’ll avoid most of the problems I see working with a team.
Some of them are obvious.
You might even say, “Dan, not me. My team wouldn’t do that.”
Problem is, your team might have the best intentions and not even know they’re putting your company at risk.
These 5 team “commandments” will keep you safe and prevent a lot hair pulling.
Keep growing your team, just make sure you put these 5 rules into place.
What are your rules for working with a team?
Drop ‘em in the comments, would love to hear from you 🙏🏼
Dan “saas protector” Martell
P.S. I’m curious…
If my team showed you exactly what to do to get to $100k MRR, would you roll up your sleeves and do it with us?
First we’ll build a custom scale plan for you, then give you all the playbooks you need.
We’ll even keep you accountable to make sure you stay focused.
