Chip Design Startups

The tape-out timeline looked promising. Consider this hypothetical example.

A fabless startup with around 30 engineers in Bengaluru had validated its architecture in simulation, secured its budget and told investors that first silicon would arrive within the year. A government incentive milestone was also tied to the programme.

The team signed the foundry’s standard agreement to secure a slot. It accepted the electronic design automation (EDA) vendor’s licence terms and a standard licence for high-speed interface intellectual property (IP). Each agreement appeared to be a routine procurement document.

For the first few months, the programme stayed on track.

Then the dependencies surfaced. A design services partner engaged for timing closure could not access the foundry’s process design kit (PDK), because the agreed permissions did not cover that partner. The EDA entitlement did not accommodate the proposed contractor usage. Pilot wafers returned with low yield, but the foundry agreement contained no pilot-lot yield commitment. Later, a potential acquirer asked: “Will the licences continue after we buy the company?”

These were not engineering questions alone.

The team had treated three interdependent agreements as separate purchases. Together, however, they determined whether the business could complete its design, manufacture its chip and continue commercialising it after a financing or acquisition.

Would this affect your business?

If a foundry, EDA or IP agreement had to be replaced tomorrow, which would stop your tape-out? Could you explain who owns the design, who may access the PDK and what happens to the licences when the company grows or changes hands?

The Risk Is Not Just Cost - It Is Dependency

Chip design startups understandably focus on price. Mask preparation, prototyping, design tools and licensed IP can absorb a substantial part of the budget. But the lowest quoted price is not necessarily the lowest cost of completing and commercialising a chip.

Cost is visible. Contractual dependency is easier to overlook.

A fabless business relies on external manufacturing and may depend on licensed design tools, process information and IP blocks. Replacing any critical element can require technical rework, additional expenditure and fresh approvals. Team expansion, schedule changes and a new product roadmap can therefore expose restrictions that were not apparent when the agreement was signed.

A vendor’s standard form may be the practical starting point, particularly when the tape-out date is fixed. Standard wording, however, is not confirmation that the agreement fits the startup’s operating model.

Three Contracts, One System

Foundry, EDA and IP agreements should be reviewed as one interdependent contract package, even where they are negotiated with different vendors.

The PDK provides process information used in the design flow. EDA tools must support that flow, and licensed IP may be qualified for a particular process or node. A change in foundry, node, tool flow or IP vendor may require requalification, redesign, additional licences or revised commercial terms.

Align the agreements around the same operating assumptions:

Which entity holds each entitlement? Who may use it, from which locations, for which products and for how long? What happens on assignment, change of control, suspension or termination?

Inconsistent permissions can leave the startup unable to execute its design flow, even though it has paid for each component.

The objective is not to rewrite every standard form. Prioritise the provisions that could stop the programme, and record agreed exceptions in the order form, licence schedule or side letter. Make the order of precedence clear so those exceptions are not displaced by conflicting standard terms.

If your design partner needs the PDK next week, can you identify the provision permitting access? If the partner modifies a licensed block, can you explain who owns the resulting work and what the startup may do with it?

Resolve these questions in the vendor proposal, commercial term sheet or licence schedule—not after a dependency has become urgent.

Foundry Contracts- What to Negotiate

A foundry relationship may involve an NDA, a PDK or technology licence, a manufacturing agreement, purchase orders and statements of work. Review the complete package rather than relying on the supply agreement alone.

Who can access the kit? Identify the employees, affiliates, contractors and design services partners who need access to process information. Check both confidentiality obligations and the separate licence permissions governing PDK use, including any vendor approval process.

Diligence disclosure is a different issue. Investors, lenders and potential acquirers may need selected information, not unrestricted technical access. Agree permitted recipients, confidentiality safeguards and any exclusions for particularly sensitive material. Also establish how the startup’s design data may be used, retained, returned or deleted.

MPW shuttles or dedicated runs? Multi-project wafer (MPW) shuttles reduce upfront prototyping expense by sharing mask and wafer costs among participants. Dedicated runs offer different scheduling options, volume economics and control. Compare the actual deliverables, die allocation and support offered, not just the headline price.

Negotiate the bridge from prototype to production. What qualification work is required? What pricing and capacity will apply? Which existing permissions survive, and which new documents or approvals are needed? A successful prototype should not leave the company without a workable production route.

What is the NRE paying for? Define the scope of non-recurring engineering (NRE) charges: physical verification, mask preparation, prototype wafers, engineering samples and any agreed support. Where commercially achievable, link payments to defined milestones. Clarify re-spin and metal-only correction costs, mask ownership, design-data ownership and any permitted reuse. Build an appropriate contingency into the budget rather than assuming the first run will require no correction.

Yield and quality. Distinguish pilot-lot expectations from production commitments. Do not assume a pilot run carries a guaranteed yield. Define the applicable measurement method, acceptance criteria, test conditions and allocation of responsibility for design-related and process-related defects.

Specify access to relevant yield and quality data, root-cause analysis and available remedies, including replacement wafers or credits. Read these remedies alongside exclusions and liability caps. A cap based on affected wafer charges may leave the startup bearing significant downstream costs.

Capacity, cost and volume. Confirm lot sizes, minimum order economics and reservation lead times with the specific foundry. Address:

Price validity and adjustment mechanisms.

Minimum purchase commitments and any take-or-pay obligations.

Forecast tolerances, cancellations and rescheduling.

Allocation priority and treatment of capacity constraints.

Delivery milestones and the consequences of delay by either party.

Changes, assignment and exit. Address work in progress, masks, data, outstanding orders and surviving confidentiality obligations on termination. Examine assignment and change-of-control triggers separately. Export-control and sanctions obligations should identify the information, approvals and cooperation required from the startup and its partners.

EDA Vendor Contracts - Where the Cost Hides

EDA tools are an essential part of the design workflow. Their licence terms determine who may use them, where, for how long and on what charging basis. An entitlement that fits today’s team may not fit next year’s operating model.

Siemens’ Electronic Design Automation Supplemental Terms, version 1.6 (June 2025), illustrate the importance of reading definitions and order-specific exceptions. They are an example, not a universal description of other vendors’ terms.

Perpetual, term or pay-as-you-go? Separate the right to use software from maintenance, updates, support and cloud access. Confirm what is included in the purchased model and what requires a further fee. For a fluctuating tape-out workload, ramp pricing and temporary peak capacity may matter more than the lowest annual rate.

Usage model. Seats, tokens, pools and concurrent sessions are not interchangeable. Siemens’ cited terms limit each licence to a single session by a single authorised user at a time, unless otherwise specified in the order. Confirm the unit of entitlement, reallocation rules and charges for borrowed, burst or cloud usage.

Users and territory. The cited Siemens terms define an authorised user as a customer employee or an authorised agent; the agent definition addresses contractors working on the customer’s premises. They also recognise occasional off-site use where the user’s official and customary workplace is a licensed site. Do not equate that exception with unrestricted remote contractor access. Align permissions with the actual and planned offices, design partners, remote working arrangements and cloud deployment model.

Audits and true-ups. Agree the notice period, frequency, scope and safeguards for audits. Clarify how usage records are assessed, how disputed findings are resolved, the pricing of excess use and responsibility for audit costs. Maintain records that match the contractual entitlement model.

Renewals. Record renewal and non-renewal deadlines, automatic renewal provisions and price-adjustment rights. Seek sufficient notice of proposed changes and an orderly transition period. Discovering a restriction shortly before renewal can materially reduce negotiating leverage.

Regulatory disruption. On 3 July 2025, Siemens announced that restrictions set out in a 23 May letter from the US Bureau of Industry and Security were no longer in place, and that it had restored access to the specified EDA software and technology, subject to applicable export-control laws. The episode illustrates how quickly access can change. Seek notice where legally permissible, a defined suspension process and agreed treatment of prepaid fees. Contractual arrangements cannot require a vendor to act contrary to applicable law.

Taxes and payment. Check whether the quoted price is inclusive or exclusive of taxes and whether the agreement contains a withholding gross-up. Identify the documents the vendor must supply and the invoice requirements needed for the startup’s tax and accounting treatment. Assess cross-border payments by category rather than treating all software, IP and manufacturing charges alike.

Assignment and restructuring. Identify the events that require consent or notice, including asset transfers, mergers, intra-group changes and any expressly covered changes of control. Where achievable, agree successor and group-restructuring permissions before the transaction becomes time-critical.

IP Licences - Rights, Devices and the Product Roadmap

Licensed processor cores, interface blocks, memory compilers and libraries can be critical to a chip’s design and manufacture. The licence must support the intended commercial lifetime of the product. Fees may include upfront payments, royalties and NRE charges; the structure varies by licensor and IP offering.

Read the definitions and licence grant before accepting the commercial calculation. A favourable royalty rate is of limited value if the permitted product or manufacturing rights are too narrow.

Licence grant. Map the rights required to design, integrate, modify, manufacture and commercialise the chip. Check whether the licence permits the foundry to manufacture for the startup through appropriate “have-made” rights, and whether contractors, customers or outsourced semiconductor assembly and test (OSAT) providers need separate permissions. Do not assume a manufacturing permission also permits sublicensing or disclosure of source material.

Field, territory and roadmap. Check product, process, node, field-of-use and geographic restrictions. Identify minimum royalties, commercialisation milestones and the permissions needed for second-generation products. The current product definition should not inadvertently exclude foreseeable variants.

Device and royalty trigger. Establish whether royalties are calculated per die, packaged device, IP instance, port or another agreed measure, or by reference to sales value. Define when the payment obligation arises and how returns, samples, replacements and internal transfers are treated.

Consider multi-die packages and reuse across product variants before accepting the definition. Address volume discounts, caps or buy-outs where relevant, minimum annual commitments, reporting periods and audit rights. The royalty calculation should remain intelligible as the product architecture evolves.

Modifications. Separate the right to modify IP from ownership of the modifications and the right to use resulting improvements. Andes Technology’s announcement of 12 January 2026 described an agreement with L&T Semiconductor Technologies incorporating a cumulative commercial structure supporting expanded modification rights. The announcement illustrates an available commercial approach; it does not disclose the full contract. Specify ownership, permitted reuse, licensor access to improvements and NRE deliverables expressly.

Warranties, indemnities and support. Seek appropriate conformity warranties, technical support and an IP infringement indemnity, and examine their interaction with liability caps and exclusions. Confirm the extent of silicon validation on the intended process and node, including any further qualification required. Agree errata notification, fixes, support duration and end-of-life arrangements. For a critical dependency, assess whether a workable escrow or continuity arrangement is commercially available.

Term and survival. Identify whether the startup may continue manufacturing, selling and supporting already-designed products after expiry or termination, and on what conditions. Address inventory, committed orders, continuing royalties and access to essential materials. A licence described as “perpetual” still needs to be read alongside its termination provisions.

Change of control. Review this separately from assignment. A share acquisition, asset sale, merger and internal restructuring may engage different provisions. Identify consent, notice and termination triggers, negotiate appropriate exceptions and allocate the process for obtaining any required consent.

India-Specific Considerations - Incentives, Ownership and Payments

For an Indian startup, the same contract package must also support incentive eligibility, ownership of design assets and the treatment of international payments.

Design Linked Incentive Scheme. The published DLI framework provides product design-linked incentives of up to 50% of eligible expenditure, capped at ₹15 crore per application, and deployment-linked incentives of 6% to 4% of net sales turnover over five years, capped at ₹30 crore per application. Design infrastructure support includes EDA tools and IP cores. These are conditional benefits, not automatic reimbursements of every vendor invoice.

Structure vendor documents, statements of work and invoices to evidence eligible expenditure and agreed milestones. The published guidelines define domestic ownership by reference to more than 50% beneficial ownership by resident Indian citizens and/or Indian companies ultimately owned and controlled by resident Indian citizens. Approved applicants claiming incentives must retain domestic status for three years after claiming incentives. Assess financing and acquisition proposals against these requirements as well as the applicable approval conditions. Separately check the terms for any tools or IP made available through the scheme, including commercial use and continuity on exit.

Layout-design protection. The Semiconductor Integrated Circuits Layout-Design Act, 2000 protects qualifying registered layout-designs. Section 7 requires originality and the prescribed distinctiveness conditions; its commercial-exploitation proviso permits qualifying layouts exploited for not more than two years to be treated as not commercially exploited for registration purposes. The Registry explains the filing requirement as within two years of first commercial exploitation. Under section 15, the ten-year term runs from the earlier of the filing date and first commercial exploitation anywhere. Registration and subsequent assignments or transmissions are prima facie evidence of validity under section 19. This protection is distinct from patents and trade secrets; printed circuit boards are not registrable under this Act.

Ownership in the Contract Package

Identify the startup’s original design work, licensed background IP, modifications and commissioned deliverables separately. Employee, contractor and design services agreements should contain appropriate ownership and assignment provisions, while the IP licence should explain the rights retained by the licensor. Do not rely solely on a foreign template’s “work made for hire” label to establish the intended ownership position.

Cross-Border Payments

Assess withholding, applicable treaty treatment and indirect taxes separately for each payment stream. Software access, IP rights, engineering services and the supply of wafers should not be assumed to receive identical treatment. Agree responsibility for applicable taxes, any gross-up, supporting documentation and invoicing. For services, the place-of-supply analysis is material to GST treatment. A clause allocating tax costs does not, by itself, determine the statutory tax treatment.

Dispute Resolution

Evaluate governing law, dispute forum and enforcement together. Consider where the vendor and relevant assets are located, the practicality of urgent relief and the cost of pursuing a claim. The agreed remedy should be usable where it matters—not merely acceptable on paper.

Questions to Answer Before Signing

Before the first NDA, the next EDA renewal or a new IP licence, management should be able to answer:

• Which dependency would prevent tape-out if access ended tomorrow, and what continuity measures are available?

• Which entities, employees and partners may access the PDK, EDA tools and licensed IP, from which locations?

• What may be disclosed to investors, lenders and acquirers, and under which confidentiality and licence permissions?

• How does the prototype programme transition to production, at what price and with what capacity?

• Which yield and quality commitments apply, and what remedies and liability limits support them?

• Who owns the masks, original design data, commissioned deliverables and modifications to licensed IP?

• How is EDA usage measured, audited and renewed, and when must notice be given?

• What triggers each royalty, including for product variants and multi-die packages?

• Can already-designed products continue to be manufactured, sold and supported after licence expiry or termination?

• Which financing, restructuring and acquisition events require consent or notice?

• How are regulatory suspension, prepaid fees and export-control compliance handled?

• How are taxes, gross-ups and supporting documents addressed for each international payment?

• Do incentive claims have the required expenditure records, milestones and ownership compliance?

• Do employee, contractor and partner agreements establish the intended chain of title?

• Can the company produce a coherent contract and entitlement record for an investor, auditor or buyer?

Contracts That Support the Next Stage

A missed access permission can delay tape-out. An unexpected audit true-up can absorb runway. A limited remedy can leave the company bearing the cost of a failed lot. Unresolved transaction consents or incentive conditions can complicate an investment or acquisition. These risks deserve attention before the startup loses its negotiating flexibility.

The question is not only: “How quickly can we sign and tape out?” It is also: “If this chip succeeds, will these contracts still support the company manufacturing and selling it?”

Standard documentation may be a workable starting point. The objective is to align the critical permissions, economics and continuity provisions with the second product, the next funding round and a potential acquisition.

Your chip design startup does not need longer contracts. It needs contracts that fit how the business will operate.

This article provides general information on contractual risk and is not a substitute for advice on a specific agreement or transaction.