Features

Everything the platform does.

One governed store over the whole book, documents that read themselves, and answers that cite their source. Every capability below earns its place by making a real question answerable, and keeps a human in the loop wherever judgment belongs.

01 · The unified store

PE and CRE in one time-series store.

Private equity and commercial real estate share a single store, with fund-level consolidation from day one. The store keeps time-series, not snapshots, so both "the portfolio as of any date" and "what changed this quarter" are answerable; today they are not, because NAVs blend quarter-ends.

Consolidation

142 positions, 118 funds

The 142 positions across the book resolve to 118 unique funds; some are held through multiple entities, and the store ties those rows back to one fund automatically.

Look-through

Total exposure, one query

Full look-through exposure across the whole book comes back in a single query, PE and CRE together, rather than being reassembled by hand across sheets.

Time-series

As of any date

Because the store records figures over time rather than overwriting them, "the portfolio as of March 31" and "what moved this quarter" are both real questions with real answers.

02 · Ingestion

Documents read themselves.

A proven taxonomy of about a dozen document types (GP and Goldman statements, capital calls, distributions, and more) has been validated against real mail. Extraction is engineered to be trustworthy before it is fast: senders are gated, confidence is earned across runs, and failures route to a person rather than guessing.

Whitelist

Sanctioned senders only

A sanctioned-sender whitelist admits documents for parsing. Non-whitelisted senders are rejected outright, never parsed, so nothing off-list reaches the extraction path.

Confidence

Agreement, not raw scores

Confidence is multi-signal, based on agreement across multiple runs rather than a single model's self-reported score, so a lucky guess cannot pose as certainty.

Validation

Fail to review, not to guess

Schema-validation failures route to review with a best-effort extraction attached, so a person picks up exactly where the machine stopped.

Dedupe

Absorbed once

Content-hash dedupe means the same document arriving from several inboxes is absorbed a single time, without double-counting a call or a distribution.

Rollout

Shadow, then canary

Every extraction agent ships through a shadow-then-canary rollout, proving itself against live mail before it is trusted with the book.

Taxonomy

A dozen known types

The document taxonomy covers roughly a dozen types validated against real mail, so the common shapes of the firm's inbox are handled, not hypothesized.

03 · A human in the loop

Nothing lands until a person says so.

Extracted figures surface in a Slack review queue as claim-and-resolve cards. This human layer is the verification step before anything enters the store; the machine proposes, a person disposes.

The review queue

Claim-and-resolve in #ingestion-review

Every extracted figure appears in #ingestion-review as a claim to confirm, correct, or reject. A person is the last step before a figure is real, so verification is a habit, not an afterthought.

Checking the checker

A weekly random-sample audit

A weekly random-sample audit, on the order of 5 percent, tests the automated scorer itself. The system that judges confidence is held to the same scrutiny as the documents it reads.

04 · Provenance and reconciliation

Every figure ties back, and ties out.

Each figure carries its source document, data class, and as-of date: figure-to-document links, not cosmetic notes. The store reconciles to the systems of record, complementing them and never replacing them, and refuses to migrate quietly if the numbers do not agree.

Provenance

Source, class, and as-of

Every figure links to the document it came from, along with its data class and as-of date. These are load-bearing links back to evidence, not decoration.

Reconciliation

Reconciles to record

The store reconciles to the accounting system of record (Sage Intacct) and the investor portal (Juniper Square), complementing both. It is a governed view over the book, not a replacement for either.

Migration gate

Fails loudly

A set of reconciliation checks gates the migration off the legacy spreadsheet and fails loudly if counts and totals do not tie out, so the switch happens only when the numbers agree.

05 · Query and dashboards

Ask in plain English. Get a cited answer.

Natural-language query from Slack or a dashboard, with answers that come back cited by source and as-of date. Clearance is enforced in the answer itself: an above-clearance ask returns a dashboard deep link, not the figure.

Query

From Slack or dashboard

Ask in #portfolio or on a dashboard in plain English. No query language, no spreadsheet spelunking; just the question you would ask a colleague.

Citation

Answers cite themselves

Every answer comes back with its source and as-of date attached, so a number is never separated from the evidence and the moment it was true.

Refusal by class

A link, not the figure

When an ask sits above your clearance, the platform returns a dashboard deep link rather than the number. Refusal is a governed answer, not a dead end.

06 · Deal pipeline

Sourcing to close, in Linear.

The live pipeline runs in Linear across two teams, an Alternatives track and a CRE track, one issue per deal. Agents do the busywork under a dedicated identity, but only a human changes a deal's stage, and no book-of-record position exists until a person has checked it.

  1. One issue per deal, two tracks

    The pipeline lives in Linear across an Alternatives track and a CRE track, with one issue per deal. Agents create, comment, label, and attach under a dedicated identity, so their work is visible and attributable.

  2. Only a human moves the stage

    Agents never advance a deal on their own; only a person changes a deal's stage. Deal and deal-stage-history records live in the store, so the pipeline is queryable, not just visible.

  3. The morning brief sees it move

    The morning brief gains a live pipeline diff, and capital-weighted pipeline, conversion, time-in-stage, and kill analysis all come from the store with citations.

  4. Closing hands off to a person

    Closing a deal spawns a human-owned handoff checklist. No book-of-record position row exists until a human has checked it, so the record of truth is never created by a bot.

07 · The Slack channel surface

Durable channels, each with one job.

Process channels are durable and single-purpose; per-deal channels are ephemeral, created at screening and archived on decision. Threads act as working sessions, corrections are first-class, and posts are batched by default so only what is urgent interrupts.

#portfolio

Queries and cited answers

Ask in plain English and get an answer with its source and as-of date attached.

#ingestion-review

The review queue

Extracted figures wait here as claim-and-resolve cards for a person to confirm.

#capital-activity

Calls and distributions

Extracted capital calls and distributions post with their source documents linked.

#data-quality

New, stale, missing

A weekly report on what arrived, what has gone stale, and what is missing.

#cre-alerts

DSCR, LTV, maturities

Coverage and loan-to-value thresholds and upcoming maturities, surfaced early.

Per-deal channels

Created, then archived

Ephemeral channels open at screening and archive on decision, so the surface stays clean.

Threads as working sessions

An artifact, iterated in place

A thread is a working session: an artifact is posted and iterated in-thread with version notes, so the history of a decision stays with the decision.

Corrections are first-class

Edited and flagged

When a source finalizes late, the bot edits the original post and threads a correction notice, so a stale figure is never left standing silently. Posts are batched by default; only deadline-class items post on their own.

08 · The financial surface

Waterfalls and economics, computed deterministically.

The economics of the book are computed by a deterministic, versioned engine, never by a model. Every figure below is reproducible from the deal's terms, so the numbers are auditable rather than approximate.

Waterfall

Per-investor, with preferred return

Per-investor waterfall and preferred-return tracking, computed from each deal's terms rather than maintained in a shadow spreadsheet.

Cash

Balances and expected flows

Bank and cash balances alongside expected flows, so the live cash picture and what is coming are in one place.

GP economics

Fees and promote

GP fee and promote economics computed the same way every time, by the deterministic engine and never by a model.

Side letters

A register of non-standard terms

A side-letter register captures non-standard terms, so the exceptions that today live in a few people's heads become findable with their record.

09 · Connectors

Built once, gated by role.

The connectors to the systems of record are built a single time and shared, each access-gated by role with one credential store. Where a source offers no API, the plan is export parsing rather than blocking on it.

Accounting

AI Gateway to Sage Intacct

The accounting AI Gateway reads Sage Intacct read-only, so the store reconciles against the ledger without ever writing to it.

Investor portal

Juniper Square connector

The investor-portal connector reads Juniper Square, keeping the store aligned with what investors see.

No API

Parse the export

Where a source has no API, such as Goldman, the plan is export parsing rather than blocking. A missing API slows a source down; it does not stop the book.

10 · Extend

Where it grows next.

The same foundation reaches further without changing shape: consolidation across the firm, alerts that arrive inside the briefing rather than in yet another notifier, and tools to model what-ifs.

Consolidation

Firm-wide

Firm-wide consolidation extends the single look-through view beyond the initial book, on the same governed store.

Alerts

Into the briefing

Alerts flow into briefings rather than a separate notifier, so what matters arrives where you already look instead of a new place to check.

Scenarios

Model the what-ifs

Scenario tools let you model alternatives against the governed store, with the same provenance and clearance rules in force.

Get started

See how adoption works.

Adoption is staged and safe by construction: the data layer first, then ingestion with a human in the loop, then query and dashboards, then the extras. Each stage earns the next, and every access follows the rules the firm already ratified.