DILA — Signal by Run Tech Club · Light Mode
Signal by Run Tech Club · DILA Engine 1.03
Diligence Intelligence Layer · Active
Diligence · Intelligence · Signal

Most memos confirm what you already know.
Not DILA.

Diligence that surfaces what's least examined — the real constraint, the logic gap, what must actually be true for this company to work.

What DILA is

Not pattern-matching.
Constraint analysis.

Traction can be manufactured. Narrative can be rehearsed. A pitch deck is a founder's best argument for why they've already won.

DILA measures something different — constraint clarity, mechanism credibility, and learning velocity. The framework runs forward: what must be true next, not what has already been proven. The output names gaps plainly. It doesn't soften for optics.

Every evaluation states its mode. Public mode runs on public signal and what you provide. Connected mode reads the timestamped build record — months of behavioral data accumulated before the founder is fundraising. The distinction is stated on every output. That transparency is the product.

Evaluation modes

Connected to the build.
Or reading public signal.

DILA runs on founders already in the system and companies you're considering from the outside. The evaluation framework is the same. The data source isn't.

Mode 02
Connected mode
DILA reads directly from the proof engine — constraint sequence, experiment log, decision history, failure gate honesty. Founder behavioral record logged, tracked, and evaluated over time. The arc is a data layer no external platform reaches. It sits alongside what funds already use.
What you receive

The evaluation framework.

Applied consistently across vertical and stage, without prior comparable — exposing constraint and logic gaps.

01
Constraint analysis
The real bottleneck — not the stated one. Named plainly.
02
Mechanism credibility
Does the product actually cause the behavior it claims? Is the causal chain real or assumed?
03
Wedge strength
Does the product displace an existing behavior or workflow?
04
What must be true next
Specific, binary conditions. Not aspirations. The bar the company has to clear.
05
Named gaps
What's missing. What's unproven. What's being avoided. Stated without softening.
06
Verdict
Track · Watch · Pass for now. Directional, not scored. Re-entry is always possible.
First call to decision

How funds use it.

01
Before the first call
Walk into the meeting already knowing the real constraint, the mechanism question, and what must be true. The call becomes a hypothesis test.
02
Before diligence
DILA runs the full evaluation before the memo gets written — constraint analysis, named gaps, verdict. A clear look at the risk gap. Know what you're underwriting before you write it.
03
Inside your AI stack via MCP
Connect DILA directly to your existing AI workflow. Query from your own environment. No new dashboard. No context switching.
Proof it works

Unobvious truth.
Constraints pinpointed.

Every evaluation below advances the logic — named constraints, identified gaps, what must be true next. Public signal or connected proof. The output standard doesn't change.

For funds that run on AI
DILA inside your AI stack.

MCP integration in development. Authenticated API access — query DILA directly from your fund's existing AI environment. No dashboard. No context switching.

Request early access →
Early access available to partner funds. partners@rtc.fund