The board brief
Before each board meeting, fein lists what is open: the asks the founder made, the promises the firm made, and what changed since the last pack. It reads the decks, the threads and the notes. Nobody rebuilds the picture by hand.
fein reads your firm’s email, calendar, notes and CRM. Every board deck, introduction and founder ask becomes one record per company. Ask in Claude, ChatGPT or Cursor what is open before the board meeting, and who in your network can meet a founder’s ask. Each answer carries its source.
It reads and answers in the tools you already use
fein answers each one from the record your firm already makes. Answers arrive in seconds, and each line shows its source document.
Before each board meeting, fein lists what is open: the asks the founder made, the promises the firm made, and what changed since the last pack. It reads the decks, the threads and the notes. Nobody rebuilds the picture by hand.
Every introduction the firm promises is filed to the company it belongs to, with the meeting it was made in. fein marks the ones that happened and flags the ones still open. A promise stops depending on the memory of the person who made it.
A founder asks for a hire, a customer or an expert. fein searches the firm’s whole graph, not one partner’s memory: every candidate the firm can actually reach, ranked by how warm the path is, ending in the colleague who should make the call.
What the firm actually did for each company, as a list with a source behind every line. It is the answer when the founder compares term sheets, when the next investor diligences you, and when an LP asks what the platform is for.
fein reads your email, calendar, Drive, LinkedIn and CRM, and it reads them continuously. Board packs, threads and call notes land on the company they belong to. Your platform team logs nothing and changes nothing.
Every duplicate copy of a contact joins into one identity, and every document lands on one company record. When a fact stops being true, fein strikes it and dates it. Nothing is deleted, so the whole history stays answerable.
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.
A tracker on its own
With fein
What it holds
The rows somebody remembered to update after the board meeting.
Everything that already exists. Every deck, thread, invite and note, resolved onto the company it belongs to.
Who keeps it current
The platform team, chasing partners for updates they half remember.
Nobody. fein reads the record your firm makes anyway. If the tracker is stale, fein is still current.
Promises and asks
In whoever’s head was in the room, until they forget.
Filed and flagged. Each promise keeps the meeting it was made in, and stays open until it is closed.
The firm’s network
Asked for in Slack: whoever answers, answers.
Queried. Every candidate the firm can reach, ranked by real warmth, with the colleague who should make the call.
Where it runs
A vendor’s cloud, on terms you renegotiate at renewal.
Yours. Your own servers, on code you can read before you run it.
fein works with 30+ tools. It reads your CRM, your portfolio tracker and everything around them. 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.
DealCloud, Affinity, Salesforce, Attio, HubSpot, Airtable
Gmail, Google Calendar, Outlook, Microsoft 365
Google Drive, SharePoint, OneDrive, Dropbox, Box, DocSend
Granola, Zoom, Google Meet, Slack, Microsoft Teams, Notion
LinkedIn, PitchBook, Crunchbase, Harmonic
Carta, Standard Metrics, Google Sheets, Excel
If your firm runs something else, we read that too. Ask us.
Board material 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.
fein runs in your environment. It sends nothing to us.
Every line that touches your data is public. Audit it before you run it.
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.
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.
The whole platform on your own servers. No trial, no seat count, no call with us.
A forward-deployed engineer builds fein into your stack and stays on it.
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
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, board packs and call notes into one record per company. Day by day, it is written up once, on its own page. What the fortnight covers
A tracker holds what somebody typed into it after the meeting. It does not know that a promise made at the June board is still open, or that the candidate a founder needs emailed a partner last week. fein reads the record your firm already makes, files it to the company it belongs to, and keeps it current with nobody maintaining it.
The tracker can stay. fein reads it too.
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.
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.
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 board pack can stay with the partner who holds the seat while the promise ledger and the support record stay shared. The detail is on the security page.
fein reads as far back as your mail retention allows. Most firms give us years of history on the first pass, which usually covers each company from the first meeting on. On day fourteen fein answers like a colleague who sat through every board meeting your firm has attended.
Nothing stops. fein runs on your servers. The graph, the connectors and every answer stay where they are. They keep working.
Tell us the name of your firm. We come to the call with what we can already see in public data: your portfolio, the networks around it, and the paths your firm likely has into them. If it is not interesting, we have taken twenty minutes of your time and none of your money.