Partnership

V7 and Affinity Integrate to Turn Deal and LP Documents Into CRM Records

V7 and Affinity Integrate to Turn Deal and LP Documents Into CRM Records

6 min read

Affinity and V7 logos side by side with a plus sign on a dark background.
Affinity and V7 logos stacked with a plus sign on a dark background.
Deal teams and investor relations teams run V7 Go workflows against the documents they already receive, and the results land on the right Affinity record.

London and San Francisco – September 10, 2026 – V7 Go, AI infrastructure for private markets, now integrates with Affinity, the relationship intelligence platform for dealmakers. Deal teams and investor relations teams can run V7 Go workflows against the documents that arrive in their inbox and have the results land on the right Affinity record, with every value traced back to the page it came from.

V7 Go is not a CRM. It is not a data room and it is not a portfolio monitoring system. Affinity holds the deal and the relationship. V7 Go reads the documents that should be filling it in.

The document set is wider than any one format

Teasers and pitch decks at the top of the funnel. Information memoranda, management accounts, audited financials and QoE reports through diligence. GP and fund reports, capital account statements, DDQs, LPAs and side letters on the investor side. Terminology moves by desk: a growth team says pitch deck and data room, a credit team says information pack, an allocator says GP report and DDQ.

All of it carries the fields a CRM record wants. None of it arrives as fields.

A forty-page information memorandum holds perhaps fifteen values a deal team will actually use. Moving those fifteen into the system of record costs an analyst twenty to thirty minutes, and by then the next document has landed. Across a year of deal flow the practical result is familiar: most documents get skimmed, and the record reflects whatever someone had time to type.

Five workflows at launch

Each of these is configured against a firm’s own documents and its own Affinity field structure, and each writes back with citations attached.

Deal document to Affinity record. Company, sector, financials, transaction size and advisor are pulled from an inbound teaser, pitch deck or information memorandum, checked against existing Affinity organisations before anything is created, and written into the right opportunity with the source file attached.

Screening against the firm’s own criteria. Inbound opportunities are scored against the mandate before anyone opens the deck. The score and the reasoning behind it land in Affinity as structured fields, so the pipeline view reflects the screen rather than a partner’s recollection of it.

Data room to investment memo. Every document in the room is read, not the tenth of it a team has hours for, and the output arrives in the firm’s own memo template with deal history and prior interactions pulled from Affinity alongside it.

DDQ completion and operational due diligence. Questionnaires are answered from the firm’s own source material rather than from memory, and operational reviews run to a fixed checklist with exceptions surfaced for a person to judge. Both sit inside the wider due diligence work a deal team runs before an investment committee sees anything.

LP reporting and relationship records. Capital account statements, GP reports and quarterly packs are normalised into the same structure every quarter, feeding the same portfolio monitoring cycle, and the LP-side records a firm keeps in Affinity are reconciled against the documents behind them. See also CRM data hygiene.

Why the five hundredth run looks like the first

An assistant re-solves the problem every time it is asked. V7 Go runs steps that were defined once.

Each step carries its own instruction, its own tool and its own output type. A named model where the work is judgment. Python where the answer is arithmetic, a date format or a cross-foot. A direct call to Affinity where the data already sits in the CRM. A step told to check an inbound company against the firm’s investment criteria checks them on every run, not on the runs where it happens to.

Outputs are typed up front — fields, tables, selects, nested structures — so every run returns the same shape, ready for the same memo and the same Affinity field mapping.

Review gates sit wherever the firm puts them. Where a match against an existing Affinity organisation is ambiguous, the workflow stops and routes to a person rather than opening a second record. Judgment stays with the deal team.

Context a single document does not carry

Reading one document against itself is the easy half of the problem. The harder half is everything the firm already knows and cannot fit in the prompt.

Context Graph is V7 Go’s context layer: a knowledge layer over a firm’s portfolio, market data and deal history. When a teaser arrives, the screening workflow already knows the firm looked at that company two years ago, why it passed, and which of its portfolio companies sit in the same supply chain. That is what stops a familiar name from becoming a second Affinity record, and what lets a screen carry the firm’s memory instead of only the document in front of it.

Configured with your team

Implementation is part of what a firm buys, not a services line item. V7 solutions engineers scope the use case, build a proof of concept before any commitment, configure the workflows against the firm’s own documents, map output fields to its Affinity fields, and stay involved after go-live.

Permissions stay where they already are

The integration runs on the Affinity API and on the Affinity MCP server released on 28 April 2026. Both inherit the security, permissioning and privacy controls a firm has already configured in Affinity. Through V7 Go a user sees what that user sees in Affinity, and nothing beyond it.

Data originating from Affinity is labelled as such wherever V7 Go displays it, and is never used to train or develop any model. V7 holds SOC 2 Type II certification and ISO 27001, applies role-based access control across every workflow, and keeps an audit trail showing which step produced which value and from which page of which document.

Availability

The integration is available to firms with an active Affinity subscription and a V7 Go workspace. No separate data pipeline and no custom build are required.

V7 Go connects to more than 300 systems and runs as an MCP server itself, so the same defined workflows can be driven from an assistant a team already uses. Teams who want to watch it run against their own deal flow can book a demo.

About V7

V7 is a London-based AI company building infrastructure for document-heavy knowledge work. Its platform, V7 Go, lets teams in private markets, insurance and legal define workflows that read complex documents, run the same way every time, and return outputs traceable to their source. V7 was recognised in Tech Nation’s Future Fifty 2025 cohort and Sifted’s Rising 100.

About Affinity

Affinity is the leading relationship intelligence platform for dealmakers. With its AI-powered CRM, Affinity helps private capital firms, investment banks, and strategic acquirers find, manage, and close more deals by harnessing the power of their networks. Affinity is used by more than 3,000 firms across 30 countries to unlock relationship insights, drive efficiency, and win more opportunities.

Media Contact Information:

V7:
Casimir Rajnerowicz
marketing@v7labs.com

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.