Companies vs. Deals: The Critical Distinction
A company is an entity that exists independently of your fund. Stripe is a company. It has founders, funding rounds, employees, a product, customers. Stripe exists whether or not your fund ever talks to them. A deal is your fund’s relationship with a company. You sourced Stripe, you met with the founders, you decided to invest (or pass), you negotiated terms, you closed the investment. The deal represents your fund’s interaction with that company. Your fund can have multiple deals with the same company. You might:- Pass on their seed round (Deal 1: Status = Passed)
- Invest in their Series A two years later (Deal 2: Status = Closed)
- Consider a follow-on in their Series B (Deal 3: Status = In Diligence)
Other entities to model
People - Founders, executives, employees. Core attributes: name, email, LinkedIn URL. People connect to companies through roles, not direct relationships. Roles - The connection between people and companies capturing who works where, in what capacity, and when. Model as a separate entity to track full history: a founder worked at Google (2018-2020), started Company X (2020-present), while advising Company Y (2021-present). Education - Where people went to school, what they studied, when. Model separately to capture multiple degrees and overlapping education. Enables analysis like “which universities produce the most founders in our focus areas?” Funding Rounds - Capital raised by companies. Attributes: round type, amount, valuation, dates, investors. Expect messiness: unreported SAFE notes, incomplete data from vendors, unannounced rounds. Your data model needs to handle uncertainty (covered in “Dealing with Messy Reality” below). LPs (Limited Partners) - Individuals and institutions who invest in your fund. Required for fund operations tools or LP portals. LPs can be individuals (HNWIs with personal info) or institutions (pension funds, endowments with organizational info). Model with a type field and nullable columns, or separate tables if managed differently. The list above isn’t exhaustive. Depending on what you’re building, you might also model: board seats, advisors, customers (for B2B portfolio companies), competitors, acquisitions, exits, fund entities (if you manage multiple funds), and more. Start with the entities your application actually needs, not a comprehensive schema you think you might need someday.Investors and funds
Other VC firms, angels, corporate investors who participate in rounds. You care about investors for co-investment patterns, warm intro paths, and understanding who’s active in your sectors. One firm can manage several funds with different mandates. For your own investments, you need to know which fund or SPV invested: ownership, reserves, and returns belong to that vehicle. Keep decisions such as a fund passing on a deal in your deal records, not in a table of completed round participations. For external market data, you may only know that a firm participated. That’s still useful for co-investment analysis and warm introductions. An angel may invest directly without a fund at all. Don’t invent a placeholder fund to make incomplete data fit your schema. Model each participation with an investor and an optional fund. When you know the vehicle, link it. When you don’t, leave it unknown. For example:The SQL below is simplified to illustrate entity relationships - not production-ready code.
Dealing with Messy Reality
Don’t assume perfect funding round data Early-stage companies raise money in ways that aren’t always captured in data sources. SAFE notes, convertible notes, rolling closes, stealth rounds. Crunchbase and PitchBook miss things, especially for pre-seed and seed companies. Your data model should allow for:- Unknown or estimated funding amounts
- Approximate dates (Q2 2024, not a specific day)
- Rounds that might not exist (rumored but unconfirmed)
- Multiple rounds of the same type (Seed, Seed Extension, Seed II)
Temporal Data and History
Companies change constantly. Employee count grows. Funding rounds happen. Valuations change. Products pivot. You need to decide what history to keep and how to model it. Start with append-only tables Append a new row with a timestamp when you get new information about a company. This preserves the history of changes without overwriting earlier values.pitchbook_company_changes (full history) and pitchbook_companies (latest values). Applications usually query the latest values table. When you need to analyze “how did this company change over time?” you go back to the append-only table or create a custom table for those types of queries.
For standard company datasets, storage cost is rarely the main reason to discard useful history. Keeping snapshots in staging tables can be simpler than predicting which changes will matter later. Size the data and estimate storage costs rather than assuming every source is cheap to retain.
The practical considerations are query performance and data warehouse costs (if you’re using Snowflake or BigQuery where you pay per query). But even there, you’re usually querying the transformed and materialized “latest values” tables, not the full historical append-only tables.
Retention and deletion are covered in Security and Compliance.
A snapshot captured in June tells you what the vendor reported in June. If a round closed in March and the vendor first picked it up in May, those are two different dates. Use the closing date to analyze investment activity. Use the observation date if a partner asks what you could have known at the time.