All insights
    Fundraising & Investor CommunicationSeptember 7, 20267 minutes

    What to Prepare Before You Raise, So Every Investor Gets the Same Answer

    Raise preparation covers far more than communication, but one part founders can fix before the first call is making sure the questions that repeat throughout a raise have one current, agreed answer behind them.

    In short

    Before you raise, settle one thing a longer deck will not fix on its own: what you say when an investor asks how you define recurring revenue, or what your net margin actually covers, and whether that answer holds up the third time someone asks it as well as it did the first. Preparing for a raise covers far more ground than that, but this is the part founders can handle before the first call, and it is often the part left to whoever happens to be on the call that day.

    Key facts

    • This article covers one part of preparing for a raise: the reference layer of facts, definitions and explanations sitting underneath it, not financials, cap table or diligence documentation.
    • A shifting metric definition costs more trust than most founders expect, even when nobody meant to change it.
    • Investors rarely hear you only once: they revisit earlier answers, loop in a colleague, or check what they remember against what they read.
    • Staying consistent means keeping the same figure, definition, period and explanation underneath whatever wording a conversation calls for, not memorising identical, word-for-word answers.

    What "ready to raise" actually means in this article

    Getting ready to raise usually covers a lot of ground: financials in order, a cap table an investor can review without confusion, terms, whatever documentation a specific investor asks for during diligence, the review investors do before they commit. All of that matters, and none of it is what this piece is about.

    What this covers is narrower and, for many founders preparing to raise, easier to overlook: the reference layer sitting underneath the deck and the diligence room, the actual definitions, current figures and standard explanations everyone on the company side is working from whenever a question comes up. Get that layer right, and the deck, the data room and every answer in between end up drawing from the same source instead of being reconstructed separately each time. Miss it, and no amount of polish on the deck closes the gap.

    Consistency is not the same as scripting

    None of this means memorising a script or giving every investor the identical sentence. The wording can, and should, change with the conversation, a first introduction calls for a different level of detail than a third follow-up call with the same fund. What should not change is the figure underneath the answer, how that figure is defined, the period it covers, and the explanation the company has agreed to give when a number needs context.

    That distinction is worth making explicitly, because "be consistent" can sound like "sound rehearsed," and that makes the whole idea less appealing to actually do. The goal is closer to the opposite: the facts hold still so the conversation itself is free to stay natural.

    Where answer drift actually comes from

    Fundraising conversations do not happen in isolation. The same investor can hear an answer once, forward the deck internally, bring in a colleague three weeks later, and compare what that colleague hears against what they read the first time. A number can also simply get answered from memory twice, slightly differently each time, because a slide changed in between, or because whoever took the second call defined the metric a little differently than whoever took the first one.

    None of that reflects dishonesty so much as what naturally happens when the only record of an answer is whoever last gave it. A metric that changes definition between conversations can create avoidable doubt, even when the difference was entirely accidental, and that doubt is a cost a raise does not need to carry.

    What should be settled before the first call

    Four things are worth agreeing before a raise starts, not partway through it.

    • Definitions. What counts as a customer, what is included in gross margin, what "recurring" actually means for this business. The definition matters as much as the number itself, because changing the definition can make the same metric mean something different from one conversation to the next.
    • Dates and sources. Every figure needs a period it belongs to and, ideally, a note on where it came from, so nobody ends up defending a number that has since moved on without realising it.
    • Explanations. The two or three hardest questions, a slowing metric, a customer concentration, a competitor gaining ground, deserve a decided answer worked out in advance, rather than one improvised for the first time in front of an investor.
    • Ownership. Each figure needs someone specific responsible for it: who can update it, who approves a change to how it is defined, and which version counts as current when more than one exists.

    This sits underneath a deck or a diligence room rather than replacing either: it is the reference layer that the whole team, knowingly or not, is already pulling answers from.

    Keeping that record current while the raise is still running

    A raise can run for weeks, sometimes months, and the business does not pause for it. A growth figure moves, a competitive dynamic shifts, a new hire ends up fielding calls that someone else used to take. A reference layer that only ever gets set once, at the very start, goes quietly stale exactly while it matters most.

    The fix is a habit rather than a project: whoever owns a figure updates it when it changes, and whoever is taking a call checks the current version beforehand rather than relying on what they remember from the last one. A raise that closes eight weeks after it opened should not still be running on day-one numbers.

    Where MIRA fits once that reference layer exists

    Once those definitions, figures and explanations live in one place, the natural next step is letting investors reach them directly instead of routing every question back through you. MIRA is built as a source-grounded IR assistant: it draws its answers straight from that approved reference set, so what comes back is grounded in the record the company has already agreed on, rather than improvised again from memory. What that involves in full is explained here: What Is a Source-Grounded IR Assistant, and Why Now?

    The five-question prep check

    Write down the five questions you are most confident an investor will ask, and the exact answer to each one: the figure, its definition, and the date it is true as of. Hand that same list of questions, without your answers, to whoever else might field a call on your behalf, a co-founder or a CFO, and have them answer independently. Compare the two sets side by side.

    Any difference in the figure, the definition, the reporting period, or the underlying explanation is worth resolving before the process starts. A different choice of words is not what this test is looking for.

    The bottom line

    The aim is not to script every investor conversation. It is to remove avoidable variation from the facts underneath those conversations, so that whichever investor asks, and whenever they ask it, the figure, the definition and the explanation stay the same even as the conversation around them changes.

    Establish that reference layer before the first call, then keep it current as the raise progresses, and the rest of the process gets to be about the business itself, rather than about reconciling what was said earlier.

    Book a MIRA demo and let investors reach that same agreed answer directly, instead of waiting on you for it.

    About the author: Nataly Usuga is in Business Development at Finvictum, where she works daily with founders and IR teams on how their story gets found, or misunderstood, by AI before anyone ever talks to them. Connect on LinkedIn: https://www.linkedin.com/in/nataly-usuga-ramirez

    More insights