Joe Powered by Dakota

Re-Benchmark a Portfolio on a Recurring Basis

Because benchmarking is a repeatable capability built on top of the dataset rather than a static, one-time report, the same peer group logic can be re-run on a schedule as new performance data and vintages are added.

Request Access See the Example ↓

QuarterlyOr Annual Cadence

Same LogicReused, Not Rebuilt

FlaggedMeaningful Position Shifts

Why it matters

A benchmark run once at the point of initial commitment goes stale. Re-running the same custom benchmark quarterly or annually surfaces whether a manager’s relative standing has shifted since the last review.

See it in practice

Example

Re-run the custom benchmark for every fund in a multi-manager portfolio each quarter, and flag any fund whose relative position within its peer group has moved meaningfully since the prior refresh.

Powered by the same connected dataset

Every Joe use case, including this one, draws on the same underlying data — nothing here is a siloed feature.

18,000+ funds with individual, named performance data — not anonymized or pooled

20,000+ GPs covered, including firms currently in market and fundraising

164,000+ portfolio companies held across the funds in the database

1M+ private companies tracked in total, beyond current portfolio holdings

26,000+ private company transactions, with 2,000+ added every month

Daily industry news, keeping fund, GP, and transaction records current rather than static

15,000+ documents, including consultant reviews, pension documents, fund presentations, and more

Put this use case to work.

Get access to Joe and run this workflow on live, named fund and GP data.

Request Access

Re-Benchmark a Portfolio on a Recurring Basis

Why it matters

See it in practice

Powered by the same connected dataset

Explore other Joe use cases.

Put this use case to work.