Tamanaha v. DroneBase CA2/3

CourtCalifornia Court of Appeal
DecidedFebruary 10, 2022
DocketB307866
StatusUnpublished

This text of Tamanaha v. DroneBase CA2/3 (Tamanaha v. DroneBase CA2/3) is published on Counsel Stack Legal Research, covering California Court of Appeal primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Tamanaha v. DroneBase CA2/3, (Cal. Ct. App. 2022).

Opinion

Filed 2/10/22 Tamanaha v. DroneBase CA2/3 NOT TO BE PUBLISHED IN THE OFFICIAL REPORTS California Rules of Court, rule 8.1115(a), prohibits courts and parties from citing or relying on opinions not certified for publication or ordered published, except as specified by rule 8.1115(b). This opinion has not been certified for publication or ordered published for purposes of rule 8.1115.

IN THE COURT OF APPEAL OF THE STATE OF CALIFORNIA

SECOND APPELLATE DISTRICT

DIVISION THREE

ELI TAMANAHA, B307866

Plaintiff and Appellant, (Los Angeles County Super. Ct. No. BC705004) v.

DRONEBASE, INC., et al.,

Defendants and Respondents.

APPEAL from a judgment of the Superior Court of Los Angeles County, Lia Martin, Judge. Affirmed. Miller Barondess, Christopher D. Beatty and Minh-Van T. Do for Plaintiff and Appellant. Prospera Law, Victor T. Fu and Shane W. Tseng for Defendants and Respondents.

‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗ Plaintiff/appellant Eli Tamanaha (plaintiff) appeals from a judgment confirming an arbitration award in favor of defendants/respondents Daniel Burton (Burton) and DroneBase Inc. (DroneBase; collectively, defendants). Plaintiff contends the trial court erred in entering judgment on the arbitration award because his claims were not covered by the parties’ arbitration agreement, the arbitration agreement was substantively and procedurally unconscionable, and the arbitrator exceeded his authority by excluding plaintiff from portions of the arbitration hearing. We conclude that while the arbitration agreement was substantively unconscionable, it was not procedurally unconscionable, and its broad language encompassed plaintiff’s claims. We further conclude that plaintiff’s exclusion from a small portion of the hearing, even if erroneous, was not prejudicial. We therefore will affirm the judgment. FACTUAL AND PROCEDURAL BACKGROUND A. Backgound Plaintiff is an electrical engineer with 15 years of experience working as a senior software engineer at large technology companies such as Amazon, Netflix, and Microsoft. Plaintiff left Microsoft in 2014, and thereafter received offers from several large technology companies, including Google and Roku. In August 2014,1 a mutual friend introduced plaintiff to Burton, who had recently founded DroneBase, a drone services company. Plaintiff and Burton thereafter discussed the possibility of plaintiff joining DroneBase to design and build its technical systems, including its website, server, and apps.

1 All dates are in 2014 unless otherwise indicated.

2 In a series of meetings and emails in September and October, plaintiff and Burton discussed plaintiff’s potential compensation, including his salary and equity in the company. On September 17, Burton proposed meeting in-person to “go over the details” so plaintiff could “walk away confident that you can indeed support your family.” Plaintiff and Burton apparently met a few days later, after which Burton emailed plaintiff that there was “[n]o rush on the information we discussed today, and I look forward to discussing that and other steps forward next Monday.” Several days later, plaintiff emailed Burton that he “like[d] the direction we’re headed in” and was “about to reject Google and Roku’s offers that are currently on the table.” Plaintiff asked what Burton’s salary expectations were, noting that he would need to earn at least $200,000 a year to meet his current expenses, but was “willing to live off of savings for a while if necessary.” The following day, Burton responded that he was open to a “detailed discussion around finances, investors, salary and equity” so plaintiff could feel “happy and confident in the path forward” before turning down other job offers. After a September 29 meeting, Burton emailed that he was glad to have had “an honest, if a bit tough, conversation today” and set out his thoughts regarding “the salary versus equity split.” Burton followed up on October 2 that “we need to find the balance of equity versus salary for you,” and proposed “either $95k salary with 40% founder’s equity or $125k salary with 30% founder’s equity.” Burton asked plaintiff to “[l]et me know how those numbers sound, and if those equity levels are adequate for you to feel like a true partner and co-founder (which you will be).” Burton also set out “what the equity upside for DroneBase might look like” under a variety of different scenarios.

3 Plaintiff responded by email that “[o]f the two options outlined, I prefer the 95k salary with 40% founder’s equity,” and stated that he was “ready to sign an official agreement to solidify everything we’ve discussed.” Burton responded that he, too, was ready “to make a formal commitment to our partnership and to DroneBase.” He proposed to contact his law firm to “have them start all official paperwork (including your equity shares, etc.). At the same time, I will ask them to work up a simple one-pager in writing (that we can both sign) that spells out what we discussed so you can be confident in the terms of our partnership. If possible, I would also like to meet briefly on Friday morning to shake your hand as my word is as important as formal paperwork to me.” Plaintiff responded that “[t]he process you outlined sounds great,” and he agreed “to meet on Friday morning to sign documents and shake hands.” On October 8, Burton emailed plaintiff a formal offer letter (offer letter), to which a “Proprietary Information Agreement” (PIA) was attached. Burton’s email said as follows: “This document reflects our previous discussions and I would be more than happy to walk you through the entire document if helpful. Please read through it and let me know if you have any questions. [¶] . . . [¶] On the first page or two, you will find the salary level, equity issuance (that reflects 40% of Founder’s Equity), and health care coverage as we discussed. For your information, only you and I will have Class E shares (which have special rights)—hired employees will be issued Class A shares. [¶] The rest of the document outlines some IP and non-disclosure issues drafted by our law firm. Again, please let me know of any issues. [¶] If this document works for you, please sign and send back to me, and we can consider it executed. If you have any

4 questions whatsoever, I am happy to get on the phone . . . or answer via email. If you would prefer to review in person Friday morning, that works too. [¶] Regardless, I hope that we can shake hands Friday morning and start this partnership together.” Plaintiff responded the following day, October 9, as follows: “I know you’ll be traveling today, but do you have to time to talk briefly on the phone? I have a few questions about the equity classes for DroneBase and my start date.” Burton responded: “Of course. . . . I am happy to clarify any questions you might have and can reach out to the law firm if we have any remaining questions after our call.” Later on October 9, plaintiff emailed Burton, “I am so happy to accept the offer to work at DroneBase as your partner. Attached is the signed offer letter. Let’s conquer the world!” B. The Offer Letter and PIA 1. Offer Letter The offer letter provided that plaintiff would join DroneBase as “Co-Founder and Chief Technology Officer” and would “be responsible for such duties and responsibilities consistent with your title of Co-Founder and Chief Technology Officer, and any other areas of responsibility as determined or assigned to you by the Company from time to time.” Plaintiff would receive compensation in the form of a base salary of $95,000 per year and benefits, plus equity in the form of 4,382,895 shares of the company’s Class E common stock.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Sonic-Calabasas A, Inc. v. Moreno
311 P.3d 184 (California Supreme Court, 2013)
Rosenthal v. Great Western Financial Securities Corp.
926 P.2d 1061 (California Supreme Court, 1996)
Mercuro v. Superior Court
116 Cal. Rptr. 2d 671 (California Court of Appeal, 2002)
Trivedi v. CUREXO TECHNOLOGY CORP.
189 Cal. App. 4th 387 (California Court of Appeal, 2010)
Coast Plaza Doctors Hospital v. Blue Cross
99 Cal. Rptr. 2d 809 (California Court of Appeal, 2000)
Lynch v. Cruttenden & Co.
18 Cal. App. 4th 802 (California Court of Appeal, 1993)
Efund Capital Partners v. Pless
59 Cal. Rptr. 3d 340 (California Court of Appeal, 2007)
Spinello v. Amblin Entertainment
29 Cal. App. 4th 1390 (California Court of Appeal, 1994)
Stirlen v. Supercuts, Inc.
51 Cal. App. 4th 1519 (California Court of Appeal, 1997)
In Re Tobacco Cases I
21 Cal. Rptr. 3d 875 (California Court of Appeal, 2004)
Fitz v. NCR Corp.
13 Cal. Rptr. 3d 88 (California Court of Appeal, 2004)
Armendariz v. Found. Health Psychcare Servs., Inc.
6 P.3d 669 (California Supreme Court, 2000)
Baltazar v. Forever 21, Inc.
367 P.3d 6 (California Supreme Court, 2016)
Sandquist v. Lebo Automotive, Inc.
376 P.3d 506 (California Supreme Court, 2016)
Samaniego v. Empire Today, LLC
205 Cal. App. 4th 1138 (California Court of Appeal, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
Tamanaha v. DroneBase CA2/3, Counsel Stack Legal Research, https://law.counselstack.com/opinion/tamanaha-v-dronebase-ca23-calctapp-2022.