Teaching My Adult Children Beancount: When 15 Years of Plain Text Meets "Dad, Why Not Just Use Mint?"

For 15 years, I’ve tracked every single dollar through Beancount. Every coffee, every stock trade, every mortgage payment - all recorded in plain text files with perfect double-entry accounting. The result? I hit FIRE at 42, retired from my analyst job, and now spend my days optimizing my portfolio and writing Python importers that save me 3+ hours every month.

My kids see this success. They know dad retired early. They want to learn.

But here’s the problem: they’re 24 and 26, and when I show them Beancount, they look at me like I’m demonstrating a 1995 DOS program.

“Dad, why not just use Mint?”
“There are apps for this now.”
“Can’t AI just… do it automatically?”

The Generational Collision

My daughter uses Venmo for everything, YNAB for budgeting ($15/month), and gets her financial advice from FinTok. My son wants to “automate everything” and doesn’t understand why I manually type transaction entries when AI categorization exists.

Meanwhile, I’ve got a beautiful Fava dashboard, custom Python importers for 7 different institutions, and can generate ANY financial report about my life in 30 seconds flat. I have 15 years of perfect transaction history. I can prove every number to the IRS. I own my data.

But to them, Beancount looks like homework. It looks complicated. It looks old.

The Dilemma

Do I insist they learn Beancount? It’s a life skill - understanding double-entry accounting, maintaining an immutable audit trail, owning your data forever. These are principles that will serve them for 50+ years.

Or do I let them use commercial tools? Lower barrier to entry. Pretty interfaces. They actually might stick with it instead of quitting after two weeks of syntax errors.

The Math Nobody Wants to Hear

I did the calculation (of course I did - I’m a Beancount user):

  • YNAB: $14.99/month = $180/year
  • Monarch Money: Similar pricing
  • Over 50 years: $9,000 in subscription fees (not even accounting for inevitable price increases)
  • Beancount: $0, forever, no company can shut it down

But my kids don’t think 50 years ahead. They think in terms of “what works this month.”

What I’ve Tried So Far

I showed them my Fava dashboard. Cool visualizations, they said, but can’t I just give them access instead of making them build their own?

I explained version control for financial data. They use Git for code, they get the concept intellectually - but they don’t feel the pain point yet. They’ve never lost data. They’ve never needed to audit 5 years of transactions for a tax question.

I offered to write their importers for them. They said thanks but they’re not even sure what an “importer” is.

The Question I’m Wrestling With

How do you make plain text accounting appealing to digital natives?

People who grew up with:

  • One-click app installs
  • AI that “just works”
  • Subscription models for everything
  • TikTok tutorials instead of documentation
  • Expecting software to be beautiful

They see Beancount’s power, but they don’t yet need that power. They see the learning curve, and they have alternatives that look easier.

What I’m Asking This Community

Have you successfully taught family members Beancount? Especially younger adults (20s-30s)?

  • What was the hook that got them interested?
  • What was their “aha moment” when they understood the value?
  • At what age or life stage did it click?
  • Did you let them start with commercial tools first?
  • Did you build simplified tooling on top of Beancount for them?

I know my FIRE success is the seed. They’ve seen the results. But I’m stuck on the pedagogy.

Any wisdom from this community would be genuinely helpful. I want to teach them skills that will serve them for life, but I also don’t want to force a tool that creates resistance instead of understanding.


P.S. Yes, I’ve already calculated that if they start at 26 with my savings rate, they could hit FI by 42 like me. I have the spreadsheet ready. They haven’t asked to see it yet. This may be part of the problem.