How Should Management Prepare For Diligence Questions That Challenge The Assumptions In Its Financial Model?

Management should prepare a sourceable assumption log, test base, downside, and stress scenarios, and assign an owner to each material input. This helps management answer diligence questions about growth, margin, retention, and capital deployment with documented support.

A financial model earns institutional confidence only when management can defend every material assumption with documented support, a clear methodology, and a prepared response to the most common stress-test questions diligence teams ask. The model itself is a starting point. The discipline behind every material assumption is what determines whether a raise moves through diligence on schedule.

Institutional diligence teams apply systematic pressure to financial models before any capital commitment moves forward. They check whether growth rates are grounded in operational evidence, whether margin assumptions hold under realistic cost conditions, whether churn figures match cohort data, and whether capital deployment logic connects to the projected return. When management walks into that first meeting without documented answers to those questions, the round stalls.

Most management teams build a model that works as a presentation tool. A model that survives a follow-up question requires documented assumptions, sourced methodology, and a prepared response for every material input.

This guide covers which assumptions get challenged most often, how to build a defensible assumption log, how to present sensitivity analysis, and why preparation before the first investor meeting protects the entire raise timeline. For context on the structural red flags diligence teams identify before they even reach the assumptions, see financial model red flags that institutional diligence catches in 15 minutes.

The Four Assumption Categories Diligence Teams Challenge First

Institutional diligence follows a predictable sequence. Teams prioritize the assumptions that drive the largest share of projected return. For most models, that means four categories get scrutinized before anything else.

Growth Assumptions

Diligence teams compare projected growth rates against historical compound annual growth rates. When forward projections exceed historical CAGR without a documented operational catalyst, reviewers treat the gap as a signal that the model was built to show a target return. The question management must answer is specific: what changed operationally that justifies a higher forward rate? Pipeline capacity, signed contracts, hiring timelines, and other documented operating evidence can help support a higher forward rate. 

Reviewers also check whether projected revenue growth relies on acquiring new customers, expanding existing accounts, or both. A model that depends heavily on upselling a concentrated customer base without documented expansion history carries concentration risk that diligence will surface.

Margin Assumptions

Gross margin assumptions face two lines of questioning. First, reviewers check whether all direct costs are properly classified in cost of goods sold. Reviewers may examine whether costs associated with delivery, customer support, and infrastructure have been classified consistently with the company's accounting framework and reporting methodology. When they are buried in operating expenses, gross margin reads higher than the business actually produces. Second, reviewers test whether margin improvement projections have an operational basis. A model showing material margin expansion over a three-year period requires a documented explanation: pricing increases, vendor renegotiations, or automation milestones. Without that documentation, the projection reads as an output target built backward from a desired return.

Churn and Retention Assumptions

Churn is one of the first places diligence teams look when the revenue model depends on recurring revenue. Reviewers validate gross churn and net revenue retention figures against cohort-level billing data. When a churn assumption diverges from the cohort data in the data room, the discrepancy raises questions about every other assumption in the model.

Gross churn figures must be traceable to customer-level revenue schedules with contract start dates, billing frequency, and cancellation records. An assumption that lives only in the model, unsupported by data in the data room, will be challenged.

Capital Deployment Logic

For raises where capital deployment is central to the return thesis, diligence teams verify that the deployment schedule in the model matches the operational timeline. A model that assumes full capital deployment in month three, when the operational plan requires 12 months of build-out, creates a cash flow mismatch that reviewers will identify. The deployment schedule must connect to the milestone plan, the hiring plan, and the capital stack structure.

Run a Diagnostic Before the First Investor Meeting

Management teams that go into diligence without a prior stress-test of their own model discover the weak assumptions in the room, at the highest possible cost.

The Capital Raise Pre-Flight is IRC Partners' fixed-fee diagnostic that scores a raise against the same twelve institutional gates a deal must clear before IRC Partners takes it into a strategic partnership.

The Pre-Flight surfaces assumption gaps, reconciliation failures, and sensitivity weaknesses before any LP sees the model. Management teams that complete it before outreach arrive at the first investor meeting with documented answers to the questions diligence will ask. Management teams that skip it discover the same gaps during diligence, when the cost of finding them is highest.

The preparation window is the raise's most valuable asset. A diligence team that finds an undocumented assumption in the first meeting will spend the rest of the process looking for more. A management team that presents documented assumptions with clear sourcing and methodology shifts the meeting from interrogation to evaluation.

For a broader diligence lens on how real estate decision makers evaluate capital and risk, see Urban Land Institute for industry context on institutional real estate standards.

How to Build a Defensible Assumption Log

An assumption log is a dedicated record of every material input in the financial model. Institutional reviewers prioritize the assumption log over the model's output figures, because the log reveals whether management understands the operational basis for its own projections. Every material input must carry its source, the date it was last reviewed, and the confidence level assigned to it.

A defensible assumption log has five components for each material assumption:

1. The assumption itself. State the specific input: growth rate, churn rate, gross margin percentage, deployment timeline.
2. The source. Identify where the figure came from: audited financials, signed contracts, market data, internal cohort analysis.
3. The date. Record when the source was last verified. A market data point from two years ago that has gone unrefreshed will draw a follow-up question.
4. The methodology. Explain how the figure was derived. A bottom-up build from sales rep capacity and pipeline data is more defensible than a top-down percentage of market.
5. The owner. Assign a person on the management team who can speak to the assumption in a meeting. An assumption without an owner becomes a liability when a follow-up question arrives.

What an Assumption Log Looks Like in Practice

A simple format works. A structured tab in the model spreadsheet, or a companion document in the data room, works. Maintaining discipline and ensuring every material entry is complete matters far more than the specific format. Every material assumption must appear, and every entry must be complete. For a parallel view of how operating metrics must be reconciled before they reach an institutional reviewer, see reconciling operating metrics for institutional investors.

Management teams that maintain a living assumption log, updated as market conditions or operational results change, arrive at diligence with a document that demonstrates ongoing rigor. Those that build the log after a diligence request has arrived are building it under pressure, and reviewers can tell the difference.

Every assumption in the log must be sourceable, dated, and explainable in a meeting. Build the log before outreach begins, and update it before every investor meeting.

How to Present Sensitivity Analysis That Holds Up Under Scrutiny

Sensitivity analysis is where management demonstrates that it has tested its own model before asking an investor to trust it. Institutional diligence teams reviewing a raise in the $5M to $250M range expect three scenarios: a base case, a downside case, and a stress case.

The downside case must reflect a meaningful shift in key assumptions. A downside case that reduces projected revenue by a marginal amount and leaves every other assumption unchanged reads as cosmetic. Diligence teams recognize cosmetic downside cases and treat them as a signal that the model was built to show a result, with stress-testing skipped.

Building a Stress Case That Earns Credibility

A credible stress case tests the two or three assumptions that drive the largest share of projected return. For each one, management should be able to answer a single question: at what level of deterioration does the model break?

• At what churn rate does the preferred return fail to be covered?
• At what gross margin compression does the cash runway shorten below the deployment timeline?
• At what growth rate slowdown does the capital efficiency ratio exceed the threshold for additional financing?

The answers to those questions, built into the model before diligence begins, demonstrate that management has done the same analysis the diligence team will do. That preparation shifts the conversation.

Sensitivity Tables as a Communication Tool

A sensitivity table that shows the output range across key variable combinations gives reviewers a structured view of the model's risk profile. The table should show at minimum: the base case output, a moderate adverse shift in the primary driver, and a severe adverse shift. For raises where a single variable dominates the return, a single-variable break-even analysis belongs in the data room.

Management teams that present sensitivity analysis proactively, before it is requested, signal preparation discipline. Those that produce it only after a diligence request signal that the work was done reactively. For guidance on how to structure risk presentation across scenarios in an investor deck, see how to present risk in an investment committee deck.

{{main-cta}}

Why Preparation Before the First Meeting Protects the Round

Diligence timelines for institutional raises in the $5M to $250M range run 4 to 9 months. Diligence teams allocate their attention based on what they find in the first meeting. A model that arrives with documented assumptions moves through review on schedule. A model that arrives with gaps becomes the subject of the review. A round where assumptions are documented and defensible from the first meeting moves through the diligence process on schedule.

The first meeting sets the tone for everything that follows. Diligence teams form an early judgment about management's preparation discipline. That judgment shapes how they interpret subsequent materials. A management team that answers the first follow-up question with a prepared, sourced response signals that the rest of the model will hold. A diligence team that receives sourced, dated answers in the first meeting shifts its focus from testing management's preparation to evaluating the deal itself.

Preparation discipline is visible from the first question. The goal is to walk into the first meeting with every material assumption sourced, dated, and assigned to a team member who can speak to it directly.

The practical steps before outreach begins:

• Complete the assumption log for every material input in the model.
• Run base, downside, and stress scenarios with meaningful shifts in key variables.
• Verify that every headline figure in the pitch deck reconciles to the model output tab.
• Confirm that every assumption in the model traces to a source that is in the data room.
• Assign an owner on the management team to each material assumption.

Institutional confidence follows from documentation built before the first question arrives.

Frequently Asked Questions

What is an assumption log and why do institutional diligence teams ask for it?

An assumption log is a structured record of every material input in a financial model. It lists the specific figure, the source it came from, the date the source was last verified, the methodology used to derive the figure, and the management team member responsible for defending it. Institutional diligence teams prioritize the log over the model's output numbers because the log reveals whether management built the model from operational evidence or from a return target working backward.

Which financial model assumptions get challenged most often in a $5M to $250M raise?

Growth rate assumptions, gross margin projections, churn and net revenue retention figures, and capital deployment schedules are the four categories diligence teams challenge first. Growth rates that exceed historical CAGR without a documented operational catalyst, margin improvements without a cost basis, churn figures that do not match cohort billing data, and deployment timelines that conflict with the operational plan are the specific patterns that draw follow-up questions.

How many scenarios should a financial model include?

Three scenarios are the baseline expectation for a $5M to $250M institutional raise: a base case, a downside case, and a stress case. The downside case must reflect a meaningful shift in key assumptions, with adverse movements in the primary value drivers that are operationally plausible. Diligence teams recognize that pattern and treat it as a signal that the model was built to show a result.

What does a diligence team do when a management team cannot source an assumption verbally?

When management defers a basic assumption question to a follow-up email, the diligence team treats that gap as a signal about the model as a whole. Reviewers begin looking more closely at adjacent assumptions, and the pace of the diligence process slows. The burden of proof for every subsequent assumption increases. Preparation before the first meeting prevents this pattern.

How should management handle a diligence question about a growth assumption that exceeds historical performance?

The answer requires a documented operational catalyst. Management should identify the specific change: a new sales channel, a signed contract with a major customer, a headcount expansion with a verified hiring timeline, or a product launch with pre-order data. The catalyst must be documented in the data room. A verbal explanation without supporting documentation will be followed by a request for the documentation, which delays the process and signals that the assumption was built after the fact.

What does a stress case test in a financial model diligence review?

A stress case tests a severe combination of adverse conditions simultaneously, targeting the two or three assumptions that drive the largest share of projected return. It answers a direct question: does the deal still return capital to investors if multiple drivers deteriorate at once? Building the stress case before diligence gives management an opportunity to identify weaknesses before reviewers raise them. 

How does capital deployment logic affect diligence on a financial model?

Capital deployment logic is the connection between the raise amount, the deployment schedule, and the projected return. Diligence teams verify whether the deployment schedule aligns with the operational milestone plan and the capital stack structure. When those three elements conflict, reviewers treat the mismatch as a modeling error that requires resolution before the process moves forward.

Continue reading this series:

• Common mistakes companies make in capital raising
• How to package project-level financials for LP committee review
• How Should a Company Sequence Readiness Work, Materials Preparation, Deal Structuring, and Diligence Before Launching an Institutional Raise?

The Capital Raise Pre-Flight is IRC Partners’ fixed-fee diagnostic that scores a raise against the same twelve institutional gates a deal must clear before IRC Partners takes it into a strategic partnership. It is where every engagement begins, whether you are pre-revenue building toward a first institutional round or scaling a company that has raised before. For deals that clear, the full strategic partnership follows. IRC Partners advises operators raising $5M to $250M of institutional capital. If you are taking a raise to market, start here.