Folio

VC CRM Software: 8 Tests to Run Before You Buy

Cover: VC CRM Software: 8 Tests to Run Before You Buy

Choose VC CRM software by loading a small demo pipeline with eight planted problems and running one pass-or-fail test on each. Make four tests critical, so a failure on any one blocks signing until the vendor fixes it and the fix passes a re-run. In our view, vendor demos run on tidy data. Without planted problems, a fund can sign a CRM that cannot even count first meetings by channel.

This applies when a fund tracks more than about 200 opportunities a year or has three or more investors sourcing (our suggested thresholds). Below that, a well-kept spreadsheet can be enough.

Summary

  • Build a demo pipeline of 30 companies with eight planted traps, and write down the right answer to each before the demo.
  • Treat four tests as critical: duplicates merge, stage history is kept, email access is narrow, and confidential deals stay hidden.
  • Fail any CRM that stores only the current stage (test 2): it can count at most 8 of every 25 first meetings.
  • Ask which email permission the CRM requests: test 3 passes only if the CRM offers access without message bodies, or asks each user to opt in.
  • Ask for the vendor's SOC 2 report (an auditor's report on its controls) and read which criteria it covers, which period, and which exceptions it lists.

What does a VC CRM do?

A VC CRM, also called venture capital CRM or deal flow CRM, keeps one record of every company, person, introduction and deal a fund has seen, with each deal's stage and history. The test is whether the record stays clean as volume grows: in a survey of 885 VCs, firms considered roughly 100 opportunities for each deal they closed, so a fund making 12 investments a year handles about 1,200 opportunities.

What it is not

  • Not a sales CRM with new labels. Deals involve companies, founders, introducers and co-investors at once.
  • Not the portfolio record. Once a fund invests, monthly company data belongs in portfolio monitoring.
  • Not an inbox. Email is evidence for a deal; the deal record is the source.

How do you build a demo pipeline with planted traps?

A demo pipeline is one fictional fund's deals, loaded into every CRM on the shortlist: 30 companies, 40 people and 6 months of activity, with eight problems planted on purpose.

TrapWhat to plantCorrect output
Duplicate companyThe same company entered twice, with two spellings and one website domainOne company, both histories merged
Stage historyOne deal: first look 2 March, first meeting 9 March, partner meeting 23 March, diligence 6 AprilThose four dates, each on its stage
Email permissionConnect one test inboxThe CRM offers access without message bodies, or asks each user to opt in
Confidential dealOne deal marked confidential to two investors, its founder's emails syncedOther users cannot find the deal or its emails, even through search or the founder's profile
IntroducerAn introduction from a co-investor, plus one cold inbound dealChannel required on both; introducer required on the introduced deal only
Returning companyA company passed at first meeting a year ago, reason "too early", returns"Too early" and "first meeting" still visible
One person, two companiesA founder who started two companies you have seenOne person linked to both
ExportThe whole pipelineCompanies, people, deals and stage history in one export

Keep the demo pipeline in one spreadsheet, one row per deal: company, website domain, founder, channel, introducer, first seen, a date for each stage, pass reason and a confidential flag. Write each trap's correct output before the first demo.

If your pipeline lives in partners' inboxes and a spreadsheet nobody updates, you already have the stage-history and introducer problems these traps test. For VC funds and family offices, Folio's deal flow and CRM module is where Folio runs this pipeline. See deal flow and CRM in Folio.

What are the eight tests for VC CRM software?

The eight tests for VC CRM software give a pass or a fail on duplicates, stage history, email permissions, access, introducers, returning companies, people and export, each against one trap in the demo pipeline. Tests 1 to 4 are critical, our suggested default.

#TestPasses ifCritical
1Duplicates mergeThe two entries merge by domain, keeping both historiesYes
2Stage history is keptEach deal shows the date it entered every stageYes
3Email access is narrowThe CRM offers access without message bodies, or asks each user to opt inYes
4Confidential deals stay hiddenOther users cannot find the deal or its emails, even through search or the founder's profileYes
5Channel and introducer are requiredNo deal saves without a channel; no introduced deal saves without its introducerNo
6Returning companies keep historyThe old pass reason and stage show on the new dealNo
7People link to companiesOne founder links to both companiesNo
8Everything exportsCompanies, people, deals and stage history export in one stepNo

Test 3 matters because inboxes hold more than deal email. Google's Gmail API scopes range from metadata-only, which shows labels and headers but not the email body, to full access, which can read, send and permanently delete email. For Outlook, Microsoft's Mail.ReadBasic permission gets messages without the body or attachments. Ask the vendor which permission it requests, and why.

Worked example: the CRM that cannot count its channels

An illustrative fund counts first meetings by sourcing channel every quarter and runs the tests on two CRMs.

CRMTests passedFailedCritical failures
CRM A7 of 8Test 2: only the current stage is stored1
CRM B6 of 8Tests 6 and 70

CRM A has the smoother email sync and wins on score, 7 to 6. But when a deal goes from first meeting to passed, CRM A keeps only "passed" and loses the first-meeting date. In the survey above, only a third of first meetings with management led to a partner meeting. Once the rest are passed, CRM A can count at most 8 of every 25 first meetings. The quarterly channel review, which decides where partner time goes, would run on a third of the real count. Under the critical-test rule, CRM A is out until it keeps stage history and passes a re-run. The fund picks CRM B and logs the two failed tests as conditions for the vendor, to pass a re-run before the first renewal (our suggested default).

If a founder you passed on last year pitches again and nobody can find why you passed, the fund screens the same company twice. For VC funds and family offices, Folio's deal flow and CRM module is where Folio runs this pipeline. How deal flow and CRM work in Folio.

What should you ask about security?

Ask the VC CRM vendor for its SOC 2 report and read which criteria it covers, which period, and which exceptions it lists. The AICPA's SOC 2 guide, listed on its SOC suite page, names five areas: security, availability, processing integrity, confidentiality and privacy. In our view, the report should cover confidentiality, not only security. Then ask who at the vendor can see your deals, whether every view and export is logged, and how you get all your data back if you leave.

In India
If decks reach your team on messaging apps, add one check: forward a deck from a phone and confirm it lands on the right deal without retyping.

When should you not buy VC CRM software yet?

Do not buy VC CRM software yet when the fund sees fewer than about 200 opportunities a year with one or two investors, has no agreed stages, or has partners who will not log deals.

SituationWhat to do instead
Fewer than about 200 opportunities a year, one or two investorsKeep a spreadsheet with channel, introducer, first seen, a date for each stage and pass reason
No agreed stages or exit rulesAgree the stages first; a CRM will only store the confusion
Partners will not log dealsMake the weekly pipeline review run only from the record, then choose the tool
Family office investing directly with a handful of deals a yearTrack deals in the same record as holdings, without a separate CRM

Choose on the traps, not the demo. Build the demo pipeline, run the eight tests and let the critical ones decide. For VC funds and family offices, Folio's deal flow and CRM module is where Folio runs this pipeline. Run the tests, then see deal flow and CRM in Folio.

FAQ

What should we migrate from the old system?

Every company, person and deal, with the date each deal entered each stage and every pass reason. Migrating only current stages loses the history that test 2 protects.

Should LP fundraising live in the same CRM?

It can, as a separate pipeline with its own stages and tighter access. In our view, keep LP prospects out of the deal team's default view.

Who should own the CRM?

In our view, one named person, such as a platform lead or associate, should own fields, stages and data quality. Our suggestion: that person runs a monthly check for duplicates and deals with no next step.

Should the vendor load the demo pipeline for us?

No. In our view, the fund should load it with each CRM's own import tool, from the same file. A pipeline the vendor loads tests the vendor's team, not the import you will use after signing.

What happens to a deal after the fund invests?

Its record should carry on into portfolio monitoring, so the history, people and documents stay with the company. Re-keying them into a second system is where manual portfolio data collection starts. Check how each CRM hands a closed deal to the fund's operating record.

About Folio

Folio is Incentiv's fund platform for private market investors: VC funds, family offices and their LPs. It covers deal flow, portfolio, LP and fund management. Its deal flow and CRM module is where the pipeline lives. Explore deal flow and CRM in Folio.

This post is general information, not investment advice. Tool results in the example are illustrative.