Every venture capital fund has a pipeline. Companies come in, get evaluated, move through stages of diligence, and either receive an investment or get passed on. The question is not whether you have a pipeline, but how well you can see it, manage it, and act on it.
For years, most VC teams managed their deal flow in spreadsheets or list-based CRMs. Rows of company names, status columns, date fields, partner assignments. These tools work, in the sense that they store information. But they fail at the thing that matters most: giving you an intuitive, at-a-glance understanding of where every deal stands and what needs to happen next.
Kanban boards solve this problem. Borrowed from manufacturing and popularized by software development teams, the kanban approach to deal management is gaining rapid adoption across venture capital. Here is why it works and how to implement it effectively.
Why Visual Pipelines Work
The human brain processes visual information fundamentally differently from text and numbers. When you look at a spreadsheet with 200 rows of deal data, you are reading. When you look at a kanban board with cards arranged in columns, you are seeing. The difference is profound.
Instant Pattern Recognition
A kanban board shows you patterns that a spreadsheet hides. You can immediately see:
- Which stages are overloaded. If your "Due Diligence" column has 15 cards and your "Partner Review" column has two, something is off. Either due diligence is taking too long, or not enough deals are advancing.
- Which deals are stale. Cards that have been sitting in the same column for weeks stand out visually. In a spreadsheet, you would need to sort by date and scan for old entries.
- How your pipeline is shaped. A healthy pipeline looks like a funnel: wide at the top (many inbound deals), narrowing through each stage (selective advancement), and tight at the bottom (few investments). You can see this shape instantly on a kanban board.
Reduced Cognitive Load
Switching between a spreadsheet and your mental model of the pipeline requires constant translation. You read "Status: Diligence" in a cell and mentally place that company in your pipeline. Multiply this by 100 or 200 active deals and the cognitive load becomes significant.
A kanban board eliminates this translation. The spatial position of the card is the status. Your eyes do the work that your brain would otherwise have to do, freeing mental energy for actual decision-making.
Natural Workflow Alignment
Deal evaluation is inherently a sequential process. Companies move from one stage to the next (or get filtered out). This sequential flow maps perfectly to the left-to-right movement of kanban cards across columns. The visual metaphor matches the real workflow, which makes the tool feel intuitive rather than imposed.
Designing Your Column Structure
The columns on your kanban board represent the stages of your deal process. Getting this right is important because the columns define how your team thinks about and discusses the pipeline.
A Practical Column Structure for VC
Here is a structure that works well for most early-stage funds. Adjust it based on your specific process.
1. Inbound / Sourced
This is the entry point. Every company that enters your pipeline starts here, whether it came through a warm introduction, a cold email, an event, or an application. At this stage, you have basic information (company name, founder, sector, one-line description) but have not yet engaged.
The key metric for this column is volume. It should be your widest column, representing the full breadth of your deal flow.
2. Initial Review
Companies move here when someone on the team has done a preliminary assessment. This might involve reading the deck, doing a quick market scan, or having a brief introductory call. The goal of this stage is to determine whether the opportunity warrants a deeper conversation.
Most companies will not advance past this point. That is expected and healthy. The initial review stage is your primary filter.
3. First Meeting
This column contains companies where you have scheduled or completed a first substantive meeting with the founding team. The meeting might be a pitch, a product demo, or a deep-dive conversation. The output of this stage is a preliminary assessment of team quality, market opportunity, and product potential.
4. Deep Dive / Due Diligence
Companies that pass the first meeting threshold move into active diligence. This involves customer calls, reference checks, financial analysis, competitive landscape mapping, technical review, and any other evaluation steps your fund requires.
This stage is where most of the team's analytical work happens. Cards in this column should have clear owners and defined next steps.
5. Partner / IC Review
Deals that survive diligence advance to partner review or investment committee. At this stage, the deal is being presented to the full partnership (or the decision-making body) for a final investment decision.
This column should be small. If it is overflowing, either your diligence process is not selective enough or your committee is not meeting frequently enough.
6. Term Sheet / Negotiation
The fund has decided to invest. This column tracks deals where terms are being discussed, legal documents are being drafted, and closing mechanics are underway.
7. Closed / Invested
The deal is done. The card moves to the final column, and the company transitions from "pipeline" to "portfolio."
8. Passed
Companies that are declined at any stage move to a "Passed" column (or are archived). This column is valuable for tracking your pass rate, understanding why deals did not advance, and potentially re-engaging with companies that improve over time.
Customizing Columns for Your Fund
The structure above is a starting point. Your fund may need additional or different columns based on your process:
- Funds with a two-stage committee process might split "Partner Review" into "First Committee" and "Final Committee."
- Funds that do significant technical diligence might add a "Technical Review" column between "Deep Dive" and "Partner Review."
- Funds with a strong outbound sourcing program might split "Inbound / Sourced" into "Inbound" and "Outbound" to track sourcing channels separately.
The key principle is that columns should represent meaningful, distinct stages in your process. Avoid creating too many columns (which adds clutter and confusion) or too few (which obscures where deals actually stand).
WIP Limits for Deal Review
One of kanban's most powerful concepts is the Work-In-Progress (WIP) limit. A WIP limit caps the number of items that can exist in a given column at any time. When the limit is reached, no new items can enter that column until existing items are moved forward or removed.
Why WIP Limits Matter for VCs
Without WIP limits, it is easy for deals to pile up in certain stages. The "Due Diligence" column grows to 20 or 30 companies, each receiving a fraction of the team's attention. Nothing moves forward decisively because the team is spread too thin across too many active evaluations.
WIP limits force prioritization. If your "Deep Dive" column has a WIP limit of eight, and it is currently full, the team must either advance or pass on a deal before taking on a new one. This creates healthy pressure to make decisions and prevents the chronic accumulation of "maybe" deals that drain team bandwidth without producing outcomes.
Setting Effective WIP Limits
WIP limits should reflect your team's actual capacity. Consider these factors:
- Team size. A solo GP might set a WIP limit of three for deep dives. A team of four might handle eight to ten.
- Stage complexity. Stages that require more work per deal (diligence, committee prep) should have lower WIP limits than lighter stages (initial review).
- Cycle time goals. If you want deals to move through diligence in two weeks, your WIP limit for that column should be low enough that each deal gets sufficient attention within that timeframe.
Start with conservative WIP limits and adjust as you learn your team's throughput. It is better to start too tight and loosen than to start too loose and let deals accumulate.
Moving Deals Across Stages
The act of moving a card from one column to the next should be intentional and meaningful. It represents a decision, not just a status update.
Advancement Criteria
Define clear criteria for what it takes to move a deal to the next stage. These criteria should be documented and understood by the entire team. Examples:
- Inbound to Initial Review: A team member has been assigned and has read the deck or pitch materials.
- Initial Review to First Meeting: The reviewer believes the opportunity meets basic criteria (stage, sector, market size) and warrants a meeting.
- First Meeting to Deep Dive: At least one partner believes the team, market, and product warrant further investigation. Initial concerns have been documented.
- Deep Dive to Partner Review: Diligence is substantially complete. A written assessment has been prepared. The deal champion recommends advancement.
- Partner Review to Term Sheet: The investment committee has approved the investment, subject to final terms.
Documenting the Move
When a card advances, the person moving it should add a brief note explaining why. This creates an audit trail that is invaluable for portfolio review, LP reporting, and process improvement.
A simple template works well: "Advancing to [stage] because [reason]. Key next steps: [actions]." This takes 30 seconds and adds enormous value over time.
Backward Movement
Deals do not always move forward. Sometimes new information emerges during diligence that sends a deal back to an earlier stage for further evaluation. Sometimes a committee declines to approve but wants to revisit after certain conditions are met.
Your kanban board should accommodate backward movement without stigma. Moving a deal back is not a failure. It is evidence of a rigorous process.
Team Visibility and Collaboration
One of kanban's greatest strengths is the visibility it creates across the team. Everyone can see the full pipeline at any time, which enables several important behaviors.
Shared Situational Awareness
When the entire team can see the board, conversations become more productive. Instead of asking "what is the status of that fintech company?" in a meeting, everyone already knows. Pipeline reviews can focus on substance (what do we think of this company?) rather than status updates (where is this deal?).
Load Balancing
Visual pipelines make workload imbalances obvious. If one partner's deals are concentrated in the diligence stage while another partner has nothing in diligence, the team can rebalance. This prevents bottlenecks and ensures deals do not stall because one person is overloaded.
Accountability
When your name is on a card and the whole team can see it, there is natural accountability to keep things moving. Stale deals are visible. Missed follow-ups are apparent. This social pressure is gentle but effective.
Cross-Pollination
When teammates can see each other's deals, they can offer input and connections that would otherwise be missed. "I see you are looking at a logistics company. I met a founder in that space last month who might be relevant." This kind of cross-pollination happens naturally when the pipeline is visible and rarely happens when deals are locked in individual spreadsheets.
Filtering and Views
A kanban board with 200 cards across eight columns can become overwhelming without filtering capabilities. Effective deal management requires the ability to slice the board in multiple ways.
Common Filters
- By partner or owner. Show only the deals assigned to a specific team member. Useful for individual pipeline reviews and one-on-one meetings.
- By sector. Filter to see only healthcare deals, or only fintech deals. Useful for sector-specific pipeline analysis.
- By source. Show deals that came through a specific channel (inbound, event, referral). Useful for evaluating sourcing effectiveness.
- By date. Filter to deals added or moved within a specific timeframe. Useful for tracking pipeline velocity.
- By tag or label. Custom tags (e.g., "AI-native," "repeat founder," "international") allow flexible, ad-hoc filtering.
Saved Views
Power users create saved views that they access regularly. A partner might have a "My Active Deals" view, a "Committee Pipeline" view, and a "This Week's New Inbound" view. Each provides a different lens on the same underlying data.
Board vs. Table Toggle
The best deal management tools let you switch between kanban and table views of the same data. The kanban view is ideal for pipeline reviews and status assessments. The table view is better for sorting, filtering, and bulk operations. Both views should reflect the same underlying data and stay synchronized.
Integration with CRM
A kanban board for deal management is most powerful when it is integrated with your broader CRM. The board should not be a standalone tool. It should be a view layer on top of your deal database.
What Integration Looks Like
- Card click-through. Clicking on a kanban card opens the full company profile with all associated data: contacts, meeting notes, documents, metrics, and communication history.
- Automatic status updates. When you drag a card to a new column, the underlying deal record updates automatically. No double entry required.
- Activity logging. Meeting notes, emails, and other interactions logged in the CRM should be visible from the kanban card. The board provides the overview; the CRM provides the detail.
- Notification triggers. Moving a card to certain stages can trigger automated actions: notify the partner, schedule a committee review, send a follow-up template to the founder.
The Danger of Disconnected Tools
Some teams use a standalone kanban tool (like Trello or a general project management app) alongside a separate CRM. This creates a synchronization problem. The board and the CRM inevitably drift out of alignment, and the team loses confidence in both. The overhead of maintaining two systems erodes the efficiency gains that kanban is supposed to provide.
The solution is a CRM that has native kanban functionality, or a kanban tool that is deeply integrated with your deal database. Either way, the principle is the same: one source of truth, multiple views.
Measuring Pipeline Health
Once your kanban board is set up and your team is using it consistently, you can start measuring pipeline health with metrics that would be difficult to track in a spreadsheet.
Conversion Rates by Stage
What percentage of deals advance from each stage to the next? A healthy pipeline might show:
- Inbound to Initial Review: 60%
- Initial Review to First Meeting: 30%
- First Meeting to Deep Dive: 25%
- Deep Dive to Partner Review: 40%
- Partner Review to Term Sheet: 50%
Tracking these rates over time reveals whether your pipeline is getting more or less selective, and where bottlenecks exist.
Cycle Time by Stage
How long does the average deal spend in each stage? If diligence takes six weeks when your target is two, that is a process problem. If deals sit in "Partner Review" for three weeks because the committee only meets monthly, increasing meeting frequency might unlock faster deployment.
Pipeline Value
Assigning an estimated round size or check size to each deal lets you calculate the total potential deployment in your pipeline. This metric helps with fund pacing and ensures you have enough active opportunities to deploy your target capital within your investment period.
Getting Started
If your fund is currently managing deals in a spreadsheet or a list-based CRM, transitioning to a kanban approach does not require a complete overhaul. Start with these steps:
- Map your current process. Write down the stages your deals actually go through, from initial contact to investment or pass. These become your columns.
- Choose a tool. Select a platform that supports kanban views natively and integrates with your deal data. Avoid bolting a kanban tool onto a system that was not designed for it.
- Migrate active deals. Move your current pipeline onto the board. This is a one-time effort that pays dividends immediately.
- Set initial WIP limits. Start conservative. You can always adjust.
- Run your first pipeline review on the board. Use it as the focal point for your weekly deal discussion. The team will adapt quickly once they experience the benefits.
If you are looking for a VC-specific CRM with built-in kanban pipeline management, customizable stages, and deep integration with your deal records, Roulette is designed for exactly this workflow. It gives your team a visual, collaborative pipeline that stays in sync with all your deal intelligence.