I’ve been tracking accounting industry trends for my FIRE blog, and there’s a seismic shift happening that affects all of us using Beancount professionally (or thinking about it).
The data is stark: Advisory services grew 20% in 2025 in terms of net client fees. Meanwhile, 94% of U.S. accounting firms now offer advisory services, up from 52% just last year. And over 60% of CPA firms are now prioritizing advisory and consulting as core growth drivers, not side offerings.
Why? Because technology is automating the majority of low-level transactional work—the compliance work that once drove profitability. AI-powered tools handle data entry, reconciliation, and basic bookkeeping. Clients no longer see compliance as a value differentiator.
So where does this leave Beancount practitioners?
Here’s the positioning challenge I’m wrestling with:
Traditional CPA firms’ “advisory”:
- QuickBooks + weekly review calls + dashboard discussions = advisory
- Client sees: familiar tool, polished interface, “professional” look
- Pricing: $1,500-3,500/month for advisory packages
Beancount practitioners’ “advisory”:
- Custom BQL reports + Python analytics + scenario modeling = advisory?
- Client sees: text files, terminal commands, Git commits
- Pricing: ??? (Are we still charging hourly for building queries?)
But here’s the fundamental problem: clients perceive “advisory” as strategic business consulting—pricing strategy, expansion planning, cash flow optimization—not technical mastery of query languages.
When I tell someone “I wrote a complex BQL query with metadata filtering,” they don’t see value. When I tell them “I identified three product lines losing money that you thought were profitable,” they see value.
The Translation Challenge
How do we translate Beancount’s technical capabilities into business value clients will pay for?
Some examples I’m thinking through:
| Technical Capability | Business Value Translation |
|---|---|
| BQL queries with metadata tags | “I track your unit economics by product line and customer segment” |
| Python scripts for cash flow projection | “I model your cash runway across three scenarios so you know when you’ll hit zero” |
| Git hooks monitoring key metrics | “I alert you within 24 hours if spending exceeds budget in any category” |
| Historical data analysis with perfect audit trail | “I show you exactly why Q4 was different from Q3, transaction by transaction” |
But notice: none of these mention Beancount. And maybe that’s the point?
The Pricing Dilemma
Here’s where I’m really stuck: Value-based pricing can increase monthly revenues by up to 50%, and it makes sense for advisory work—you’re paid for outcomes, not hours.
But how do you price outcomes when your efficiency comes from automation? If I write a BQL query in 30 minutes that saves a client $50K annually by identifying waste, what do I charge?
- Hourly rate: $75-150 (punishes my efficiency)
- Value-based: 10% of savings = $5,000 (but client thinks “30 minutes of work?”)
- Monthly retainer: $2,000/month (but what if I don’t find $50K in savings every month?)
Traditional firms don’t have this problem because their tools are slower, so they burn more hours and hourly billing still works (sort of). We’ve automated ourselves into a pricing paradox.
Questions for the Community
I know many of you use Beancount professionally or are considering it. I’m curious:
-
Have you made the transition from transactional bookkeeping to advisory? What does your advisory work actually look like day-to-day?
-
How do you price advisory services? Hourly? Value-based? Monthly retainer? Per-project?
-
How do you explain Beancount’s value to clients without drowning them in technical jargon? What’s your elevator pitch?
-
Is Beancount an advantage or disadvantage for advisory work?
- Advantage: deeper data analysis, perfect audit trail, unlimited customization
- Disadvantage: clients want familiar tools, no polished dashboards, steep learning curve if they want to participate
-
What advisory services actually work? Monthly financial reviews? Quarterly strategic planning? Cash flow forecasting? Scenario modeling?
I feel like Beancount gives us superpowers for financial analysis, but I’m not sure we’ve figured out how to monetize those superpowers in an “advisory services” world. Would love to hear how others are thinking about this.
For context: I’m a financial analyst by day and run a FIRE blog by night. I use Beancount for my own finances and have been approached by two friends about “doing their books.” I’m trying to figure out if there’s a business model here beyond basic bookkeeping.