Attio for VC
A CRM that models how a venture fund actually runs. Custom objects for Portfolio companies and LPs. Deal-flow pipeline with partner vote and pass reasons. Sourcing automation from inbound, events, and scouts. Built from live implementations for Outlander, Graduate, Prudence, and Anorak.
Short answer
Attio for VC is an implementation pattern for venture funds: custom objects for Deals, Portfolio Companies, LPs, and Network; deal-flow pipeline, Monday review dashboards, LP and portco update workflows. Used by 4+ funds we work with directly.
This is for you if
You run a fund and deal flow is split across Airtable, Notion, and Gmail
Your partnership cannot answer 'how many deals did we source last quarter' without a spreadsheet
Portfolio companies report in a Google Sheet nobody keeps up to date
LP relationships happen between fundraises and get forgotten in between
Scouts send you deals through email threads that die in inboxes
You pay for three tools (CRM, portfolio tracker, LP tracker) and still cannot see the fund in one view
What standard CRMs miss
Venture runs on entities and relationships that a contact/company/deal model was never designed for.
A venture deal is not a sales deal
Sales deals close in weeks with a purchase order. Venture deals close in months with term sheets and partner votes. Using a default CRM pipeline collapses both into the same shape and the numbers stop being trustworthy.
Portfolio and pipeline are different workflows
Sourcing cares about filters and stage fit. Portfolio cares about health, runway, and next raise. Forcing both through one company record means one workflow gets neglected.
LPs are their own book of business
LPs have commitments, capital calls, distributions, and a reporting cadence. Treating them as contacts loses the structure that makes the next fundraise easier.
The network is a first-class asset
Co-investors, angels, scouts, and operators send you deals, follow on in rounds, and take calls about future funds. A flat contact list cannot map who sends what or who is owed an intro.
Your data model
Five objects connected through real relationships. Companies as the universe. Deals as one-check-per-deal. Portfolio companies with the post-investment workflow. LPs as their own book of business. People as the link across contexts.
Companies
The universe. Sourced, Evaluating, Portfolio, Passed, Alumni. Filterable by thesis, stage, and category.
- Relationship status (Sourced, Evaluating, Portfolio, Passed, Alumni)
- Business stage (Pre-seed, Seed, Series A, B+)
- Current ARR, last-round valuation, runway estimate
- Category tags (vertical SaaS, AI infra, marketplace, etc.)
- Deck link, data room link, one-pager
Deals
One deal per check. Follow-ons are new deals. Partner vote and champion tracked on the record.
- Stage (Sourced, Screened, Evaluating, Diligence, Partner Vote, Term Sheet, Closed/Passed)
- Round size, allocation requested, allocation received
- Pre-money valuation, lead investor status
- Partner owner, partner champion, IC date
- Pass reason (multi-select, not free text)
Portfolio companies
Custom object created when a Deal closes Won. Holds the fund's position and the post-investment workflow.
- Initial check, total invested, ownership %
- Board seat, observer seat, board cadence
- Current ARR, runway, last update date
- Follow-on status, reserve allocated
- Quarterly update notes and links
LPs
Custom object for limited partners with commitment, cadence, and relationship history.
- Commitment size, prior fund commitments
- Capital called, distributions paid
- Reporting cadence preference
- Last partner interaction, next-touch date
- Referrer, relationship strength
People
Founders, co-investors, LP contacts, angels, scouts, operators. One record linked across contexts.
- Role in the ecosystem (founder, co-investor, scout, LP, operator)
- Warm-intro strength, intro source
- Last partner conversation
- Linked Companies, Deals, Portfolio companies, LPs
How deal flow moves
Eight stages from sourcing to wire sent or passed. Every stage has a clear exit criterion. Pass reasons are structured, not free text.
Stage 1
Sourced
Inbound, outbound, scout, event, referral
Stage 2
Screened
First partner meeting taken
Stage 3
Evaluating
Second meeting, preliminary memo drafted
Stage 4
Diligence
References, market work, memo finalized
Stage 5
Partner Vote
Investment committee decision
Stage 6
Term Sheet
Negotiation and lead status confirmed
Stage 7
Closed / Invested
Wire sent, portfolio record created
Stage 8
Passed
Reason logged, follow-the-founder enabled
Pipeline views
Pre-built views that match how a partnership talks about the fund on Monday morning. By stage, by horizon, by portfolio health, by LP touch.
Partner Monday view
Deals awaiting partner action + portco missed updates + LP overdue
Inbound (last 7 days)
Source = Inbound OR Event, created in last 7 days
Active diligence
Stage = Evaluating or Diligence, partner owner = me
IC this week
Stage = Partner Vote, IC date within 7 days
Term sheet out
Stage = Term Sheet, signed = false
Follow-the-founder
Pass reason = Too Early, reminder date within 30 days
Portfolio health
Portfolio company runway < 9 months OR last update > 45 days
Follow-on candidates
Portfolio raising next round in next 6 months
LPs overdue
No interaction in 90+ days
Automations that pay for the setup
Sourcing without manual entry. Portfolio updates without chasing founders. LP cadence without a partner remembering. Network relationships that stay warm between deals.
Inbound email to Person and Company
An email from a founder or co-investor creates or updates records without duplication. Source tagged Inbound. Domain matched against the existing company universe.
Scout submission to deal flow
Scouts submit via Typeform or a firm email alias. A workflow creates the Company and Deal, routes to the right partner based on stage or category, notifies the Slack channel.
Deal stage change opens IC thread
When a deal hits Partner Vote, a Slack thread opens in the IC channel with the memo link, partner champion, and round terms pre-filled.
Closed-Won creates portfolio record
A deal closing Won spawns a Portfolio Company record with inherited fields: check size, ownership, board seat. Board cadence defaults from the check size.
Quarterly update reminders
Every portfolio company gets a scheduled task on its reporting cadence. Missed updates surface on the partner dashboard within 48 hours.
Follow-the-founder reminders
Pass reason Too Early creates a task 6 months out. No founder disappears because the timing was wrong on the first conversation.
LP touch cadence
Any LP with no interaction in 90 days surfaces on the partner's Monday view. Next fundraise starts warm.
Co-investor decay flag
Any co-investor with no interaction in 180 days gets flagged for an intro. The network stays active between deals.
Dashboards the partnership actually opens
Two dashboards cover most of the work. One for the partner's Monday. One for the LPAC.
Partner Monday view
Pipeline by stage. Deals awaiting partner action. Portfolio companies that missed their update. LPs overdue a touch. Five minutes of review, the week starts.
Fund-level dashboard
Total deals sourced vs evaluated vs invested by quarter. Pass reasons by category. Portfolio health. Follow-on pipeline against reserve. The dashboard the managing partner shows the LPAC.
Portfolio tracking without a second tool
For seed and early-stage funds, Attio holds everything a GP actually looks at on a portfolio company. Deeper metrics can sync from Visible or a Google Sheet when the fund wants them.
Current ARR, MRR, or revenue proxy
Runway and burn multiple
Headcount and recent hires
Last raise amount, valuation, and date
Next raise timing estimate
Board cadence and last board meeting
Key risks flagged by the GP
Recent wins and customer logos
How venture funds run deal flow, portfolio, and LPs in one workspace
The data model, the pipeline, the automations, and the traps that break standard CRMs for investors. Drawn from implementations for Outlander VC, Graduate VC, Prudence VC, and Anorak VC.
Read the article →The venture data model, in full
This is the build itself: the five objects, how deal flow moves through them, and the six automations that pay for the implementation. Five objects hold across stage focus and fund size \u2014 only the fields shift.
What standard CRMs get wrong for VC
Four mismatches, and every one of them shows up as a number nobody trusts.
- A deal is not a sale. A B2B sales deal closes in weeks with a purchase order; a venture deal closes in months with a term sheet, a partner vote, a lead-investor handshake and a legal close. The default pipeline forces you to pretend a partnership vote is a proposal and a term sheet is a contract.
- A company is not a contact database. A portfolio company has a cap-table position, a board seat, a valuation history, a follow-on plan and a stage in the fund lifecycle. A standard company record holds a name, a domain and a few tags, so everything the GP actually tracks ends up in a Google Doc.
- LPs are their own universe. They have capital commitments, capital calls, distribution history, reporting preferences and a relationship cadence. Treat them as contacts and you collapse two books of business into one and lose sight of both.
- Co-investors and networks matter. A fund runs on relationships with other funds, angels, operators and scouts who refer deals and follow on in rounds. A flat contact list cannot map who sends you the best deals or who you owe an intro to.
The five objects
- Companies — the universe. Startups sourced, passed, invested in. Split by relationship type (Sourced, Evaluating, Portfolio, Passed, Alumni) with stage of business, last-round valuation, current ARR, category and a link to the most recent deck.
- Deals — active opportunities, one per check rather than one per company, so a Series B follow-on is a new deal. Round size, allocation requested and received, pre-money valuation, lead status, partner champion, partner vote status.
- Portfolio companies — a custom object created when a Deal closes Won. Cap-table position, initial check, total invested, board and observer seats, board-meeting cadence, next reporting date, links to the quarterly updates. Separate from Companies because the workflows differ: sourcing cares about filters, portfolio cares about status health and follow-on planning.
- LPs — a custom object with commitment size, commitments to prior funds, capital called, distributions paid, preferred reporting cadence and next interaction due. Not every fund needs it on day one; it becomes load-bearing fast.
- People — founders, co-investors, LPs, angels, scouts and operators, with role in the ecosystem, warm-intro strength, last partner conversation and intro source. One record that links out to Companies, Deals, Portfolio companies or LPs depending on context.
How deal flow actually moves
Attio handles this with the Deals object plus a status field for the partner vote, a link to the decision memo, and a relationship back to whoever brought the deal in. Every deal has a partner owner and a champion. Pass reasons are a multi-select rather than free text, so pass patterns are analysable later.
- Sourced — inbound intro, event, cold email, scout tip or portfolio-founder referral. Gets a partner owner within 48 hours.
- Screened — first partner meeting. Screen pass, or proceed.
- Evaluating — second meeting, often with another partner. Preliminary memo drafted.
- Diligence — references, market work, founder deep-dive. Memo finalised.
- Partner vote — investment committee. Term sheet, wait, or pass.
- Term sheet signed — negotiation on details, lead-investor role confirmed.
- Closed / Invested — wire sent, portfolio company record created.
- Passed — reason logged, record kept for follow-the-founder tracking.
Sourcing automation that pays for the subscription
Every fund wants the same sourcing list and never quite builds it, because nobody has the time. In Attio it compounds instead.
- Inbound intros into a People record: an email to the firm mailbox triggers a workflow that checks for an existing record, creates one if missing, and tags the source as Inbound Email.
- Event-based sourcing: a conference CSV imports in minutes flagged Source Event, and founders missing from your network become a single view to work through the following week.
- Scout deal flow: scouts submit through a form or an email alias, and a workflow creates the company and deal, routes it to the right partner by stage or category, and notifies the Slack channel.
- Founder follow-up reminders: a pass reason of Too Early creates a task six months out, so no deal is lost to timing.
Portfolio and LP relations, without a second tool
Funds often bolt on a separate portfolio tool. For seed and early-stage funds, Attio covers what most portcos actually report: revenue, runway, headcount, next raise timing, key risks, key wins. The Portfolio Company record holds the current-quarter numbers, a quarterly update is a note or a linked email, and a dashboard surfaces the portcos that missed their last update, the ones short on runway, and the ones hitting follow-on thresholds. For deeper metrics the record integrates with a dedicated tool or a sheet, while the relationship data and the follow-on pipeline stay in Attio.
A fund that ignores LP relations between fundraises pays for it in the next one. LPs get their own pipeline: the LP object with commitment, cadence and next-touch date; a scheduled workflow that surfaces any LP with no interaction in 90 days into the partner's Monday view; capital call and distribution dates as structured fields rather than spreadsheet rows; and a separate fundraise pipeline when the next fund kicks off, pre-populated with existing LPs. None of it is clever. It is structure replacing a partner's memory.
The six automations, and the two dashboards
Two dashboards do most of the work. The partner Monday view shows pipeline by stage, deals waiting on partner action, portfolio companies that missed an update, and LPs overdue a touch — five minutes and the week starts. The fund-level dashboard shows deals sourced against evaluated against invested by quarter, pass reasons by category, portfolio health by status, and follow-on pipeline against reserve. That is the one the managing partner shows the LPAC.
- New inbound email creates or updates a Person and Company record, deduplicated on email, so there are never two records for the same founder.
- A deal stage change updates the partner owner and opens a thread in the IC Slack channel with the memo link.
- Closed-Won creates a Portfolio Company record with inherited fields, board cadence defaulting from the check size. No copy-paste.
- A quarterly update reminder puts a task on every portfolio company at its reporting cadence, and missed updates bubble up to the GP dashboard.
- An LP quarterly-letter send list: a view filtered by cadence preference, one click to export or pipe into a mail tool.
- A co-investor relationship decay flag surfaces anyone with no interaction in 180 days for a coffee intro.
Why this works in Attio and not in a standard CRM
The bar for a fund CRM is high, because partners will not use a tool that costs them more than it gives. A venture setup takes about 7 to 10 working days once the fund has decided on the custom objects and the pipeline stages. The blocker is rarely the tool — it is the partnership agreeing what a deal-stage definition means.
- Custom objects are first-class. Portfolio companies and LPs are not awkward extensions of Deals or Contacts; they have their own workflows, views and automations.
- Relationships are real. One person links to multiple companies across sourced, portfolio and co-investor contexts, rather than being forced through duplicate contact records.
- Speed and focus. A partner on the road opens Attio on mobile, updates a deal in 20 seconds, adds a note and closes the tab.
FAQ
Is Attio a real CRM for a venture fund?
Yes, when the custom objects are set up properly. Portfolio companies and LPs get their own objects with their own workflows, not forced into the default Deals and Contacts model. The funds we have worked with (Outlander, Graduate, Prudence, Anorak) all run their full fund operation in Attio.
Do I still need Affinity, Visible, or a portfolio tracker?
Attio handles deal flow, portfolio tracking, and LP relations for most seed and early-stage funds. For deeper metrics tracking or automated portfolio data collection, Attio integrates with Visible or a Google Sheet. The relationship data and the follow-on pipeline stay in Attio.
How do you handle deal-flow velocity without the CRM slowing partners down?
Partners on the road open the deal on mobile, update status in 20 seconds, add a note, close the tab. Most inbox and scout sourcing is automated so the partner never types a record from scratch. The CRM only asks for judgment, not data entry.
Can we track LP relations in the same workspace?
Yes. LPs are a custom object with commitment size, capital called, distributions, cadence preference, and last touch. A scheduled workflow surfaces LPs overdue for an interaction. The next fundraise starts from a warm list, not a cold rebuild.
What about co-investors and the broader network?
Co-investors, angels, scouts, and operators live as People with a role field. A decay flag surfaces relationships that have gone quiet for 180 days. The fund's network becomes a managed asset instead of a partner's memory.
How long does a VC setup take?
About 7 to 10 working days once the partnership agrees on pipeline stages and custom object fields. The tool is rarely the blocker. The decision on what a deal-stage definition means takes the longest.
Should a follow-on be a new deal or an update to the existing one?
A new deal. One deal per check, not one per company — a Series B follow-on gets its own record with its own allocation, valuation and partner vote. Modelling it as an update to the original deal destroys your ability to report on the fund's actual deployment.
Do we need the LP object from day one?
Not always, but it becomes load-bearing faster than most funds expect. If you are between fundraises, the cost of not having it is invisible until the next raise, when nobody can say which LPs have been touched in the last quarter. Adding it early is cheap; retrofitting the history is not.
Why keep Portfolio Companies separate from Companies?
Because the workflows are different. Sourcing cares about filters and stage; portfolio cares about status health, reporting cadence and follow-on planning. Keeping them in one object means every portfolio view has to filter out the universe first, and the fields that matter for one are noise for the other.
137,000 records, and the same deal saved five times
A capital-raising firm asked whether their own Attio build would hold as they grew. The audit said yes, and named the three things that would break first. Then the build: an import deduper, a whole-workspace backup runner, and computed reports Attio dashboards cannot express.
Read the case study →Keep reading
Most funds reach us from Affinity or Folk. Here is how each compares, and what a migration actually involves.
Ready when you are.
Book a call and we will tell you honestly whether this is worth doing, or start with the free 48-hour audit and decide afterwards.