CFO's Budget Season Playbook: Christian Wattig's Top Frameworks
Speakers

Christian Wattig, Founder, Inside FP&A

Kirk Kappelhoff, Senior Director of Strategic Finance, Drivetrain
It’s the first week of budget season, the kickoff email has gone out, the templates are sitting in everyone's inbox, and the deadline is a comfortable four weeks away. Plenty of time, right?
Well, you would think so. Then the submissions arrive (on the day of the deadline, naturally), and the bottom-up total lands nowhere near the number leadership has in mind. As a result, you are the one who has to go back to every department head and ask them to do more with less, and you have about a week to do it.
If this sounds familiar, you're in good company. Christian Wattig has run eleven annual planning cycles at companies like P&G, Unilever, and Squarespace, and the top-down and the bottom-up never matched. Not once. But Christian doesn't see that as a problem. In his view, the mismatch is what starts the conversation about what's realistic. Finance's job is to reconcile the two numbers, ideally without going back to department heads every time they disagree.
In the webinar below, Christian shares his budget season playbook with Kirk Kappelhoff, Drivetrain’s Director of Strategic Finance.
No time to read? This article covers it all, with the live Q&A and full webinar transcript at the end.
Here, we explain what top-down and bottom-up budgeting are and why the two numbers almost always diverge. We'll also show you how to build each one so they can be compared, and how to challenge a department's numbers without creating friction.
59:07What is top-down vs. bottom-up budgeting?
A top-down budget starts with the end result in mind. It is expectation-setting, and it usually comes from senior leaders or from finance. However, Christian's rule is that it still has to tie back to real business drivers, such as headcount, advertising spend, product development, or market expansion. "We should grow eight percent" is not a top-down budget. It is a wish.
In contrast, a bottom-up budget starts from scratch. Each department builds it up from the initiatives and campaigns it actually plans to run next year, along with what those will cost and what they are expected to return.
Each side also comes with a predictable bias:
Bottom-ups tend to be conservative (people want to under-promise so they can over-deliver), while top-downs tend to be aggressive since they come from leadership and are a bit removed from the day-to-day.
Both sides have to build their own version for the comparison to mean anything. If finance builds the whole plan alone, the assumptions are too thin to be useful when you are trying to explain variances later in the year. On the other hand, if departments simply send in numbers and finance adds them up, finance is not adding the value it should. Neither one is a budget on its own, but together, they are the start of one.
What does the gap between top-down and bottom-up tell you?
For example, imagine leadership's top-down calls for $12 million in new ARR next year, and the sales team's bottom-up comes in at $9 million. Neither number is wrong. Sales built theirs from the reps they have and the ramp times they have seen, while leadership built theirs from the growth the board expects and the market they believe is there.
Now, you could split the difference and call it $10.5 million. But nobody built that number. So there’s no plan behind it: no hiring target, no ramp assumption, and nothing to measure against as the year goes on. If you fall short, you can't tell whether it was due to a problem with execution or an unrealistic target, because nobody said what the extra $1.5 million depended on.
The better move is to put leadership's number in the same terms sales used. What does $12 million assume about headcount, hiring dates, and ramp time? Set that beside sales' plan, and the $3 million gap becomes a question of sales capacity: something like eight more reps, starting by March. That's a question sales can answer.
Christian's method applies the same logic to every department. He builds the top-down from a handful of tactic-level drivers, chosen with the business teams, so that each gap turns into a question about specific assumptions rather than a total.
How do you build a driver-based, top-down budget?
Christian is a big fan of driver-based top-down planning. Instead of starting from a growth rate, you model what the business is going to do differently next year and what results those changes should yield, so that the conversation with a department is about the drivers rather than the total.
For example, at a subscription company, he modeled unaided awareness, direct-response spend, inflation, and promo strategy across three scenarios: balanced, aggressive, and conservative. That let him show the board exactly where the plan was taking risk, and it made the same model useful all year long, because you can pull it out monthly or quarterly and adjust it for reforecasts.
It's worth noting that a driver-based top-down has its drawbacks, too. It requires a real understanding of the business, it can be time-intensive, and more drivers mean more compounding uncertainty. This is why Christian follows these best practices when developing the driver list:
- Drivers live at the tactics level: "Marketing" and "sales" are line items. Unaided awareness, direct-response spend, and promo strategy are drivers.
- Five to ten of them, not a hundred: Apply the 80/20 rule. A handful of drivers explain most of the result, and every extra one adds uncertainty.
- Finance can't pick them alone: It takes real collaboration with the business teams, because they're the ones who know which tactics actually move the number.
- Every assumption has to be measurable, yours or a department's: If you can't tell afterward whether it held, you can't explain the variance.
How do staggered budget deadlines work?
The first of the three budget-season challenges Christian described is late inputs. You set one deadline four weeks before the board meeting, thinking that is plenty of time. Then, departments wait until the day itself and submit something that is not where it needs to be, in depth or in the numbers, and now you are scrambling with no time left.
The fix is a staggered timeline with multiple deadlines. For example, kicking off in early November, a first-pass deadline [at the] end of November, a second pass mid-December, and a final lock in mid-January.
The early deadlines assume the first pass won't be what you need. People go back and improve it for the second pass, and finance gets more time to analyze the submissions and run scenarios. But there is a catch. This only works if senior leadership (ideally the CEO or your SVPs) has bought in, because the first-pass deadline only gets respected when there is an actual business review afterward that sends things back for changes.
Through the whole stretch, finance acts as the project manager, following up, reiterating deadlines, and explaining the reasoning behind them. Simply put, if nobody is chasing, nobody is submitting early.
Why should you ask for budget inputs as a range?
Here is the part of the webinar that got the most nods. The bottom-up almost never matches leadership's expectations on the first pass, which means finance ends up sending people back to do more with less, sometimes more than once. Christian's fix is in how the inputs are collected in the first place: ask each department for a range rather than a single number, starting with the very first submission.
That way you don't have to keep going back to department owners every time there's a gap. You can just use the more aggressive end of their own range, and the width of that range also tells you something about their level of uncertainty.
In other words, you get a second number from every department without a second meeting, and the width of each range tells you how confident each team is in its own plan. A department that submits $800K to $850K knows its business. Likewise, a department that submits $600K to $1.2 million is telling you something, too.
How do you challenge a department head's number without friction?
An anonymous audience question got the most practical answer of the session: how do you challenge a department head's assumptions without causing friction? After all, you are usually more junior than the person across the table, and they know their business better than you do. Christian's answer is to do your homework before you walk in.
The best way is to do your homework first — build your own top-down estimate, even a rough back-of-envelope one, before the conversation. Then go in and say, 'here's my own projection and my assumptions, walk me through where yours differ' — completely different tone than opening with 'your number looks low, we need it higher.'
Coming in with your own assumptions turns the meeting from a negotiation over a total into a comparison of two views, driver by driver. It is also usually how you find a way to genuinely help the department rather than simply push on its number. For a department that does not want to engage at all, Christian's line is that a high-ROI idea gets funded through this process, and that what a team is allowed to spend can flex with business realities even though the budget commitment itself does not change.
How does the full reconciliation run, start to finish?
Let's walk through the full reconciliation, start to finish:
- Build the top-down first. Five to ten tactic-level drivers, with balanced, aggressive, and conservative cases.
- Collect the bottom-up as ranges by the first-pass deadline.
- Compare driver by driver. Start from your assumptions and ask where theirs differ.
- Consolidate with version control. Know who submitted which version, when, and whether the department head actually signed it off.
- Use the aggressive end of their range where the total falls short, before you ask for anything new. Only go back for a real change.
- Review, send back, and repeat through the second pass. Lock in mid-January.
Once the plan locks, the number becomes a commitment to your stakeholders about what the company will achieve and how it plans to get there, which is why Christian says it shouldn't change six months in. That's the core difference between a budget and a forecast: the budget holds, and the forecast updates the picture as the year unfolds.
Get the bottom-up from the team, challenge it with your top-down, and go through the iteration. It can be painful having multiple rounds where the bottom-up is far from your top-down, but that pain is exactly where the value and the real understanding comes from.
How to use ChatGPT to prepare for a budget conversation
Christian also showed how he uses ChatGPT to prepare for budget conversations. He follows a prompting structure borrowed from Greg Brockman, OpenAI's president, which has four parts: the goal, the return format, warnings about what the model should check, and a context dump. He demonstrated it live, playing a finance manager preparing to discuss a CMO's bottom-up submission. His prompt covered each part:
- Goal: Talk to the CMO about their bottom-up submission and get their thoughts on improving marketing ROI.
- Return format: Define a specific structure for the output.
- Warnings: Make sure each question can be used to run financial analysis and lead to a concrete recommendation.
- Context: "I'm more junior than the CMO, I want this to feel collaborative rather than imposing, and I don't want to seem like I'm posturing for our CFO."
The output was five questions. The first asked which marketing programs had punched above their weight over the last twelve months, which Christian liked because it lets the CMO start with wins. The next asked about the CMO's biggest bets and the assumptions behind them, and along the way, the model suggested asking for customer lifetime value data.
Christian calls brainstorming one of his favorite uses for AI in budgeting, because it doesn't matter if the model makes something up when you're not relying on it for facts. For facts, a search engine is usually the better tool.
Leverage technology to take the pain out of consolidation
Of all the steps in the reconciliation, consolidation is the one a tool improves most directly. In the webinar poll, 90% of attendees were still running the process in Excel or Google Sheets. If files from ten departments take more than a day to roll up into company revenue and profit, there are already new updates by the time you finish. And as Christian pointed out, it isn't only about time. You're also never quite sure the formulas are right or that you used the right version.
Kirk's demo showed how Drivetrain handles it. Each department head works from one template that shows only their own actuals, forecast, headcount, and attrition, so finance isn't "rebuilding the same report thirty times for thirty teams." Comments live in the budget itself and ping the owner in Slack, Teams, or email. And when it's time to investigate a variance between budget, actuals, and the reforecast, Drivetrain's AI drafts the commentary for you, with live references to the underlying metrics so the text updates as the numbers do.
Christian's reaction went straight to the send-back rounds and the flood of "this number needs to change" emails. You could comment in Google Sheets, too, he said, "but you'd still have the version-control problem, whereas everything stays organized in Drivetrain."
The budgeting use case shows the collaborative flow end to end, from collecting ranges to locking the plan. If you're a SaaS company building the top-down side, our top-down revenue modeling template is a good place to start. And if you'd like to see how your own budget season could run with a lot less scrambling, contact us today to book your demo.
About Christian Wattig
Christian Wattig has spent more than 14 years in FP&A, including eleven at Procter & Gamble and Unilever leading FP&A and accounting teams. He has an MBA from NYU Stern and was an FP&A leader at Squarespace through its IPO. He's the founder of Inside FP&A, a corporate training firm that has trained teams at Google, Merck, Lowe's, and Discover, and he directs the Wharton School's FP&A Certificate Program, which he created. He writes a weekly newsletter.
Summary
Top-down vs. bottom-up budgeting works like this: the top-down is the target that leadership or finance sets, tied to a handful of business drivers, while the bottom-up is the target from the combined budgets that each department builds from its own initiatives. You build both types of budgets separately, and you should expect them to disagree.
Christian's method for resolving the differences has three parts:
- A top-down built on 5–10 drivers, not a hundred: Each driver is a specific tactic, such as promo strategy or direct-response spend, so the conversation with a department is about assumptions rather than a total.
- A staggered calendar, not a single deadline: An early first pass, a business review that sends weak submissions back, and a second pass before the lock in mid-January, so you're not fixing everything the week of the board meeting.
- Bottom-up inputs collected as ranges, not single numbers: When a department's number falls short of the target, you can often use the more aggressive end of its own range instead of sending it back to redo the plan. The width of the range also shows how sure each team is about its numbers.
Note that this page covers the reconciliation process, which is one stretch of a longer budget season timeline that starts well before kickoff, with a review of last year's process, a planning roadmap, and a RACI.
Questions from the webinar
How do you build a living budget instead of a one-and-done exercise?
Reforecast at least monthly or quarterly, and tie each reforecast back to the original budget rather than running it separately. Once a year plus a mid-year update is not enough. Tying back is much easier when the budget was built at the driver level, and a driver-level budget is exactly the comparator you need for variance analysis.
How do you communicate the value of budgeting to leadership in a non-finance-driven organization?
Ask what they worry about, then run the process to answer it. For example, a fast-growing company cares whether the growth is sustainable, whereas a nonprofit may care most about what happens if funding falls through, so the budget becomes that scenario plan.
Which non-monetary goals belong in the annual plan?
Start from each team's strategy and tactics, then work back to the metric that tracks them. For example, if product quality is a goal, something like consumer hotline call volume works as a leading indicator. A spike there can point to a quality issue that will eventually hit sales, and in a subscription business, it shows up as churn.
Why does ChatGPT give a different answer each time?
For brainstorming, that is actually useful, so regenerate to get more options. For a fact, like the population of Paris, use a search engine.
How does the annual budget fit a five-plus-year strategic plan?
The strategic plan sets the guardrails and the starting expectations, and the annual budget is informed by it rather than reconciled to it line by line.
Speaker spotlight

Christian Wattig
Founder, Inside FP&A
Christian Wattig is an FP&A expert with 14+ years of experience in MNCs (P&G, Unilever) and high-growth tech startups (Squarespace). After earning his MBA from NYU Stern, he helped take Squarespace public. Now an entrepreneur, Christian directs the FP&A certificate program at Wharton and runs his firm, FP&A Prep, offering corporate training, online programs, and sharing insights through LinkedIn, newsletters, and his 'FP&A Tuesday' series.

Kirk Kappelhoff
Senior Director of Strategic Finance, Drivetrain
Kirk Kappelhoff is a financial modeling expert with a BBA in Finance & Accounting and nearly a decade of experience at Deloitte, EY, and KPMG, where he built models for pre-IPO companies, M&A transactions, and strategic planning initiatives. At KPMG, he led the Business Modeling Services team, specializing in equity stories and financial forecasts that help high-growth companies communicate their value to investors. At Drivetrain, Kirk writes about strategic planning, granular reporting, and modern FP&A best practices for rapidly scaling finance teams.
- 00:24
Kirk Kappelhoff
Oh, very nice. Okay. Very good. Well, you should be right next door to me somewhere there. If I look out my window, I'm sure I'll see you somewhere. We're excited to have you here, obviously, to talk about the CFO playbook with Christian Wattig. You need no introduction, but, of course, I'm gonna give you one nevertheless. I'm the director of strategic finance here at Drivetrain. If you're interested in learning more about us, we can talk more about that at the end. Christian, however, is who I have the privilege of interviewing today. And, honestly, I don't know how much interviewing will be needed because he is gonna be doing most of the presenting. But in short, Christian's an FP&A expert with fourteen years of experience with multinational corporations like P&G, Unilever, and high growth tech startups like Squarespace. After earning his MBA from NYU Stern, he helped take Squarespace public. Now he's an entrepreneur, and he directs the FP&A certificate program at Wharton School of Business and, of course, runs his own firm insidefpna.com. He offers corporate training there, online programs, and now with us, he's sharing his insights through LinkedIn newsletters and his FP&A Tuesday series. Christian, thank you so much for joining us today.
- 01:29
Christian Wattig
Thank you so much, Kirk. I'm excited to be here. It's going to be a privilege of ours.
- 01:35
Kirk Kappelhoff
Budget season's around the corner, of course, that's what we're talking about. This is what we plan to go through at a high level today: we're gonna go up through Christian's five phases of budgeting with those best practices, tackling common hurdles from cross-functional and AI collaboration. And just a general note, always reach out to us — Christian is obviously a thought leader in this space, and Drivetrain isn't just an FP&A tool, we've got thought leadership through our blogs and our diverse range of teams touching pretty much every area of FP&A and strategic finance. So please, at any point, reach out. Let's start off as we always do with a poll. Question one: what's your biggest pain point during budget season — getting timely inputs from other teams, too many manual updates, lack of clarity around assumptions, or consolidation? Question two: what tool do you use to manage your budget process — Excel or Sheets, a dedicated FP&A tool, or others? Growing up I was always an Excel guy, but Google Sheets seems to be taking the helm mainly for collaboration purposes. Looks like about a ninety percent response rate on that one — all of the above at thirty-six percent for the main issues. Any thoughts here?
- 03:00
Christian Wattig
From what I see, for question one, "all of the above" takes about a third of the answers — seems like everything is just too much of a hassle. Another third put too many manual updates and version control issues, and the last third is getting timely inputs from other team members. I love it.
- 03:24
Kirk Kappelhoff
Tools do you use? Oh, sorry, go ahead.
- 03:27
Christian Wattig
No, I see it now — I love that response, because that's exactly what we'll touch on today, especially getting timely inputs and how to speed up the process.
- 03:40
Kirk Kappelhoff
Beautiful — looks like only ten percent are using a dedicated FP&A tool, so we can touch on that toward the end too. As a segue into your content, Christian, quick question: I hear budgeting sometimes gets a bad rap. What are your thoughts on that in general?
- 04:03
Christian Wattig
I like that we're starting with the elephant in the room — budgeting isn't everyone's favorite process. PwC actually ran a recent survey on this. Let me share my screen. The most common responses: it takes too much time, it doesn't help me run the business, it's out of date before it's even finished, too many iterations, too many people involved, cast in stone, includes allocations I can't control, gameplaying, and by the time it's done I don't even recognize my own numbers. Those objections come from one of two reasons: either people misunderstand what budgeting is about in the first place, or the process simply isn't run effectively. Hopefully you'll leave today with ideas on how to improve that effectiveness. Looking closer, there are advantages and disadvantages to annual planning. On the advantage side: financial control and delegation — giving people a budget lets you empower them to make decisions within guardrails, rather than approving every small expense individually. It helps with coordination — say the head of product wants to launch something, but marketing doesn't have the resources to support it; the annual process is where you catch that. It's also good for performance evaluation, target setting, resource allocation, managing expectations, and strategic reassessment. On disadvantages: it can be time-consuming, but that concern usually ties back to not getting enough value out of the process — if you're getting real value, you're fine investing the time. There's the outdated-assumptions complaint, but that comes back to the actual purpose of a budget: a budget is not a forecast. It's a commitment to stakeholders about what the company is trying to achieve financially and how it plans to get there — strategies, tactics, investments. That's why it shouldn't change six months in; that's what forecasts are for. Then there's short-term focus and potential for misuse. It's important to be clear that a budget isn't meant to be restrictive — you still need to look for new opportunities worth pursuing even if they exceed budget, and finance needs a process (financial modeling) to evaluate those. You need flexibility in how you spend without changing the actual budget commitment itself.
- 09:13
Kirk Kappelhoff
That's super helpful, Christian. I know you've led many annual planning processes — what are some common themes or best practices you've seen?
- 09:30
Christian Wattig
Before themes and best practices, I want to address a common misconception first. There's a quote — "plans are nothing, but planning is everything," credited to Eisenhower. Your annual plan shouldn't just be about the documents you produce, the projected P&L, balance sheet, and cash flow — those get outdated, nobody has a crystal ball for ten to twelve months out. The real benefit comes from the planning process itself: getting busy leaders to step out of day-to-day firefighting and have a real conversation about whether strategies are still working, how they translate to tactics, and how you'll measure success. Your budget needs to be much more than financial projections, and you can only get there by collaborating with the team. Oh, I love it, Sarah — I see the question in chat: what's the difference between an AOP and a budget? That's exactly what I wanted to cover next. Companies often use the terms interchangeably, but they're different things. AOP stands for Annual Operating Plan. A budget in the traditional sense is just the financial projection — what the company plans to achieve. An AOP is the how: what does the sales headcount look like, what tactics is marketing using, what is product launching, and how does it all link together. So you're not just doing a budget, you're doing an annual operating plan, and finance needs to lead that cross-functional process of tying strategies and tactics back to performance. Now, back to your question about themes and best practices, Kirk — there are five distinct phases in annual planning, and at each phase there's stuff that can go right or wrong: pre-kickoff (planning a plan), joint planning (asking the right questions), consolidation (what's the bottom line), iteration (where things can fall apart if you're not careful), and final alignment (we are all one team). Pre-kickoff is often overlooked. Before you send out the "time for budgeting again" communication with timelines and deadlines, you should review the previous year's plan — how long did the process take, were there delays, how useful was the budget for decision-making. I don't see many finance teams do this, but it's important. Then you build the planning roadmap: timelines, deliverables, input-collection templates, and ownership. I'm a big fan of the RACI model here — Responsible, Accountable, Consulted, Informed — because the common budgeting problem is too many cooks in the kitchen; RACI makes clear upfront who's actually the decision-maker. Then implement process improvements focused on three things: speed (a planning tool like Drivetrain helps a lot — ninety percent of you are still on Excel/Sheets), accuracy (not perfect prediction, but is it accurate enough to inform decisions), and trackability — your assumptions need to be measurable. For example, at a tech company I worked at, marketing wanted to raise brand awareness through ads that weren't directly selling anything. Measuring ROI on that is tricky since the payoff might come much later, so we built a machine-learning-based attribution model with our data science team, specifically so we could later tell if it was working. Then there's the joint planning phase: business teams build a bottom-up, FP&A builds a top-down, and together you compare and discuss variances, assess risks and opportunities, and prepare a joint departmental plan. Both teams need to be involved — if it's just a finance exercise, the assumptions are too thin to be useful for variance analysis later; if it's just business leaders sending inputs and finance just consolidates, finance isn't adding the value it should. Top-down starts with the end result in mind — expectation-setting, usually from senior leaders or finance — but it still needs to tie back to real business drivers (headcount, advertising spend, product development, market expansion, competitive dynamics), not just "we should grow eight percent." Bottom-up starts from scratch, built up from actual initiatives and campaigns. You do them separately because they rarely match — across eleven annual planning processes I ran, they never matched. That's not a bad thing, it opens a conversation about what's realistic. Bottom-ups tend to be conservative (people want to under-promise so they can over-deliver), while top-downs tend to be aggressive since they come from leadership and are a bit removed from the day-to-day. Combining them and discussing the gap is where a lot of value and understanding comes from. I'm a big fan of driver-based top-down planning — looking at what you're going to do differently and what results that should yield. For example, at a subscription company, we modeled unaided awareness, direct-response spend, inflation, and promo strategy assumptions across three scenarios — balanced, aggressive, conservative — which lets you tell a clear story about exactly where you're taking risk in the plan. Great for board presentations. The advantages: forces analysis of what actually matters, enables scenario planning, useful year-round since you can pull it out monthly or quarterly and adjust. Disadvantages: requires real business understanding, can be time-intensive, and more drivers means more compounding uncertainty. Best practices: business drivers need to be at the tactics level, not just "marketing" or "sales" as a line item; apply an 80/20 approach — five to ten of the most impactful drivers, not a hundred; and it requires real collaboration, finance can't do it alone. Quickly on zero-based budgeting — extremely detailed, reviewing essentially every expense line individually: keep the vendor or not, is there a cheaper option, is there positive ROI. Time-intensive and can reward short-term thinking, but fantastic for finding cost savings if you do it outside of budget season itself, not during it. Best practices: don't do it all at once, start with one department, bring the cross-functional team in, and consider "ring-fencing" instead of straight cuts — let people earn budget back by pitching a high-ROI use for it. After joint planning comes consolidation — the input collection phase, which ninety percent of you do in Excel. Version control is critical here: make sure you know who submitted which version and when, and that it's the one the department head actually signed off on. Then the iteration phase, which is where it gets hectic, since the initial bottom-up almost never matches leadership's expectations — you have to send people back to do more with less. What helps a lot here is requesting inputs as a range rather than a single number, even in the initial bottom-up submission. That way you don't have to keep going back to department owners every time there's a gap — you can just use the more aggressive end of their own range — and the width of that range also tells you something about their level of uncertainty. Kirk Kappelhoff: I've got a question for you, Christian — back to you.
- 35:26
Kirk Kappelhoff
I've got a couple from the audience and a couple from me. First, from Austen Moya: many companies spend months on the budget only for it to be obsolete within a few quarters due to market changes — what's your top framework for building a living budget and a continuous forecasting process rather than an annual one-and-done exercise?
- 35:50
Christian Wattig
First, you need an actual process to reforecast — I trained a large company recently that only reforecast once a year, plus a mid-year update; that's not enough. You need to reforecast at least monthly or quarterly, and ideally that forecast ties back to the original budget rather than existing separately, which means setting the budget up at the right level of detail from the start — a driver-based approach makes this easy to refresh regularly. It's also fine for the budget to differ from actuals — the budget was never meant to be a perfect projection, it's a commitment. That's exactly where the value of variance analysis comes from: comparing where you are now to where you expected to be, understanding the root cause of the gap, and using that to make a concrete recommendation. That's genuinely one of the most important things FP&A delivers, and you can only do it well if you have a comparator built at the right level of detail.
- 37:15
Kirk Kappelhoff
Super helpful. One more from me: when you have a strategic plan spanning five-plus years as part of a shareholder agreement, how do you manage the annual budget process around that?
- 37:35
Christian Wattig
The strategic plan informs the budget, but the budget shouldn't have to match it exactly — they're done at different levels of detail and for different purposes. The strategic plan sets long-term guardrails; the annual budget just needs to be informed by it and get you started with high-level expectations, not forced to reconcile perfectly against it.
- 37:55
Kirk Kappelhoff
Perfect. I know you've got more to cover, but this next question ties in — nothing ever goes the way it should, so what are the biggest challenges people hit across these phases, and how do they push through them?
- 38:10
Christian Wattig
Challenge number one: departments submit inputs late. You set a deadline four weeks before the board meeting thinking that's plenty of time, but people wait until the deadline itself and submit something far from where it needs to be, both in depth and in the actual numbers — and now you're scrambling with no time left. The fix is a staggered timeline with multiple deadlines. For example, kicking off in early November, a first-pass deadline end of November, a second pass mid-December, and a final lock in mid-January. This gets people submitting earlier, gives more time to analyze and run scenarios, and assumes the first pass won't be what you need — people go back and improve it for the second pass. This only works with real buy-in from senior leadership, ideally the CEO or SVPs, because the first-pass deadline only gets respected if there's an actual business review afterward that sends things back for changes. Second challenge: departments don't want to collaborate, or feel too busy to partner with finance through a lot of budgeting meetings — sometimes because they don't see the value, sometimes because they don't feel it's data-driven enough, sometimes because they feel it won't actually change their outcomes. You need to make clear that if they have a high-impact, high-ROI idea, the budgeting process is exactly how they get support and funding for it — and that what they're allowed to spend can flex with business realities even though the budget commitment itself doesn't change. Third challenge: consolidation takes too much time. If you've got Excel files coming in from ten departments and rolling them up into total company revenue and profit takes more than a day, you're chasing your tail by the time you're done — there are already new updates. Tools like Drivetrain do a much better job here and take a lot of the stress out, because it's not just about time, it's also about whether the formulas are right, whether you accidentally used the wrong version. So I actually want to hand it over to Kirk here — I'd love to see how a tool like Drivetrain makes this easier.
- 39:22
Kirk Kappelhoff
Happy to take a look. I'm a big Excel lover myself — back in the day it was the only tool I used, but every company eventually hits that point where you need more than a million rows and forty-eight thousand columns, and that's where tools like Drivetrain help. We still use DAX-style expressions, so all the Excel logic you love — IF, AND, OR, MIN, MAX — is right here. This is our integrations page, where you connect your data sources — hang on, let me just—
- 39:50
Christian Wattig
Sorry, we don't see it — you may need to share again.
- 39:55
Kirk Kappelhoff
No problem, let me jump back — is that easier now? There we go. So, this integrations page — the idea is you shouldn't need an IT team or consultants to connect anything, whether it's an ERP, a spreadsheet, a data warehouse, a currency provider, or an accounting tool — you should just be able to log in. From there, people bring in their templates. We're big believers in the fully integrated three-statement model — revenue to net income, net income to cash flow, cash flow to ending cash, ending cash back to the balance sheet — which then flows into budget views like this P&L. The point is I can interact with my team at a detailed level across actuals versus budget, see the variance, and drill into any dimension — say by department — and leave commentary directly, visible to everyone or just budget leaders, pinging them in Slack, Teams, or email. The biggest pain point is always investigating variances between budget, actuals, and now a reforecast — which, by the way, Christian, due to your point earlier, I'm going to start doing monthly. We've put a lot of work into AI here, since we're an AI-native tool, to generate commentary automatically as part of that investigation, and I can still edit and add to it myself, including inserting a live reference to a metric like revenue so the commentary text updates automatically as the underlying number changes. From a budget perspective, I'd actually rather have each person work from a template that displays differently depending on who's logged in — I see every department, but my head of engineering only sees their own actuals, forecast, and headcount and attrition, not everyone else's. That way I'm not rebuilding the same report thirty times for thirty teams just to add one new chart — I build it once, and permissions handle the rest. So I'll stop there, Christian, and get back to your material — does that answer the question?
- 43:55
Christian Wattig
Yes, and actually a few things you showed touch on something else I hadn't mentioned — the sheer volume of emails flying around during budgeting, "this number needs to change," and so on. Being able to comment directly in the budget is great — sure, you could do that in Google Sheets, but you'd still have the version-control problem, whereas everything stays organized in Drivetrain. It's also fantastic that leaders can see information directly in visualization form rather than constantly re-pasting updated charts into a PowerPoint deck every time something changes. And you mentioned AI — great to see that built in already. What I want to cover as the last thing before Q&A is how people can actually use ChatGPT and other AI day-to-day when budgeting. The most important thing with AI is the prompt itself — how you ask the question. Let me share a prompting framework — not one I came up with, but one Greg Brockman shared; he's the co-founder and current president of OpenAI, the company behind ChatGPT, so if anyone knows how to prompt well, it's probably him. His structure: goal, return format, warnings, and a context dump. His example is finding a hike to do with his girlfriend — he doesn't just state the goal, he specifies the return format (name as it'd appear on AllTrails, address, top three results), adds warnings (double-check the trail name and details are accurate, since reasoning models like o1, o3, ChatGPT, Gemini 2.5 Pro, Claude, and Grok all benefit from being told explicitly what to verify), and then a big context dump — "my girlfriend and I hike a ton, we've done pretty much all of the nearby hikes" — because AI knows nothing about your specific situation unless you tell it. Let me show how this applies to budgeting. I'm in ChatGPT o3 with a temporary chat so it doesn't interfere with memory. The prompt: I'm a finance manager who needs to talk to my CMO about their bottom-up submission and get their thoughts on improving marketing ROI — that's the goal. Return format: specific structure requested. Warnings: make sure each question can actually be used to run financial analysis and lead to a concrete recommendation. Context: I'm more junior than the CMO, I want this to feel collaborative rather than imposing, and I don't want to seem like I'm posturing for our CFO — a bit more color, doesn't need to be exhaustive. Let's see what it gives us — five respectfully framed, data-oriented questions. It opens by asking which marketing programs are punching above their weight over the last twelve months relative to revenue — I like that, it starts on a positive note and lets the CMO highlight wins first. Then it asks about their biggest bets going forward and the assumptions behind them — nice framing, focusing on "bets" rather than "where are you unsure." It also suggests specific data to request, like customer lifetime value, and where quick wins might be. This is genuinely one of my favorite AI use cases — brainstorming, where it doesn't matter if it makes things up, since you're not relying on it for facts, so hallucination risk is irrelevant here. That's exactly why I find this kind of prompting so useful to prepare for these annual budgeting conversations.
- 50:48
Kirk Kappelhoff
That's super cool, Christian, thank you for sharing — I'm hearing more and more finance leaders talking about leveraging AI in their processes. Do you have any workflow tips for how to actually build this into budget planning?
- 51:10
Christian Wattig
On workflow, sharing that detailed staggered timeline I mentioned earlier makes a big difference — being crystal clear on who needs to do what by when. It really comes down to finance acting as a project manager: having a strategy for following up, reiterating deadlines, and communicating the reasoning behind them clearly. One more question I saw — about prompts giving different answers each time you ask. That's actually fine, and expected: I wouldn't ask AI a pure fact like the population of Paris and expect consistency to matter much either way — you could just look that up. But if I ask it to help brainstorm questions for my CMO, it's totally fine, even useful, if it gives me five different questions the next time — I might deliberately regenerate it to get more options, or just ask follow-up. So the distinction is: fact-based questions versus brainstorming. For facts, a search engine is often better; for brainstorming, AI shines — and it'll keep getting better on the facts side too, though it's worth remembering how fast some of those facts change. I've got a couple more questions, but let me launch our final poll first: would you like to explore a demo of Drivetrain's capabilities?
- 53:48
Kirk Kappelhoff
If anything you saw earlier was interesting, we'd love to give you a demo tailored to your use case. Also more generally — did you find this webinar a good use of your time? We want to keep improving these. While that's being answered, Christian, here's an anonymous question I'd probably ask anonymously myself: how do you challenge inputs and assumptions from department heads without causing friction? Feels like a whole book could be written on that one.
- 54:30
Christian Wattig
The best way is to do your homework first — build your own top-down estimate, even a rough back-of-envelope one, before the conversation. Then go in and say, "here's my own projection and my assumptions, walk me through where yours differ" — completely different tone than opening with "your number looks low, we need it higher." Coming prepared to contrast their thinking against yours, step by step, is often how you find a way to genuinely help them, using your planning background as a resource rather than a challenge. Another one, from Nana: what are the most compelling ways to communicate the value of budgeting to leadership in a non-finance-driven organization? It comes down to understanding what that leadership actually cares about. If the business is growing fast, maybe they don't care much about current spend, but they do care whether that growth is sustainable — so you run the budgeting process to answer that specific question. If you're in a nonprofit, budgeting might be about scenario planning for what happens if funding falls through, which a lot of nonprofits had to grapple with recently — having that plan ready means you're not scrambling from scratch when the worst case hits. Really, it comes down to asking leadership what they worry about and showing how planning addresses exactly that. One more, similar vein: what non-monetary goals do you include in annual planning? I'd reframe that — rather than starting with "what non-monetary goals," start with the strategy and tactics each part of the business is using to hit their targets, then work backward to what non-monetary metrics you'd need to track those. For example, if product quality is a stated goal, track something like consumer hotline call volume as a leading indicator — a spike there can point to a quality issue that will eventually hit sales, especially in a subscription business where it shows up as churn. Start with strategy, then tactics, and the right non-monetary metrics become obvious. We've got about a minute left — the one thing you'd want people to remember going into budget season? The most important takeaway: it has to be a collaborative budget process, not just collecting inputs, and not finance doing all the projections alone. Get the bottom-up from the team, challenge it with your top-down, and go through the iteration — it can be painful having multiple rounds where the bottom-up is far from your top-down, but that pain is exactly where the value and the real understanding comes from.
- 58:51
Kirk Kappelhoff
That's time for us, Christian — thanks so much for joining. Everybody, thanks for jumping on, we look forward to seeing you next time. Christian, have a great day.
- 59:01
Christian Wattig
Thank you.






