30 Common Startup Legal Mistakes and Questions for Counsel
Startup legal mistakes often start as undocumented assumptions about ownership, promises or responsibilities. These thirty issues are a preparation checklist for local counsel, not a determination that a company has met every obligation. Prioritize the ones connected to an imminent sale, hire, launch, investment or dispute.
The examples use U.S. federal and UK references only where stated. Corporate, employment, tax, consumer, privacy and insolvency rules differ by jurisdiction and activity. All examples below are hypothetical. The practical output is a factual document pack, a named owner for each issue and advice addressed to your actual business.
Ownership, financing and authority
1. Treating a founder conversation as completed ownership
An agreed percentage does not establish that all issuance and approval steps have occurred. Gather incorporation records, resolutions, purchase documents and the current ownership ledger. Ask counsel to reconcile what was intended with what was legally completed. For example, two founders may each expect half while the records show only one issued shareholder. Resolve the discrepancy before offering more equity rather than presenting an unverified spreadsheet as the final cap table.
2. Leaving founder departures undefined
A founder leaving early can create uncertainty about shares, ongoing work, access and customer relationships. Discuss departure, vesting, repurchase and decision arrangements before conflict develops. A hypothetical founder responsible for engineering might leave while retaining critical account access and an expected share allocation. Counsel needs the agreements and facts to assess options. Do not improvise forfeiture or assume the remaining team can remove ownership merely because someone stops contributing.
3. Promising employee equity without an approved process
A recruiting email promising a percentage may omit vesting, dilution, approvals, tax and the instrument being offered. Have a suitable plan and communication process reviewed for the actual jurisdiction and worker. Show candidates the approved terms instead of an informal future-value estimate. A hypothetical “one percent” offer is ambiguous if nobody has defined the capitalization basis. Record promises already made so advisers can identify inconsistencies before additional offers are sent.
4. Ignoring existing convertible instruments
Notes, SAFEs or other convertible arrangements can change future ownership and investor rights. Collect every signed version, amendment and side letter. Have the actual conversion scenarios modeled before negotiating new equity. A founder may calculate dilution from a new investment while omitting an earlier instrument that converts at the same event. The relevant result depends on the documents; a simple online percentage calculation cannot settle the legal interpretation.
5. Assuming fundraising is outside securities rules
In the United States, securities offers and sales require registration or an available exemption. SEC guidance is a starting point, not an exemption determination for your raise. Explain the instrument, potential investors, jurisdictions and communication plan to counsel before circulating terms. A small friends-and-family round is not automatically outside the rules. Other countries need separate analysis, especially where investors or promotional materials cross borders.
6. Advertising investment terms before choosing a pathway
The intended offering route can affect how a U.S. company approaches investors. Review public posts, pitch events, mailing lists and referral arrangements before publishing an offer. A hypothetical founder might share terms widely and only later decide on a private-placement route. That sequence can create avoidable questions. Ask what communications are permitted and retain the approved process; do not infer that a private-looking slide deck makes every distribution private.
7. Signing commitments without checking authority
Contracts, borrowing and major purchases may require approval under the company’s governance documents or existing financing terms. Define who can commit the business and where approvals are recorded. A sales employee signing an unusually large liability clause can expose a gap between operational practice and authority. Counsel should review the actual effect; internally, prevent recurrence with escalation rules. An electronic-signature account is a technical capability, not proof of authority.
Intellectual property and information
8. Assuming payment transfers all intellectual property
An invoice does not answer every ownership and licensing question. Gather contractor agreements, proposals, emails, source files and third-party components. Ask counsel what rights exist and what documents are missing. A hypothetical application may be paid for while the company lacks a clear right to modify or sublicense part of it. Investigate before making ownership warranties to customers or investors rather than inserting stronger language into a pitch.
9. Forgetting work created before incorporation
Founders may bring code, designs or datasets created before the company existed. Identify their origin, previous agreements and any employer or collaborator involvement. Ask how rights should be documented for company use. A prototype developed during another employment relationship needs more investigation than a founder’s assurance that it was a personal project. Preserve the evidence and avoid an unsupported claim that incorporation automatically moved every asset into the company.
10. Overlooking third-party license restrictions
Software, photographs, fonts, data and templates can carry different permission conditions. Maintain an asset and component register with the relevant license version and intended use. A hypothetical team may have permission to use an image internally but not in a commercial product. Have uncertain uses assessed before distribution. “Found online” and “open source” are not complete license descriptions; requirements depend on the actual terms and how the asset is used.
11. Confusing domain ownership with trademark clearance
A domain registration, business name and trademark are distinct matters. In the United States, USPTO guidance explains the different intellectual-property systems. Check the proposed brand in the markets and goods or services that matter, with appropriate help. A startup may buy an available domain yet encounter a conflicting brand used elsewhere. Do the investigation before major packaging and marketing commitments, and do not treat a single database search as universal clearance.
12. Disclosing an invention without IP advice
Public demonstrations, crowdfunding pages and technical documents can affect protection strategies differently across jurisdictions. If patent protection may matter, obtain advice before disclosure and describe what has already been shared, when and with whom. A hypothetical founder planning a trade-show demonstration should not rely on a generalized online grace-period claim. Counsel needs the invention, commercial goals and countries involved to assess options and practical deadlines.
13. Using confidentiality documents without controlling access
A confidentiality agreement is only one part of protecting sensitive information. Identify what is confidential, who needs access and how disclosures are recorded. Share staged information with potential partners rather than sending an unrestricted archive immediately. For example, an early buyer discussion may not require named customer records or complete source code. Have the agreement reviewed for its purpose, while maintaining practical access controls and records of what was disclosed.
14. Copying a privacy notice from another company
A notice should describe actual information handling and applicable requirements. Start with a data map: people, information, purposes, vendors, locations, retention and access. A copied notice may promise deletion or security practices the startup cannot perform. For UK activities, current ICO guidance helps organize questions, but its small-organization pages are under review following legislative changes. Check the relevant current position rather than treating a copied paragraph as compliance.
15. Collecting data without a defined purpose
An extra registration field creates information to secure, explain and manage. Ask why each category is needed and what applicable law requires for its collection and use. A hypothetical newsletter signup may not need a customer’s full birth date. Remove unnecessary collection where appropriate, and document justified purposes and retention. Avoid the assumption that obtaining a general checkbox resolves every later use, particularly for sensitive information or children.
16. Assuming a vendor handles every privacy obligation
A platform’s marketing or security documentation does not establish that your use is lawful. Review roles, contracts, locations, access, deletion, exports and incident support for the actual service. For example, a customer request cannot be handled reliably if the startup does not know which vendor stores the record. Ask advisers about applicable transfer and contract requirements. Keep a vendor register and assign someone to maintain it when tools change.
17. Having no route for rights requests or incidents
Customer requests and suspected information incidents need an owner and a way to reach specialist advice quickly. Record incoming facts and preserve relevant evidence. The legal response and timing depend on the regime and incident; there is no universal deadline suitable for every case. A hypothetical support agent receiving an access request should know where to route it rather than improvise a reply or ignore it until the next meeting.
Contracts, customers and commercial operations
18. Letting sales promises exceed the contract
Compare website claims, proposals and emails with the actual service commitments. Define who can approve custom scope, delivery dates and warranties. A hypothetical salesperson promising continuous availability may create expectations beyond a limited pilot agreement. Have counsel assess existing inconsistencies and correct the operating process. A standard contract is less useful when the team routinely makes additional promises without recording or pricing them.
19. Leaving acceptance and change control unclear
Projects need a practical description of completion, review and changes. Discuss acceptance evidence, customer inputs, revision limits and how new work is approved. A fictional website project can become an indefinite redesign if nobody distinguishes a defect from an added feature. The appropriate legal language depends on the transaction; operationally, keep a scope and change record so both parties can understand what was requested and agreed.
20. Ignoring payment, renewal and cancellation mechanics
Review the purchase flow as well as the written terms. State the commitment, billing frequency, renewal and available cancellation route accurately, subject to applicable consumer and other rules. A hypothetical annual commitment paid monthly differs from a cancel-any-time monthly service. Have the actual market and customer type reviewed. Track supplier renewals too, because the company may incur costs even when it has stopped using the product.
21. Accepting liability clauses without pricing the exposure
Liability limits, indemnities, warranties and insurance interact with the actual risk. Escalate unusual terms rather than accepting them solely to close a sale. A small pilot that includes a broad obligation to cover customer losses may create exposure disproportionate to its fee. Counsel and an insurance adviser can assess the documents and coverage. Do not assume an insurance policy covers every contractual promise or that a clause is harmless because it is standard for the buyer.
22. Taking prepayments without a fulfillment plan
Deposits and preorders can create delivery, refund and consumer obligations. Document the product, expected timing, payment use and response if fulfillment fails. A hypothetical batch manufacturer should forecast production and potential refunds before spending collected funds on unrelated expansion. Obtain advice on the actual offer and markets. Cash received is not automatically free profit, and a supplier delay does not erase commitments to customers.
23. Assuming product safety is the supplier’s problem
Physical products may require checks, documentation, labeling or approvals based on category and destination. Identify the parties responsible for manufacturing, importing and selling, and obtain relevant specialist advice. A hypothetical founder importing a powered device should not rely solely on a supplier’s informal assurance. Retain specifications and traceability records, and investigate the applicable regulator’s requirements before ordering. A generic checklist cannot establish that a particular product is safe to sell.
24. Missing licenses or sector restrictions
Activities involving finance, health, food, education or other regulated areas can need specialized review, but regulation is not limited to those labels. Describe the service in operational detail rather than choosing a favorable category name. A startup that “only introduces” parties may still need analysis of what it actually does and charges for. Ask local advisers or relevant authorities about required permissions before launch and retain the answer’s factual scope.
People, records and business continuity
25. Treating a contractor label as decisive
For U.S. federal employment taxes, the IRS examines the relationship and the evidence of control and independence. Other employment laws, states and countries may apply different tests. Bring the actual role, working arrangements, location and supervision to an adviser. A contract calling someone independent does not settle all those questions. Review arrangements again if the work changes from a short specialist project into ongoing managed operations.
26. Hiring remotely without location analysis
The worker’s location can create payroll, employment, tax, immigration and data questions. Resolve those before work starts, including where an intermediary is involved. A hypothetical company incorporated in one country cannot assume all obligations follow that address when a person works elsewhere. Collect location and role facts, then obtain appropriate advice. An employer-of-record or payroll service provides defined services; inspect what remains the company’s responsibility.
27. Using informal hiring and departure processes
Employment terms, required checks, leave, compensation and departure steps need local review. Operationally, maintain an onboarding and offboarding checklist with named owners. A departing worker may retain customer-system access even after payroll stops if no one coordinates the handoff. Avoid improvised withholding, deductions or termination promises. Counsel should assess the actual relationship and facts, while the company records equipment, access, ongoing obligations and relevant documents.
28. Keeping incomplete financial and corporate records
Reliable records support tax work, financing, disputes and a sale. Assign ownership for reconciliations, invoices, approvals, filings and document retention based on local requirements. A hypothetical founder may have bank transactions but lack evidence explaining why payments were made. Reconstruct missing support promptly and establish a consistent process. The required records and retention periods vary; do not copy a universal duration without checking the actual obligation.
29. Waiting until cash is exhausted to seek advice
A forecast showing possible inability to meet obligations deserves timely local insolvency and legal advice. Directors’ duties, creditor treatment and permitted actions depend on jurisdiction and circumstances. Do not assume delaying payments or transferring assets is an acceptable response. Bring dated cash forecasts, liabilities, guarantees and proposed actions to the adviser. A still-positive bank balance does not establish that the business can responsibly make every new commitment.
30. Signing an exit document before understanding it
Letters of intent, exclusivity, broker terms and sale documents can contain important commitments even early in a transaction. Have the actual document reviewed before signing. A hypothetical founder focused on the headline price may overlook a long exclusivity period, contingent proceeds or personal obligations. Ask what is binding, what remains uncertain and which approvals are needed. Model available proceeds, tax and shareholder allocation separately from the announced transaction value.
Turn the list into an adviser agenda
Do not attempt to solve every item in a single unstructured meeting. Group the issues by business consequence and timing. Put an impending investment or worker engagement ahead of a speculative future expansion, while identifying any current serious exposure.
Prepare a fact sheet with the entity, locations, owners, customer types, products, worker arrangements and data handled. Attach the relevant documents and a short chronology. For each issue, write the question, decision needed, deadline and person responsible for acting on the advice. Ask advisers to state assumptions and jurisdiction so later changes can be checked against them.
A hypothetical contractor-built application illustrates the sequence. The startup wants to license it to customers but cannot locate a signed rights agreement. It gathers the proposal, invoices, code history and contributor list, asks counsel to assess the existing rights, then completes an appropriate remediation process if needed. It does not declare ownership verified while the question remains open.
Maintain resulting actions in the compliance checklist, connect hiring issues with the first-employee guide and use operations ownership to keep responsibilities visible. Professional approval remains a separate step based on the company and its actual circumstances.