2ndSys — Data Room Sanity Check
Pre-Close Structural Assessment

Before you wire the funds.

A five-day structural review of what the data room doesn't show — and what it can't hide. Surfaces the operating system risks most likely to determine whether the thesis holds.


5
Business Days
$35–50k
Fixed Fee
1
Written Determination
Request a Sanity Check
The Problem with Pre-Close

The data room was built to support the deal, not assess the system.

Financial and technical diligence tells you what the company has built. It doesn't tell you whether what they've built can carry what you're underwriting.

AI-native companies in particular present a specific pre-close risk: the model performs, the demo lands, the revenue is real — and underneath it, the operating system is already at its limit. The architecture hasn't been stress-tested against the growth plan. Decision rights are informal. State is inconsistent across subsystems.

These aren't implementation details. They are structural constraints that will determine your return. Five days is enough time to know whether you're walking into them.

What We Look For

Six structural red flags. Any one of them matters.

The DRSC focuses on the structural signals most predictive of post-close failure — across the technology, organization, and operating model.

Technology
Architecture at capacity
The system works at current load. Evidence suggests it cannot absorb the volume or complexity the growth plan assumes.
Technology
State traceability gaps
Outputs cannot be traced to inputs with confidence. The system produces results but cannot explain them — a compliance and scalability liability.
Organization
Diffuse decision authority
No clear accountability for cross-functional decisions. Works at current headcount. Will not work at 2×.
Organization
Key person dependency
Critical system knowledge lives in one or two people. Not documented. Not transferable. A single point of failure for the whole operating system.
Operating Model
Probabilistic/deterministic confusion
AI inference outputs are being used in contexts that require deterministic behavior. The boundary between the model and the business logic is not governed.
Operating Model
No failure containment
When something breaks, it propagates. There are no clear boundaries that stop a technology failure from becoming an organizational one.
Process

Five business days. One written determination.

The DRSC is designed for the pre-close window. It works with what's available — data room materials, architecture documentation, and limited leadership access — and returns a written determination before the deal moves.

01
Materials Review
Data room documents, architecture diagrams, technical documentation, and org charts reviewed against the declared growth thesis. Day one and two.
02
Targeted Leadership Access
Focused conversations with the CTO or Head of Engineering and one operating leader. Scoped to structural questions — not a full interview process. Day two and three.
03
Structural Red Flag Assessment
Six structural risk categories evaluated against available evidence. Each is classified as confirmed, probable, or not evidenced. Day three and four.
04
Written Determination
Single written deliverable: dominant structural concern, red flag classification, and a preliminary readiness signal — Ready to Proceed, Proceed with Conditions, or Structural Concern. Day five.
Deliverable

A structural read, not a diligence report.

Data Room Sanity Check Brief
Designed to give an investment committee a clear structural read before the deal closes. Not a comprehensive assessment — a targeted determination of whether there are structural concerns material enough to affect the decision.
Dominant Structural Concern
The single most significant structural risk identified from available evidence. Named, explained, and located in the operating system.
Red Flag Classification
Each of the six structural risk categories classified as confirmed, probable, or not evidenced based on available materials and access.
Preliminary Readiness Signal
One of three signals: Ready to Proceed, Proceed with Conditions, or Structural Concern. With the reasoning that produced it.
Post-Close Recommendation
Whether a full System Readiness Review is warranted post-close, and which structural areas it should prioritize.
DRSC vs. System Readiness Review

Two different questions. Two different moments.

The DRSC and the SRR are complementary, not competing. The DRSC answers the pre-close question. The SRR answers the post-close question.

Data Room Sanity Check
Timing: Pre-close
Duration: 5 business days
Fee: $35,000–$50,000
Access: Data room + limited leadership
Question: Are there structural concerns material enough to affect this decision?
Output: Preliminary readiness signal + dominant concern
System Readiness Review
Timing: Post-close
Duration: 3–6 weeks
Fee: $200,000–$250,000
Access: Full system access + leadership team
Question: Can this operating system carry the growth plan we've underwritten?
Output: Full readiness classification + dominant constraint + first failure signature

Five days. Before the deal closes.

The structural concerns that matter most are visible before you wire the funds. Let's look.

Request a Sanity Check