Easiest way to modify LLC control? I need to create a two member LLC. Initially the LLC will need to be fully controlled by one person, but in the future control will have to change to be 50/50. What is the easiest / safest way to accomplish this? Make one member a 10% owner and the other 90% and then shift to 50/50? Or do 50/50 ownership at the start and use an operating agreement that specifies 90/10 control and then file a new one to 50/50? Both partners are happy signing any type of updated operating agreement or form to change ownership from 90/10 to 50/50. Trying to figure out which method is easier. Thanks in advance!
First - do it all with an operating agreement in writing; always - no exceptions! Second - what you are describing in fairly simple for any competent lawyer to draft. The voting section of the operating agreement needs to include a provision stating something to the effect that until a Trigger Event occurs, Big Member will have 90% of the voting power of all membership interests; following the Trigger Event, Big Member and Little Member (assuming no other members join the LLC in the interim) will each own 50% of the voting power. The operating agreement (including this provision) is executed at the inception of the LLC, and will be self-executing, that is - when the trigger Event occurs, voting power should automatically shift without the need for any additional action. Have your lawyer make sure there's no hitch in the applicable state LLC law; that equity interests don't shift on the Trigger Event (that would cause tax problems) and, of course, don't forget to (very clearly) define the Trigger Event....
This is neither unusual nor illegal, assuming that the buyback price is specified in the agreement. If your friend does not wish to take advantage of the "nice discount" he can decline the deal, and decide for himself whether he wishes to buy shares without restriction, at the market rate. (It would be interesting to know what happens if he sells his shares and then leaves the company. I am fairly sure the agreement will cover this, but requiring an ex-employee to buy shares and then give them to the company could be considered unconscionable. That might be worth asking a lawyer about).
are there any safeguards you could take to preemptively block such behavior, such as a disclaimer inside the book cover that reads something like The safeguard you outline would be overridden as soon as the author enters any contract that requires assignment of copyright. (I would not delve in the differences between licensing and copyright assignment because that hypothetical author is dealing with a contract of adhesion which readily requires assignment; the author has no option to change the ToS to allow for licensing only) Under contract law, one of the essential prerequisites is that the conditions of a contract be entered knowingly and willfully. By deliberately clicking on a ToS page to move forward with the uploading a copyrighted work, the author is signaling his awareness and acceptance of the ToS. The fact that the author chose not to read the ToS is irrelevant and very unlikely to strike whatever entitlements the website owner formulated in the accepted ToS. For the same reason, the author's safeguard disclaimer does not bind the website owner: It cannot be said that the website owner was aware of that disclaimer at the time of the formation of contract between the author and the website owner. That is, the website owner did not knowingly and willfully accepted the author's safeguard. The website owner is not even expected to know about any safeguards which one of its potential user intends to establish. The length of a ToS document is also irrelevant because the website owner has the valid argument that "the user-author could have skimmed through the ToS or do a search (via Control-Find) of keywords such as 'copyright' or 'property', whence any allegation of 'inadvertent' assignment of copyright is untenable". Is there a way to protect your IP from inadvertently being licensed/stolen/assigned via TOS "agreements", without having to waste your life reading huge one-sided online "contracts" that are "subject to change without notice" anyway? Yes. That consists of not uploading one's works in such platforms. In contract law that would be expressed as "declining an exchange of considerations". There are many other alternatives for an author to promote his work without being required to assign copyright.
If your LLC made 300K before paying salaries, and paid 300K total in salaries, that seems quite reasonable. You might have a point if the order of events was: LLC pays 100K in salaries, LLC gets sued for 200K, LLC raises salaries by 200K. Note that the owners have to pay income tax on 300k earnings, plus whatever else employers and employees have to pay. And an LLC doesn't pay salaries to owners, it pays salaries to employees who be sheer coincidence are also owners. It's a different matter if the company pays dividends. A company must keep dividends low enough so that it can run its business, including paying damages for lawsuits that it knows about. So if the company planned all along to pay 300k in dividends, then is sued for 200k, they likely have to reduce the dividends.
The shareholders can change who is the company director, but the company director runs the company (until he or she resigns or is forced to sign by the shareholders). So the company director is who has the say what happens in the company. If the contract is between Fred and John Smith directly, then I would expect John Smith to give the orders and to pay Fred. However, Tom is company director, so he can order Fred to stay off the company premises. He can't order Fred what to do, since there is no contract between Fred and the company, and the company won't pay Fred if it doesn't want to - it's up to John Smith to pay Fred from his own pocket. The whole setup is highly unusual. I would assume that the situation is unsatisfactory for everyone involved, so likely they will agree that the contract between John Smith and Fred is cancelled, that there is a new contract between Small Company Ltd and Fred, and from then on the company director gives the orders.
You would report unpermitted lock replacement to the home owner. The building code regulates new construction and renovations, and is not a requirement of any and all residences. This seems to correspond to a "secondary suite", which is supposed to be registered with the city (if it is allowed in your city). Here is a link for Vancouver, for instance. Such suites are supposed to be registered and inspected, the inspection being carried out by Development, Building and Licencing: By-Law Compliance &amp; Administration (a division of the city government). This article discusses some of the legal problems that can arise from an illegal secondary suite, however the penalties would land on the property owner, and he may not have approved of this subletting or the basement suite. A less-nuclear first step would therefore be reporting it to the property owner.
The part about "If I'm the owner of the content, surely I have the right to request its deletion" is the problem. Sure, you have the right to request, but you can't legally compel. You have an agreement with them, according to which you got something, and they got something. You can't then take back the thing that you gave them, which is permission to use. You didn't give them the IP itself, which you still hold. Here's an analogy. You may own a car, and can give a person permission to use the car (let's say "if you bring me back a pound of cheese from the store"). You cannot later change your mind (especially after you've gotten the cheese) a say that you retract that permission and therefore they actually stole your car. When permission to use is given, as long as the conditions for granting permission are satisfied, you can't un-give permission.
By &quot;unlicensed&quot; you mean that it doesn't state a license for use (MIT, GPL, etc.)? Those licenses are just a codified bundle of terms of use that cover many many edge cases. You have in place a much simpler agreement that covers the primary situation: you using/modifying the code for your own use. It's just like borrowing a car. You will ask a friend &quot;hey, could I borrow your car for a bit?&quot; &quot;sure!&quot;. You know there's a possibility that you'll get in an accident or something weird will happen, but you think the chances of that are minimal and you would be able to work it out. If you ask a car rental company, they'll give you a full contract covering every situation that may happen. Similarly, a large company would be hesitant to borrow a car for corporate use without a legal framework surrounding it. So you will likely be in the clear if you are just using it for a small project with minimal legal/financial implications. If you plan on turning your project into a multi-billion dollar empire, you should revisit your agreement.