In this article
Companies that provide engineering services for custom integrated circuits. Capabilities vary across architecture, digital design, analog design, verification, physical implementation and production support.
Look for the right specialization
A custom IC design firm may focus on analog circuits, digital ASICs, mixed-signal integration, physical implementation or a broader development scope. The label alone does not establish technical fit. Describe the product's critical functions and constraints, then ask which parts the proposed team can deliver directly and which depend on external resources. A demanding sensor front end and a large digital accelerator require different expertise. The selection process should connect the firm's actual capabilities to the functions that dominate the project's risk.
Evaluate the working team
Ask how technical leadership, specialist review and continuity are organized. A company's overall experience is useful context, but the engineers assigned to the project need relevant support and clear responsibilities. Review how architecture, verification and implementation teams communicate. If the engagement includes customer-supplied design data, agree how assumptions and open issues are reviewed. A firm should be able to explain how it identifies integration risks and demonstrates progress without relying only on a generic milestone chart or an unqualified claim of experience.
Protect ownership and maintainability
Clarify the deliverables, permitted use of IP, access to source and models, and the information needed for future changes. The customer should understand which assets it owns and which remain licensed dependencies. Discuss what happens when an engineer leaves, a tool version changes or the product needs a later revision. Maintainability is not established by receiving a folder of files if the essential context, licenses or reproduction steps are missing. Make these questions part of the engagement while responsibilities are still being defined.
Compare the complete proposal
Normalize scope before comparing cost. Include verification depth, physical sign-off, packaging and test support where needed. Identify assumptions about process access, IP readiness and customer inputs. Ask how engineering changes and unresolved issues affect the plan. A technically detailed proposal can reveal both strengths and limitations, which is more useful than a universal claim of low cost or fast delivery. The final decision should weigh technical fit, execution discipline, ownership and support alongside the commercial terms.
Questions about design firms
Is an analog specialist automatically suitable for a large digital SoC?
Not necessarily. Some firms cover both areas, while others specialize. Evaluate the actual team, resources and integration plan for the proposed scope.
Should the lowest quote determine the choice?
Only after the scopes and assumptions are comparable. Missing verification, licensing, productization or support work can materially change the total effort and risk.
Write a responsibility matrix
For each major activity, identify who supplies the input, performs the work, reviews the result and authorizes the next step. Include requirements, IP, verification, implementation, manufacturing preparation and product release where relevant. A broad service label cannot answer these questions by itself. Make customer dependencies visible and define how incomplete or changed inputs affect the plan. This gives both organizations a practical basis for managing handovers and prevents important work from being assumed to belong to the other party when a project reaches a difficult decision.
Use milestones with acceptance evidence
Describe deliverables and checks, not only dates or percentage-complete estimates. An architecture review should leave an approved specification and open-issue record. An implementation handover should identify the source revision, constraints and supporting reports. A manufacturing release should name the required evidence and authorization. The appropriate details vary by engagement, but the principle is consistent: progress should be observable and reviewable. If an exception is accepted, preserve its scope and approval so later teams understand the intended limitation rather than rediscovering it as an unexplained inconsistency.
Manage changes without losing context
Requirements and technical assumptions can evolve. Define how a proposed change is evaluated for engineering, verification, schedule and commercial impact. Keep the approved decision connected to the affected design and documentation revisions. This avoids treating an informal conversation as a replacement for the source of truth. An escalation path is useful when teams disagree or when a supplier dependency affects several activities. Good coordination does not mean avoiding difficult findings; it means bringing them to the right decision-makers with enough evidence to choose a practical next step.
Review ownership and continuing support
Clarify the rights and deliverables associated with source data, licensed IP, models and production information. Identify what the customer will need to maintain or revise the product later. Ask how errata, personnel changes, tool dependencies and supplier changes are handled. Current program participation or a certificate can support an evaluation, but its actual scope should be checked rather than assumed. A strong engagement leaves the customer with an understandable engineering record and a clear support path, in addition to the immediate deliverables described in the proposal.
A practical cross-discipline review
Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.
Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.
Explore the related Avnet offering or discuss your project requirements.
