Document type: Guide Practice area: Corporate — Joint Ventures and Alliances Jurisdiction: United States, with cross-border notes Last reviewed: 5 September 2026


Stage 1 — Decide whether you need an entity

Start here, and be willing to answer no.

Signals that a contract is enough:

  • The collaboration has a defined scope and a natural end date;
  • Neither party needs to own anything jointly;
  • No third-party liability will attach to a shared vehicle;
  • No employees will work for the collaboration;
  • Financial reporting will remain separate.

Signals that an entity is required:

  • The venture must hold licenses, permits, real property, or contracts in its own name;
  • It will raise debt or outside equity;
  • It will hire;
  • The parties want a transferable, valuable ownership interest;
  • Liability ring-fencing matters.

The intermediate structure people forget: a contractual alliance with a governance layer — a steering committee, a defined budget, shared personnel, and an agreed profit split, without an entity. This works well for co-development and co-marketing arrangements and avoids most of the difficulty described in this guide.


Stage 2 — Negotiate a real term sheet

Most joint ventures fail at the term sheet stage by deferring the hard terms. The following must be settled before drafting begins, because each one determines the architecture:

Term Why it cannot be deferred
Scope of the venture's business Determines non-competes, IP field, antitrust analysis, and reserved matters
Contributions and their agreed values Determines ownership, tax treatment, and capital accounts
Ownership percentages Determines governance defaults and economics
Governance: board size, appointment, reserved matters Determines whether the venture can act
Capital: who funds, how much, on what call, and consequences of non-funding Determines who ends up in control
Distribution policy, including tax distributions Determines whether the venture is an investment or a subsidiary
IP: assigned or licensed, field, exclusivity, improvements, survival Usually the largest value item
Exit: mechanism, trigger, valuation standard Determines who owns the business in year seven
Term and termination Determines whether the parties are ever free

A useful discipline: write the term sheet as though the definitive agreement will simply expand it. If a term is "to be discussed," it will be discussed at the worst moment.


Stage 3 — Choose and form the vehicle

The default: Delaware LLC

For US ventures, a Delaware LLC is the default because it offers governance flexibility, pass-through taxation, and — uniquely important here — the ability to modify or eliminate fiduciary duties by contract.

Formation steps:

  1. Reserve the name and file the certificate of formation.
  2. Adopt the LLC agreement, which is the real constitutional document.
  3. Obtain an EIN and make any necessary tax elections (including a check-the-box election if a party wants corporate treatment).
  4. Qualify to do business in each state where the venture will operate.
  5. Open bank accounts, and — this is routinely delayed — establish the venture's own accounting system rather than running it on a parent's ledger.

When to use a corporation instead

  • The venture will seek institutional venture capital or a public offering;
  • A foreign partner's home-country tax treatment favors a corporation;
  • The parties want the predictability of corporate law and are willing to give up fiduciary flexibility;
  • Employee equity incentives are important and the parties prefer conventional options to profits interests.

When to use a partnership

Limited partnerships appear in ventures with a clear sponsor-and-investor dynamic, in fund-like structures, and in certain regulated or real estate contexts. The general partner's control and the limited partners' passivity map onto some venture relationships well and onto most badly.


Stage 4 — Document the contributions

The contribution agreement

Separate from the LLC agreement, a contribution agreement (or a schedule to it) should specify, for each contributing party:

  • Exactly what is contributed, by schedule, with identifying detail sufficient to transfer it;
  • The agreed value, and the methodology;
  • Representations and warranties about the contributed assets — title, condition, non-infringement, no undisclosed liabilities, compliance with law;
  • Indemnification for breach, with survival periods and caps;
  • Excluded liabilities that remain with the contributor;
  • Third-party consents required to transfer, and who obtains them; and
  • The closing mechanics and conditions.

Treat this like an acquisition agreement, because it is one. The venture is acquiring assets, and it should have the protections a buyer would have. Parties frequently skip reps and warranties on the theory that everyone is on the same side, and then discover an environmental liability attached to a contributed facility.

Intellectual property specifically

Answer all of these in writing:

  • Assignment or license? Assignment gives the venture ownership and durability. License preserves the contributor's freedom but leaves the venture dependent.
  • Field of use. Define it by application, market, and product, and test the definition against the parties' adjacent businesses.
  • Territory.
  • Exclusivity. Exclusive within the field is common; consider whether the contributor is excluded too.
  • Sublicensing. The venture will need to sublicense to manufacturers and distributors.
  • Improvements. Who owns improvements made by the venture? By the contributor? Is there a grant-back, and is it exclusive?
  • Survival on exit and on termination. The single most consequential provision, as it determines whether the venture has standalone value.
  • Prosecution and enforcement. Who files, who pays, who controls litigation, and who gets recoveries.
  • Escrow. For software contributions, a source code escrow with defined release conditions.

Secondment

For each seconded employee, document: who directs the work, who pays and who reimburses, benefits continuity, invention assignment to the venture, confidentiality flowing both ways, the term, and what happens at the end. Invention assignment is the one that bites — a seconded engineer who invents at the venture while employed by a parent creates an ownership dispute unless the paperwork is clear.


Stage 5 — Design governance that can decide

Sizing the board

Keep it small. Four to six managers is workable; ten is a legislature. Each party appoints a number reflecting ownership or the negotiated split, with the right to remove and replace its own appointees at will.

Building the reserved-matter list

Draft it in two columns: the matter, and the vote required. Resist the urge to require unanimity for everything. A practical structure:

  • Ordinary course — board majority.
  • Significant — supermajority or specified consent (budget, senior hires, contracts above a threshold, litigation).
  • Fundamental — unanimous or member-level consent (amendment, new equity, merger, sale, dissolution, change in business).

Building in anti-deadlock defaults

Every provision requiring consent should have a fallback. Examples:

  • Budget: if not approved by December 15, prior year plus CPI, capital expenditure capped at prior year.
  • Distributions: mandatory tax distributions regardless of any consent requirement; discretionary distributions above that.
  • Senior hires: if no agreement within 60 days, an executive search firm presents three candidates and the board must select one.
  • Auditor: rotate among named firms if no agreement.

These fallbacks are what separate a functioning venture from a standing dispute.

Officers and delegated authority

Adopt a written delegation of authority matrix at formation: who can sign contracts at what value, who approves capital expenditure, who hires, who can bind the venture to a settlement. Without it, every decision escalates to the board and the board becomes management.


Stage 6 — Run the parallel workstreams

These start at term sheet, not at signing.

Antitrust. Determine whether the formation is HSR-reportable; assess the substantive analysis if the parties compete; draft the information protocol; scope the non-competes to the venture's field.

Tax. Model the contribution treatment, built-in gain allocations, the distribution waterfall's tax consequences, state apportionment, and — for cross-border ventures — treaty and withholding analysis.

Regulatory. Identify licenses the venture will need in its own name and their lead times. Utility, healthcare, financial services, transportation, and defense ventures routinely discover that a license takes nine months and cannot be transferred.

Employment. Determine who employs whom, whether a transfer of employees triggers notification or consultation obligations, and how benefits will be provided.

Systems and data. Decide what the venture runs on. A venture operating on a parent's ERP is not separable and is an antitrust information risk. Budget for standing up independent systems, and set a deadline.

Insurance. The venture needs its own coverage. Confirm the parents' policies do not silently cover — or silently exclude — venture operations.


Stage 7 — Build the exit before you need it

Decide three things at formation:

1. What triggers an exit? Deadlock, a lockup expiry, material breach, change of control of a partner, failure to fund, failure to meet performance milestones, or simply a unilateral right after a period.

2. What is the mechanism? Shotgun, put/call, ROFO, forced sale, or dissolution. Match it to the parties' relative financial capacity — a shotgun between a $40 billion company and a $200 million company is not a mechanism, it is a call option for the larger party.

3. How is price set? Formula, appraisal, baseball appraisal, or market test. Specify whether discounts for lack of control and lack of marketability apply. Specify the treatment of member loans, accrued preferences, and the contributed IP license.

Then stress-test it. Take the agreement and ask: if the deadlock happened tomorrow, what exactly would each party do, and could it afford to? If the answer is that neither party could fund a purchase, the mechanism is a forced sale in disguise, and the parties should say so explicitly rather than discovering it.


Stage 8 — The first hundred days

Ventures fail operationally more often than legally. The launch checklist:

  • Appoint the CEO before closing, not after. A venture without a leader on day one drifts for a quarter.
  • Hold the organizational board meeting and adopt the delegation matrix, the information protocol, the code of conduct, and the initial budget.
  • Stand up separate email, systems, and accounting. Independence is easiest to establish at the start.
  • Deliver the seconded staff and run their onboarding, including antitrust and confidentiality training.
  • Execute the shared-service agreements with each parent, with pricing, service levels, and termination rights.
  • Open the customer pipeline. Ventures that spend six months on internal setup lose the commercial momentum that justified them.
  • Set the reporting calendar: monthly management accounts to both parents, quarterly board meetings, annual budget cycle with the fallback dates in the calendar.

Working the governance negotiation

The governance section is where most negotiating time goes, and it goes there badly, because the parties argue about principles when they should be arguing about scenarios. A more productive method is to run the agreement against a fixed list of decisions the venture will actually face and ask, for each one, who decides.

Take a manufacturing venture. In its first three years it will have to decide whether to add a second shift, whether to accept a large customer's demand for exclusivity, whether to settle a warranty claim for $3 million, whether to replace a chief financial officer who is not working out, whether to open a plant in Mexico, whether to accept a supply contract that requires a $30 million capital commitment, whether to license its process technology to a third party, and whether to distribute cash or reinvest. Run each of those through the draft. If the answer to any of them is "the parties will have to agree," ask what happens when they do not — and if the honest answer is "nothing happens," the provision needs a fallback.

Three patterns emerge from that exercise. First, most disputes are about capital, not strategy; a partner that would happily approve a plan it does not have to fund will block the same plan when it does. That means the capital call and dilution provisions carry more governance weight than the reserved-matter list. Second, personnel decisions deadlock more often than commercial ones, because each parent has a candidate and neither will concede; a mechanical tiebreak for senior hires is worth more than another paragraph on strategic alignment. Third, the decisions that matter most — a large customer's exclusivity demand, a technology license to a third party — are precisely the ones where the parents' interests diverge structurally, because the answer affects each parent's separate business differently. Those belong on the reserved-matter list explicitly, and the parties should discuss the likely divergence openly at formation rather than discovering it in year two.

Independent managers: useful, and harder than they look

A neutral manager with a casting vote solves deadlock on paper. In practice, finding one is difficult and keeping one neutral is more difficult. Consider who is actually available: industry veterans, who usually have relationships with one parent; retired executives, who may lack current operating knowledge; and professional directors, who may lack industry credibility with the operating teams.

If the parties use an independent, define carefully: how they are selected (an agreed list at formation, or a nomination process with a fallback to an appointing authority); how long they serve and how they are removed (removal should require both parties, or the independence is illusory); what they are paid and by whom; whether their vote is available on all matters or only on defined ones after a deadlock period; and what indemnification and insurance they receive. The last item is not a detail — an independent who breaks a tie on a $200 million decision will be sued by the losing side, and will not serve without protection.

An alternative worth considering: rather than a standing independent, provide for a deadlock referee appointed only when needed, with a defined scope and a short mandate. This avoids the cost and awkwardness of a permanent third manager while preserving a tiebreak.


Documenting the relationship: the full document set

A joint venture is not one agreement. Expect to negotiate and deliver most of the following, and to sequence them so that the commercial agreements do not lag the entity documents by months.

Constitutional documents. The certificate of formation and the LLC agreement (or charter, bylaws, and stockholders agreement in a corporate venture). The LLC agreement carries governance, economics, transfer restrictions, exit mechanics, and the fiduciary duty modifications.

Contribution documents. The contribution agreement, with schedules of contributed assets, assumed and excluded liabilities, and agreed values; bills of sale; assignment and assumption agreements; deeds or leases for real property; and the consents required to transfer contracts.

Intellectual property documents. Patent, trademark, and copyright assignments in recordable form; a license agreement for anything not assigned, with field, territory, exclusivity, sublicensing, improvements, prosecution, enforcement, and survival; a technology transfer plan; and, where software is involved, a source code escrow agreement.

Commercial agreements between the venture and each parent. Supply agreements, distribution agreements, shared services agreements (IT, HR, finance, legal, facilities), manufacturing agreements, and any offtake commitments. These carry most of the venture's actual economics and deserve as much attention as the LLC agreement.

Employment documents. Secondment agreements for each seconded employee or a master secondment agreement with schedules; employment agreements for direct hires; equity or phantom equity plans; and confidentiality and invention assignment agreements running to the venture.

Financing documents. Any credit agreement, guarantees or comfort letters from parents, subordination arrangements for member loans, and security documents.

Compliance documents. The antitrust information protocol; the code of conduct; anti-corruption policies and third-party diligence procedures; and, for regulated industries, the compliance plan required by the regulator.

Transition documents. A transition services agreement covering the ramp-up period, with services, pricing, service levels, terms, and exit assistance — and, ideally, a pre-agreed unwind protocol for the end.

Practical sequencing advice: negotiate the LLC agreement and the commercial agreements together. Parties routinely settle the governance document first and then discover that the supply agreement one parent expects would transfer most of the venture's margin back to that parent, at which point the ownership split they just agreed is wrong.


Regulatory and clearance planning

Two clearance questions determine the timetable, and both should be answered in the first two weeks.

Premerger notification. Formation of a joint venture is treated as an acquisition of the venture's voting securities or interests by each contributing party, and it is reportable if the applicable size tests are met by the value of what each party acquires. The analysis is not intuitive: contributions of assets, cash, and IP all count toward value, and a party contributing only services may still acquire a reportable interest. Do the analysis on the term sheet, because a filing adds at least thirty days to the timetable and a second request adds many months.

Sector-specific approvals. Depending on the industry, formation may require approval from a state public utility commission, a banking regulator, an insurance department, a gaming authority, a health department, the Federal Communications Commission, or a foreign investment screening body where a foreign partner is involved. Lead times vary from weeks to a year, and several of these approvals cannot be sought until definitive documents exist, which means the documents must be drafted to accommodate a long gap between signing and closing — with covenants governing conduct in the interim, allocation of the risk of non-approval, an outside date, and a break arrangement.

A practical trap: the venture frequently cannot obtain its own licenses until it exists, and it cannot operate without them. The workaround is a transition period in which one parent operates under its own licenses and the venture reimburses, coupled with a binding plan and timetable for transfer. Document that arrangement carefully, because operating under another entity's license without a proper agreement can itself be a regulatory violation.

A worked example: sequencing under time pressure

The situation. Two medical device companies, Hallberg Surgical and Ozturk Imaging, want to launch a combined navigation-and-implant system before a competitor's product clears regulatory review in fourteen months. Their general counsel, Renata Oyelaran and Marcus Dietz, have to structure a venture in ninety days.

What they do first — and it is not drafting. They run three parallel diligence questions:

  1. Can the venture hold the regulatory clearance, or must a parent? The answer determines whether the venture is a real business or a marketing entity. It turns out clearance can be transferred but takes five months, so the venture will operate initially under Hallberg's clearance with a defined transfer plan and a fee.
  2. Is formation HSR-reportable? Contributions exceed the threshold. That sets a 30-day waiting period and dictates the closing timetable.
  3. What does Ozturk's imaging IP license actually cover? Its core algorithm is itself licensed from a university under an agreement that prohibits sublicensing without consent. This is the deal-breaker risk, discovered in week two rather than week ten.

The consequence of finding it early. They negotiate directly with the university for a venture-specific license, which takes six weeks and costs a milestone payment. Had this surfaced at signing, the venture would have launched on an IP foundation that a licensor could revoke.

Structuring choices made under the deadline:

  • Delaware LLC, 55/45 Hallberg, reflecting the regulatory clearance contribution.
  • Even board of four, despite unequal ownership, with an independent fifth manager holding a casting vote only on matters unresolved after two meetings. Unusual, but it prevents the majority from steamrolling and prevents paralysis.
  • Contributions: Hallberg contributes cash, manufacturing capacity, and the clearance pathway; Ozturk contributes an exclusive field-limited license, sublicensable, surviving exit, with improvements included for four years.
  • Capital: committed funding of $85 million from each side over three years, with non-funding triggering proportionate dilution capped at a 15-point swing.
  • Exit: no exit for four years; thereafter a ROFO, with a forced sale available to either party after year six.
  • Information protocol adopted at formation, with segregated systems funded in the initial budget.

What they deliberately deferred. The detailed transition services schedule and the long-form shared-services pricing, handled by a framework agreement with a benchmarking mechanism and a 120-day period to complete schedules. This is the right thing to defer — it is operational, it is not adverse, and deferring it does not change anyone's leverage.

What they refused to defer, over commercial pressure to sign: the IP survival provision and the capital commitment. Both determine the venture's value, and both would have been negotiated from a weaker position after launch.


Valuing contributions when the assets are not comparable

The hardest conversation in venture formation is the one where one party contributes $200 million of cash and the other contributes "our technology and our channel." There is no objective answer, and the parties are negotiating with asymmetric information — each knows the value of what it contributes and can only guess at the other's.

Several techniques make the conversation tractable.

Value the venture, not the contributions. Rather than pricing each input, build a joint business plan and value the resulting enterprise. Then ask what each party's contribution is worth as a share of that enterprise — essentially, what the venture would have to pay a third party to obtain the equivalent input, or what the venture would be worth without it. This reframes the argument from "my technology is worth $300 million" to "without the technology there is no venture, and without the capital there is no plant," which is a more honest starting point.

Use a build-or-buy comparison. For each contribution, ask what it would cost the venture to replicate: to license comparable technology from a third party, to build the plant, to hire the sales force, to obtain the regulatory clearance. Replacement cost is a floor, not a value, but it disciplines the discussion and is verifiable.

Separate value from timing. A contribution that will be delivered over three years is worth less than one delivered on day one. If a party's real contribution is a commitment to sell the venture's product through its channel for five years, that is a stream of future performance, and it should be compensated as it is performed — through a distribution margin, an earn-in of equity against milestones, or a performance-adjusted ownership ratchet — not as an upfront equity grant that vests regardless.

Consider putting the disagreement in the economics rather than the ownership. Where the parties cannot agree on relative value, structure around it: give the cash contributor a preferred return until its capital is returned, give the IP contributor a royalty, and split the residual equally. Each party is then paid for what it actually brought, and the ownership percentage — the thing they were fighting about — becomes less consequential. This is often the deal that unlocks a stalled negotiation.

Do not let the auditors decide. The purchase accounting and tax valuations that follow formation are important for reporting, but they answer a different question under different rules. Negotiate the commercial values first and let the accounting follow.

Earn-ins and ratchets

Where one party's contribution is a promise, an earn-in aligns ownership with delivery. Structures include equity issued in tranches against milestones (a regulatory approval, a product launch, a revenue threshold, delivery of a defined number of engineer-years); a ratchet that adjusts percentages annually based on measured performance against a committed metric; and a reverse ratchet that returns equity if commitments lapse.

The design questions are the familiar earnout questions: what exactly is measured, who measures it, what happens if the venture's own conduct affects the measurement, and how disputes are resolved. Keep the metric simple and objectively verifiable — units delivered, headcount seconded, approvals obtained — rather than something like "revenue attributable to the channel," which requires an attribution methodology nobody will agree on later.


When the venture is with a customer, a supplier, or a competitor

The counterparty's relationship to the venture changes the structuring priorities substantially.

With a customer. The venture exists partly to secure demand, and the customer-partner's leverage runs through the offtake agreement rather than the equity. Focus on pricing mechanics, volume commitments, term, and what happens if the customer's requirements fall. Watch for a customer that uses venture access to obtain cost transparency it will later use against the supplier-partner in unrelated negotiations — the information protocol should address this specifically.

With a supplier. The mirror image. The venture depends on the supplier-partner's inputs, and the supply agreement's pricing and continuity provisions matter more than governance. Insist on a right to qualify a second source, and on continued supply obligations that survive an exit for a transition period.

With a competitor. Everything in the antitrust discussion applies, and two structural points deserve emphasis. First, scope the venture narrowly and document the scope; a narrow, well-integrated venture is defensible, a broad one that touches the parties' core competition is not. Second, plan the unwind carefully — competitors who separate after sharing personnel, systems, and plans face a genuine risk that the separation itself becomes an antitrust problem, and a pre-agreed unwind protocol with information cleansing is the answer.

With a financial sponsor. A private equity partner has a defined hold period and will want exit rights the strategic partner will resist. Negotiate the timing explicitly: a lockup, then a put or a ROFO, then a forced sale. A sponsor that cannot see an exit will not invest; a strategic that faces a forced sale in year four may not either. The compromise is usually a staged menu of rights that become available over time.

Common structuring errors

  • Creating an entity for a contractual relationship. Adds cost, tax complexity, and an exit problem, for nothing.
  • Leaving fiduciary duties on the default setting in an LLC where each party appoints its own employees as managers. This makes the ordinary operation of the venture a breach.
  • Reserved-matter lists that reach operational decisions. Deadlock over hiring a regional sales manager.
  • No budget fallback. The most common cause of paralysis.
  • A shotgun between unequal parties. A call option dressed as symmetry.
  • IP licensed rather than assigned, terminating on exit. The licensor holds a veto over the venture's value forever.
  • No tax distribution provision. Members owe tax on income they never received.
  • No information protocol between competing parents. A discoverable antitrust problem and a real commercial one.
  • Deferring the exit terms. They are always harder to negotiate later, because by then everyone knows who wants out.

Living with the venture: the governance year

A venture that is structured well and then administered badly still fails. The ongoing obligations are modest but must actually happen, and in-house counsel for both parents should own a calendar.

Quarterly. Board meetings with real agendas and real minutes. Minutes matter more in a venture than in a wholly owned subsidiary, because they are the record of who agreed to what and they will be the first exhibit in any dispute. Record decisions, dissents, and the information the board relied on. Circulate management accounts to both parents on a fixed schedule; a partner that stops receiving information stops trusting the venture, and information disputes are a leading indicator of governance disputes.

Annually. The budget cycle, run against the calendar in the agreement, with the fallback date diarized so that nobody discovers the deadline after it passes. The audit, with the auditor engaged directly by the venture. A review of affiliate transactions and shared-service pricing against the benchmarking provision. Compliance training refreshes for venture and seconded staff. A confirmation that insurance remains in place and that the parents' policies have not been restructured in a way that leaves a gap.

Continuously. Enforce the information protocol. This is the obligation most likely to erode, because the people who joined the venture from each parent maintain their old relationships and their old email accounts, and the protocol becomes a document nobody reads. Periodic spot checks and a short annual certification from each seconded employee are proportionate and effective.

On any triggering event. A change of control of a partner, a failure to fund a capital call, a material breach, or a missed performance milestone should trigger a formal process rather than an informal conversation. Send the notice the agreement requires, on time. Parties frequently forgive a default informally and then find, two years later, that they waived a right they now need.

Warning signs

Certain patterns reliably precede venture failure, and each one has a response available while it is still early:

  • Board meetings that are briefings rather than decisions. The venture is being run by one parent's management, and the other parent has disengaged. Response: put real decisions on the agenda and require pre-reads.
  • Repeated use of the budget fallback. The parties cannot agree a plan. Response: escalate deliberately, and consider whether the strategic divergence is now permanent.
  • Capital calls funded by one party as loans. Ownership is drifting. Response: address it explicitly rather than letting the drift accumulate.
  • Requests for information that are refused or slow-walked. The relationship is deteriorating and someone is building a record. Response: comply, and find out why.
  • A parent reorganizing so that the venture reports to a more junior executive. Commitment is declining. Response: raise it at the parent-company level while it is still a conversation rather than a claim.

Ventures rarely die suddenly. They are usually visibly ill for a year first, and the parties who act during that year get a negotiated exit at a fair price. The parties who wait get a deadlock, a buy-sell, and a lawyer's fee.

Disputes: what actually gets litigated

When ventures end up in court, the claims cluster into a small number of recurring shapes, and knowing them helps at the drafting stage.

Breach of the express agreement is the cleanest and the least common, because well-drafted venture agreements are specific and parties usually comply with terms they can read. Where it happens, it is typically about capital calls, distribution obligations, or a commitment covenant a parent stopped honoring.

Breach of the implied covenant of good faith and fair dealing is the workhorse claim in the alternative-entity context, precisely because express fiduciary duties have been waived. The theory is that a party exercised a contractual right in a way that defeated the other's reasonable expectations — calling capital solely to dilute, exercising a call right on inside information, or manipulating the metric that drives an earn-in. The implied covenant cannot be eliminated, which makes it the residual protection in every heavily negotiated LLC agreement and the reason that waiver-of-duties clauses do not license bad faith.

Disputes over the exit mechanism — whether a trigger occurred, whether a notice was valid, how the valuation standard applies, whether discounts are permitted. These are contract-interpretation cases and they are won by whoever drafted more precisely. A "fair market value" clause that does not address minority discounts generates a nine-figure argument.

Deadlock petitions and dissolution actions, where a party asks a court to dissolve a venture that cannot function. Courts are reluctant to dissolve a profitable business and will look first to whether the agreement provides a mechanism the petitioner has not used. A party that skips its own buy-sell and runs to court usually loses.

Books-and-records and information disputes, often as a prelude to something larger. Because LLC agreements can restrict statutory inspection rights, the negotiated information rights are what the party actually has.

Claims about competitive conduct — that a parent diverted an opportunity, competed in the venture's field, or used venture information in its own business. These turn entirely on the scope and non-compete drafting, which is why the field definition deserves more attention than it usually gets.

A drafting response to all of the above: include a provision stating expressly what the parties' reasonable expectations are with respect to the most sensitive discretionary rights — capital calls, the exercise of a call, the measurement of an earn-in. The implied covenant fills gaps; a party that states the standard in the contract reduces the gap and controls the fill.

A one-page structuring summary

For the partner who wants the whole method on a single page:

Decide whether you need an entity. Most collaborations do not. An entity is justified by ownership, liabilities, financing, employees, or a transferable stake.

Settle nine terms in the term sheet: scope, contributions and values, ownership, governance and reserved matters, capital and the consequences of not funding, distributions including tax distributions, intellectual property with survival, exit mechanism and valuation standard, and term.

Form a Delaware LLC unless a specific reason points elsewhere, and modify fiduciary duties expressly.

Document contributions like an acquisition, with representations, indemnities, and consents — and treat the IP grant as the most valuable term in the transaction.

Design governance around scenarios, not principles, and give every consent requirement a fallback so that inaction has a defined consequence.

Run antitrust, tax, regulatory, employment, systems, and insurance in parallel from the term sheet, not after signing.

Build the exit at formation, price it, and stress-test whether either party could actually fund it.

Launch properly: a CEO before closing, separate systems, executed shared-service agreements, and a reporting calendar.

Administer it: real board meetings, real minutes, a live information protocol, and formal notices when triggers occur.

The structure will not make a bad business idea work. But a good business idea inside a badly structured venture fails just as reliably, and far more expensively — because the parties spend three years discovering that the document they signed does not answer the question they now have.

Related documents