CoastFIRE at 35: The Terrifying Freedom of 'Enough to Never Save Again' (If You Don't Touch It)

General
1

I just hit a milestone that should feel amazing, but instead I’m having an existential crisis.

The Numbers

At 35, my investment accounts just crossed $420,000. According to every CoastFIRE calculator I’ve tried (CoastFIRECalc, WalletBurst, the Playing With FIRE calculator), this means I’m done. If I never contribute another dollar to retirement, these accounts will compound to roughly $2 million by age 60 at a conservative 6% real return. That supports $80K/year at the 4% withdrawal rate - more than enough for my planned FIRE lifestyle.

I’ve been tracking every transaction in Beancount for 10 years. I built Python scripts that read my balances and project forward under different scenarios. The math is clear. I’ve hit CoastFIRE.

So why can’t I stop saving?

The Psychological Crisis

For the past decade, I’ve maintained a 55% savings rate. Every raise went straight to index funds. Every bonus disappeared into my retirement accounts before I could think about it. This discipline took me from $15K at age 25 to $420K today.

But here’s what the CoastFIRE calculators don’t tell you: your brain doesn’t intuitively accept compounding. I look at $420K and think “that’s not nearly enough.” My rational brain knows the math - 25 years of 6% growth gets me there. But my lizard brain screams “WHAT IF MARKETS CRASH? WHAT IF YOU NEED IT EARLIER? WHAT IF HEALTHCARE COSTS EXPLODE?”

The Kitces article on CoastFIRE mentions this: “For lifelong savers, it may feel unsettling to turn off the savings switch and rely solely on compounding for portfolio growth.” That’s the understatement of the year. It feels absolutely terrifying.

The Opportunity Cost

If I keep saving at my current rate, I’ll hit traditional FIRE (full $2M) by 45 instead of 60. That’s 15 years earlier. But those are also 10 years (35-45) where I could:

  • Take a lower-stress job that pays less but gives me back my evenings
  • Pursue passion projects without worrying about income
  • Actually live instead of optimizing every dollar toward the future

Financial Samurai calls CoastFIRE “the most dangerous early retirement strategy” because it requires discipline not to inflate lifestyle spending. When you stop saving 55% of income, suddenly you have 55% more to spend. If you get used to that elevated spending, you’re no longer on track for CoastFIRE - you need a bigger nest egg.

My Beancount Approach (So Far)

I built a Python script that uses Beancount’s query language to:

  • Extract current investment balances by account type (taxable, Roth IRA, 401k)
  • Calculate “required return rate” under different contribution scenarios
  • Model what happens if I stop contributing vs. reduce to 30% vs. continue at 55%
  • Track my “CoastFIRE buffer” - how far above the bare minimum I actually am

Right now I’m at 127% of the minimum CoastFIRE threshold. That buffer helps psychologically, but not enough to actually flip the switch.

The Questions I’m Wrestling With

For those who’ve hit CoastFIRE:

  • Did you actually stop saving? Or just reduce the rate?
  • How do you handle market volatility without the comfort of “buying the dip” with new contributions?
  • How long did it take before it felt psychologically safe?

For everyone tracking toward CoastFIRE:

  • How are you modeling this in Beancount?
  • Do you track a “safety buffer” above the minimum threshold?
  • What return assumptions are you using in 2026? (I’m using 6% real, which feels conservative but realistic)

The Meta-Realization

Maybe CoastFIRE isn’t meant to be a binary on/off switch. Maybe it’s a spectrum of security where you gradually shift from “saving desperately” to “saving comfortably” to “saving optionally.”

The value might not be in actually stopping contributions. The value might be in knowing you could if you wanted to. That’s a form of freedom too.

But I’d love to hear from others who’ve been here. How did you handle the psychological transition? Did the fear ever go away?

TL;DR: Hit CoastFIRE at 35 with $420K invested. Math says I’m done saving for retirement. Psychology says “ARE YOU INSANE?!” How do you bridge that gap?

2

Congratulations on hitting CoastFIRE, Alice! I went through this exact psychological crisis two years ago when I hit my number at 38.

What I Actually Did (Spoiler: Didn’t Stop Cold Turkey)

I couldn’t bring myself to stop saving completely either. Instead, I compromised: I reduced my savings rate from 60% down to 30% over about 6 months. It felt less terrifying than flipping a switch overnight.

Here’s what worked for me psychologically:

I started tracking a “CoastFIRE buffer” in Beancount. Instead of just asking “Am I above the threshold?”, I track exactly how far above it I am. My account structure looks like:

Assets:Investments:Retirement:CoastFIRE:Required  ; The bare minimum
Assets:Investments:Retirement:CoastFIRE:Buffer     ; Everything above minimum

Every quarter, I recalculate the split based on updated return assumptions and target dates. Right now I’m at 142% of the minimum - meaning I could take a 30% market crash and still be on track.

That buffer number gives me incredible psychological comfort during volatility. In Q4 2025 when markets dropped 12%, I could see my buffer shrink but stay positive. I wasn’t tempted to panic-contribute new money because the math still worked.

The Gradual Approach

Month 1-2: Reduced from 60% to 50% savings rate
Month 3-4: Down to 40%
Month 5-6: Settled at 30%

Each step, I’d track for a full month to see if lifestyle inflation crept in. It did a little - my restaurant budget went from $200/month to $400/month. But that was intentional spending on quality of life, not mindless inflation.

What’s Changed Since CoastFIRE

The biggest shift isn’t financial - it’s psychological freedom:

  • I turned down a promotion last year because it would have meant 60-hour weeks. Old me would have taken it for the salary bump. CoastFIRE me said “no thanks, my retirement is already handled.”

  • I spent 3 months last year building a side project that made zero money but taught me new skills I wanted to learn.

  • When my company had layoffs in February, I felt zero financial stress. Worst case? I coast for a while. The retirement is secured.

Your Questions, My Experience

Did you actually stop saving?

No, but I dropped from 60% to 30%. I’m now optimizing for life quality, not maximum speed to FIRE.

How do you handle market volatility?

The buffer tracking is key. As long as I’m above 100% of required, I’m fine. I’ve set a personal rule: if I ever drop below 110% for two consecutive quarters, I’ll bump savings back up temporarily.

How long before it felt psychologically safe?

About 6-8 months. The first few months I kept recalculating obsessively. Now I check quarterly and don’t stress in between.

Your Meta-Realization is Spot On

Maybe CoastFIRE isn’t meant to be a binary on/off switch.

This is exactly right. The value isn’t in stopping contributions - it’s in having choice. You’re no longer saving because you’re desperate. You’re saving because you choose to, at whatever rate feels right for your current priorities.

That psychological shift is huge. Desperation savings leads to burnout. Choice-based savings is sustainable and actually enjoyable.

Welcome to the club! It gets less terrifying with time, I promise. And that Python script you mentioned? Definitely share it when you’re ready - I’d love to compare approaches!

3

Alice, this post resonates deeply with me. I’m tracking toward CoastFIRE myself (currently at about 75% of the threshold) and your psychological struggle is something I’m already anticipating.

The Healthcare Wild Card

One thing that keeps me up at night: healthcare costs before Medicare. As a CPA, you probably see this in client planning all the time, but for those of us pursuing CoastFIRE, the math gets really dicey in those pre-65 years.

Let’s say you hit CoastFIRE and decide to take a lower-paying passion job or go part-time. Suddenly you’re:

  • Paying ACA marketplace premiums (easily $800-1200/month for a single person in 2026)
  • Dealing with high deductibles ($5,000-8,000)
  • Covering dental and vision out of pocket
  • Hoping subsidies don’t get cut in future legislation

I’ve been building that into my CoastFIRE models as a separate “pre-Medicare healthcare reserve” - basically treating it as an additional expense category that needs coverage beyond the base FIRE number.

The Tax Planning Opportunity

Here’s something I’m excited about though: CoastFIRE creates incredible Roth conversion opportunities.

If you drop from your CPA income (let’s say $150K+) down to a $60K passion job, you suddenly have:

  • Lower marginal tax bracket
  • Room to convert traditional IRA/401k funds to Roth at favorable rates
  • Potentially 10-15 years of tax-advantaged conversions before RMDs kick in

I’m tracking this in Beancount with projected tax liability accounts for different conversion strategies. The long-term tax savings could be massive - potentially hundreds of thousands over retirement.

Your Safety Buffer is Smart

That 127% of minimum CoastFIRE threshold you mentioned? That’s not excessive - that’s prudent. Here’s why:

  1. Sequence of returns risk: If you hit CoastFIRE right before a major bear market, your compounding timeline gets compressed
  2. Lifestyle changes: Marriage, kids, aging parents - these can increase your FI target number
  3. Inflation assumptions: We’re using 6% real returns, but what if it’s actually 5% over the next 25 years?

The buffer gives you flexibility to adjust without panic. Mike’s (helpful_veteran) approach of tracking buffer percentage quarterly is brilliant - it turns a binary “am I safe?” question into a continuous confidence metric.

My Beancount Tracking Approach

I’m doing something similar to what you described:

# Monthly script that reads from Beancount
import beancount.query as query

# Get current investment balances
balances = query.run_query(ledger, "SELECT sum(position) WHERE account ~ 'Assets:Investments'")

# Calculate CoastFIRE scenarios
scenarios = {
    'conservative': calculate_coast_fi(balances, return_rate=0.05, years=25),
    'moderate': calculate_coast_fi(balances, return_rate=0.06, years=25),
    'optimistic': calculate_coast_fi(balances, return_rate=0.07, years=25)
}

# Output markdown report with buffer percentages

I run this monthly and commit the output reports to my Beancount repo. The version control history shows my progress toward CoastFIRE over time - super motivating to see the buffer percentage climbing.

The 401(k) Match Trap

One practical note: don’t stop contributing to get your 401(k) match, even if you hit CoastFIRE. That’s literally free money - typically 50-100% instant return.

Even if you’re “coasting,” contribute enough to max the match. That’s not really breaking the CoastFIRE concept - it’s just not leaving money on the table.

Questions for You

Since you’re tracking this in Beancount:

  1. Are you using balance assertions to validate your projection assumptions quarterly?
  2. How are you handling the psychological accounting of “which dollars are for CoastFIRE vs. which are for earlier goals”?
  3. Have you thought about the estate planning implications? (CPAs always think about this stuff)

Looking forward to seeing your Python scripts when you share them. The FIRE community could really benefit from more plain-text, version-controlled approaches to these calculations!

4

Reading this as someone at 29 with $85K saved… wow, this is both incredibly inspiring and slightly terrifying.

The Math That Makes Me Believe

Alice, you went from $15K at 25 to $420K at 35. That’s $405K in accumulated savings over 10 years. Even accounting for market returns, that’s an average savings rate that’s just… incredible.

I’m sitting here at $85K at 29, trying to figure out if CoastFIRE is even possible for me, and your story shows it absolutely is. But it also shows the discipline required.

My Developer Brain Has Questions

Coming from a software engineering background (DevOps at a startup), I’m fascinated by how you’re tracking this in Beancount. Some questions:

Version Control for Financial Assumptions

When you change your return rate assumptions (say, from 7% to 6% based on 2026 conditions), how do you track that decision in your Beancount setup?

In code, I’d write a commit message like: chore: adjust expected returns from 7% to 6% due to Fed policy outlook. Do you version control your projection scripts alongside your ledger? That feels like it would create an incredible audit trail of your thinking over time.

The “FIRE by X Age” Target Tracking

You mentioned tracking CoastFIRE buffer percentage. I’m imagining something like:

2026-03-28 * "CoastFIRE Checkpoint"
  Assets:Investments:Retirement:Required     420000.00 USD
  Assets:Investments:Retirement:Buffer       113400.00 USD  ; 27% above minimum
  Equity:FIRE:CoastFIREAchieved             -533400.00 USD

Is that roughly how you model it? Or do you keep projections entirely separate from your historical transaction ledger?

The Lifestyle Inflation Fear is Real

Fred’s point about going from 55% savings to 55% more spending is what keeps me up at night. I’ve seen this happen to friends who get big raises:

  • They were saving 40% on $80K salary
  • Got promoted to $120K
  • Somehow still saving 40% but now spending $72K instead of $48K
  • Lifestyle inflated without them noticing

It’s like the inverse of the boiling frog problem - you don’t notice the creep until suddenly your “needs” have expanded to fill all available income.

How do you defend against that? Do you track a “lifestyle inflation budget” in Beancount to make it explicit when you’re choosing to spend more vs. accidentally spending more?

The Timeline That Blows My Mind

If I understand the math correctly:

  • Your path: Aggressive saving ages 25-35, then CoastFIRE from 35-60 (25 years of compounding)
  • My projected path: If I maintain my current trajectory, CoastFIRE by 40, traditional FIRE by 50

But here’s what’s wild: your 10 years of discipline from 25-35 bought you 25 years of career flexibility. That’s a 2.5x return on time invested in savings discipline. That ratio is insane.

My Current Beancount Setup (For Comparison)

I’m tracking toward CoastFIRE but much earlier in the journey:

  • Monthly net worth snapshots using bean-query
  • Separate “FIRE Progress” accounts that I don’t actually transact in - just use for tracking milestones
  • A Python script that calculates my “FIRE age” based on current trajectory (currently showing age 47 at current savings rate)

I’d love to see your Python projection scripts when you’re ready to share. The more concrete examples of “here’s how to track FIRE goals in plain text,” the better.

The Question I’m Wrestling With

At 29, should I even be thinking about CoastFIRE? Or should I be focused on building skills, maximizing earning potential, and just letting the FIRE timeline work itself out?

It feels like there’s a tension between:

  • Optimize for FIRE speed (live cheap, save aggressively, hit CoastFIRE ASAP)
  • Optimize for career growth (invest in skills, networking, experiences that compound income over time)

Did you face that tradeoff in your 20s? How did you think about it?

Anyway, huge congrats on hitting the milestone! Even if the psychological transition is hard, you’ve mathematically secured your future. That’s incredible. And thanks for sharing the struggle - it’s way more helpful than the “I hit FIRE and everything is perfect” posts.