IDM vs. Fabless vs. Foundry: A Practical Guide to Semiconductor Decision-Makers
IDMs, fabless chip companies, and foundries occupy different operating positions. An integrated device manufacturer designs chips and owns meaningful fabrication capability; a fabless company concentrates on design while outsourcing wafer production; a foundry manufactures customer designs. The commercial implication is simple: target the person who owns the affected workflow—not a generic “semiconductor buyer.”
The labels are useful starting points, not perfect boxes. Texas Instruments reports that it performs most manufacturing in-house but also uses outside foundries and subcontractors. NXP describes a hybrid model combining owned facilities, a jointly operated facility, foundries, and assembly/test subcontractors. Always verify the current boundary before building an account plan.
What IDM, fabless, foundry, and OSAT mean
The Semiconductor Industry Association production primer separates the chain into design, front-end wafer fabrication, and back-end assembly, test, and packaging. Its U.S. ecosystem definitions describe fabless companies as design companies with no or limited wafer fabrication, foundries as factories that manufacture chips on wafers, and IDMs as vertically integrated companies that design, manufacture, and sell integrated circuits.
| Model | Primary role | Typical operating concerns |
|---|---|---|
| IDM | Designs products and owns substantial fabrication capability. | Factory loading, process technology, yield, capital planning, product road maps, and internal/external sourcing. |
| Fabless | Designs and markets chips while contracting fabrication. | Design productivity, IP, tape-out readiness, foundry capacity, packaging, qualification, and supplier concentration. |
| Foundry | Fabricates wafers using customer-provided designs. | Process capability, yield, utilization, customer onboarding, capacity commitments, quality, and manufacturing execution. |
| OSAT | Provides outsourced assembly, packaging, and testing. | Package technology, test coverage, throughput, traceability, quality excursions, and logistics. |
Current filings show why labels need verification
IDM example: Texas Instruments
Texas Instruments' 2025 Form 10-K says it owns and operates wafer fabrication and assembly/test facilities, performs most manufacturing in-house, and uses outside foundries and subcontractors selectively. That combination still fits an IDM, but it creates both factory-system and supplier-integration opportunities.
Fabless example: NVIDIA
NVIDIA's fiscal 2026 Form 10-K says it uses foundries including TSMC and Samsung to produce semiconductor wafers and uses independent subcontractors and contract manufacturers for assembly, test, and packaging. The operational center of gravity is therefore design, supplier capacity, product planning, and multi-partner coordination rather than owned wafer-fab operations.
Foundry example: TSMC
TSMC's 2025 Form 20-F states that it manufactures semiconductors on wafers using proprietary circuit designs supplied by customers and describes itself as a dedicated foundry. The customer relationship centers on technology qualification, capacity, yield, manufacturing quality, and secure design-to-fab handoffs.
Hybrid example: NXP
NXP's 2025 Form 10-K explicitly describes a hybrid manufacturing model. This is a reminder that target selection should follow the specific product family and workflow: one program may rely on an internal fab while another depends on an external foundry and OSAT.
How the operating model changes the decision-maker
| Problem | Likely problem owner | Supporting stakeholders | Evidence to bring |
|---|---|---|---|
| Design-cycle delay, verification bottlenecks, or engineering compute | VP Engineering, Design Engineering, or Design Operations | EDA/CAD, infrastructure, security, finance | Workflow map, cycle-time baseline, tool integration, security controls, capacity model |
| Fab uptime, yield data, equipment integration, or traceability | Fab operations, manufacturing engineering, or process IT | MES, automation, quality, equipment, data | Downtime cause, data latency, interface design, genealogy, recovery path |
| Foundry or OSAT capacity, lead time, and allocation risk | Supply chain, procurement, or COO organization | Product planning, quality, engineering, finance | Supplier dependency, forecast accuracy, qualification status, scenario plan |
| Quality excursion or qualification delay | Quality or product engineering | Manufacturing, suppliers, customer engineering | Containment flow, root-cause data, audit trail, change-control evidence |
| ERP, MES, PLM, CRM, analytics, or security integration | CIO, enterprise applications, data, or security | Business process owner, architecture, compliance | System-of-record map, APIs, ownership, controls, measurable business outcome |
A five-step semiconductor account-planning method
- Classify the actual business unit. Do not assign a global label from the parent company's reputation. Identify the product line, facility, and sourcing model in scope.
- Map the value-chain boundary. Document who owns architecture, design, fabrication, assembly, test, logistics, and customer support.
- Name the measurable problem. Examples include tape-out cycle time, capacity visibility, yield-learning latency, quality containment time, forecast accuracy, or manual reconciliation.
- Find the owner and approval path. Separate the person accountable for the outcome from IT, procurement, finance, security, and legal reviewers.
- Lead with evidence. Offer a focused assessment or pilot with baseline metrics, system boundaries, pass criteria, risk controls, and a realistic integration plan.
Questions that reveal the right buyer
- Which team owns the KPI this project must change?
- Is the affected manufacturing step internal, outsourced, or split by product family?
- Which system is authoritative for design revision, lot status, quality disposition, forecast, order, and customer commitment?
- Where do teams rekey data or reconcile spreadsheets between engineering, manufacturing, suppliers, and commercial systems?
- What qualification, security, export-control, or customer-approval gates constrain the project?
- Who controls the budget, and who can stop deployment?
Position technology around the handoff
Hexagon IT Solutions supports API integration, ERP services, CRM workflows, custom software, automation, and database optimization. In semiconductor operations, the strongest use case is usually a concrete handoff: synchronizing engineering and enterprise records, connecting supplier and factory events, automating quality workflows, or giving account teams a reliable view of commitments and exceptions.
Frequently asked questions
What is an integrated device manufacturer (IDM)?
An IDM designs and sells semiconductor products and owns meaningful manufacturing capability. Many IDMs also use external foundries or subcontractors, so current sourcing should be verified rather than inferred from the label.
What is a fabless semiconductor company?
A fabless company focuses on chip design and product development while contracting wafer fabrication and usually some assembly and test to manufacturing partners.
What does a semiconductor foundry do?
A foundry fabricates customer chip designs on semiconductor wafers. A dedicated or pure-play foundry emphasizes manufacturing services rather than selling its own competing chip products.
Where do OSAT companies fit?
Outsourced semiconductor assembly and test providers handle back-end services such as packaging and testing after wafer fabrication. They form a separate part of the value chain from wafer foundries.
Which semiconductor decision-maker should a technology provider contact?
Target the owner of the problem: engineering for design workflows, fab operations for manufacturing systems, supply chain for capacity and supplier risk, quality for qualification, and the CIO or enterprise applications team for cross-system integration and governance.
Sources and methodology
Definitions come from SIA materials. Operating examples come from the cited 2025 or fiscal 2026 company filings. The article uses those examples to explain routing logic; it does not claim that any company operates only one model or that organizational titles are identical across firms.
