What we believe about planning — and why it shapes how we work
The way we approach financial planning follows from a set of convictions about what makes organizations run well and what financial models are actually for.
← Back to HomeWhere this starts
Forethink was built around a straightforward observation: most financial planning processes are designed to produce a document, not to support decisions. The budget exists because someone needs to file it — not because it helps leadership think more clearly about where the organization is going.
That gap — between planning as compliance and planning as a genuine management tool — is where we operate. Everything we build is oriented toward making financial information useful, not just accurate.
What financial planning can actually be
We believe financial models should function as a shared language between finance and leadership — a way of expressing, testing, and refining assumptions about how the business works and where it's going.
When a budget is built collaboratively, with visible assumptions and multiple scenarios, it stops being a finance department output and becomes a tool for organizational thinking. Decisions get made in reference to the model rather than around it.
That's what we're aiming for with every engagement — not just a well-built spreadsheet, but a planning instrument that your leadership team actually uses.
over technically complete
over comprehensive but opaque
over historically accurate but stale
by leadership, not just finance
What we hold to be true about financial planning
Assumptions matter more than outputs
A budget is only as credible as the assumptions underneath it. If those assumptions aren't visible and documented, the numbers can't be questioned, updated, or trusted — which makes them decorative rather than functional.
Certainty in forecasting is a fiction
No model predicts the future. What a good model does is make explicit what you believe about the future, so when those beliefs turn out to be wrong, you can identify where and adjust. Acknowledging uncertainty is more useful than pretending precision.
Planning should reduce options, not just document them
The value of financial planning isn't the plan itself — it's the thinking process that produces it. When leadership genuinely works through the assumptions, they make better decisions in real time, regardless of whether the plan is followed precisely.
A model that no one understands is a liability
Complex models aren't inherently better. A model that only one person can interpret creates dependency — and risk. We build for legibility, so the people who need to act on the model can understand what it's telling them.
Variance is information, not failure
When actuals diverge from a forecast, that's data about where the model's assumptions didn't hold. Treating variance as a failure to be explained away misses the most valuable signal financial monitoring produces.
The handoff is part of the work
A financial model that depends on its creators to remain useful has a limited lifespan. We treat knowledge transfer — documentation, guided review, walkthroughs — as an essential deliverable, not an afterthought.
How these beliefs show up in the work
We document assumptions before building the model
Before any spreadsheet is opened, we work with your team to surface and agree on the key assumptions the model will rest on. This prevents the model from encoding disagreements that nobody noticed.
We build three scenarios as a baseline, not an extra
Every engagement includes optimistic, expected, and conservative paths. This isn't an add-on — it's the minimum that makes a model intellectually honest about the range of possible outcomes.
We write commentary with every update
Numbers without interpretation invite misreading. Each forecast update includes a written memo that explains what changed, what it means, and what leadership should watch going forward.
We review with the people who'll use it, not just the people who commissioned it
A budget reviewed only by the CFO before distribution is a budget most people don't understand. We involve the relevant leadership in the review so the model reflects shared understanding, not just shared sign-off.
Financial planning happens between people, not inside spreadsheets
A budget reflects the collective thinking of the people who built it. When that process is rushed, isolated, or poorly facilitated, the resulting model carries those flaws into every decision it informs.
We invest time at the start of every engagement understanding who uses the financial information, what decisions it needs to support, and where the current process creates friction. That context shapes everything about how we build.
Different organizations have genuinely different planning needs. A professional services firm forecasting utilization has different drivers than a manufacturer forecasting material costs. We don't impose a single framework — we adapt the methodology to the business.
Intake before model
We learn your business before we build anything. The model follows from understanding the business, not the other way around.
Facilitated, not just delivered
Planning sessions are structured conversations, not presentations. Input from leadership shapes the model; we don't just collect it for the record.
Adapted to your organization
We work with your existing tools, reporting cycles, and management structure rather than asking you to change how your business operates to fit our process.
We improve the process, not just the output
Financial planning methodology has evolved significantly over the past decade. Rolling forecasts, driver-based models, and real-time dashboard integration have changed what's possible — but not every organization needs every innovation.
We're deliberate about what we incorporate. If an additional layer of complexity serves your organization's specific planning needs, we'll use it. If it adds maintenance burden without meaningful insight, we won't recommend it. The standard for improvement is whether it makes the model more useful, not whether it's technically impressive.
Driver-based modeling
where your business actually runs on identifiable drivers
Continuous updating
when your operating environment changes faster than annual cycles
Dashboard formatting
where visual summary genuinely aids how leadership reads the information
Honest about what financial models can do
We won't tell you the model is certain
Every forecast rests on assumptions. We document those assumptions and build scenarios precisely because the future isn't fixed. We'll never present a single projection as the outcome — only as one of several realistic possibilities.
We'll tell you when a scope isn't right for you
If your organization would be better served by a different service than the one you're considering, we'll say so during intake. We'd rather match the engagement to what you actually need than complete a project that doesn't serve you well.
We document everything we deliver
Assumptions, methodology, model structure, and update guidance — all documented in writing. Transparency about how the model works isn't optional; it's what makes the deliverable actually trustworthy.
We build with you, not for you
Financial planning that's handed down from finance — or from consultants — tends not to stick. When leadership doesn't understand how the numbers were arrived at, they're less likely to use the model to guide real decisions. They comply with it, or they work around it.
Our process is deliberately collaborative. We run facilitated planning sessions specifically because we want leadership to shape the assumptions, not just receive them. That investment of time at the front produces a model that the team actually trusts — because they built it.
It also means that when something unexpected happens and the model needs to be revisited, leadership already understands the logic well enough to engage with that process productively, rather than waiting for someone else to update the spreadsheet.
Budget built, model established, team aligned on assumptions and methodology.
Variance history informs tighter assumptions. Forecasts become more grounded in observed patterns.
Institutional knowledge embedded in model. Leadership reads forecasts fluently and acts earlier on signals.
Compounding value as the model accumulates history and the team's planning fluency grows.
Planning value builds over time
The most valuable financial models are the ones that accumulate history. In year one, you're working with assumptions. By year three, you're working with assumptions calibrated against observed reality — which is a meaningfully different and more useful foundation.
We build with that trajectory in mind. The structure, documentation, and update methodology we put in place at the start are designed to make year two and year three more productive than year one — not just to deliver something useful now.
How our philosophy translates into your experience
You'll understand how the model works
Every engagement includes documentation and walkthrough time specifically so you're not dependent on us to interpret your own financial model.
You'll know exactly what the numbers assume
Assumptions are documented and reviewed with your team before they're built into the model. No hidden logic or embedded estimates that someone made up quietly.
You'll have more than one version of the future
Every model includes scenarios so your leadership can make decisions against a realistic range of outcomes rather than a single projected path.
You'll be told honestly what the model can and can't say
We won't present a forecast as a prediction. We'll be clear about the assumptions, the ranges, and where genuine uncertainty exists — because that's more useful than false precision.
If this approach fits how you think about planning, we'd like to talk
Share what you're working on and we'll respond with an honest assessment of how — and whether — we can help.
Get in Touch