Category Definition
The Private Market Stack: Judgment vs. Workflow
// CATEGORY DEFINITION: WHY PIPELINE IS NOT CONVICTION
The short answer
Workflow software automates the process of deploying capital: pipelines, CRM records, memo formatting. Judgment infrastructure evaluates the asset itself, testing a deal's claims against business physics and returning a reproducible verdict. The private-market stack has incumbents for retrieval, analytics and workflow. The judgment layer is the one without one.
The private capital software market has historically focused on the mechanics of deploying capital, not the physics of the asset itself. Consequently, venture capital remains the last unaudited asset class.
askOdin does not manage your pipeline. We audit your assets.
// THE FOUR LAYERS
The Four Layers of the Venture Stack
The market is rigidly divided into four layers. Only the Judgment layer has no incumbent.
| Layer | Function | askOdin Position |
|---|---|---|
| Retrieval e.g., AlphaSense, Tegus | Function Finds documents and transcripts. | askOdin Position We do not compete; we consume retrieval data. |
| Analytics e.g., PitchBook, Crunchbase | Function Aggregates historical market data and cap tables. | askOdin Position We do not compete; we consume analytics. |
| Workflow e.g., Affinity, Rogo | Function Automates CRM pipelines and formats IC memos. | askOdin Position We sit upstream of workflow. A CRM manages the pipeline, but it will happily track 1,000 structurally insolvent startups. |
| Judgment askOdin | Function Compiles narrative claims against structural outcomes. | askOdin Position Category Creator. |
The LP Perspective
Why Internal Tools Fail
When funds attempt to build internal judgment tools, they face a structural ceiling: an internal score is illegible to Limited Partners. It is the fund grading its own homework. Furthermore, an internal tool only benchmarks against a single fund's deal flow.
askOdin's Judgment Graph™ holds 110,000+ Clarity Scores built on public deal data. We provide a third-party, portable standard that survives LP audit.
The Category Line
Retrieval retrieves.
Analytics aggregates.
Workflow automates.
We compile judgment.
// JUDGMENT VS. WORKFLOW
Frequently Asked Questions
What is the difference between judgment infrastructure and workflow software?
Workflow software manages the process around a deal: the pipeline, the CRM record, the IC memo template. It will track a thousand structurally insolvent companies as diligently as a thousand sound ones, because it never evaluates the asset. Judgment infrastructure evaluates the asset: it compiles the claims in the deal's documents against business physics and returns a reproducible verdict with a Defensible Audit Log.
Does askOdin replace PitchBook, AlphaSense or Affinity?
No. Retrieval, analytics and workflow tools each own their layer, and askOdin sits above them. We do not compete; we consume. Market data and retrieved documents are inputs to judgment, and the CRM is where the verdict gets recorded. What none of those layers does is test whether the claims in a deal survive the math.
Why can't a fund build its own internal judgment tool?
It can, but an internal score is the fund grading its own homework: illegible to limited partners and benchmarked only against that fund's own deal flow. askOdin's benchmark corpus holds 110,000+ Clarity Scores on public deal data, which gives a third-party standard an LP can read.
What does the judgment layer actually produce?
A Clarity Score from 0 to 100, scored across five pillars with three audit checks, a verdict, and a Defensible Audit Log anchored to SHA-256 fingerprints of the documents read. The same recorded variables return the same score under the same Framework version, so the result is checked later from its record.