Pitch & Investor Readiness

What to include in a founder follow up email

A credible pitch helps people understand the opportunity and the evidence behind it. Clarity and thoughtful preparation matter more than dramatic claims. This guide explains a workable approach to what to include in a founder follow up email and the decisions to make before you act.

A practical approach

1. Define the outcome: explain what successful progress on what to include in a founder follow up email would look like in your business or programme.

2. Identify the participants and constraints: list the people, skills, data, time and resources required before choosing a tool or event format.

3. Choose one practical activity: create a short worksheet, conversation, checklist or experiment that advances the outcome without adding unnecessary complexity.

4. Capture evidence: decide which two or three indicators you can measure ethically and reliably, and record a starting point.

5. Review and improve: gather feedback, identify a bottleneck and document the next change you will test.

What to watch for

Be explicit about what is included, what remains optional and which details still need confirmation.

Prefer verifiable examples, practical templates and feedback over unsubstantiated success claims.

Start with a clear decision

Consider a founder preparing for a programme selection interview or first investor meeting. Before acting on what to include in a founder follow up email, write down the actual decision to be made. Is the aim to improve quality, reduce wasted effort, create a reliable opportunity pipeline or build a new capability? If several outcomes are mixed together, choose a primary one and state what is outside scope. This makes it easier to compare options rather than simply following the most visible trend.

A realistic situation to work through

Imagine a startup that has early customers but needs to explain its market, traction and funding use. The immediate temptation is to buy a tool, book a meeting or launch a campaign. Instead, sketch the steps as they happen today: who initiates the work, what information is needed, where it is recorded and what counts as a completed handoff. Write the points of uncertainty beside the flow. This exercise often reveals a smaller, testable improvement that can be made before spending more money.

Questions worth answering

Before allocating a budget, use three questions as a decision filter: What evidence can a reviewer verify independently? Which milestone will the next investment or programme unlock? What would make this opportunity a poor fit for both sides? Write the answers in plain language and ask a colleague or founder peer to challenge them. A useful answer identifies a specific audience, action or piece of evidence; a weak answer relies on broad promises such as “more visibility” or “better growth”.

Make the first version measurable

Choose a simple baseline and track number of qualified investor conversations, requested follow-up materials and gaps resolved in the data room. Record the measurement period and who owns the data so the numbers can be interpreted later. Keep the first experiment manageable: a small group, one process, or one defined event cycle. Compare outcomes with the starting point and note what you did not measure. The aim is to learn whether the method deserves expansion, not to manufacture a success story.

Avoid predictable mistakes

Common problems include ambiguous financial assumptions, unsupported market-size claims, unclear cap table information and sharing sensitive documents without a purpose. Build a lightweight checkpoint into the workflow: verify permissions and inputs, assign a responsible owner, review messages or materials before they go live, and agree on the next action when something goes wrong. These safeguards are particularly important when collaborating across organisations or handling founder data.

Turn the guidance into a working asset

To make what to include in a founder follow up email useful, produce something the business can reuse: a briefing document, qualification checklist, process map, communication template or measurement sheet. Keep it short enough that someone else could follow it without a long explanation. Prepare a concise one-page company overview, a current financial snapshot and a clear list of unanswered diligence questions. Save the first version, invite feedback from someone directly affected and revise it after a real-world test.

Review and decide what comes next

After the initial test, hold a short review. What changed? What remained difficult? Which assumption did the team get wrong? Compare the evidence with the original objective and decide whether to continue, revise or stop. When working with FIT, bring these questions into a coaching discussion or programme enquiry so the learning is connected to an actual business challenge rather than an abstract topic.

Turn this into action

Set aside a focused working session. Write down the outcome, name the person responsible for the next step and set a date to revisit what changed. Progress comes from using a useful method consistently, not from collecting another checklist.

At Founders in Tech, we focus on founder-first learning, practical systems and stronger execution. Explore our programmes or get in touch to discuss a suitable learning pathway.