The 5 Questions That Matter More Than the Pitch

Intended audience: Investors and family offices evaluating advanced reactor deals, and the founders preparing to be evaluated.

Executive Summary

Advanced reactor pitches are compelling, and the most compelling ones aren't always the most credible. Technical founders can be genuinely brilliant and still be years away from a defensible licensing basis — fluency and maturity are not the same thing. This post lays out five questions, deliberately built to require no technical background to interpret, that separate reactor programs with real regulatory traction from ones still running on enthusiasm. One of the most common failure patterns these questions surface: developers trying to pursue NRC and DOE pathways simultaneously without understanding that this splits — not doubles — their program's effectiveness.

Why These Questions Are Built the Way They Are

Nuclear startup founders are often exceptional engineers and physicists. That's precisely what makes technical due diligence hard for a non-technical investor: a founder who can talk fluently about core geometry, passive safety systems, or fuel behavior can sound credible whether or not the program behind them is actually mature. Technical charisma is real, and it isn't the same thing as regulatory readiness. Clever founders can b*llsh!t too — not necessarily out of dishonesty, but because depth of knowledge in one area can stand in for progress in another.

These five questions are designed to route around that problem. None of them require an investor to evaluate physics. Each one asks about documentation, control, and decision-making process — things that exist or don't exist, independent of how well someone can explain them.

1. What is your actual licensing basis?

Ask whether the team is designing to 10 CFR 50, 52, or 53 — or to a DOE or Department of War authorization process under 10 CFR 830. If the answer is vague, or if the team is pursuing more than one pathway at once without a clear reason, that is a red flag, not a technicality.

A growing number of developers want to pursue both an NRC pathway and a DOE authorization simultaneously, without recognizing that this splits engineering, licensing, and QA effort rather than hedging risk. There is currently no harmonized set of requirements between the two frameworks. The closest thing available is draft interim staff guidance — DANU-ISG-2026-XX, issued for public comment in April 2026 — which maps where NRC and DOE/DOW requirements are expected to overlap, largely in quality assurance, design criteria, and source term analysis. It is explicitly a draft, not a final agency position, and it does not eliminate the need for a complete, independent NRC application.

One more version of this same question, worth asking directly: if the answer is 10 CFR 57, is the founder aware that Part 57 is still a proposed rule? Executive Order 14300 originally called for a final rule within 18 months of the order — November 2026 — but that timeline assumed the proposed rule would publish for comment by February 2026. It didn't publish until May 1, 2026. Applying the same roughly 9-month proposed-to-final cadence the EO built in, but anchored to the actual publication date, my own estimate is a final rule closer to February 2027 — later than the original EO target, and my professional calculation rather than an NRC-confirmed date. Either way, a founder building a licensing strategy around Part 57 today is designing to a framework that isn't final, on a timeline that has already slipped once. I've written a longer explainer on the proposed framework's mechanics, linked below, for readers who want more detail.

2. Which design version is configuration controlled today?

Is there a formally baselined design? Who has authority to approve a change to it? How are safety-impacting changes tracked once they're made? If the answer is "it's evolving," the program should expect rework later — because an uncontrolled design invalidates the safety analyses and QA records built on top of it.

3. Which parts of the design are locked — and which are still assumptions?

Core geometry, materials selection, safety-related interfaces, balance-of-plant dependencies: at some point, each of these has to stop being flexible. Construction and licensing punish ambiguity in different ways, but they both punish it. A team that can clearly separate "locked" from "still assumption" is further along than a team that describes everything as in-progress.

4. What QA system are you operating under right now — not eventually?

Not "we'll implement QA later" or "we'll scale it when we need it." The real question is what standards apply today, who holds QA authority, and how work is verified independently of the person who did it.

This is also where the dual-pathway problem shows up again, and it's expensive. A quality assurance program description built for the NRC for 10 CFR 50, Appendix B alone, or a quality assurance program plan for DOE authorization for DOE-STD-1271-2025 alone, is a substantial undertaking on its own. Building one QA program intended to satisfy both requires a regulatory crosswalk between the two frameworks to make sure nothing gets missed on either side — an extra layer of work most developers don't anticipate and are surprised to see priced into a QA engagement. If a team hasn't budgeted for that crosswalk, they likely haven't accounted for the real scope of what a dual-pathway QA program actually requires.

5. Which assumptions have to remain true for your safety case to hold?

Fuel performance, materials behavior, passive system response, operator actions, external hazards, an assumed ultimate heat sink that behaves as modeled — every one of these is a risk until it's proven, and every one is something a regulator will eventually challenge. A team that can name its own assumptions is telling you where its real risk lives. A team that can't has probably not looked hard enough.

What These Questions Reveal, Together

None of them test vision. They test program maturity. Enthusiasm sounds like "we're moving fast" and "the technology is proven." Maturity sounds like "here's what's frozen," "here's what's controlled," and "here's what we've validated." The second set of answers takes longer to produce and is far less exciting to hear in a pitch meeting — which is exactly why it gets skipped, and exactly why it matters.

What Investors Should Do Now

Ask these five questions before the term sheet, not after. If a founder's answers are confident but non-specific, ask for the artifact behind the answer — the actual document, baseline, or QA procedure — not just the description of it. A program's ability to produce that artifact on request is itself a data point.

Diligence on an advanced reactor investment doesn't have to stop at the physics. The same questions that reveal program maturity to an investor are the ones a licensing team lives inside of every day.

FAQ

Q: Can a reactor developer legally pursue both NRC and DOE authorization pathways at the same time?

A: Yes, but doing so effectively requires the developer to understand that there is no fully harmonized regulatory framework between the two today. Draft interim staff guidance DANU-ISG-2026-XX (ADAMS ML25363A192), issued for comment in April 2026, identifies where NRC and DOE/DOW requirements are expected to overlap — largely in quality assurance, design criteria, and source term development — but it remains in draft form and does not substitute for a complete NRC application.

Q: Why is a QA program for both NRC and DOE authorization more expensive than for one pathway alone?

A: Because the two frameworks aren't identical, a developer pursuing both needs a crosswalk between NRC's 10 CFR Part 50 Appendix B / ASME NQA-1 requirements and DOE's authorization requirements to confirm nothing is missed under either framework. That regulatory crosswalk is additional scope beyond a single-pathway QA program description, and it's frequently underestimated in early cost planning.

Q: What does it mean for a reactor design to be "configuration controlled"?

A: It means there is a formally baselined version of the design, a defined authority for approving changes to it, and a documented process for tracking any change that could affect the safety basis. Without configuration control, safety analyses and QA records built against an earlier design version can become invalid the moment the design changes.

Q: Isn't asking about "locked" versus "conceptual" design elements too technical for a non-technical investor?

A: No — the investor doesn't need to evaluate whether the locked elements are the right engineering choices, only whether the team can clearly say what is locked and what isn't. The clarity of the answer, not its technical content, is the signal.

Q: How is the Reactor Program Maturity Index™ (RPMI) different from these five questions?

A: These five questions are the investor-facing lens — quick, non-technical, and designed to surface program maturity in a single conversation. RPMI is the founder-facing version: a free, ten-category self-assessment covering licensing strategy, regulatory engagement, safety basis, QA, design control, and more, with each question built and peer-reviewed specifically to produce a defensible, regulator-aligned score rather than a self-rating a founder might inflate without realizing it.

Q: Is 10 CFR Part 57 a safe pathway for a founder to build a licensing strategy around today?

A: 10 CFR 57 is a proposed rule, not yet final. Executive Order 14300 originally targeted a final rule by November 2026, based on an 18-month clock from the order and an assumed 9-month gap between proposed and final rule. But the proposed rule, which was supposed to publish for comment by February 2026, didn't publish until May 1, 2026. Applying that same ~9-month cadence to the actual publication date puts my own estimate for a final rule closer to February 2027 — my professional calculation, not an NRC-published date. A founder pursuing Part 57 as their licensing basis is designing to a framework that isn't locked yet, on a schedule that has already slipped once. Investors should treat a Part 57-based strategy as further from execution than a strategy built on an already-finalized rule like Part 50, 52, or 53. For the full mechanics of the proposed framework, see my earlier explainer, "Explaining 10 CFR Part 57 – A New Pathway for Microreactors."

Q: What's the single biggest tell that a reactor program isn't as mature as its pitch suggests?

A: Enthusiasm-based marketing language in place of artifact-based answers. "We're moving fast" or "the technology is proven" describes a feeling. "Here's our configuration-controlled baseline" or "here's our QAPD" describes something that exists and can be reviewed.

Sarah Gibboney, P.E. is the Founder of Gibboney Nuclear, PLLC, a nuclear licensing consultancy serving advanced reactor developers. She has 17 years of nuclear energy experience, including co-authoring Construction Permit Applications for both ARDP awardees, TerraPower Natrium and X-energy Xe-100.

Related reading: "Explaining 10 CFR Part 57 – A New Pathway for Microreactors," Sarah Gibboney, P.E.