What should my 30/60/90-day VC fundraising plan be?

Days 1 to 30, remove the reasons to say no

Nothing here involves an investor. That is the point: this block exists so that the second block is not spent discovering gaps in front of people whose time you cannot get back.

• Run the readiness check and record which of its nine items are evidenced rather than asserted. Blueprint's readiness page is the instrument.
• Fix the cheap gaps: providers appointed, references asked, the room organised, the track record attributable and dated.
• Settle the number. Work the four constraints on Blueprint's page about what size a record supports and know which one binds you.
• Build the target list and score it. Blueprint's page on scoring and prioritising prospects turns a list into a sequence.
• Settle the offering position for every market you intend to approach, which is a counsel question and one that constrains outreach rather than following it.
• Finish the deck last, not first, because it should express a case the preceding items have already made defensible.

Days 31 to 60, test the case

Now the conversations start, in a deliberate order.

• Open with prospects scored high on fit and reachable, but not with the most important ones. The first few conversations are where you find out what the case sounds like out loud.
• Record every question you could not answer well. That list is the most valuable output of this block and it is usually short and repetitive.
• Fix what the list reveals, weekly, rather than at the end of the block.
• Move to the high-value conversations once the case has stabilised, which is usually two or three weeks in.
• Track responses by category rather than as a running total, so that a pattern becomes visible. Blueprint's page on interpreting rejections and non-responses covers the categories and the four tests for a real pattern.
• Keep the pipeline inside your capacity. Blueprint's page on a manageable pipeline gives the arithmetic, and this is the block where a small team most often exceeds it.

Days 61 to 90, convert or diagnose

Two activities running in parallel, and the second is the one managers skip.

• Convert: advance the conversations that are progressing, which now means diligence rather than meetings. Blueprint's page on answering a limited partner questionnaire covers what arrives.
• Protect capacity for diligence, because it lands on the same weeks as everything else and it is the stage where a slow response costs most.
• Diagnose: for everything that is not progressing, work the four failure points on Blueprint's page about stalled raises and record which one is binding.
• Reconcile the pipeline honestly, meaning move every conversation with no recent activity from the investor out of the live column.
• Recalculate the runway, both personal and firm, against where the raise actually is.
• Decide, using Blueprint's page on pausing, resizing, or restructuring, and write the decision down with its reason.

What ninety days should produce

Three possible outcomes, all of them legitimate, and one of them is not a close.

• Momentum. Confirmed commitments and live diligence sufficient to plan a first close, which turns the next block into the checklist on Blueprint's page about what should be ready before a close.
• A corrected plan. A clear diagnosis, a fixed problem, and a second ninety days with a different target list, a different number, or a different case.
• A changed decision. Evidence that the fund as designed is not the fund to raise now, which routes to the pause, resize, or restructure page. Reaching this conclusion in ninety days rather than in eighteen months is a good outcome, however it feels.

Evidence, judgment, and assumption

A plan is mostly assumption at the start and should be mostly evidence at the end. Whether that conversion happened is the real test of the ninety days.

• Evidence, by day ninety: meetings held, questions asked, documents sent, commitments confirmed in writing, providers appointed.
• Judgment: which conversations are genuinely progressing, which should be recorded as your read rather than as fact.
• Assumption: the timeline, the conversion, and the availability of investors you have not yet spoken to. Write them down on day one so you can check them on day ninety.
• The test at the end: how many day-one assumptions turned into evidence. A plan where most of them are still assumptions did not fail, it just has not started yet, and knowing that is worth more than the plan.

Where the plan changes

Five variables reshape the blocks rather than the structure.

• Limited partner type. Institutional and development finance processes run far longer than ninety days, so the plan's job with those investors is to start them, not to close them. Practitioner commentary published in June 2026 advises first-fund managers to begin development finance outreach twelve to eighteen months before a target close and notes diligence periods of six to twelve months for that category.
• Geography. Cross-border outreach needs its permissions settled inside the first block rather than the second.
• Whether you have an anchor. An anchor conversation reorders everything, because its diligence can consume the whole second and third block.
• Team size. A solo manager cannot run outreach and diligence in parallel at the same intensity, and the plan should say which one gives.
• Whether this is a first ninety days or a second. A second cycle should start from the diagnosis rather than repeating the first block.

What this plan does not promise

It does not promise a close, a commitment, or investor interest, and no plan can. What it produces is a decision made on evidence at a defined point rather than a raise that continues by drift.

Ninety days is a planning horizon rather than a claim about how long raising a fund takes. This page states no expected timeline, conversion rate, or number of meetings, because no verified source publishes them for venture fundraising.

This page is educational and general. It is not investment, legal, tax, or securities advice.