Debrief: Avery Dustin — 2026-05-22
Summary
Dustin met with Avery, a former McKinsey senior engagement manager in semiconductor and aerospace/defense manufacturing who is starting a TSMC internship. The conversation surfaced operational supply chain tracking failures in Patriot missile and Boeing manufacturing contexts, explored defense as a target market while raising ethical and venture-model concerns, and produced a near-term introduction to a Huntington Ingalls executive. Avery positioned herself as a more valuable connector post-internship and flagged a network of McKinsey semiconductor contacts for later stages.
Key Themes
1. Supply Chain Tracking Failures as Operational Reality Avery provided two grounded, firsthand examples of the exact problem Bliss and Dustin are trying to solve. On a Patriot missile project, finished products had defects with no way to identify which team last touched the part — root cause analysis was paralyzed by absent material tracking. At Boeing, external supplier complexity meant a broken door lug nut could be sourced to a vendor but not to the specific process step where failure occurred. In both cases, the goal wasn’t just fixing the current defect — it was preventing recurrence. Avery framed TSMC and Nvidia as facing the same problem at larger scale, with triage cycles measured in weeks. This is among the most operationally specific validation of the founders’ core problem statement across all interviews to date.
2. Defense as Target Market — Genuine Compliance Need, Complicated Venture Profile Avery confirmed that defense is the one sector where China restriction compliance is taken seriously. However, the conversation surfaced two complications the founders have not fully resolved. First, Dustin raised the structural concern about government as a sole client and its effect on venture attractiveness. Second, Avery introduced a personal philosophical tangent about the ethics of conflict-correlated wealth creation — noting that a company whose valuation spikes with ‘light conflict’ with China creates a strange moral position. The conversation did not resolve either concern but named them explicitly.
3. Huntington Ingalls (HII) as a Near-Term Access Point Avery’s former manager is now Director of Operations and Technology Strategy at HII, which manufactures submarines and aircraft carriers. He holds a Stanford PhD, is open to talking with Stanford-connected founders, and is actively interested in AI enablement. One sharp operational note: avoid the phrase ‘digital twin’ — a prior failed implementation made it a loaded term. Avery offered to make the introduction and seemed confident in the contact’s receptiveness.
4. Semiconductor Industry Hierarchy and TSMC’s Geopolitical Posture Avery mapped the foundry landscape as TSMC → Samsung → GlobalFoundries → Intel, with Intel historically struggling but now gaining relevance through preliminary Apple partnership talks — which she characterized as ‘devastating for TSMC.’ She offered a nuanced read on TSMC’s capacity expansion in the US and Japan: she believes their de-risking intent is genuine, not performative, driven by a realistic assessment that a Chinese invasion of Taiwan would strand their engineering base. This aligns with and deepens the geopolitical framing from earlier synthesis memos.
5. Avery’s Network — Staged Value Avery was explicit that her value as a connector increases post-TSMC-internship. Her current contacts include McKinsey semiconductor senior partners (senior, high-bar, not yet appropriate), Taiwan contacts Melissa Shi (TSMC-adjacent through family) and Charles Chen (McKinsey Taiwan, no semi experience), and South Korea contact Cla Choy (McKinsey Korea, likely serves Samsung). GlobalFoundries was surfaced briefly via a departed contact. Austin, Texas was highlighted as a more accessible geography for physical fab visits than New York, though Avery noted it’s the office relationships — not fab floor access — that matter most.
Notable Quotations
“They would get to a finished Patriot missile, they wouldn’t know what went wrong. And then they would find one piece that was broken, and they would have no idea how to get it back to the team that, like, last touched it.” — Avery. Context: Firsthand McKinsey project experience; the most operationally grounded description of the core tracking problem heard across interviews.
“There’s gonna be so much money that stands to benefit from not like a full scale war with China, but like some sort of light conflict. And like, I just wonder what it would be like… if there’s some sort of light war, becomes worth tens of billions of dollars. And like you create billions of dollars of personal wealth. Like, that’s just like a crazy like. So that’s like I’m kind of grappling with.” — Dustin. Context: Founder surfacing an ethical concern about conflict-correlated upside; unprompted and unresolved.
“I feel like I will be a lot more valuable to you after my summer internship… TSMC is so secretive. Not that I would share like trade secrets with you guys, but I think understanding how they approach even supply chain type stuff would be helpful.” — Avery. Context: Explains why near-term McKinsey semiconductor intros are premature; frames herself as a staged asset.
Themes & Contradictions
This conversation is largely confirmatory but adds operational texture that prior interviews lacked. The most direct parallel is with Yisroel (2026-05-08), who validated the defense/compliance wedge specifically for DoD and defense primes — and Avery’s firsthand Patriot missile anecdote is the strongest practitioner-level confirmation of that thesis to date. Both Yisroel and Avery point to defense as the sector where China compliance genuinely matters, which aligns with the founders’ own framing.
However, Avery’s conversation creates a soft contradiction with Josh (2026-04-30), who characterized compliance as ‘table stakes’ for defense — not a differentiator — and had never heard of UFLPA. Avery’s Patriot missile example is more about internal tracking and root cause analysis than export compliance per se, which raises the question of whether the tracking problem and the compliance problem are actually the same product, or two adjacent ones that the founders are treating as one.
The supply chain tracking failure narrative (Patriot missiles, Boeing) is the closest this interview series has come to a practitioner confirming the operational pain at the manufacturing/traceability layer — which is distinct from the compliance certification layer that Kyle (2026-04-28) and Minseok (2026-05-05) addressed. Minseok’s point that ‘compliance data is binary, not granular’ remains an unresolved challenge to converting compliance screening into a richer data asset. Avery’s examples suggest the richer data problem is real and felt — but she is describing it from a consulting intervention frame, not a buyer frame.
The TSMC geopolitical de-risking discussion extends and corroborates Minseok’s framing of TSMC as a structurally motivated actor, though neither conversation reached a conclusion about whether TSMC’s US expansion creates a discovery or sales opportunity for the founders.
Business Problems & Painpoints
Avery surfaced two distinct, operationally credible pain points grounded in her McKinsey project experience. First, within-facility traceability failure: on the Patriot missile project, a completed product with a defective part could not be traced back to the last team that touched it — root cause analysis required manual reconstruction that took far too long. This is a micro-level version of the founders’ core thesis, playing out inside a single building. Second, multi-supplier root cause attribution: at Boeing, the failure might originate at an external supplier, pass a quality check at handoff, degrade further in Boeing’s process, and reach the finished aircraft with no clean chain of custody to identify where the failure introduced. The goal in both cases was prevention, not just remediation — but the traceability infrastructure didn’t exist to enable it.
Avery framed TSMC and Nvidia as facing the same challenge at scale, with triage cycles measured in weeks. This validates the problem as real and cross-sector, not just a defense-specific edge case. Notably, Avery did not describe these as problems that had been solved — only that McKinsey was brought in to help build stopgap tracking systems, suggesting the underlying data infrastructure remains weak.
Avery did not speak as a buyer or a potential budget holder. Her pain is consulting-observed pain, not buyer-expressed pain — an important distinction. She also did not name a specific tool or workflow she wished existed, which limits the signal strength relative to what would come from a direct operator conversation.
Emotional Signals
Avery came across as warm, engaged, and genuinely curious about the problem space — not just performing helpfulness. She lit up on the Patriot missile and Boeing anecdotes, speaking quickly and with specificity, suggesting these experiences were genuinely frustrating at the time and memorable. Dustin’s unprompted philosophical detour about conflict-correlated wealth was the most emotionally charged moment in the conversation — he flagged it as something he’s ‘grappling with,’ which suggests it’s a real internal tension, not a performative scruple. Avery’s response was sympathetic but brief; she didn’t push back or validate in depth. The HII introduction was offered easily and without hesitation, signaling genuine willingness to help. Avery was candid about McKinsey senior partners being ‘assholes’ — a relaxed, trust-signaling disclosure.
For Founders
- Avery’s examples — Patriot missile traceability failure, Boeing multi-supplier root cause — describe a tracking and attribution problem inside manufacturing operations, not an export compliance problem. Are you building for these two different pain points, or are they the same product in your current thinking?
- The HII introduction is the first direct defense-prime access point in your interview series — but Yisroel framed compliance as ‘table stakes’ for defense, not a wedge, and Josh said compliance is already assumed there. Does HII validate your thesis, or does it test whether the tracking problem and the compliance problem are actually one product?
- Dustin named the ethical tension around conflict-correlated wealth creation unprompted and in front of a new contact. Is that a resolved question between the two of you, or something that needs a direct co-founder conversation before you go deeper into defense?