Client Forecasting Packs

This use case shows how an accounting firm or advisor can turn Model Reef into a forecasting product that can be delivered reliably across many clients.

Instead of building a bespoke spreadsheet for every engagement, you will:

  • Create one or more standard forecasting templates.

  • Attach each client to the relevant template via imports or live ledger connections.

  • Produce a repeatable forecasting pack that you can update each period.

When to use this pattern

Use this pattern when:

  • Clients ask for ongoing forecasting support, not just one off models.

  • You want a consistent structure that team members can work with across clients.

  • You need to scale advisory services without scaling spreadsheet risk.

This pattern works for small businesses, scale ups and more complex entities, as long as they can fit into a common structural template with some customisation.

Architecture overview

The pattern has three layers:

  • Template models

    • One or more pre built 3 statement models designed for common client types (for example SaaS, retail, simple services).

    • Contain branches, variables, drivers and reporting layouts.

  • Client specific models

    • Copies of templates that are connected to client data via PDF, Excel, Xero or QuickBooks imports.

    • Contain actuals plus client specific drivers and assumptions.

  • Forecasting packs

    • Dashboards and reports exported from client models for monthly or quarterly review.

1

Design your firm level forecasting templates

Start by building one or more template models that reflect common client archetypes, for example:

  • Template - Simple Service Business

  • Template - Product and Services Mix

  • Template - SaaS

  • Template - Retail Multi Site

Each template should include:

  • A clean branch structure (for example Group plus one or more divisions).

  • Variable sets for revenue, COGS, Opex, staff, tax, assets and liabilities.

  • A central assumption library for inflation, FX, tax and global drivers.

  • Core outputs: P&L, Balance Sheet, Cashflow, Cash Waterfall and a small set of dashboards.

Aim for templates that cover 80 percent of typical client needs, with the remaining 20 percent handled by client specific tailoring.

2

Onboard a client by cloning the appropriate template

For each new client:

  • Pick the closest matching template.

  • Clone it to create a client specific model, for example:

    • Client - ABC Plumbing - Forecast Model

  • Set the model currency and fiscal year settings to match the client.

You now have a starting point that already contains full 3 statement logic and reporting.

3

Bring in client history via ledger or PDF/Excel

Populate the client model with real historical data using:

  • Xero or QuickBooks integration where the client uses those systems.

  • PDF or Excel import where management accounts are available as files.

  • CSV import for specific drivers or operational metrics.

During import:

  • Map the client Chart of Accounts into your firm level categories.

  • Check that historical P&L and Balance Sheet match client reports.

Once this is done, the template becomes a client specific model with the right history.

4

Configure client specific drivers and assumptions

Next, adjust the template assumptions to reflect the client reality:

  • Revenue:

    • Define units, prices and growth paths per branch or product.

  • COGS and Opex:

    • Link cost drivers to revenue where appropriate.

    • Use central assumption library entries for inflation or general escalation.

  • Staff:

    • Input current headcount and planned hiring.

  • Capex and funding:

    • Model any planned asset purchases, debt or equity events.

Keep these drivers as simple as possible while still reflecting the main economics of the client business.

5

Build the client forecasting pack outputs

Within the client model, build or reuse a forecasting pack layout, for example:

  • An executive dashboard showing revenue, EBITDA, cash and runway.

  • A summary P&L and Cash Waterfall.

  • A simple valuation summary if appropriate for the engagement.

  • Scenario views where relevant (for example Base and Downside models derived from the client model).

These outputs will be exported or presented directly to the client.

For more detail on reporting outputs, see:

  • Build an Executive Dashboard

  • Build a Board Reporting Pack

6

Establish an update cadence

Turn the client model into an ongoing service by:

  • Agreeing a review frequency, for example monthly or quarterly.

  • At each cycle:

    • Refresh actuals from Xero/QuickBooks or updated files.

    • Update key assumptions if new information has emerged.

    • Regenerate dashboards, reports and any bundled valuations.

  • Present the updated forecasting pack in a meeting or written update.

This process lets you maintain a living forecast without rebuilding the model.

7

Standardise across clients

To scale this offering across many clients:

  • Use consistent naming and structure across template models.

  • Maintain a firm level assumption playbook that can be quickly customised per client.

  • Build standard checklists for onboarding, update and review.

You can also use your GitBook documentation as an internal manual for staff delivering forecasting packs.

Check your work

  • Templates are clean, documented and easy to adapt.

  • Client models reconcile to their source accounts for historical periods.

  • Forecasts are driven by simple but realistic assumptions.

  • Packs present the same core metrics across clients, with room for client specific detail.

Troubleshooting

chevron-rightTemplates become overcomplicatedhashtag

Periodically refactor templates to keep them lean. Move unusual features into client specific layers rather than bloating the shared template.

chevron-rightClients provide data in inconsistent formatshashtag

Use the PDF and Excel import tools, along with clear internal procedures, to normalise data as it enters Model Reef.

chevron-rightToo many client variants are hard to managehashtag

Focus on a small number of robust templates and standardise around them, even if this means some clients fit less perfectly.

Last updated