It is a question that comes up almost every time, somewhere around the twelve-to-eighteen month mark of a fund's life: why hasn't more of the capital been deployed by now? The commitment was made, the thesis was clear, so the expectation is that the money should already be largely at work. It is a fair question, and a common one across the industry, not a sign that something unusual is happening in any one fund. The honest answer is that deployment speed in a technology-focused fund is not a proxy for conviction or urgency. It is a function of how long it genuinely takes to diligence a tech company properly, to manage the portfolio's follow-on needs alongside new sourcing, to time entries sensibly, and to build a portfolio that isn't quietly concentrated in a single year's worth of decisions.
None of this is unique to any one manager. It shows up across the industry, and it shows up more in technology-focused funds than in funds built around retail or consumer-facing businesses, for reasons that are structural rather than a matter of pace or effort.
The Investment Period Is Built for This
Most venture funds are structured with a commitment, or investment, period of roughly four to six years, inside an overall fund life that typically runs seven to fifteen years. That structure is not an accident or a compliance formality. It reflects an industry-wide understanding that deploying an entire fund's capital in the first year or two of its life is generally a sign of a rushed process, not a disciplined one. A fund that puts most of its capital to work slowly and deliberately over several years, rather than in a rush at the outset, is following the model as designed — it is what the structure is built to accommodate, not a departure from it.
Where Tech Diligence Actually Takes Longer
The clearest, most measurable reason tech deployments take time shows up in the sales cycles of the companies being evaluated, because those same cycles shape how long it takes to verify that a startup's growth claims are real.
A retail or consumer (B2C) business typically sells to an individual, in a purchase decision that can close in days. An enterprise technology company sells into an organization, and the data on how long that actually takes is stark: average B2B SaaS sales cycles run around three months overall, but that number hides enormous variation by segment — a small-business deal can close in two to four weeks, a mid-market deal in three to six months, and a genuine enterprise deal in six to eighteen months or longer. Deal size drives this directly: contracts under $10,000 in annual value tend to close in about a month, while contracts above $100,000 routinely take six to nine months or more, because the buying group scales with the stakes. Gartner's research puts the average B2B buying group at six to ten decision-makers — procurement, legal, IT, and multiple layers of business sponsors — compared to one or two decision-makers on a typical consumer or small-business purchase.
That matters to a fund manager for a very concrete reason: verifying that an enterprise tech company's revenue and customer traction are real, rather than a handful of pilots that never convert, means diligencing sales cycles that are themselves six, twelve, or eighteen months long. A manager cannot compress a company's own enterprise sales motion just because a fund is eager to deploy. In consumer or retail-facing businesses, growth and retention signals typically surface faster and are easier to verify directly, which is one reason those checks can often move faster.
Deep technology adds a further layer. Hardware, life sciences, and other science-driven ventures increasingly rely on milestone-based verification — a manager waiting for a working prototype, a regulatory checkpoint, or a technical proof point before committing further capital, rather than underwriting on a roadmap alone. That is a materially slower process than diligencing a consumer app that can ship, iterate, and show usage data within weeks. It is also, when done properly, the entire point: the diligence is slower because it is designed to catch the technical risk that a faster process would miss.
Follow-On Decisions Are a Second Deployment Process
Initial checks are only part of the job. At any given point in a fund's life, a manager is also reading the performance of every company already in the portfolio, because a meaningful share of total capital gets deployed as follow-on rather than as first checks into new names. That reading takes real time to do properly, and it happens in parallel with sourcing and diligencing new investments — not before or after.
The easy version of follow-on is to treat it as close to automatic: a portfolio company raises a new round, the fund has pro rata rights, other existing investors are participating, so the fund writes the check to avoid dilution. That is not disciplined capital allocation. It is deferring the decision to whoever set the terms of the round.
A disciplined process asks harder questions before that capital goes out. Has this company's actual performance — revenue, unit economics, retention, competitive position — earned the valuation the new round is proposing, or is the markup being driven by sector momentum that has little to do with this specific company? Is this genuinely the right moment for this company to raise, and is it the right moment for its segment more broadly, or is capital chasing a category that is already due for a correction? And critically: does adding more capital here push concentration — in this one company, or in this one segment — past what the portfolio was built to tolerate, regardless of how attractive the individual round looks in isolation?
None of those questions can be answered quickly, and none of them should be skipped just because "the round is happening" and the fund has the right to participate. Each follow-on dollar also has to be weighed against a live view of the exit path for that specific company — whether more capital actually improves the odds or economics of a future exit, or simply extends runway without changing the trajectory. Getting that analysis right, across an entire existing portfolio, at the same time as evaluating new opportunities, is a large part of why full deployment stretches across years rather than compressing into the first one or two.
Market Timing Is Not the Same as Market Chasing
A second reason deployment takes time is more judgment-based than data-based, but it is just as real. Disciplined managers do not deploy capital on a fixed calendar just to hit a pacing target. They wait for entry points that make sense — valuations that reflect a company's actual stage and risk, rounds that aren't being driven by momentum alone, and moments when a sector's expectations and its fundamentals are reasonably aligned.
This is also where vintage year risk enters the picture. Industry data from sources including Cambridge Associates, Burgiss, and PitchBook has consistently shown that venture returns cluster meaningfully by the year capital was deployed, largely because of the interplay between entry pricing and the macro environment a portfolio company matures into. A fund that rushes to deploy a full commitment inside a single hot year takes on concentrated vintage risk it did not need to take on. Spreading deployment across market conditions, rather than deploying all at once into whatever the market looks like this quarter, is a deliberate hedge against that risk, not a symptom of indecision.
Pacing Is Portfolio Construction, Not a Delay
The third reason is the most straightforward: a fund that deploys too quickly is choosing concentration, whether or not that is the intent. Spreading investments across multiple years naturally spreads them across multiple market cycles, multiple stages of company maturity, and multiple sets of prevailing valuations. That diversification is a core part of how a venture portfolio manages the power-law dynamics inherent to the asset class — where a small number of winners are expected to carry the fund, and where entering across a range of conditions improves the odds that at least some of those entries land at the right price and the right moment.
Pacing capital deliberately, in other words, is not the fund falling behind schedule. It is the schedule.
What This Means in Practice
None of this means every dollar of unspent commitment is doing exactly what it should — pacing discipline and simple execution speed are not the same thing, and LPs are right to ask managers to be specific about which one explains a given quarter. But the baseline expectation is worth setting clearly: a technology-focused fund that has not fully deployed its capital eighteen months or even three years into its investment period is, more often than not, behaving exactly as the structure intends. The alternative — deploying quickly to satisfy a pacing expectation — trades away the very discipline that a fund's diligence process, its entry timing, and its portfolio construction are all built to protect.
The honest measure of a tech fund's deployment pace isn't how fast the capital went out the door. It's whether each dollar went out at a moment, and after a process, that gave it a real chance to be one of the investments that ends up carrying the portfolio.