Version. 0.1
Date. 2026-07-29
Status. Working draft for Operator review. Internal — carries honest statements about current Loomworks demonstrability that do not go outward as written.
Author. Claude.ai. Operator: Marvin Percival.
Companion. hebbia-comparison-v0_2 (the protocol-level comparison: Hebbia versus FORAY as a standard). This document is the product-level comparison: Hebbia versus what DUNIN7 proposes to sell venture firms — the two-vertical pair (deal engagement + fund record) and the FORAY operational-visibility direction. It inherits v0.2's source limits and does not re-derive its findings.
Sources. Hebbia's public surface as read by v0.2 (2026-07-29), plus Hebbia's private-equity and finance resource pages and one third-party category survey, read 2026-07-29 — this partially closes v0.2 §9's unread-blog gap. Statements about what Hebbia does not do remain statements about its public surface, not its product. No valuation figures appear, per v0.2's ruling.
DUNIN7 grounding. The venture pair set in verticals/venture-diligence/ (walkthrough read at v0.3 — v0.4 exists in the record and was not readable from this session; a reconcile pass against it is owed before outward use); the FORAY operational-visibility investigation v0.1; the pain-points mapping; the walk-audit report v0.1; the no-live-recall-demonstration rule (queued-directions v0.30).
Hebbia is the strongest product in the category the venture pair deliberately does not enter: reading a data room and answering questions about it, fast, with page-level citations. On the deal team's screen during the diligence weeks, Hebbia and its category peers solve finding. The Loomworks venture solutions solve a different problem Hebbia's surface does not claim: the record — what the fund came to know, from whom, when, with corrections preserved — through the decision, the holding years, and the fund's decade.
The sharpest way to hold the difference: Hebbia's evidence is documents someone else wrote; Loomworks's evidence is what your team learned and decided, and much of diligence's highest-value evidence — the reference call, the employee interview, the partner's dissent — never exists as a document for Hebbia to read at all. FORAY then extends the record below documents entirely, to the target's own operational events.
They are complementary in a fund's stack and competitive only for attention. The posture for the venture sale: never argue with Hebbia's category — use it. The category's own density is the proof that finding is being solved and commoditised; the governed record is what remains scarce, and it is the only part an investment committee, a limited partner, or a court will ask for in year four.
Per its private-equity and finance pages: Matrix ingests the full virtual data room into an indexed, searchable library — the pitch is auditing one hundred percent of the data room instead of sampling the top contracts; CIM screening at volume; multi-source synthesis with citation-linked responses; IC memo drafting from the analysis; agents encoding firm processes and running them continuously. The positioning register is speed and coverage: faster diligence, sharper narratives, decisions "grounded in verifiable evidence."
Two things in Hebbia's own material matter for this comparison. First, its "verifiable evidence" is v0.2 §5's retrieval provenance — this finding came from that page — which is real and valuable and silent on everything upstream of the page. Second, Hebbia's own survey material reports that while a large majority of finance teams say AI speeds diligence, a majority still manually re-check most or all outputs. That re-checking gap is not a speed problem; it is a trust and provenance problem — and it is the gap the Loomworks side of the stack exists to close, not by better extraction but by a governed record of what was accepted, by whom, with machine origin marked.
v0.2 distinguished two; the venture solutions require holding three, because each answers a different question a fund will actually be asked:
| Property | Question it answers | Who holds it | |---|---|---| | Retrieval provenance | Where did this number come from? — which document, which page | Hebbia, natively and well | | Contribution provenance | Who knew this, when, and what superseded it? — attributed contributions, corrections preserved, trajectory walkable | Loomworks, natively — the deal record's commitment | | Tamper-evidence | Has this record changed since it was made? — anchored, append-only | FORAY, by protocol |
None implies the others. Hebbia can cite a page perfectly in a document that was edited before ingestion. Loomworks can attribute a claim perfectly that later proves wrong — which is exactly why corrections are preserved rather than smoothed. FORAY can prove a record unchanged without making it true. A fund's defensible position — to its committee, its limited partners, an auditor, or opposing counsel — needs the second and third; the first accelerates analysts. The venture pair holds the second natively and the third by protocol; Hebbia's surface claims only the first.
| Lifecycle stage | Hebbia (per its surface) | Loomworks venture solutions | |---|---|---| | Sourcing / screening | CIM screening at volume; ranking against firm patterns | Not claimed — out of scope by design | | Diligence weeks — documents | Full-VDR ingestion, Q&A, matrices — the category's home ground | Documents enter the record as contributions with provenance; analysis findings (including Hebbia's, if the fund uses it) land as machine-origin-marked contributions | | Diligence weeks — human evidence | Not on its surface — reference calls, employee interviews, and founder conversations are not documents until someone writes them | The record's highest-value content: attributed contributions from credentialed external people, held-until-admitted, confidentiality-shaped | | The decision | IC memo drafted from the analysis | The memorandum produced from the Manifestation at the meeting — every claim one step from its source, unknowns on the page, the partner decides; no machine-produced "decision ready" state | | Holding period | Agents run continuous document workflows | The fund record engagement — entry baseline, concern trajectory; and the FORAY direction: the target's own attested operational events replacing deck-shaped self-reporting | | Exit | — | The record as evidence-grade asset in the sale | | The fund's decade | — | Institutional memory: thesis trajectory, pass reasoning, the across-tenure test — a partner who joined in year six reconstructs year two |
The table's shape is the argument: Hebbia is dense at one stage and silent at the rest; the pair is deliberately absent at the first stage and owns the rest. The lifecycle framing the marketing alignment note adopted survives contact with the category's best product.
Claim discipline cuts both ways. On ask-anything retrieval at corpus scale, Hebbia demonstrably delivers today what Loomworks is barred from demonstrating: the no-live-recall rule stands (wholesale fifty-item window, no index; and the walk audit's W-5 found active wrongness at small scale). On ingestion breadth, Hebbia lists the commercial data providers and enterprise stores; Loomworks currently accepts three of six core data-room types with spreadsheet and presentation extraction absent. On maturity, six years, enterprise logos, and a certification posture against one operator and a pipeline whose Manifestation-through-Rendering surfaces the walk audit found to be placeholders. None of this changes the positioning — the pair does not sell retrieval — but every outward document must be written so that no sentence invites a retrieval bake-off we would lose this quarter. The working-session demo remains door-3 creation and the record story, exactly per the standing pitch posture.
The record of the team's own knowledge, not just its documents. Corrections preserved, not smoothed — the restated figure remains beside its restatement, which is a defensible account of process no extraction layer produces. Machine origin marked non-suppressibly — directly answering the re-check gap: a fund using analysis tools can show forever which conclusions were machine-assisted, which is a compliance property the tools themselves cannot grant. Operator authority — Hebbia's agents "trigger workflows unprompted" and its worked example ends with an agent sending a deck to a managing director (v0.2 §7's live seam: under whose authority?); the Loomworks answer is structural: the system surfaces and signals, the partner approves, and no deal state advances on its own. External-contributor isolation — founders and references contribute attributed without reading the file (CR-2026-157's shape). The decade — no vendor in the diligence category claims the fund's institutional memory as a product. And under it all, attestation at the moment of the act rather than analysis after it.
For a fund that runs both, the composition is clean and worth stating in sales conversations because it defuses the "we already bought AI" objection: Hebbia is an instrument; Loomworks is the record the instrument's findings answer to. A Matrix finding that survives the analyst's judgment enters the deal engagement as a contribution — machine origin marked, retrieval citation carried as source metadata, admitted by the team, thereafter governed, correctable, and walkable. v0.2 §7 already established the integration is technically approachable (Matrix API, MCP connector) without vendor cooperation. The audit posture v0.2 said "has to buy one and build the other" — for venture firms, the pair is the other, productised.
Inherited open items from v0.2 §9 stand except the blog gap, partially closed here. New: the walkthrough v0.4 reconcile is owed before this document informs outward material; Hebbia's API documentation remains unread (whether Matrix exposes an action log bears on §6's integration shape); and the category survey remains single-pass. Recommended next moves: fold §7's four postures into the marketing-site copy draft when D-5 commissions it; add Hebbia as the named Column-1 reference case per v0.2's move 3; no approach to Hebbia, unchanged.
DUNIN7 — Done In Seven LLC — Miami, Florida Hebbia versus the Loomworks venture solutions — comparison — v0.1 — 2026-07-29 Statements about Hebbia derive from its public surface as read 2026-07-29; statements about absence describe that surface, not the product. Internal draft; Section 4 does not travel outward as written.