GenAI for Private Equity

AI that finishes the job, down to the last 20 percent.

We build AI into the deal and portfolio workflows of Dutch private equity firms, so sourcing, IC memos and value creation move faster and stay consistent. The systems below already run in production inside a Dutch PE firm.

Compounding system
context · workflows · review
Grounded in the institutional GP stack
Affinity DealCloud PitchBook SourceScrub Gain.pro Crunchbase Datasite Drooms Firmex eFront IQ-EQ Trustmoore KvK DocuSign Looker SharePoint
Daniël Poolman
Founder

Daniël Poolman

Founder, Poolman Ventures · Delft, NL

Most AI consultants have never sat in a deal team. I spent three years inside Dutch PE (Vortex Capital Partners, then embedded at Lexar Partners), building the systems above from the inside, on an engineering and econometrics foundation (TU Delft, VU Amsterdam). Poolman Ventures is founder-led and PE-native by design: you work directly with the person who builds, grounded in how the workflow really runs rather than a generic AI playbook.

TU Delft VU Amsterdam Cloud Solutions Vortex Capital Partners Lexar Poolman Ventures
Track record

Production systems, not prototypes

Four production systems built and shipped end-to-end inside a Dutch private equity firm, across competitor intelligence, portfolio value creation, deal-flow analytics and LP reporting. Plus a sourcing engine proven at cross-sector scale.

0
production systems live inside a Dutch PE firm
0+
deal announcements scraped, classified and thesis-scored
0
companies mapped in one cross-sector sourcing run
0
competitors tracked deal-by-deal across the market
Live

Value-creation platform

An operating cockpit for the firm and its portfolio companies: portfolio management, a valuations engine, quarterly roll-up, an 8-pillar maturity scorecard and playbook-driven task management. Production SaaS with single sign-on and role-based access for staff, operators and admins.

React Node SharePoint BI
Live

Competitor and deal intelligence

Scrapes 10,000+ PE deal announcements, classifies each against a 23-firm competitor map, enriches it with LLM research and scores it for thesis fit (1 to 5). A BI dashboard surfaces competitor activity, advisor league tables and the relevant deals the team never saw. Five quarterly intelligence cycles shipped.

Python OpenAI Affinity React
Live

Deal-flow analytics and LP reporting

The firm's sourcing funnel read straight out of Affinity (leads, appointments, NBO, term sheet, close, split platform vs add-on, season on season) on live dashboards. Plus an automated pipeline that builds the quarterly LP advisory-board slides end-to-end: pull the export, parse it, render the deck, send it for review. Every quarter since 2023.

Affinity Looker Python PowerPoint
Live

Buy-and-build sourcing engine

An automated pipeline that maps an entire market: every company found, enriched, filtered and scored against the target profile, with per-company web research as the quality gate. Proven at cross-sector scale on a B2B market-mapping run outside PE: 93,497 companies across 12 EU countries, narrowed to a research-qualified shortlist.

Google LinkedIn KvK Firecrawl OpenAI Anthropic

One market-mapping run, end-to-end

From every company in the market down to the research-qualified premium players.
93,497 companies found
across 12 EU countries
500,000+ URLs analysed
scraped and summarized by GenAI
4,332 match the target profile
scored on profile fit
1,324 premium players
filtered after deep research per company
The problem

How AI is used in PE teams today, and why it stalls

It works for simple tasks (summarise, draft, reformat). On anything complex it stalls at 70-80 percent, and tomorrow starts from the same blank prompt.

Models
ChatGPT
Claude
Copilot
External context, pasted in by hand
Affinity DealCloud Gain.pro Datasite eFront Excel Word Outlook SharePoint OneDrive
Prompt + paste context
Model output
70 to 80% draft
Manual fix, close tab
↻ Repeat next session, from scratch

Works for simple tasks (summarise, draft, reformat). On anything complex it stalls, and nothing carries forward.

You cannot trust the output for real work.

Underlying problems
1

Cold start every session

It cannot see Affinity, the data room, or last week's IC memo, and remembers none of your workflows, preferences or corrections. Every session starts from zero.

2

Hidden assumptions

It picks the structure, the weighting and the criteria without checking. You catch the mismatch only in the final draft.

3

No edge of your own

What comes back is the average of the internet: fluent, plausible, and the same answer any fund would get. It reflects none of your thesis or judgment.

Two root causes

The symptoms trace back to two structural gaps

Root cause 01

We onboard every hire, then hand AI a prompt

An LLM is a brilliant new hire on day one: sharp, well-read, fast. What it lacks is everything a person absorbs over years inside a firm. We onboard every human, then hand AI a prompt and expect senior work.

We skip onboarding. No context, no training, no ways of working, no checkpoints, no feedback.
So output stays generic. The model fills every gap silently, and the goal drifts as it runs.
Root cause 02

PE's digital ops are not structured for AI

The systems hold the data, but not in a shape an agent can use. Meaning lives in people's heads, and every run is driven by hand.

1
Systems are siloed. Each system of record holds one fragment. None holds the whole picture.
2
Knowledge is implicit. What "Stage 3" means, which template fits: it lives in people's heads, never encoded.
3
Work is manual. No way to package a workflow, trigger it, or carry its output forward.
The approach

Close both gaps with a new way of working and a new layer of infrastructure

Two moves, and they only work together. Each run produces reviewed, reusable artifacts that make the next run faster, more accurate and more aligned.

1 A new way of working

Break workflows into reviewable layers

Decompose each workflow into an abstraction hierarchy. Each layer produces a distinct artifact, and each artifact gets reviewed before the next layer proceeds.

2 A new layer of infrastructure

Make context and workflows persistent and reusable

A layer on top of your existing ops stack that holds persistent context (the data every run reads and writes) and packages reusable workflows, for both humans and agents.

Layer
Stage
Artifact
Seniority
L1
Narrative
Why we are doing this, for whom, why now
Partner-level decisions
L2
Spec
Evaluation criteria, structural choices, output scope
Partner + associate shaping
L3
Wireframe
Structure, key claims, data points
Associate + analyst building
L4
Final artifact
The memo, deck, scored longlist, drafted email
Analyst-level execution
+

Both are required. Together they create a compounding system. A correction or new signal enters at the layer it belongs to and re-flows from there, so you fix the cause rather than rerun the whole job.

Today

Raw, unstructured, siloed

  • Deal facts scattered across Affinity, the VDR and email
  • Conventions and criteria live in people's heads
  • Past runs leave nothing reusable behind
Affinity SharePoint eFront Datasite
Agentic

Structured, connected, persistent

  • Records: deal, portco and thesis facts in one queryable place
  • Conventions: what "Stage 3" means, the target profile criteria, house style
  • Artifacts: versioned briefs, target profile specs, scored longlists and corrections
Affinity SharePoint eFront Datasite
A worked example

Buy-and-build lists, before and after

Today, the only structured step is the lowest-value one. What "fit" means, the target profile, never gets written down, so there is no place for an agent to plug in.

Partner
Sets the sourcing brief
"Find bolt-on targets for portco X, construction SaaS, BeNeLux."
Associate
Carries the target profile in their head
Product shape, commercial model, founder profile, geographic preference.
Analyst
Applies structured filters
Sector, employee count, geography. 1000+ rows, eyeballed one by one.
Output
A shortlist of 30 to 80
Sent to the partner in a spreadsheet. The brief-to-list cycle takes weeks.
Why AI cannot help here

No place for an agent to plug in

Filtering is the only structured step, and the analyst already does it by hand. What "fit" means is locked in the associate's head: no artifact for an agent to match against, no checkpoint for the partner to validate.

The redesign: a four-layer pyramid

Every layer owns one artifact. Write the target profile down once, and an agent can finally plug in. Hover any layer to open its artifact.

Cross-layer loop: a brief edit re-runs the layers below; a finding revises the artifact above Within-layer loop: agent drafts, human reviews, agent revises
L1
Partner
Analysis brief
Goal: 3 platform bolt-ons for portco X within 18 months. Scope: vertical SaaS, NL / BeNeLux / DE, construction. Exclusions: pre-revenue, US-only, hardware-heavy, non-SaaS.
↓ hover to open the artifact
Analysis brief · L1 artifact
Goal3 platform bolt-ons for portco X within 18 months.
Deal lensbolt-on at €15-40m EV; minority OK for proof-of-thesis.
Scopevertical SaaS · NL / BeNeLux / DE · construction.
Exclusionspre-revenue · US-only · hardware-heavy · non-SaaS.
L2
Associate
Target profiles what “fit” means, written down
One profile per sub-segment: field service, estimating tools, compliance and safety SaaS. Each carries: product shape, owner profile, signals, anti-patterns.
↓ hover to open the artifact
Target profiles · L2 artifacts · one per sub-segment
Field service mgmt
Productdispatch + ops
Ownerfounder, €2-8m
Signalsvertical, NL HQ
Estimating tools
Producttakeoff + quote
Ownersubscale ARR
SignalsBIM, NL/DE
Compliance / safety SaaS
Productsafety + training
Ownerfounder fatigue
Signalsregulated, SaaS
L3
Analyst
Ranked longlist
Scored against the L2 target profiles, ranked with rationale. 1000+ rows ranked, with an edge-case queue for the in-between calls.
↓ hover to open the artifact
Ranked longlist · L3 artifact · scored against L2 target profiles
CompanySegmentMatch scoreRationale
FieldServiceCo (NL)Field service9.2exact fit · NL-HQ · founder-led
EstimaXYZ (BE)Estimating8.4estimating · BIM ties · subscale
ComplyHub (DE)Compliance7.8safety SaaS · founder fatigue
DispatchPro (NL)Field service7.1adjacent vertical · off-thesis
… 1000+ rowsranked vs L2 target profiles
L4
Team
Final artifacts
IC memo, curated shortlist, market map by sub-segment, outreach drafts. Nothing missed, and every call is traceable.
↓ hover to open the artifact
Final artifacts · L4 · downstream deliverables
IC memo
deal-specific writeup
Curated shortlist
10-20 for partner review
Market map
by sub-segment
Outreach drafts
per-target email + brief
Way of working

A clear path from first sprint to live, maintained workflows

Entry point

Discovery sprint

2 to 4 weeks
  • Workflow map of where AI plugs in
  • Prioritised AI implementation roadmap
  • Standalone, or phase 1 of an engagement
Execution lane

Build

Implementation engagement
4 to 16 weeks
Smaller workflows that automate cleanly. Scope is well-defined from day one because Discovery produced a clean spec.
OR
Platform build
3 to 6 months
Custom platform: auth, RBAC, portfolio access, data model. Production SaaS, built to last.
Continuation

Maintenance + hosting

Ongoing
  • Hosting and uptime monitoring
  • Bug fixes and eval drift alerts
  • Model and vendor rotations, cost guardrails
Working session
Weekly 60 to 90 min

Analyst + Investment Manager. Scope on the table, design, build, blockers.

Steering committee
Biweekly 30 to 45 min

Partner + working-session group. Roll-up of decisions, scope, risk, budget.

Milestone review
At gates 60 min

Full sponsor group + IC member. Kickoff, mid-engagement, pre-handoff sign-off.

Security & confidentiality

Your AI policy decides where your data goes

We know PE firms handle highly sensitive data, so we build on a choice of models, each with its own data residency, risk profile and tradeoffs. You set the posture per workflow, with identity, access and audit always in your own environment. Hover a posture to see how it runs.

Open
Balanced
Restricted
Gatewayruns in your tenant
  • Identity & access (your SSO)
  • PII detection & handling
  • Router, by data class
  • Full audit log
1

Vendor APIs

Open leaves tenant · zero-retention
Where it runs

Frontier model via enterprise API (Anthropic, OpenAI), or Azure OpenAI inside your own Azure tenant.

Where data goes

Leaves the tenant under a zero-retention contract. Never used to train a model.

PE example

Market maps, public company research, general drafting.

Top capability, lowest cost, fastest to stand up.
2

Hosted cloud, open models

Balanced
Where it runs

Open-weight model on EU cloud, ideally your own cloud tenant.

Where data goes

Stays in the EU and your cloud boundary. Never reaches a model vendor.

PE example

Portfolio KPIs, internal memos, archive retrieval.

Balanced: strong models, data in your perimeter.
3

On-prem, local models

Restricted
Where it runs

Local open model on a dedicated workstation inside the firm.

Where data goes

Never leaves the building. Air-gapped option.

PE example

Live deal data, data-room contents, a live IC memo.

Maximum confidentiality, lower throughput, higher cost.
Across every tierYour environment
Identity & access

Your IdP / SSO governs every tier

No training on your data

Across all three tiers, always

Full audit trail

Who asked what, over which documents

Let's make this a conversation

The best first step is a discussion about your workflows

Where you are today

What are your biggest operational challenges?

What are you already doing with AI?

Where does your data live, and how structured is it?

Where AI could pay off

Where do you see the highest-ROI use cases?

Which workflow would you want to tackle first?

What would make a first pilot a success?

Let's find your highest-ROI workflow

A short Discovery sprint maps where AI plugs into your deal and portfolio work, and gives you a prioritised roadmap to act on.