How a custom financial model is developed for a client's project

Clients often ask: "How long will the model take?" and "What will you need from me?" In this article, I describe the entire process in detail — from the initial inquiry to delivery of the finished file. This will help you understand what happens at each stage, why we request certain information, and what determines the timeline.

Client inquiry

Everything starts with an inquiry. The client submits a request through the website, fills out a brief, or reaches out directly. At this stage, a general description is enough: what the project is about, what industry it's in, and why a model is needed.

Typical descriptions at this stage:

• "We're planning to launch a production facility and need to understand how much to invest and when it will break even."
• "We're looking for an investor and need a model for the project presentation."
• "We have an existing business and want to evaluate an expansion."
• "The bank requires a financial model for a loan application."

Even a brief description is enough to determine the project type, estimate the scope of work, and ask initial clarifying questions. A response with a preliminary cost and timeline estimate usually takes one business day.

Clarifying the model's purpose

Before starting development, it's essential to understand exactly what the model will be used for. The purpose determines the structure, depth, set of metrics, and presentation format.

A model for an owner's internal decision and a model for a bank's investment committee are entirely different documents. In the first case, flexibility and the ability to quickly change parameters matter most. In the second, compliance with specific standards, DSCR (debt service coverage ratio) calculations, quarterly or monthly granularity, and justification of every assumption are required.

At this stage, we define:

• Who will use the model — the owner, an investor, a bank, or a partner.
• What decisions will be made — whether to invest, which financing structure to choose, what cost structure to plan for.
• Planning horizon — 3, 5, 7, or 10 years, depending on the project type and recipient requirements.
• Level of detail — monthly for the first one to two years, quarterly or annual for subsequent periods.

Brief and data collection

After aligning on the purpose, we send the client a structured brief. It's not a ten-page questionnaire — it's a compact document with questions that genuinely affect the calculations.

What a typical brief includes:

• Product or service. What exactly is being sold, at what price, in what units.
• Capacity. How many units the business can produce or serve.
• Investments. Equipment, renovations, licenses, IT, initial inventory.
• Expenses. Rent, staff, raw materials, marketing, logistics, other.
• Financing. Equity, debt, investor capital — proportions and terms.
• Specifics. Seasonality, regulatory requirements, industry-specific factors.

The brief is not a formality. It is the foundation of the model. The more accurate and complete the brief, the fewer iterations will be needed, and the faster you'll receive the finished result. We help with the process: if data is missing for any item, we'll suggest where to find it or what range to use.

Sometimes clients cannot provide exact figures for every parameter. That's perfectly normal. In such cases, we use industry benchmarks and flag assumptions so they can be refined later.

Building the project logic

Based on the brief, we build the logical framework of the project: how the business works, where money comes from, where it goes, and what dependencies exist between parameters.

This stage is critical because it lays the "skeleton" of the model. For example:

• A restaurant's revenue depends on the number of seats, table turnover, average check, and occupancy rate by day of week.
• A manufacturing plant's revenue depends on line capacity, production yield, selling price, and warehouse capacity.
• A tech product's revenue depends on the sales funnel, conversion rates, average deal size, and churn rate.

The project logic determines which formulas will be used, how parameters are interconnected, and what happens when any one of them changes. Without this stage, the model becomes a collection of disconnected numbers.

Preparing the model structure

The structure is the architecture of the Excel file. We follow the principle of separating inputs, calculations, and output reports.

A typical structure includes:

1. Assumptions sheet. All input parameters are consolidated in one place. The client changes numbers here — everything else recalculates automatically.
2. Revenue calculation. Breakdown by products, channels, and months.
3. Operating expenses (OPEX). Fixed and variable costs linked to volumes.
4. Capital expenditures (CAPEX). Initial investments and capital expenditures by period.
5. Income statement (P&L). Revenue, cost of goods sold, gross profit, operating expenses, EBITDA, net income.
6. Cash flow statement. Operating, investing, and financing cash flows. Cash balance for each month.
7. Balance sheet. For projects that require full financial reporting.
8. Dashboard. Summary page with key metrics, charts, and scenario switching.

Every sheet follows consistent formatting: input cells are color-coded, formulas are protected from accidental edits, and navigation between sheets is intuitive.

Base case calculation

The base case is a realistic forecast based on the data from the brief. Not optimistic, not pessimistic — the one we consider most likely given the current inputs.

This is where the core computational work happens: formulas connect parameters, revenue is broken down by month accounting for ramp-up and seasonality, costs are linked to volumes, taxes are calculated according to the applicable tax regime, and cash flow is built with consideration for payment delays, advances, and the loan repayment schedule.

The base case delivers a complete set of financial statements and key metrics: payback period, NPV, IRR, breakeven point, and maximum financing requirement.

Adding scenarios and sensitivity analysis

After calculating the base case, we add pessimistic and optimistic scenarios. Parameters that vary:

• Sales volume — the primary revenue driver.
• Selling price — may decline due to competition or regulatory pressure.
• Time to reach target metrics — one of the most sensitive parameters.
• Cost of raw materials or procurement — affects margins.
• Interest rate on debt — for projects with debt financing.

Sensitivity analysis reveals which parameters have the greatest impact on results. This allows the client to focus on critical factors and avoid spending resources on items that have minimal impact on the outcome.

Scenario analysis is not three copies of the same table. It's a switching mechanism built into the model. The client selects a scenario on the dashboard — and all metrics, charts, and reports recalculate instantly. No manual data copying.

Model review

Before delivery, the model undergoes an internal review. This is not a formality — it's a critical stage that guards against errors.

What gets checked:

• Balance sheet integrity. Assets must equal liabilities plus equity. If the balance sheet doesn't balance, there's an error in the model.
• Formula logic. Every formula is checked for correctness: proper references, proper signs, proper calculation sequence.
• Stress test. What happens if revenue is set to zero? If expenses are doubled? If the interest rate is pushed to an extreme? The model must not produce errors or absurd values.
• Data integrity. All input cells reference the assumptions sheet rather than containing hardcoded values.
• Reasonableness of results. Final metrics are compared against industry benchmarks. If the model shows 80% profitability in a business where 15% is the norm, it's a reason to re-examine the inputs.

Delivery to the client

The finished model is delivered as an Excel file (.xlsx). Along with the file, the client receives:

• A brief structural overview. What's on each sheet, how to use the model, which cells can be changed.
• A list of assumptions. Which parameters were used, based on what data or benchmarks.
• Key findings. Main results: payback period, investment volume, financing requirements, critical thresholds.

If needed, we schedule a call to walk through the model together with the client: explaining the logic, showing how to change parameters, and how to interpret results.

Revisions and clarifications

After the model is delivered, questions and adjustment requests nearly always arise. This is a normal part of the process. Typical revisions:

• Refining input data — the client obtained more accurate figures for rent, pricing, or staffing.
• Adding a new product or line of business that wasn't in the original brief.
• Changing financing terms — a different rate, a different schedule, a different debt-to-equity ratio.
• Adapting the model to the requirements of a specific bank or investor.

After delivery, we provide advisory support for 6 to 12 months, including answers to questions and adjustments within the agreed scope. If the inputs change substantially (a shift in business model, recipient, or regulatory requirements), the additional work is scoped and quoted separately.

What the client receives at the end

The final deliverable is not just an Excel file — it's a working tool that includes:

1. A complete financial model with P&L, Cash Flow, and (where needed) Balance Sheet projections over a 3-to-10-year horizon.
2. A dashboard with key metrics: NPV, IRR, payback period, breakeven point, maximum cash shortfall.
3. Three scenarios — base, pessimistic, and optimistic — with one-click switching.
4. Sensitivity analysis on key parameters.
5. An assumptions sheet where all input parameters are gathered for independent adjustment.
6. Charts and visualizations — revenue, profit, cash flow, and cumulative cash flow dynamics.

The file is delivered without protection: all formulas are open, all cells are accessible. The client can independently make changes, adapt the model, or hand it off to their CFO for further work.

Why timelines depend on project complexity

Timelines are determined individually for each project and fixed in the proposal. The difference between projects is driven by objective factors:

• Number of products or business lines. A model for a single product and a model for a business with ten product categories involve very different volumes of calculation.
• Complexity of the financing structure. Equity alone is one module. A combination of a loan, leasing, and an investor with a convertible note means three modules, each with its own logic.
• Recipient requirements. A model for internal use is simpler than one for project finance at a bank, which requires DSCR, LLCR, and a detailed balance sheet.
• Completeness of input data. If the brief is fully completed and the data is reliable, development moves faster. If market research and benchmark selection are needed, it takes longer.
• Number of iterations. Sometimes during development, the project concept changes, new data emerges, or objectives shift. Each iteration adds time.

We always provide an estimated timeline during the proposal stage and flag anything that might affect the deadline. Speed matters, but not at the expense of quality: a model with an error is worse than a model that arrives a day later.

Specific timelines depend on project scale, the number of modules in the model, and the completeness of the data provided. Exact timelines are fixed in the proposal after task analysis. Rush orders are discussed on a case-by-case basis.