04 — MemoDecision system

Leave with a decision brief

Review the thesis, risks, open questions, and the facts most likely to change the answer.

Use this route toOpen in Angel OS →

01
Prepare the meeting
Bring company-specific questions, not a generic checklist.
02
Export the view
Keep the thesis, sources, risks, and assumptions together.
03
Monitor change
Alert only when new data moves the investment view.

04.1 — Output

Specimen — illustrative company, not a real filing

A decision brief for the meeting.

Investment memo

Company under analysis

Investment signal82^/100

Meridian Runtime, Inc.

SeedDelaware C-corpSF Bay AreaConfidence: high

Primary thesis — Proprietary inference architecture emerging underneath a wrapper narrative, carried by an unusually strong founder network.

Core scores

Dimension	Score
Founders	91
Timing	93
Market	88
Technical moat	86
Defensibility	84
Capital efficiency	80
Product	74
Traction	72
Distribution	59

Predicted trajectory

12 MO Enterprise platform with usage-based compute pricing.

36 MO Vertically integrated inference stack sold beneath the application layer.

Alpha

01Hiring pattern suggests a transition into custom inference infrastructure, not model fine-tuning.

02unpublished but directly relevant prior IP held by the CTO, filed under a previous employer's assignment.

03independently hiring around the product — three early customers posting integration roles that name it explicitly.

0412–18 months behind is where the nearest competitors sit on the public benchmark artifacts.

Hidden risks

01Patent ownership may overlap with a founder's former employer ; assignment is not recorded with USPTO.

0261% of revenue appears attributable to two customers, both in one vertical.

03Pricing may not support inference costs at scale under the observed usage mix.

US context — activated

Delaware C-corp, two Form D filings. No sector regulator gates the product today; export-control exposure becomes live if the runtime ships as on-prem hardware. Talent is the binding constraint — compiler engineers in the Bay Area are the scarcest input in the plan.

Ask what changes the decision.

Each question targets an uncertainty surfaced by the company data.

What's your go-to-market strategy?Your customer announcements imply considerably faster enterprise adoption than your sales hiring would suggest. Are deployments primarily founder-led, channel-led, or expanding organically inside existing accounts?

Do you have IP?The memory-scheduling application lists an inventor who was employed elsewhere at the filing date, and we can't find a recorded assignment. How was that handled?

How do you think about pricing?Pricing moved from per-call to per-compute-unit in March. Was that a margin correction, or the first step toward selling the runtime itself?

04.2 — Δ thesis

Research never closes.

New hires, patents, customers, lawsuits, rounds, and releases trigger a fresh read. See what changed—and whether the thesis should move.

Get alerted when the thesis moves—not whenever a job runs. Every change keeps its reason and timestamp, so correct and failed predictions remain measurable.

Material change detected · 14 days

72→84

The enterprise expansion predicted in April appears to be occurring. Four Fortune 500 customer signals detected, three of them from job postings naming the product. Technical-moat score unchanged; distribution revised upward.

Prediction heldIP flag still open