Your team has already decided that a program is no longer earning its place in the budget. The analysis is done. The hard part is saying it to leadership without sounding either careless or accusatory.
Too soft:
"Maybe we should look at cutting this at some point."
Too harsh:
"This was a waste of money and we need to kill it now."
More precise:
"This line is overhead we can no longer justify against its return. We recommend sunsetting it over the next two quarters. Most of the cost is already baked in for this fiscal year, but there's wiggle room to reduce the renewal starting next quarter."
The stronger version names the cost category, the recommendation, and exactly how much flexibility actually exists.
This article covers how to communicate a budget recommendation your team has already reached. It does not decide what should be cut; that judgment, and the evidence behind it, belongs to the finance and business teams who own the analysis.
Quick check
Test what you just read.
Ready to go beyond the quiz on "Sunset"?
Take the full learning path: hear it in real workplace contexts, watch short explanations, learn its nuances and when to use it, then practice using it yourself.
Start learning for free →Now see if you can use it naturally yourself.
Try it yourself
You know how to use "Sunset," too.
Keep going with the full learning path — more workplace contexts, related expressions, and continued practice.
Continue with "Sunset" →There's more to "Sunset" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Sunset" in depth →Name the cost precisely before recommending anything
Overhead is a cost that supports the business without directly driving revenue or output. Calling something overhead is a classification, not a criticism.
"Facilities and admin support are overhead; they don't scale with revenue the way the sales team does."
Boondoggle is a stronger, judgment-loaded word for spending that produces little real value, often used when a project persists past the point it should have been reconsidered. It carries more blame than overhead does, so use it carefully and only when the evidence supports it.
"The regional office pilot became a boondoggle: two years and no measurable customer impact."
Sunset, used as a verb, means winding something down on a planned schedule rather than cutting it abruptly. It is the recommended action, not a description of the cost itself.
"We recommend sunsetting the pilot by the end of Q2 rather than stopping it immediately."
Naming a cost as overhead is a classification. Calling it a boondoggle is a judgment about its value. Recommending to sunset it is the action you propose. Keep the three separate: a leader can accept the classification and still disagree with your recommended pace.
For the individual words, see What Does "Overhead" Mean at Work?, "Boondoggle" Meaning at Work, and What Does "Sunset" Mean at Work?.
Show what's already locked in and what's still flexible
Bake in, used with a cost or assumption, means it is already built into the current budget or model and cannot be changed without a separate decision.
"The vendor contract is already baked into this year's budget through December."
Wiggle room describes the flexibility that remains once the fixed costs are accounted for.
"There's wiggle room to reduce the license count starting next renewal, but not before then."
Naming what is baked in stops leadership from expecting a change that isn't actually available yet. Naming the wiggle room shows exactly where a decision can still take effect.
For the individual words, see "Bake In" in a Sentence and What Does "Wiggle Room" Mean at Work?.
Want to actually use "Sunset" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Sunset" learning path →Use a five-part budget recommendation
- Classification: Is this overhead, or a cost tied directly to output? Name it.
- Evidence of the problem: What specific data supports reconsidering it? Be ready to name the source; avoid boondoggle unless the evidence is strong enough to support that word.
- Recommendation: What action are you proposing, and on what timeline? Sunset signals a planned wind-down, not an emergency stop.
- What's baked in vs flexible: What is already committed, and where does the wiggle room actually start?
- Decision owner and timeline: Who needs to approve this, and by when?
Pattern:
"[Cost] is [classification] that [evidence]. We recommend [action] by [timeline]. [Amount] is already baked in through [date]; the wiggle room starts at [point]. [Owner] needs to approve this by [date]."
Bad vs better budget recommendations
When the cost has clearly stopped paying off
Weak:
"This isn't really working out."
Better:
"This line is overhead that hasn't produced a measurable return in three quarters. We recommend sunsetting it by the end of Q3. The team can be reallocated once the transition plan is approved."
When part of the cost can't be changed yet
Weak:
"We should just cut this now."
Better:
"The contract is baked in through December, so we can't reduce it before then. There's wiggle room on the renewal terms starting January, and that's where we'd focus a reduction."
When the language risks sounding like blame
Weak:
"This whole program was a boondoggle from the start."
Better:
"The program hasn't delivered the customer impact we projected when we approved it. We recommend sunsetting it rather than continuing to fund it at the current level."
The second version states the same conclusion without assigning blame to the people who approved it originally.
A realistic budget review dialogue
VP of Sales: Why are you recommending we cut the regional pilot?
FP&A analyst: It's overhead relative to its output right now. It hasn't produced a measurable increase in regional bookings over three quarters, so we recommend sunsetting it by the end of the fiscal year rather than stopping it abruptly.
VP of Sales: We already committed budget for the fall event under that program.
FP&A analyst: That portion is baked in and we're not proposing to touch it. The wiggle room starts with the renewal in January, so nothing changes before then.
VP of Sales: Okay, that timeline works.
The analyst separates the classification, the evidence, the recommendation, and the flexibility, so the VP can evaluate the ask without feeling ambushed.
Scenario challenge
A tool license renews in two months. Usage data shows adoption dropped by half over the past year. Most of the current-year cost is already paid. Which response is strongest for a budget review?
A. "This tool is a waste and we should cancel it immediately."
B. "Adoption has dropped by half this year, so this license is overhead we can't justify at the current tier. This year's cost is already baked in, but there's wiggle room to downgrade or cancel at the renewal in two months."
C. "We might want to think about this tool at some point."
Answer: B. It states the evidence, the classification, what's already committed, and exactly when the flexibility begins.
Quick quiz
Which sentence uses the words most precisely?
A. "This is baked-in overhead, so let's sunset it before the contract renews."
B. "This is overhead with declining usage. Since it's baked in through the renewal date, we recommend sunsetting it starting at that renewal."
C. "This boondoggle has some wiggle room, so let's bake in a cut."
Answer: B. It respects what's already locked in and times the recommended action to when the flexibility actually starts.
Practice the full recommendation
Practice the five-part structure with different situations: a tool with falling adoption, a program with no clear owner, and a vendor contract with an approaching renewal. For each one, state the classification, the evidence, the recommendation, what's baked in versus flexible, and who owns the decision.
The goal is not to sound more decisive than the evidence supports. It is to make a defensible recommendation easy for a leader to approve or push back on.
To practice recommending budget decisions in realistic finance scenarios, try Lyra Practice or explore English for Finance.
Return to Business English for Finance Professionals for more finance vocabulary organized by situation.
Draft the next sentence
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.