Employers need to know what their assets are, what they own. It greatly simplifies things for them if you have a contract that assigns them ownership of any invention you come up with while you’re their employee. This is especially true in early stage companies, where the business model might be evolving, and employees are working all hours from all over the place. Contracts like this are very common.
The best approach in this situation is to use your own computer and network to develop the core ideas for your business, but delay any formal business activities until you’ve left your job.
IANAL either. But I do know that in most states it doesn’t matter if it’s your own time and your own PC. In California there are exceptions, I if your work has nothing to do with your employers business. Washington State has fewer exceptions but there are some, IIRC (but remember IANAL).
Also, if this project does relate to your employers business then quitting won’t solve your problems. You will need to quit and then do no work on it for six months, typically, to be free of the their legal ability to claim they own it. And regardless, they can still sue you: the six months break just gives you a better negotiating position.
If this project has any value, consult with a lawyer.
Below is an excerpt from my contract:
We understand that lots of our employees have tech related ideas that they work on outside of working hours. In a case where your idea overlaps or conflicts with the work of said company, you agree to the following:
1. You will promptly provide to said company, and otherwise keep confidential, full written details of all inventions, copyright works or designs originated, conceived, written or made by you, alone or with others (“Intellectual Property”), and work relating to Intellectual Property that you have worked on at any time during the course of your employment with said company which relate to, or are reasonably capable of being used in, the business of said company ("Employment IP"). Unless otherwise agreed in writing by the CEO, you are assigning said company absolutely all rights, title, benefits and interests in the Employment IP. The reason for this clause is to protect the Intellectual Property of the Company from infringement or misuse that may damage the position of said company in the market or our ability to serve our clients.
2. You hereby assign to said company with full title guarantee by way of assignment all present and future copyright, database and design rights and other proprietary rights (if any) for the full term of such rights throughout the world in respect of all Intellectual Property and you waive in favour of said company all moral rights conferred by Chapter 4 Part 1 of the Copyright Designs and Patents Act 1988 and all similar rights in other jurisdictions.
3. You irrevocably appoint said company as your attorney to execute any instrument and do any such thing for the purpose of giving to the Company the full benefit of clause 1.
----
I could probably last 3 years or so with no other revenue streams. There is no rent or mortgage payments needed as I bought a cheap property that is now paid in full. That was part and parcel of the preparation for leaving fulltime employment, to give the startup / product development an attempt on my own and ensure that my runway could go further if needed.
I do have a lengthy notice period, but that is priced in. Also if this venture fails, I will re-enter the market as freelancer to pick up where I left off. Also forget asking the CEO about it or personal assistent, the're far to busy to be concerned with a "tin pot / pie in the sky" idea / product.
I just don't understand why founders, and those advocating for the startup life don't provide advise in this thorny area as it affects so many of us?
Do folks go dark, build in secret, pretending they had executed their plan outside of the course/term of their employment?
I have advised others is to perform research round their ideas by upskilling in areas that they'll need to prove out their ideas. This I hope will minimise the time to build (once departed) without establishing real intellectual property whilst employed. Perform spikes and mini experiements with the technology, without building the final idea and upon departure begin the actual build.
Wondering if folks consider that a sensible strategy or could iterate on it?
Keen on your thoughts.
IANAL, but it seems pretty clear to me - as long as your idea isn't related to their work, you are in the clear. Keep in mind that the software you write is not the "work of said company" - it is just a tool. The solutions they solve in the markets to which they sell are their work. Do side gigs in other industries and you should be fine.
I was warned during onboarding of my last few jobs that most software side projects would fall under their umbrella of "related business" and that their lawyers regularly aggressively pursued side projects. Who knows, maybe they were bluffing but I'm not willing to go toe to toe with 2,000 corporate lawyers to find out.
> Do folks go dark, build in secret, pretending they had executed their plan outside of the course/term of their employment?
JIT does seem to be more common than AOT. People do the early work in secret and delay the hard decisions until they absolutely have to be made. Most of the time the whole thing unravels before that point anyway, and all the agonizing about quitting was pointless.
"Unless otherwise agreed in writing by the CEO"
This sounds like a conversation.
If they accept you go through the red tape of having your idea declared as exempt and you are fine.
If they don't accept you need to choose between your current employer and your ideas.
I tend to choose employers and contracts based on whether this is doable or not.
Usually there is a business process to declare outside interests that involves approvals from your direct manager and his manager and doesn't require you to talk to the CEO directly.
They keep a central register of declarations that the CEO rubber stamps.
Maybe you can ask HR/Legal about getting that instituted.
If this doesn't work it might be a clear signal that your current employer might not be aligned with your long term goals.
This is usually when you're on company time with company assets. If you're at home/coffee shop and off the clock and on your assets/pc its your IP.
Do you have a contract with current employer that has this specific language? I would understand a term for a non-compete agreement, but what you're saying does not sound right/legal from my perspective.
> I'm considering leaving a very well paid software developer job to free myself of this obligation
Do it!
It might take 6 months, a year or longer to make a profit. Can you afford that? Do you have other revenue streams? Does your current employer contract bind you to any terms if you quit?
Questions I don't need to know, but you should.
Good luck!