Healthcare Costs Are Rewriting FIRE Targets: The $2M+ Reality in 2026

General
1

I’ve been tracking my FIRE journey in Beancount for 3 years now, and something fundamental has shifted in 2026: the classic $1-1.5M FIRE target is dead for most Americans.

The Healthcare Inflation Reality

The numbers are sobering:

  • Healthcare inflation: 5.8-6% annually (some sources say up to 7%)
  • Social Security COLA projection for 2027: 2.4%
  • Medicare Part B premiums jumped 9.7% in 2026 alone (from $185 to $202.90/month)

For those of us planning to retire before 65, we face the “healthcare cliff”—the years before Medicare eligibility when we’re fully exposed to ACA marketplace premiums.

The Real Cost of Early Retirement

Here’s what early retirees are actually paying in 2026:

Pre-Medicare Healthcare (ages 55-65):

  • ACA marketplace premiums: $1,800 to $2,400 per month ($21,600 to $28,800 annually)
  • Total cost over 10 years: $216,000 to $288,000
  • Percentage of a typical $80,000 annual 4% withdrawal: 27-36%

That’s not a rounding error. That’s a third of your annual budget going to health insurance before you even pay for actual healthcare.

The Subsidy Cliff Problem

The ACA subsidy phase-out at roughly $83,000 MAGI (400% of federal poverty level for couples) creates a brutal planning challenge. Stay under that threshold and premiums are manageable. Cross it by $1,000 and you could pay $10,000+ more per year in premiums.

This makes strategic Roth conversion timing, capital gains harvesting, and income sequencing absolutely critical—and all of it needs to be tracked precisely.

How I’m Tracking This in Beancount

I’ve created a separate expense projection account structure. Each year I model my expected healthcare costs with a projected transaction, then reconcile against actuals. This helps me understand if I’m staying on track with my pre-Medicare healthcare budget.

I’m also modeling different withdrawal scenarios to stay under subsidy thresholds while meeting living expenses. The transparency of plain-text accounting makes it easy to run “what-if” scenarios by copying my ledger and adjusting variables.

Sources & Context

Recent research confirms these trends:

Discussion Questions

For those pursuing FIRE:

  1. How are you modeling pre-Medicare healthcare costs in your Beancount ledgers?
  2. What account structures work best for projecting healthcare across multiple scenarios?
  3. Is anyone tracking HSA contributions as a “stealth retirement account” alongside traditional retirement accounts?

For consultants/advisors:

  1. What do you tell clients who haven’t factored in these healthcare realities?
  2. How do you help them balance staying under subsidy thresholds vs meeting income needs?

The $2M+ FIRE target isn’t about lifestyle inflation—it’s about surviving the healthcare cliff. I’d love to hear how others are planning for this in their plain-text accounting systems.

Tracking every dollar toward financial independence since 2023 | Seattle, WA | Currently at 47% FI

2

This hits home, Fred. I remember when I started tracking my FIRE journey in Beancount 4 years ago, I was using the old $1.2M target too. Reality check came fast when I started modeling healthcare.

My Approach: Separate Healthcare Tracking

I created a dedicated account structure specifically for pre-Medicare healthcare projections:

Assets:Projections:Healthcare:PreMedicare
Expenses:Healthcare:Insurance:ACA
Expenses:Healthcare:OutOfPocket

The key insight for me was treating healthcare like a separate mini-retirement fund. I calculate it separately from my 4% rule withdrawals, because healthcare costs don’t follow the same inflation patterns as the rest of COLA.

The Subsidy Cliff Is Real

You mentioned the $83k MAGI threshold—this is where Beancount really shines for planning. I run monthly queries to project my taxable income across different withdrawal scenarios:

  • Roth conversions vs traditional IRA withdrawals
  • Capital gains timing (can I defer a year?)
  • Whether to tap taxable accounts first to stay under the cliff

What I learned the hard way: crossing that subsidy threshold even once can cost you $10k-15k in a single year. The ACA marketplace doesn’t prorate—you’re either under or you’re not.

Questions for You

  1. Are you including out-of-pocket maximums in your projections? Even with insurance, there’s the $9,450 individual / $18,900 family OOP max to plan for.
  2. How are you accounting for healthcare inflation at 6%+ when the rest of your budget might only inflate at 3%?

The transparency of plain-text accounting makes these scenarios so much easier to model than a spreadsheet. You can literally see every assumption and adjust them independently.

Great post—this is the reality check the FIRE community needs in 2026.

3

Fred and Mike, this thread is a wake-up call. As someone who reviews client finances regularly, I can confirm: most people pursuing FIRE have dramatically underestimated their pre-Medicare healthcare costs.

The $83K Subsidy Cliff Is Brutal

Mike, you’re absolutely right about the subsidy cliff being non-negotiable. I have clients who meticulously track every dollar in Beancount, but they didn’t realize that one large capital gain or an unexpected bonus could push them over the MAGI threshold and cost them $15,000+ in additional premiums for that year.

The ACA marketplace subsidy isn’t gradual—it’s a cliff. And in 2026, with premiums up 20-26%, the penalty for crossing that line is severe.

What I Tell Clients Who Underestimate This

When a client comes to me with a FIRE plan that doesn’t adequately account for healthcare, I walk them through this exercise:

  1. Calculate true healthcare costs: Premium + out-of-pocket max + dental + vision
  2. Apply 6% annual inflation (not the 2-3% they use for other expenses)
  3. Multiply by years until Medicare (age 65 for most)
  4. Add a 20% buffer for unexpected health events

The resulting number usually shocks them. For someone retiring at 55, we’re talking $300,000-350,000 over 10 years—and that’s in today’s dollars.

The HSA Strategy Fred Mentioned

Fred, you mentioned HSAs as a “stealth retirement account.” This is one of the smartest moves for FIRE planners:

  • Triple tax advantage (deductible, grows tax-free, withdraws tax-free for medical)
  • After 65, functions like a traditional IRA (can withdraw for anything, just pay income tax)
  • Can pay healthcare costs in retirement tax-free from accumulated HSA funds

For clients in their 30s-40s planning FIRE, maxing out HSA contributions ($4,300 individual / $8,550 family in 2026) and not spending it creates a dedicated healthcare fund that compounds for decades.

Beancount Account Structure

I recommend clients track HSA investments separately in their Beancount ledgers:

Assets:HSA:Cash
Assets:HSA:Investments
Assets:Retirement:Traditional401k
Assets:Retirement:RothIRA

This makes it clear that HSA is not part of the traditional retirement calculation, but rather a dedicated healthcare fund.

Question for the Group

For those tracking this in Beancount: are you running annual queries to project your MAGI and ensure you stay under subsidy thresholds? If so, what does that query look like?

This is the kind of precision tracking that makes plain-text accounting so powerful for FIRE planning.

4

Mike and Alice, thank you both—this is exactly the kind of community wisdom I was hoping for!

Responding to Mike’s Account Structure

Mike, I love your approach of treating healthcare as a “separate mini-retirement fund.” I’ve been doing something similar but hadn’t thought about it in those terms. Here’s my current structure:

Assets:Retirement:Traditional401k
Assets:Retirement:RothIRA
Assets:Retirement:HSA:Cash
Assets:Retirement:HSA:Investments
Assets:Taxable:Brokerage

Expenses:Healthcare:Insurance:Projected
Expenses:Healthcare:OutOfPocket:Projected

The key for me is using metadata tags to distinguish pre-Medicare projections from post-Medicare:

2026-01-01 * "Healthcare projection - Pre-Medicare (ages 45-65)"
  Expenses:Healthcare:Insurance:Projected  28800.00 USD
    coverage: "pre-medicare"
    aca-subsidy: "none"
    magi-threshold: "83000"
  Equity:Projections:Healthcare

This lets me run queries filtered by the coverage tag to see exactly how much pre-Medicare healthcare is costing in different scenarios.

Answering Alice’s Question: MAGI Projection Query

Alice, yes! I run a quarterly query to project my MAGI and simulate different withdrawal strategies. Here’s a simplified version:

SELECT 
  year(date) AS year,
  sum(position) AS total_income
WHERE 
  account ~ 'Income:*'
  AND year(date) >= 2026
GROUP BY year(date)
ORDER BY year(date)

I then manually adjust for Roth conversions, capital gains, and other MAGI impacts to see where I land relative to the $83k cliff.

The goal: Stay at $79k-80k MAGI to keep a buffer, not push right up to $83k.

Mike’s Questions About OOP Max and Healthcare Inflation

  1. Out-of-pocket max: Yes, I include the family OOP max ($18,900 in 2026) as a separate annual projection. I assume we’ll hit it every 3-4 years (not every year, but often enough to plan for it).

  2. Healthcare inflation differential: This is where it gets tricky. I use two inflation rates in my projections:

    • General expenses (housing, food, etc.): 3% annually
    • Healthcare (insurance + OOP): 6% annually

This creates a compounding gap over time, which is why the $2M+ target is becoming the new baseline.

The HSA “Stealth Retirement Account” Strategy

Alice nailed it. I’ve been maxing out my HSA for 5 years now and treating it as:

  • Primary purpose: Dedicated healthcare fund for pre-Medicare years
  • Secondary purpose: If I don’t need all of it for healthcare, it converts to traditional IRA treatment at 65

Current HSA balance: $52,000 (all invested, not touched). By the time I hit 55 (my target FIRE age), I’m projecting $140,000-160,000 in the HSA, which covers 5-6 years of pre-Medicare premiums.

Thank You Both

This is why I love the Beancount community. You can’t get this level of detailed, experiential advice from generic FIRE forums. Plain-text accounting enables this kind of precision planning.

If anyone else has MAGI projection queries or healthcare tracking strategies, please share!

5

Fred, that metadata tagging approach is brilliant! I hadn’t thought of using tags to distinguish pre-Medicare vs post-Medicare projections. I’m definitely adopting that.

The Power of “Start Simple, But Not With Healthcare”

One of my usual pieces of advice for Beancount beginners is “start simple”—don’t over-engineer your account structure on day one. But healthcare is the exception.

If you’re pursuing FIRE, healthcare tracking can’t be an afterthought. It’s too big, too volatile, and too consequential to ignore or simplify away.

Your approach of running quarterly MAGI projections is exactly the kind of proactive planning that prevents expensive surprises.

A Runway Query That Includes Healthcare

Since you mentioned queries, here’s one I run monthly to calculate my “runway” (months of expenses I can cover):

SELECT 
  sum(position) AS net_worth
WHERE 
  account ~ 'Assets:*'
  AND NOT account ~ 'Assets:House'

Then I divide by my healthcare-inclusive monthly expenses (not the idealized “4% rule” number). This gives me a more realistic runway that accounts for the healthcare cliff years.

For example:

  • Net worth (liquid): $1.8M
  • Monthly expenses (including $2,400 healthcare): $7,500/month
  • Runway: 240 months (20 years)

Compare that to the “traditional” calculation that might assume $5,000/month and show 30 years of runway. The healthcare reality cuts that by 33%.

Encouragement for Others

If you’re reading this thread and feeling overwhelmed: this is exactly why tools like Beancount exist. You’re not just tracking where money went—you’re modeling where it needs to go.

Fred’s transparency about his 47% FI progress and his detailed healthcare planning is exactly the kind of realistic, data-driven FIRE journey that succeeds.

Keep sharing these approaches, everyone. The 2026 healthcare reality demands this level of precision, and plain-text accounting gives us the tools to handle it.