Skip to main content

Show Me Your Portfolio and I’ll Show You Your Thesis

Here’s an example. A fund says: “We’re a Series A fund focused on B2B SaaS.” But when you analyze the portfolio, you see 60% Series A, 30% Seed, 10% Series B. The industry breakdown is 70% B2B SaaS, 20% fintech, 10% consumer. Average check is $3M with a range from $500K to $8M. If you built the CRM around the LP pitch, you’d already be missing two stages and two sectors. Pull the actual investments, group them by stage, check size, sector, and geography, and compare Fund I with Fund II. Ask a partner about the outliers. One unusual check could be an experiment or the start of a new strategy.

How fund type changes the work

How the deal team works

Seed funds vary widely in their approach, some are concentrated portfolios, other are more “spray-and-pray”. A typical seed fund might make 5-10 investments per year with check sizes around $500K-$2M. These aren’t tiny angel checks, but meaningful seed investments where the fund takes a significant ownership stake. These funds are often run by small teams of 2-5 people. There’s no large analyst pool. Partners wear multiple hats: sourcing, evaluating, supporting portfolio companies, managing LP relationships. The diligence process is relatively quick (1-3 weeks typically) but still substantive. They’re evaluating founder quality, market opportunity, early traction, and whether the company has a real shot at reaching Series A. Deal flow matters, but it’s not about processing hundreds of deals. It’s about seeing enough quality opportunities to make 5-10 great bets per year. The fund might review 200-500 companies annually to find those investments. Research and thesis-driven sourcing becomes important. Many seed funds actively map ecosystems and reach out to interesting founders rather than waiting for inbound. There’s a subset of seed funds that take a different approach: 30-50+ investments per fund with smaller checks ($50K-$500K). These funds operate more like volume businesses with minimal diligence and binary outcomes. But this is less common than the concentrated approach. At Series A and B, deal teams are often larger. You might have 5-10 investment professionals, plus operating partners or specialists. The diligence process involves multiple people: someone does market research, someone handles financial modeling, someone does customer reference calls, maybe someone does technical evaluation. Everything feeds into an investment committee meeting where partners debate the deal. Growth equity funds operate at the other end of the spectrum. Low deal volume (maybe 10-20 companies per fund), very large checks ($25M-$100M+), and diligence processes that can stretch 3-6 months. These deals look more like acquisitions than venture bets. The fund is evaluating mature businesses with real revenue, established customers, and clear unit economics. The focus here shifts from “will this work?” to “can this scale profitably?” Customer references matter a lot. Financial models need to be detailed. The fund often co-invests with other growth funds, so syndicate management becomes important. There’s significant operational involvement. Some growth funds effectively function as operating partners, helping professionalize finance, sales, and operations. Buyouts. Deal sourcing happens differently. Deals often come from investment banks running formal processes, not warm intros from founders. Due diligence involves consultants, legal teams, accounting firms, and operational experts. The fund isn’t just evaluating the business, they’re planning how to grow revenue, improve operations, cut costs, and eventually sell it. Here’s where the role of technology and data changes fundamentally. In PE, the questions deal teams ask are often so bespoke that the technologist’s role shifts from building systems to being part of the deal team itself. You’re using data to help deal teams get to conviction. Can we model the impact of operational improvements? What does the competitive landscape look like quantitatively? How do we assess add-on acquisition targets? Post-deal, the work continues with portfolio companies. You might help a portfolio company with M&A analysis for add-on acquisitions. Or build custom models for their specific business challenges. Each project is tailored to bespoke needs. This isn’t about building one platform that serves all portfolio companies. It’s about being a data and technology partner embedded in the operational work of the fund and its portfolio. Multi-strategy funds. The structure creates interesting dynamics. A company might start as a seed investment from the early-stage fund, then receive follow-on investment from the growth fund years later. Deal flow can be shared across funds. A company that’s too late for the seed fund might be perfect for Series A. Partners often specialize by stage or sector but can collaborate across funds. The challenge is managing complexity while maintaining the benefits of integration. Each fund needs its own LP reporting, its own capital tracking, its own performance metrics. But deals, companies, and relationships should be shared. A partner working on both the seed and growth funds needs visibility across both, but LPs for each fund should only see their specific fund’s data.

Geography and sector

A fund focused on a single city or region operates differently than a global fund. Hyper-local funds benefit from dense networks. They know everyone in the ecosystem. They track local events, community gatherings, and founder meetups. Deals come from repeated interactions and warm introductions within a tight network. Global funds face different challenges. Partners operate across time zones. The fund deals with multiple currencies and potentially multiple legal entities for regional investments. Different regions have different legal and compliance requirements. Regional partners might have deal attribution and carry allocation based on geography. Sourcing is also harder at scale. Global funds compete against local investors with deeper regional networks. Building relationships with founders across time zones requires more deliberate effort and often more reliance on data-driven sourcing to compensate for thinner local presence. From a technical perspective, geographic focus shapes your architecture significantly. Multi-entity structures require careful data modeling: which legal entity made which investment? How do you aggregate performance across entities while maintaining separation for legal and tax purposes? Currency handling affects portfolio valuation and financial reporting. Time zones affect scheduling features, notification timing, and how you display dates. Access control becomes more complex: regional partners might only see deals in their geography, while HQ needs global visibility. Deep tech and hard tech funds face long development timelines. Companies might spend years in R&D before having a product. Diligence involves technical experts, often PhDs who can evaluate the science. The fund needs to track grants and non-dilutive funding sources. IP and patent monitoring becomes important. Success metrics differ from typical startups. Fintech and crypto funds deal with regulatory complexity. Banking licenses, compliance requirements, and regulatory approval workflows need tracking. Cap tables might involve token economics alongside traditional equity. Diligence processes need to evaluate banking partnerships and infrastructure relationships. The fund needs specialized integrations, maybe with blockchain explorers or regulatory databases. B2B SaaS funds focus heavily on financial metrics. ARR, net retention, customer acquisition cost, lifetime value. These metrics are well-defined and comparable across portfolio companies. Customer reference tracking matters. Product and technical architecture evaluation is important. Go-to-market strategy gets scrutinized. Consumer and marketplace funds care about user growth, retention, cohort analysis, and unit economics. Brand strength matters. Community and network effects need assessment. The metrics are different from B2B, and the diligence process focuses on different aspects. The technical challenge for generalist funds is flexibility without chaos. Your categorization systems need to handle companies that don’t fit neat boxes. Tagging and metadata become more important than rigid hierarchies. Signal processing for deal flow requires broader pattern matching: you can’t rely on sector-specific signals, so you need systems that surface opportunities based on founder quality, market dynamics, and thesis fit across different industries. Your metric tracking needs to gracefully handle B2B SaaS, consumer apps, marketplaces, and hardware companies in the same portfolio. The key is building abstractions that work across sectors while allowing customization where needed.

Questions for the people doing the work

Ask a GP to walk you through the last deal, with the actual notes and tools open. Follow the gaps in the story. About Thesis Creation and Evolution:
  • “How do you develop and refine your investment thesis?”
  • “What data or signals inform changes to your thesis over time?”
  • “How do you track emerging trends or technologies you’re monitoring?”
  • “How do you share thesis work across the team?”
About Deal Flow:
  • “Walk me through how a deal comes in and what happens next”
  • “How many deals do you see per month? How many do you invest in?”
  • “What’s your typical timeline from first meeting to close?”
  • “Who needs to be involved in decision-making?”
  • “What opportunities have you missed that you wish you hadn’t? Why did you miss them?”
About Due Diligence:
  • “What does your diligence process look like?”
  • “What information do you need to make a decision?”
  • “How do you share information within the team?”
  • “What are the common blockers that slow down deals?”
  • “When you pass on a company, how do you track why you decided not to invest?”
About Portfolio Management:
  • “How often do you interact with portfolio companies?”
  • “What information do you need from them regularly?”
  • “How do you decide on follow-on investments?”
  • “What board materials do you receive?”
About LP Reporting:
  • “How often do you report to LPs?”
  • “What do LPs ask for that’s hard to produce?”
  • “How long does it take to prepare LP reports?”
  • “What data is hardest to gather?”
About Pain Points:
  • “What takes the most time that shouldn’t?”
  • “What information do you wish you had but don’t?”
  • “What manual processes drive you crazy?”
  • “What tools have you tried that didn’t work? Why?”

What to watch for

Shadow the team whenever possible. Sit in on partner meetings. Watch how deals get discussed. What information do they reference? What questions get asked? See how they prepare for IC. What documents get created? What analysis happens? Observe portfolio company interactions. How do updates get shared? What matters in those conversations? Watch the current tools in use. What spreadsheets do they maintain? These often reveal the data they care about most. What emails get sent repeatedly? Look for templates and patterns. What Slack channels are most active? This shows where conversation and collaboration happen. What questions get asked over and over? These reveal information gaps. Look specifically for workarounds. These are gold for understanding what’s broken. Manual processes that should be automated reveal workflow inefficiencies. Information that lives in someone’s head rather than a system shows where knowledge management fails. Data that gets re-entered multiple times indicates integration gaps. Decisions made without data or with incomplete data show where analytics and reporting fall short. Watch for red flags in your conversations. If someone says “We’ll figure out the process as we build the tool,” that’s a sign you don’t understand their workflow yet. If they say “Just build something flexible and we’ll adapt,” they don’t actually know what they need. If they say “Make it like [other fund’s tool] but better,” they’re guessing about what might work. If they say “We need everything that [vendor] has,” they haven’t thought about their actual requirements.

Translating Thesis to Technical Requirements

Example 1: Concentrated Seed Fund

Imagine a fund with these characteristics: They make 5-8 investments per year. Check sizes are $500K-$1.5M. They review 300-400 companies annually to find those investments. The diligence process takes 2-3 weeks. They focus on deep tech and take concentrated bets on technical founders. They reserve 20% of the fund for follow-ons. Here I’d keep the founder conversations and technical milestones together so you can pick up where you left off three months ago. Once a company goes into diligence, a short checklist covers the technical review, founder references, and market assessment. Keep the deck and reference notes with the deal, along with the decision the partners reached. Portfolio tracking needs to be engaged but not overwhelming. Track key metrics for early-stage companies: burn rate, runway, revenue, technical milestones, hiring progress. Support regular check-ins with founders. Track follow-on investment decisions. Which companies are raising Series A? Do we want to invest more? What’s the reserved capital allocated to each company? LP reporting happens quarterly with narrative depth. Not just numbers, but the story of each investment. What progress has the company made? What are the risks and opportunities? What’s the plan for follow-on investment?

Example 2: Series A Fund with Deep Diligence

Now imagine a different fund: 20-30 deals per year. Check sizes of $3M-$10M. Diligence process takes 3-6 weeks involving multiple team members. The fund always takes board seats and plans to be actively involved. They’re generalist, investing across sectors. Here I’d track who owns each diligence workstream, which documents are still missing for IC, and when the next board pack is due. A single ‘in diligence’ status won’t tell the team whose work is holding up a decision. Being generalist makes sourcing particularly challenging. The team sees hundreds of companies across different industries. You need systems to sift through the noise and surface the right opportunities. Signal scoring based on thesis fit, founder quality, market dynamics. Recording conversations becomes critical since partners have dozens of calls with founders and advisors. Entity resolution matters too: is this the same company we saw last year, or the founder’s previous startup? Portfolio tracking needs to be detailed and operational. Comprehensive metrics across financial, product, and team dimensions. Not just revenue, but also unit economics, customer metrics, product development, hiring progress. Board meeting scheduling and materials management matters when you have 20 board seats. Follow-on investment analysis requires tracking reserved capital and making data-driven decisions about when to invest more. Co-investor relationship tracking helps manage syndication. LP reporting happens quarterly with detail. Portfolio company deep-dives where you tell the story of what’s happening, not just numbers. Automated data aggregation from multiple sources because manually assembling quarterly reports is painful. Performance attribution so LPs understand which investments are driving returns.