fein

Get a demo

Use cases Deal sourcing Fundraising and LPs Portfolio support Private equity

Product Features Security Integrations

Pricing Get a demo

Do it yourself Self-host (free) Source on GitHub

Done for you Managed setup (14 days) Pricing

Privacy Terms Get a demo

Self-hosted · open source · live in 14 days

Every LP relationship your firm has, warm before the raise opens.

The next fund is raised in the two years before it opens. fein reads your firm’s email, calendar, notes and CRM. Every LP conversation, commitment and promise becomes one record, scored from real signal, owned by a named partner. Ask in Claude, ChatGPT or Cursor. Each answer carries the email it came from.

Book 20 minutes See pricing

Runs on your infrastructure Reads your CRM, replaces nothing Nobody enters data

It reads and answers in the tools you already use

Gmail Google Calendar Drive Salesforce Affinity Attio LinkedIn Granola Notion Slack Claude ChatGPT Gemini Cursor

The next fund is decided between raises. Nobody is watching then.

Coverage is a partner’s memoryYour firm holds hundreds of LP relationships across four partners’ inboxes. When the raise opens, the map of who is warm gets rebuilt by hand, from memory, under time pressure.
Promises quietly expireAn LP asks for co-invest deal flow in March. By the AGM, nobody at your firm remembers exactly who promised what. The LP remembers.
Quiet is invisible until it is expensiveAn anchor from the last fund drifts from quarterly contact to nothing. You learn the relationship went cold when the re-up conversation starts cold.
The last raise is not searchableWhich LPs passed on the last fund, and the exact reason each one gave, sits in threads three years old. The team re-learns it one call at a time.

Four questions your IR desk asks every quarter.

fein answers each one from the record your firm already makes. Answers arrive in seconds, and each line shows its source document.

Your LP coverage map

fein lists every LP your firm has ever spoken to. Meetings, replies and shared documents set each score, not a field somebody filled in. Each row names the partner who owns the relationship.

The LPs going quiet

fein learns the rhythm of each relationship from your history. It then flags the ones that drift away from that rhythm, years before the raise makes them urgent. Each flag shows the last contact and whose call it is. Dates and intervals do this work. Guesses do not.

What each LP asked for, and what you promised

Every ask and every commitment is filed to the LP it belongs to, with the meeting or email it came from. Before the annual meeting, one question lists what is open. Nothing expires because somebody changed jobs or lost a notebook.

The warm path to a new LP

fein finds the shortest real route to an allocator you have never met: through your existing LPs, your founders and your co-investors. It weighs each step against how well your firm knows that person, and it ends in the name of the colleague who should make the call.

Nobody enters data. The graph builds itself.

It reads what you already write

fein reads your email, calendar, Drive, LinkedIn and CRM, and it reads them continuously. The first pass takes in years of history, including the last raise. Your partners log nothing and change nothing.

One record per LP

Every duplicate copy of a contact joins into one identity. Real signal scores that identity, not a language model guess. When a fact stops being true, fein strikes it and dates it. Nothing is deleted, so the last raise stays answerable.

It answers where you work

One MCP endpoint sits behind Claude, ChatGPT, Gemini and Cursor. The answer is the same every time, and it carries its source. Your agents traverse a map. They do not scrape files and guess.

You already track LPs somewhere. This is the part it cannot do.

A spreadsheet or CRM on its own

With fein

What it holds

The rows somebody remembered to update, last updated during the last raise.

Everything that already exists. Every email, invite, call note and document, resolved onto the LPs they belong to.

Who keeps it current

Whoever owns the spreadsheet, between their other jobs.

Nobody. fein reads the record your firm makes anyway. Two years after the close, it is still current.

Relationship strength

A colour somebody chose in a cell, a raise ago.

Measured. Meetings, replies and shared documents, with the signals shown behind every score.

Promises and asks

In the notes column, if they made it there at all.

Filed to the LP. Each ask and commitment keeps the meeting or email it came from, and stays open until it is closed.

Where it runs

A vendor’s cloud, or a file on one person’s laptop.

Yours. Your own servers, on code you can read before you run it.

It sits on top of the systems you run today.

fein works with 30+ tools. It reads your CRM and everything around it. The whole picture then resolves into one context graph. fein replaces no system, migrates no data, and asks your team for no new data entry.

Ask about your stack

CRM and deal systems
DealCloud, Affinity, Salesforce, Attio, HubSpot, Airtable
Email and calendar
Gmail, Google Calendar, Outlook, Microsoft 365
Files and data rooms
Google Drive, SharePoint, OneDrive, Dropbox, Box, DocSend
Meetings, notes and chat
Granola, Zoom, Google Meet, Slack, Microsoft Teams, Notion
People and market data
LinkedIn, PitchBook, Crunchbase, Harmonic
Portfolio and back office
Carta, Standard Metrics, Google Sheets, Excel
30+ tools in all
If your firm runs something else, we read that too. Ask us.

Your data never leaves your servers.

LP correspondence is the most sensitive record your firm holds. fein reads it inside your own environment, and sends nothing to us. You can read every line of the code before you run any of it.

The full security page

Always self-hosted.
fein runs in your environment. It sends nothing to us.
Open source, end to end.
Every line that touches your data is public. Audit it before you run it.
Private by person.
Access is per person, and each person’s sensitive sources live in a private layer inside the shared graph. The rest, from the audit trail to the single token gate, is on the security page.

The software is free. We charge for the setup.

fein is Apache 2.0 licensed and self-hosted. Your team can clone it and run it for nothing. What a firm usually buys instead is the fortnight: an engineer who connects every source, resolves a decade of duplicate contacts, and hands over a working graph on day 14.

Self-hosted

The whole platform on your own servers. No trial, no seat count, no call with us.

$0forever

→Every feature. There is no paid tier of the software.
→Your engineers do the setup, the credentials and the backfill.

Run it yourself for free

Managed setup

A forward-deployed engineer builds fein into your stack and stays on it.

$5,000once, then from $250 a month

→Live in 14 days. Your part is two short calls.
→Connectors kept working through every upstream API change.

Book 20 minutes

The monthly plan is set by how much we keep doing after the setup, from $250, and never per seat. Every person at your firm can query the graph, and so can every agent they run. An annual plan, paid in advance, costs 15% less. See the plans

We take five firms this quarter.

→It is live in 14 days. The date is a commitment, not an estimate. Your part is two short calls.
→You have thirty days to decide. If fein is not useful to your firm, we refund everything. This includes the build fee.
→Your price is locked at the band you join on. It stays locked for as long as you are a customer, through every fund you raise.

We deploy fein in two weeks. Then it works on its own.

Your part is two short calls: one on day 1 to connect your systems, one on day 14 to check the answers before it goes live. Between them fein reads years of email, meetings and documents into one record, including the whole of your last raise. Day by day, it is written up once, on its own page. What the fortnight covers

What IR teams ask first.

We track LPs in a spreadsheet and it mostly works. Why change?

It works until the raise opens. A spreadsheet holds what somebody typed into it, on the day they typed it. It does not know that an anchor went quiet eight months ago, or that a promise made at the AGM is still open, or which partner actually owns a relationship. fein reads the record your firm already makes and keeps all of that current, and nobody maintains it.

The spreadsheet can stay. fein reads it too.

Where does our data go?

Your data goes nowhere. fein runs on your infrastructure and sends nothing to us. There is no telemetry, and no control plane of ours in the path. Every line of code that touches your data is public. You can read it before you run anything.

What access does your engineer have?

The engineer works inside your environment, on access your IT grants. You can revoke it at any time. Our people are bound by confidentiality, and access is limited to those who need it to support the service. Nothing is granted permanently. Access ends when the build ends, unless you ask us to keep the connectors supported.

One thing we will not overstate: fein does not today keep a tamper-proof audit trail of administrative access. Your own logging is the record that counts. The graph also sits on your machine unencrypted above the volume, so whoever you give host access to can read it. That is true of your other systems too, and it is the reason the machine is yours and not ours.

Can the IR desk use it without opening the deal side to everyone?

Access is per person. Each person’s sensitive sources live in a private layer inside the shared graph, and fein enforces that scoping inside every query. A partner’s LP correspondence can stay theirs while the coverage map stays shared. The detail is on the security page.

How far back does it read?

fein reads as far back as your mail retention allows. Most firms give us years of history on the first pass, which usually covers the whole of the last raise. That is the point. On day fourteen fein answers like a colleague who sat through every LP meeting your firm has had.

What happens if we cancel?

Nothing stops. fein runs on your servers. The graph, the connectors and every answer stay where they are. They keep working.

Give us twenty minutes. We will show you your own LP graph.

Tell us the name of your firm. We come to the call with what we can already see in public fund data: the allocators around your last close, and the paths your firm likely has to them. If it is not interesting, we have taken twenty minutes of your time and none of your money.

Or email sales@fein.vc