The What / So What / Now What framework that I'm going to share this week didn't come from accounting. It came from a man called Andy, a brilliant Englishman I worked for at NTT who had the attention span of a goldfish and absolutely no tolerance for anything he saw as wasting a moment of his time. Andy had a thousand things on his mind at any given point, and if you walked into his office without knowing exactly what you needed to say, why it mattered, and what you wanted him to do about it, he'd let you know — quickly, and without much diplomacy.
That sounds brutal, and it was, but it taught me something I've carried through every role since: the discipline of getting to the point isn't just about brevity. It's about respecting the person you're talking to enough to have done the thinking before you open your mouth.

That discipline is what turned into a framework for how we structure every client conversation at Stoneforge. But before I get to the framework itself, I need to talk about the advice that nearly everyone in this industry is giving — and why it's setting people up to fail.
The "Just Add Advisory" Trap
"You should add advisory services." You've heard this a hundred times if you're a bookkeeper, fractional CFO, or running a CPA firm. QuickBooks says it. Xero says it. Every conference speaker and industry commentator says it.
And they're not wrong — advisory is where the value is. We covered the forces driving that in Issue #1, and the capacity problem in Issue #2.
But here's what we noticed when we got deeper into the QuickBooks and Xero world through the bookkeeping firm we acquired in 2021: their advice on how to go about advisory wasn't untrue, but it was heavily slanted toward their aims as a platform provider. "Add forecasting. Build dashboards. Offer budgeting services." All of which happen to require deeper adoption of their platform and their ecosystem of add-ons.
We'd been running advisory at Stoneforge for years before we bought the bookkeeping firm. We knew what advisory conversations actually looked like in practice — the messy, relationship-dependent, context-heavy work of helping a business owner understand what their numbers mean and what to do about them. And what the platforms were promoting as "advisory" bore very little resemblance to that.
The real problem isn't that their advice is bad. It's that it starts in the wrong place.
Why Starting With Complexity Fails
The platforms tell you to start with budgeting, forecasting, and strategic planning — complex deliverables that require analytical depth and client engagement.
But you can't build a budget with a client who doesn't understand what their current numbers mean. I've watched this play out more times than I can count. A bookkeeper or fractional CFO, well-intentioned and technically capable, tries to introduce a forecasting conversation with a client who hasn't engaged with last month's results. The client sits through it, says "good meeting, thanks" — which is always the signal that it wasn't — and then nothing changes. No decisions get made. No actions get taken. And the practitioner concludes that "advisory doesn't work for my clients."
It's not that advisory doesn't work. It's that forecasting requires shared context between you and the client — they need to understand what happened last month and why it matters before they can meaningfully engage with projections about next quarter. If they won't read the basic monthly report, they're certainly not going to engage with forward-looking scenarios that require even more analytical depth.
Advisory doesn't start with forecasts. It doesn't start with complex dashboards. It starts with something much simpler, and much harder to get right.
What / So What / Now What
At Stoneforge, Kristina and I spent two years watching our bookkeepers deliver monthly reviews to clients. The books were accurate, every time. Every category correct, every variance explained. And the client would sit through it, say "good meeting, thanks," and leave having retained nothing — which meant the meeting was anything but good.
The problem was never the quality of the information. It was the structure. The bookkeeper would start at the beginning of the P&L and drive through line after line, point after point, with no differentiation in what was important. If you stacked a thousand of those meetings end on end, you would never reach a conclusion. It was a thirty-minute tutorial on how to read a spreadsheet, when what the client actually needed was three things: Are we okay? What changed? What should I do?
That's what the What / So What / Now What framework answers, and it changed how we structure every client conversation.
What happened? High-level summary — revenue up twelve percent, profit down eight percent. Not every line item. The story at the top of the business, told in plain language.
So what? Why it matters to this specific business — margins compressed because cost of goods increased faster than pricing. The interpretation that connects the numbers to decisions the owner actually needs to make.
Now what? What to focus on — review supplier costs, consider a price adjustment, schedule a follow-up in two weeks to look at the three accounts driving the increase. Specific, actionable, connected to what the client can actually do in the next thirty days.
That's it. That's the structure that gets clients to engage with their financials rather than filing them away unopened.
But here's what I didn't fully appreciate until we'd been running this for over a year: the Now What isn't just the conclusion of a monthly conversation. It's the thread that connects everything forward.
Each month's Now What becomes next month's What Happened. That's what makes advisory sticky rather than optional.
Last month you agreed together on three actions — review the supplier contracts, pause the underperforming ad spend, schedule a pricing conversation. This month, you're not starting from scratch. You're checking in on what happened with those actions, what worked, what didn't, and deciding what comes next. The value compounds because each conversation builds on the one before it.
The Now What also sets the agenda for any follow-up meetings during the month. It informs the budget or forecast recast you're going to need when the next financial year rolls around — because you're building from real decisions and real actions, not from a spreadsheet exercise done in isolation. And most importantly, it ties you and the client together in an ongoing basis of value, month after month.
That's what makes advisory sticky rather than optional. The client isn't paying you because they need someone to produce a report. They're paying you because you're the person who holds the thread between what was decided and what actually happened.
And this is precisely why the framework naturally leads to budgeting and forecasting — rather than the other way around. A forecast built without months of What / So What / Now What conversations has no foundation. It's a spreadsheet disconnected from the business. A forecast built after six months of collaborative monthly planning is grounded in real decisions, real patterns, and real trust. The client has been part of the process the whole time. They understand the numbers because you've been translating them every month. The forecast becomes a natural extension of work they already value — not a new product you're trying to sell them.
Start With Less
If the idea of making strategic recommendations feels uncomfortable — if you're thinking "I'm a bookkeeper, not a CFO" — start where the risk is lowest. What we found worked was building the confidence in layers rather than trying to arrive fully formed.
Observations are almost zero risk. "Revenue increased eight percent this month, driven primarily by three new customers in the service line." You're stating what happened. You're not telling anyone what to do. And yet most monthly reports don't even do this much — they present the numbers without highlighting what moved and why.
Interpretations require a bit more confidence. "That growth is concentrated in your lowest-margin service, which means gross profit actually compressed despite the revenue increase." You're connecting dots the client can't see on their own. You're adding the "so what."
Recommendations are where the real value lives, and where the confidence gap is widest. "I'd recommend pausing the underperforming ad spend until we figure out what's driving the cost-per-acquisition spike. That should save four thousand a month while we investigate." You're taking a position — and that's uncomfortable until you've done it enough times to trust your own judgment.
Start with observations. Build to interpretations over the first few months. Add recommendations once you've developed the confidence and the client relationship to support them. That progression isn't timidity — it's the same path every advisory relationship follows naturally. The framework just makes it deliberate rather than accidental.
The Report and the Conversation
The framework works for both the written deliverable and the monthly conversation — and ideally, one feeds the other.
The report structured around the three questions gives the client context before you sit down together. They've already seen what happened and why it matters. The meeting picks up at the Now What — the decisions, the actions, the trade-offs that need a conversation rather than a document. You're not walking them through a spreadsheet. You're starting where the value is.
And the Now What from both — the report and the conversation — is what creates the thread forward. It sets the agenda for the next meeting. It informs the forecast. It's the reason the client opens the email next month instead of filing it away.
If you take one thing from this issue, it's this: pick one client and restructure the next monthly touchpoint around these three questions — in the report, in the meeting, or both. Pay attention to whether the response changes from "good meeting, thanks" to an actual follow-up question. That's how you know the structure landed.

Tool I'm Using: Fathom
Advisory work lives and dies in conversations — and conversations disappear the moment they end unless you capture them properly. We've been using Fathom for a number of years now for our meeting recordings, and whilst there are plenty of note-taking options out there — Notion offers one, Google Gemini records when you're on Google Meet, Zoom has built-in AI transcription — we keep coming back to Fathom for a few specific reasons.
The first is that it's platform-agnostic. It works across Zoom, Google Meet, Microsoft Teams — whatever your client happens to use. If you're running a practice with clients on different platforms, that matters more than any single feature.
The second is team recordings. Kristina and I can benefit from each other's client conversations where appropriate, which means insights don't stay locked in one person's head. For any practice with more than one person doing client-facing work, this is where the real value compounds.
And the third is the API. We can take Fathom's meeting templates, transcripts, summaries, and action items and feed them downstream into other tools and systems. The work they're doing on agent-less audio transcription keeps getting better, and they've recently added universal search across all of your meetings — so when you need to find what a client said about their pricing strategy six months ago, you can actually find it.
If you want to try it, this link gives you a free month of Premium: Get a free month of Fathom Premium →
Full disclosure: if you sign up through that link, I get a free month too. That's the extent of it.
Next Week
The best analysis in the world is worthless if your client can't access it. Next week, I'm getting into the delivery problem — why technically brilliant reports get ignored, what the "five-minute rule" is, and why the gap between the kitchen and the front of house is where most advisory attempts actually die.
If you've ever put real work into a client meeting only to get "good meeting, thanks" as they exit the meeting, that one's for you. Hit reply and tell me about it — I'm genuinely curious how many of us have had that exact experience.
shared.image.missing_image
shared.image.missing_image
Know someone navigating the compliance-to-advisory transition? Forward this email — or better yet, send them to baifokal.beehiiv.com to subscribe.get "good meeting, thanks" as they walk out the door, that one's for you. Hit reply and tell me about it — I'm genuinely curious how many of us have had that exact experience.
