Investor meetings
What Does It Mean When a VC Says Send More Information?
Interpret the signal through the next action.
August 18, 2026
Read online
Open Note: “Send more information” is not a commitment and not automatically a rejection. Treat it as an incomplete decision signal until you know what the investor is trying to evaluate, who will review it, and what happens next.
Short answer: The phrase usually means the investor is not ready to decide from the current conversation. It may be a genuine request for evidence, a way to keep the conversation open, or a polite pause. Ask which question the material should answer, send the smallest useful package, and agree on a next step. If the request stays vague, keep the round moving and do not let one investor set the company’s calendar.
What the question is really asking
Founders often hear “send more information” as either a hidden yes or a soft no. Neither interpretation is reliable on its own. The practical question is whether the request is specific enough to justify another action and whether the requested material maps to an actual investment decision.
Do not respond by sending every document you have. Ask which question the investor is trying to answer: customer demand, retention, market size, ownership, technical risk, regulatory exposure, or the use of funds. A focused answer is easier to review and easier to learn from.
Clarify the request
Before sending, ask three short questions: What would you like to understand better? Is there a particular metric, customer segment, or document you want to review? Who else will be involved in the next decision? You do not need to interrogate the investor. A single clarifying reply can turn a vague request into a useful process checkpoint.
If the investor cannot name a question, do not assume bad intent. They may be busy, early in their process, or unsure what matters. Send a concise summary and invite them to point you toward the relevant gap. The lack of specificity is itself a reason to limit the time you spend preparing.
Send the smallest useful package
Match the material to the question. A cohort table may answer a retention question; a customer reference may answer a demand question; a cap-table summary may answer ownership; a product walkthrough may answer workflow or technical risk. Explain the definition, date range, and limitation of every important number.
Do not bury the answer in a large attachment. Put the conclusion near the top, link to supporting detail, and label anything illustrative or preliminary. If the file includes sensitive information, share only what is necessary and confirm that the recipient is the right person to receive it.
Connect the evidence to the decision
Evidence is useful only when it changes what the investor can decide. If you send a metric, explain what it implies for the next milestone. If you send a customer list, explain the pattern the investor should notice. If you send a market analysis, distinguish sourced facts from your assumptions.
Be honest about what the material does not prove. One strong customer does not establish repeatability. A large market does not establish distribution. A positive product demo does not establish willingness to pay. Precision makes the next conversation more productive.
Define the next step
Close the email with a low-friction process question: “Would it be useful to review this together for 20 minutes next week?” or “If this answers the question, should we schedule the partner conversation you mentioned?” Give the investor a clear way to say that the material does not change the decision.
Record what you sent, when you sent it, the question it addressed, and the next action. If the investor said they would review it with a partner, agree on when it makes sense to reconnect. If there is no next step, keep the target in an uncertain or paused category rather than treating the request as progress.
Interpret the follow-through
The request becomes more meaningful when the investor engages with the material. Specific follow-up questions, a partner introduction, a diligence list, or a proposed meeting show movement. Silence after a well-targeted package is ambiguous; send one useful follow-up, then redirect effort to other conversations.
A request that expands indefinitely can also be a signal. If each answer creates a new broad request without a clearer process, ask what decision the investor is working toward. The company should not build a bespoke diligence project for someone who cannot explain the next gate.
Illustrative example
Imagine a seed investor asks a B2B software founder to “send more information.” The founder replies with a one-page update: $42,000 in monthly recurring revenue, 93% gross retention for the last six months, the definitions behind both figures, and a short note on the next milestone. The founder asks whether the investor wants a cohort review or a partner conversation. If the investor chooses the cohort review and schedules time, the request had a real decision path. These figures are illustrative only.
Founder decision
Turn vague requests into explicit questions, send the smallest useful evidence package, and set a stopping point. Use the Investor Outreach Toolkit to track what each investor asked for, what you sent, and whether the next action is specific.
When not to follow this advice
Do not send confidential material to an unverified recipient, disclose more than the decision requires, or let an investor’s open-ended request displace customer work. If the company needs more proof before raising, pause and build that proof. The right response to “send more information” may be to wait until there is information worth sending.
Continue with How Do I Know If a VC Is Interested? and How Do I Follow Up With an Investor Who Has Not Replied?.
Disclosure: This is general educational information for founders, not legal, tax, accounting, investment, or financial advice. Illustrative numbers are examples only.
Want a clearer answer for your company?
Diligence + Fundraising OS
Run the whole raise, from first preparation through diligence, as one process.
Originally published in The Raise Memo.
