Everything you need to know about FundPulse.

FundPulse is an AI-native CRM and investor relations operating system built specifically for hedge funds. It replaces the spreadsheet-plus-Outlook-plus-OneNote pattern with a purpose-built system of record for LP relationships, fundraising pipeline, and fund knowledge.

The defining characteristic is its AI layer: every recommendation is sourced, every claim is attributed, and nothing auto-sends. The system surfaces who to contact, what to say, and why, with clickable evidence behind every suggestion.

FundPulse is built for hedge fund managers, typically in the $500M–$2B AUM range. It serves three distinct profiles:

Founders doing IR part-time: the fund's not yet ready to make an IR hire, and the founder is managing LP relationships themselves alongside running the book.

Small IR teams: typically one or two people covering a book of 100–200 LPs, where automation and intelligence create significant leverage.

Established IR functions: larger teams where the capture problem is solved but the synthesis problem is not. FundPulse acts as the intelligence layer over their existing data.

Existing CRMs (Dynamo, Backstop, FolioMetrics, Salesforce) are designed for data capture. They are reliable records. They are poor advisors. The data goes in; the synthesis does not come out.

FundPulse is built around the opposite premise. The question it answers every morning is not "what happened?" but "what should you do today, and why?" The AI layer synthesises across the full LP record (every interaction, note, condition, and piece of fund data) and surfaces prioritised actions with evidence attached.

The other key distinction is trust. Where AI add-ons to legacy CRMs tend to generate generic text that looks plausible, FundPulse's AI is source-attributed by design. It cannot produce a claim without attaching where the claim comes from.

Yes. FundPulse can integrate with an existing CRM as a data source and intelligence layer, or operate as a standalone system. For funds moving from a legacy system, we support structured migration of historical LP data, interaction records, and notes. For funds without a formal CRM, FundPulse is designed to be the system of record from day one.

Never. Every email FundPulse drafts is placed in a review queue. A human reads it, adjusts it if needed, and approves it before anything is sent. When it does send, it goes from the IR person's own email address. The LP receives a message from a named individual, not a system.

Auto-send does not exist in FundPulse. This is an architectural decision, not a configuration option.

Every claim the AI surfaces carries one of four attribution tags: FACT (from a stored record), AI (model inference, visibly labelled), EXT (external signal, such as a regulatory filing or news item), or STALE (the underlying record is older than the verification threshold).

Clicking any tagged claim reveals its source. The system is designed to make the provenance of every piece of information visible and auditable. If the AI cannot find a source for a claim, it does not make the claim.

FundPulse does not write DDQ answers. It matches an allocator's questions to your fund's approved-answer library: the actual responses your team and compliance function have already validated. When a new DDQ arrives, it auto-fills questions where a high-confidence match exists (typically 80%+ of standard questions) and routes genuine gaps to the appropriate person with context.

Nothing in the compliance workflow is AI-generated from scratch. The model's role is matching and routing, not invention.

When an LP sets a condition for future investment ("come back when you're at $2B," "we want to see a five-year track record," "we'd consider a co-investment above $20M"), FundPulse mines the interaction record to identify and log that condition automatically.

It then monitors the relevant data (AUM, fund age, deal flow) and surfaces a re-engagement alert, complete with a drafted email, the moment the condition is satisfied. Conditions set by a previous IR hire are visible and tracked for the current team.

FundPulse integrates with email (Gmail and Outlook) and calendar to auto-log interactions and keep the LP record current. It accepts structured data imports from existing CRMs, and can ingest notes, call logs, and document uploads. External signals (regulatory filings, 13F data, news) can be layered in as an EXT-tagged data source.

Every data source is labelled in the attribution system so the origin of every claim is always traceable.

FundPulse is a multi-tenant SaaS platform with strict per-fund data isolation at the database level (row-level security). Your LP records, interaction history, pipeline data, and fund documents are never accessible to another fund's instance of the system. There is no cross-fund data sharing of any kind.

Restricted documents (side letters, MFN agreements, and any document your compliance function designates as restricted) are excluded from the AI context before the model ever sees them. The information barrier is architectural, not a policy the team has to remember to enforce. The documents are stored and accessible to authorised humans; the AI simply does not have access to them.

FundPulse is on an active SOC 2 Type II path. The compliance controls, audit logging, and access management architecture are designed to meet the standard. We can provide documentation on our current security posture and timeline for certification for any fund conducting formal due diligence on the platform.

Pricing is not currently listed publicly. It is structured relative to fund AUM and team size, and is designed to be a fraction of the cost of an IR hire. That is the benchmark we are typically measured against. Speak to the team for a specific quote.

For a fund starting with a clean slate, FundPulse can be operational within days. For a fund migrating from an existing CRM with a substantial LP record, implementation typically takes two to four weeks depending on the volume and structure of historical data. We handle the data migration as part of the onboarding process. You do not need to prepare export files in a specific format.

Yes. The demo is set up using your actual fund data, not generic screenshots, so you see FundPulse with your own LP book, your own pipeline, and your own interaction history. Request a session below and we will be in touch within one business day.