Home/Glossary/Custom ASIC Development Costs and Budgeting
Semiconductor knowledge

Custom ASIC Development Costs and Budgeting

ASIC project choices made within a defined development and product budget. Cost control can involve selecting a suitable process, reusing qualified IP, limiting die area or sharing prototype fabrication through an MPW run.

← All glossary termsTechnical guide · 5 min read
In this article

ASIC project choices made within a defined development and product budget. Cost control can involve selecting a suitable process, reusing qualified IP, limiting die area or sharing prototype fabrication through an MPW run.

ASIC cost planning areas
Planning categories only. This illustration contains no supplier prices or fabricated cost proportions.

Affordable depends on the product

An affordable custom ASIC is one whose total development and delivered-product costs fit the value and requirements of the application. It is not necessarily the design with the lowest engineering quote or the smallest die. Begin with the product constraint that custom silicon addresses and compare a credible programmable or standard-component alternative. The ASIC case may rely on integration, energy, performance or lifecycle benefits. Those benefits should be explicit so a cost reduction does not quietly remove the feature that justified the custom design.

Separate non-recurring and recurring cost

Non-recurring engineering can include design effort, IP licensing, masks, package development, test preparation and validation. Recurring costs include the manufacturing and delivery activities applied to production units. Keep those categories separate, then evaluate the combined economics at realistic volumes. A prototype quotation may include a different scope from production supply. Show what each estimate covers and which inputs need supplier confirmation. An unexplained unit price can be misleading when it excludes substantial work required to reach a repeatable manufactured product.

Reduce cost by reducing uncertainty

Stable requirements, reusable verified IP and early feasibility checks can avoid expensive rework. A mature process may be appropriate when it meets the product's needs and offers suitable resources. Selective integration can avoid paying to redesign functions that are already served well by external components. These are engineering choices, not universal rules. Evaluate their effect on verification, package cost, test and future changes. The least expensive route at one stage can create greater total expense if it leaves a critical risk unresolved until after tape-out.

Use scenarios rather than a single promise

Model several plausible production volumes and development outcomes. Include the possibility of a design revision, changes in demand and assumptions about yield. Identify which variables most affect the result. This helps a startup or established company decide when to commit more funding and which evidence to obtain first. Public content cannot provide a binding price for an unspecified ASIC. A useful cost discussion prepares the information needed for a project-specific estimate and makes the uncertainty visible without inventing a universal low-cost guarantee.

Questions about ASIC affordability

Is the lowest NRE always the lowest total cost?

No. A lower development charge can exclude work or lead to a higher recurring cost. Compare complete scopes and realistic production scenarios.

Can an MPW run make every ASIC project inexpensive?

It can help some prototype programs share fabrication resources, but design, IP, packaging, test and later production still require evaluation. Availability and terms depend on the selected service.

Establish a common comparison boundary

List every activity required to reach the intended product milestone. Depending on scope, this can include architecture, source design, verification, implementation, IP, masks, fabrication, packaging, test and validation. Identify customer-supplied work and external dependencies. Two quotations are not directly comparable when one excludes essential activities that the other includes. Separate firm supplier information from preliminary engineering estimates and state the date or context of commercial inputs where available. A transparent boundary makes the budget useful for decisions instead of merely producing a single attractive number.

Model the drivers and uncertainty

Production volume, die area, yield assumptions, package choice and test effort can influence recurring cost. Development complexity, IP and the possibility of revision affect non-recurring investment. Use scenario ranges where the evidence is uncertain. Identify which variables have the greatest effect on the conclusion and obtain better information about those first. Avoid publishing invented prices or a universal break-even volume. The model should help a project team understand its own decision, including what would change if demand, architecture or the manufacturing route differs from the initial expectation.

Stage commitments around evidence

Link spending decisions to concrete learning. A feasibility study can test an architectural assumption, a prototype can support integration work, and characterization can establish important silicon behavior. Define what each stage must demonstrate before the next commitment. This does not eliminate risk, but it makes the remaining uncertainty visible. Preserve the assumptions behind an approved budget so later changes can be discussed coherently. A schedule or cost revision is easier to evaluate when the team can identify the requirement, supplier condition or technical finding that caused it.

Include lifecycle and opportunity cost

Compare the custom chip with credible alternatives over the expected product life. Consider software, board changes, inventory, support and the flexibility lost or gained. A low initial cost may be less attractive if it leaves the product dependent on an unsuitable component or makes a likely revision difficult. Conversely, a custom design can be unnecessary when an available solution meets the real requirements. The final recommendation should connect expenditure to product value and acknowledge the conditions under which another approach would be preferable, rather than treating custom silicon as a goal independent of the business need.

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.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →