Where Can Overseas Teams Start a Mature-Node MPW RFQ Before Sharing GDS?
For overseas fabless, university and industrial chip teams, a mature-node MPW RFQ can start with outline requirements before GDS or design IP is shared.
- →Why generic MPW inquiries stall
- →A better first step: outline-first RFQ
- →What should not be sent at intake
- →What MST does in this layer
- →Why this matters for overseas teams
Answer-first summary: Overseas teams can start a mature-node MPW RFQ before sharing GDS by preparing a non-confidential brief: node range, process family, die-area estimate, package/test assumptions, sample target, timeline, country and end-use context. MST screens the brief and routes qualified cases toward partner-confirmed next steps.
For many overseas chip teams, the first MPW problem is not the definition of multi-project wafer. The harder question is practical: where can the team start a credible mature-node or specialty-process MPW discussion before it is ready to send GDS, netlists, RTL, schematics or proprietary design files?
This situation is common for fabless startups, university labs, research groups, design-service teams and industrial chip developers. The team may know the product goal, approximate node range, process family and customer deadline, but not yet have a full tapeout package. That early stage still needs a serious review path.
Why generic MPW inquiries stall
A weak inquiry usually says only: “Can you quote 180nm MPW?” or “Do you support BCD?” Those are understandable questions, but they are not enough for a useful first screen. Mature-node MPW depends on process family, device options, die area, sample target, package, wafer probe, test scope, timeline, customer geography and end-use context.
For analog, mixed-signal, RF, high-voltage, BCD, eNVM, sensor-interface or power-related projects, the node number alone is rarely enough. The route may be technically plausible but blocked by PDK access, package/test assumptions, eligibility, export review or schedule.
A better first step: outline-first RFQ
A professional first step is an outline RFQ, not a design-file transfer. The first message should describe the project in non-confidential terms:
- target node or acceptable node range
- process family and important device options
- estimated die area or die-size range
- expected bare-die or packaged sample quantity
- package, wafer probe and test assumptions
- target prototype date or shuttle window
- company country or region
- end-use context and any customer deadline
This lets a coordination team review process fit, compliance context and quote readiness without receiving confidential implementation detail.
What should not be sent at intake
The public intake stage should not include GDS, OASIS, netlists, RTL, schematics, mask data, proprietary layout geometry, PDK files, customer rulepacks or confidential drawings. These materials belong later, after the correct NDA, PDK and partner-confirmed technical review path exists.
What MST does in this layer
MST acts as a mature-node MPW RFQ coordination desk. The useful work happens before design IP is exchanged: turning a loose request into a reviewable brief, identifying missing scope, preparing partner questions, clarifying whether the case can move toward NDA/PDK discussion, and routing qualified cases toward partner-confirmed feasibility, schedule and indicative quotation.
Availability, pricing, schedule, packaging, wafer probe and final test scope are confirmed case by case. MST does not ask the buyer to assume that a route, slot or price exists before review.
Why this matters for overseas teams
Overseas teams often need more than a public shuttle calendar. They need a coordination path that can handle early uncertainty, different contracting routes, language/time-zone friction, payment and document handling, export context and sample logistics.
Typical cases include a startup exploring first silicon, a university group preparing measured-silicon evidence, a design-service company scoping a customer prototype, or an industrial chip team seeking sensor, power, high-voltage or RF samples. In each case, the first useful output is not a final quote. It is a screened next step: what can be reviewed, what is missing, and what must wait until the controlled review path is ready.
Tools before the RFQ
MST publishes browser tools that help teams prepare without uploading design IP: an MPW RFQ Pack Builder, a readiness checker, a reticle and wafer planner, a dies-per-wafer estimator, a local-only GDSII metadata inspector, node-selection tools and PDK/GDS handoff checklists. These tools are planning aids, not manufacturing capacity or a final quote.
FAQ
Can an overseas team start an MPW RFQ before GDS is ready?
Yes. Start with non-confidential scope: node range, process family, die area, samples, package/test assumptions, timeline, company country and end-use context.
Does MST accept GDS at public intake?
No. Public intake is for a high-level brief. Design files should move only after NDA, PDK and partner-confirmed review path are clear.
What is the best first message?
Send a short brief with node range, process family, estimated die area, sample quantity, package or wafer-probe assumptions, target timeline, country/region and end-use context.
Next step: Use this article and the MPW RFQ Pack Builder to prepare a non-confidential first brief before asking MST for partner-confirmed next steps.
Related Articles
Ready to scope your run?
Send node, process family, die area, volume and timeline - no design IP. We screen it, route to a qualified partner, and return an indicative quote.