Use the BT retirement what-if without mistaking it for a payoff simulation

You’ve got a 0% balance transfer card with a balance sitting on it. Should you put extra money toward clearing it, or should you put that extra money into retirement? The honest answer is “it depends on facts this panel does not decide for you.” The BT retirement what-if gives you one deliberately narrow comparison: how the recorded retirement plan changes if the card’s current balance were already sitting in the primary 401(k). It produces three live values, but it is not a card-payoff simulation.

This walks through reading the simulator and getting an actionable answer. The prerequisite is the Track a balance transfer walkthrough — if you don’t have a BT tracked yet, do that one first.

What you’ll learn

• Where the BT Simulator panel lives on each active balance transfer
• What each of the three numbers represents in plain English
• How to compare the numbers and decide whether to accelerate payoff
• Where the math comes from — the panel names its assumptions and the confidence behind them

Before you start

You need:

• At least one active balance transfer tracked on /BalanceTransfers (see the prerequisite walkthrough)
• The /Retirement page set up with a retirement age later than your current age, and — the one people miss — your annual spending today, which is what the comparison actually gates on. Your bracket isn’t something you enter: GlidePath derives the starting federal bracket from the household income and filing status recorded there, after the standard deduction and any employee-only deferral you recorded
• Some retirement money in that plan — a 401(k) balance, other retirement savings, or an annual contribution. With none, the panel says so instead of quoting a success probability it would have to make up

If the panel says “Set up your retirement plan first — this comparison needs return assumptions and a retirement age,” five minutes on /Retirement unlocks the full output.

What the simulator actually does

Below each active BT on the /BalanceTransfers page, GlidePath renders an inline panel titled “What if this amount were added to retirement?”

Read that heading as the question that opens the comparison, not as a list of transactions the engine performs. Exactly one retirement input changes: the primary 401(k) starting balance increases once by the card’s current balance. The projection then runs again.

The model does not clear the card, remove its debt from net worth, spend payoff cash, calculate interest saved, or turn the freed monthly payment into recurring contributions. It does not claim a net-worth wash. The clean reading is: if this balance-sized amount were already in the 401(k), how would the recorded retirement plan look?

It then shows three numbers from that narrow comparison:

1. Modeled federal tax reduction this year — capped at your remaining plan room and priced across the brackets it crosses, with your recorded contributions already subtracted. It is an up to figure: actual savings can be lower, including $0
2. Future value at retirement — the full current balance compounded once to your retirement age
3. Change in Monte Carlo success probability — the difference between your recorded plan and the same plan with that one-time 401(k) starting-balance bump

Step 1 — Find the simulator panel (30 sec)

Open /BalanceTransfers. Below each active BT row is a collapsed disclosure whose heading is the panel’s full question — “What if this amount were added to retirement?”. That heading is the control: click it and the panel expands in place.

There’s no separate short expander to hunt for; the question you read is the thing you click.

Step 2 — Read “Modeled federal tax reduction this year” (1 min)

The first number answers: how much federal income tax could be deferred this year if some or all of this balance-sized amount fit as a deductible pre-tax 401(k) contribution?

When household income is recorded, GlidePath computes it as:

Modeled tax reduction =
  federal tax on the starting taxable-income stack
  − federal tax after the modeled deductible portion

The starting stack is gross household income less the standard deduction and the employee-only deferral you recorded. The subtraction matters: a modeled contribution can cross into a lower bracket, so multiplying every dollar by the starting rate can overstate the result.

On a $12,000 balance, GlidePath caps the deduction at what your plan can actually take this year — the §402(g) deferral limit or the §415(c) total-contribution limit, whichever binds first — and subtracts what your plan already records going in. If you have entered household income and haven’t pinned a rate yourself, it then prices the rest across the brackets the deduction actually crosses: at $134,000 of joint (married filing jointly) household income that is $1,540 on a $12,000 balance, not the $2,640 a flat 22% would suggest. With no income recorded, or with a rate you set by hand, it stays a flat-rate illustration and labels it as one. Two things it still cannot settle on its own: how much of your recorded contribution is your own deferral rather than employer match, and your plan compensation. It says so on the tile, models a range, and tells you actual savings can be $0.

The compensation gap is the one the app can’t close from what it stores. Household income is not a safe stand-in for one worker’s plan-eligible compensation, so the headline always reads up to: a planning ceiling, not a filed amount. Recording your employee-only deferral on /Retirement settles the employer-match split; it cannot settle the compensation cap.

Where the bracket comes from matters: GlidePath computes it from the household income and filing status on /Retirement. If you haven’t entered a household income, it shows a 22% rate illustration and labels it as an assumption rather than passing it off as your bracket.

Read the word defer carefully. This is not cash the app moves into your hand, and a pre-tax 401(k) contribution is not tax you escape; it is tax not paid this year. Those dollars are generally taxed as ordinary income when withdrawn. The tile is a current-year federal planning estimate, not a permanent discount or a filed amount.

What this is not. These are modeled figures for planning, not tax advice, and not a filed amount. They assume the income and growth inputs on /Retirement hold; they don’t model state tax or the second-order effects a big income year can trigger; and they read household type as joint-or-single only. A tax professional can confirm what actually applies to you.

Step 3 — Read “Future value at retirement” (1 min)

The second number answers: if a one-time amount equal to the current card balance sits in the market until I retire, what does it grow to?

GlidePath computes it as straightforward compound interest on the balance:

Future value = current card balance × (1 + growth rate) ^ years until retirement

The growth assumption defaults to 7%/yr, and it’s a nominal return — that is, before inflation. Inflation is its own separate input on /Retirement, so don’t mentally subtract it from this number too. The app’s own hint next to the input suggests a long-term average of 6-8% for a stock-heavy allocation; a bond-heavy mix has historically returned less, so the assumption you enter should reflect the mix you actually hold. You can adjust it on /Retirement.

So a $12,000 starting-balance bump, 22 years from retirement at 7%, becomes about $53,200 — in future dollars, not today’s purchasing power. This line uses the full current balance and does not depend on whether that amount could actually be contributed or deducted this year.

Worth knowing what this line is for. It’s annual compounding on a single lump — deliberately simple, meant as ballpark intuition. The Monte Carlo number below is the rigorous one.

Step 4 — Read “Change in Monte Carlo success probability” (1 min)

The third number asks: if my primary 401(k) starting balance were higher by this card’s current balance, how much would the modeled chance of the plan lasting change?

The simulator adds the current card balance to your 401(k) starting balance and re-runs your retirement Monte Carlo (a market-projection simulation across many randomized return paths) on both versions:

• Baseline: your plan exactly as it stands
• Counterfactual: the identical plan with your 401(k) starting balance raised once by the card’s current balance

The card itself is not an input to the retirement projection either way. The two runs differ by exactly one number — the 401(k) starting balance — so the delta measures having that amount invested, not shedding debt, saving interest, or redirecting a monthly payment.

There’s also a detail worth explaining, because it’s the difference between a trustworthy delta and a noisy one. A Monte Carlo draws random market paths, so two runs with different random draws land in slightly different places — noise that can easily swamp a small real effect. So the comparison pair uses common random numbers: 500 trials on each side driven by the same seed, so both runs see the identical sequence of market draws and the sampling noise cancels between them. What’s left is the effect of the bump alone. That clean delta is the number the panel leads with.

The absolute percentages shown alongside it are anchored to the same headline run that /Retirement, /Index, and the Money State statement display, so the figure here doesn’t contradict the one you see when you click through.

GlidePath doesn’t push you toward a specific decision — it makes the tradeoff visible and shows you the arithmetic behind it.

Step 5 — Compare the three numbers and decide (2 min)

Three real numbers, three different time horizons:

Number	Time horizon	What it answers
Modeled federal tax reduction this year	This calendar year	An up to ceiling, capped at remaining plan room, priced across the brackets it crosses; the deferral/match split and plan compensation are still yours to confirm
Future value at retirement	10-30 years	Full balance-sized starting bump compounded at your assumption
Monte Carlo delta	Through end of plan	Modeled plan change from that starting-balance bump

Taken together they reframe the BT-vs-retirement question from “which is more important?” (an emotional question) to “what does each one actually move?” (a quantified one). The simulator doesn’t decide for you — it gives you the three lenses and the arithmetic behind them.

What just happened

You’ve done something most personal-finance tools can’t do at all:

1. Took one card balance as the size of a retirement comparison
2. Saw three different lenses on that comparison while keeping the payoff mechanics outside the model

This is the cascading what-if pattern that’s the model for everything else GlidePath is building. Change one input → see the ripple across multiple views immediately, all computed from your real data, all explainable.

Common follow-ups

The Monte Carlo delta says 0.0 percentage points. Why?

Either your plan is already at very high success probability (so there’s no room to improve) or very low (so this one BT isn’t enough to move the needle). Open the underlying Monte Carlo on /Retirement to see which case you’re in.

Why does putting it in a 401(k) defer more tax than a Roth?

A deductible pre-tax 401(k) contribution can reduce current taxable income; a Roth contribution does not. The tax tile caps the deduction at your remaining plan room, so the figure already respects this year’s limits; what it cannot see is how much of your recorded contribution is employer match, and your plan compensation. If you would use a Roth, the current-year tax line does not apply. The Monte Carlo comparison still shows the effect of the starting-balance bump because this projection does not distinguish pre-tax from post-tax balances.

Can I run the simulator on a BT I haven’t tracked yet?

Not yet. The simulator reads the balance off a real BT row. Track the BT first (walkthrough), then expand the simulator.

My future-value number looks too high — what gives?

Check the growth assumption on /Retirement. The default is 7%/yr nominal; if you’ve set it to 10%, the future-value compounds faster and the number balloons. And remember the result is stated in future dollars — a big number two decades out buys less than the same number today, which is exactly why the Monte Carlo success change — which runs through the full retirement model rather than one compounding formula — is the more rigorous of the three numbers.

Ask Glide about this

Try: “Should I prioritize paying off a 0% BT or contributing to my 401(k)?” — Glide will walk through both sides of the tradeoff. Glide doesn’t see your numbers; it just explains the framework. The numbers come from the simulator panel.

Where to next

• Find your Tax Valley + Roth conversion math — the same cascading-decision pattern applied to the retirement side
• Track a balance transfer end-to-end — the prerequisite tutorial if you skipped it