Welcome Back to This Week’s Mailbag

When you’re driving your kids to daycare and Mase’s Welcome Back comes on the radio

This week we have the following CFOs answering your reader questions:

If your question is picked for the Mailbag, you’ll win a Mostly Metrics Yeti Rambler ($84 economic value, unlimited street cred).

Topics for today:

  1. Will the CFO / COO / CIS roles become one?

  2. Should I change our definition of land vs expand ARR?

  3. How will R&D spend change with AI?

  4. What close management tools are you using to speed things up?

  5. How do you bucket your R&D spend?

  6. How do you determine which members of the management team present at each board meeting?

Now let’s get into it!

Question #1:

Something you’ve likely talked about in the past so may be more of an evolution or update, but I’m increasingly interested in where the CFO org is going as it pertains to the intersection of CFO/COO/CIS roles - largely focused around AI/data/strategy.

Do all of these collapse into one? And, if I want to be a CFO, how does that change what I need to be good at (for context, I’m prob 5 years away)?

Peter, Boston

One Role to Rule Them All

Rob from Employment Hero:

I don’t think these roles fully merge, but the overlap is legit and getting larger.

The CFO is increasingly the connective tissue between strategy, data, AI, and risk (especially when you think about customer data/privacy in an HR/payroll software business like mine). AI pushes this hard because finance sits closest to the source of truth and can better articulate the trade-offs.

If you want to be a CFO in ~5 years, the job is less about accounting mastery and more about judgment: capital allocation and understanding how AI changes messy data into decisions. You don’t need to code, but you do need to understand systems, incentives, and where the bottlenecks are. The lines between CFO and COO are definitely blurring.

Matt from Superhuman:

I don’t think there’s a single, final version of the CFO role. Job titles can be misleading, and context really matters.

From my career - at Coda, Superhuman, and Google - the CFO title meant something different at each place. The industry matters too. For example, a software CFO needs to understand AI, data, and product speed, while a manufacturing CFO needs to deeply understand the movement of physical goods. The skills and work should match how the business creates value.

The other big variable is the management team you’re on. Organizations adapt to the people within them. I’ve played closer to product on some teams and closer to GTM on others. The CFO/COO/CIO blend is less about org charts and more about who’s best positioned to own a decision and the responsibility behind it.

Hemant Tenaja (CEO of General Catalyst) is an investor I’ve worked with closely for the past 10+ years. And at one point, he gave the advice to “play your game” - don’t play to the expectations of others.

Said differently, learn where you get energy and what you’re good at, develop that as a deep spike, and then join teams and companies where that creates alpha in the role.

Others may see a “CFO” title, but what matters is how you complement the management team, solve problems, and help build a winning company.

Robert from BillGO:

I think the CFO org stays intact (FP&A, Treasury, Controllership, Procurement). However, the clear lines of other organizations (COO/CIO/InfoSec) will continue to blur across the enterprise.  In one direction, the CFO org will play a more influential role across the enterprise to provide important insights with capital allocation, customer analytics, operations, risk management and compliance. And in the opposite direction, the Finance org will be heavily reliant on InfoSec teams for better data insights and more automated reporting.  

So, even with the blurred lines, Finance will remain a separate org, as it will still need to maintain independence and be the overall steward of data integrity across the organization.

This notion of independence will need to be maintained across strategy (likely in COO org), as Finance can serve as a "check" or independent assessment of capital allocation and would be best suited to ascertain buy, build, or partner analysis.  

What this means for an upcoming CFO... master financial management (table-stakes), understand how all the other teams interplay across the organization, and understand how enterprise data is best managed.

Question #2:

In a land small and expand model, how should I weigh changing our corporate definition of new vs. expand? (ie. We've discussed changing the definition of new to include the initial land and first 3-6 months of expansion. This would obviously increase our New ARR in the bridge, however, it would also lower our net retention).

Natalie, New England

Rob from Employment Hero:

You can change definitions, but you can’t change reality. Rolling early expansion into “New ARR” might make sense internally if that’s how customers really ramp. But externally, be careful. Investors anchor hard on NRR as a signal of product strength. Juicing New ARR at the expense of NRR usually backfires.

My bias: keep external definitions clean and consistent, and run a separate internal view that shows “land + ramp.” If you do change definitions, do it once, explain it clearly, and never touch it again.

Matt from Superhuman:

I’m a bit of a purist about this.

Your metrics should reflect how customers actually use your product, not just what looks good on a board slide.

In a land-and-expand motion, I’d anchor on which signal captures the most meaningful economic commitment for the product. If your motion is truly PLG-first and then upsell into a managed motion, I’d define New ARR as that very first credit card purchase. That’s when the customer decides, “This product is now part of my workflow.”

If your managed sales process is more independent, and you’d never close a deal without a salesperson, then I’d define New ARR as starting with the first enterprise contract. In that case, product-led growth is more about generating leads than driving revenue.

Those are the two extremes, but most companies fall somewhere in the middle. Smart investors will easily see through definition hacks - especially when they start modeling the business themselves. And at the end of the day, you want your definitions to reveal the underlying dynamics of your business, not obscure them or excessively inflate one aspect.

Questions #3 and 4:

Two-part AI tools question:

1. With AI coding tools do you expect companies to become more efficient in R&D (spend less for the same results), or spend the same % of revenue but expect faster innovation & product releases?

2. What specific AI tools are you using to accelerate month-end close? I'm having a hard time believing an agent could make sense of the complex excel templates we plop data into, but am very willing to be wrong.

McParty, Phoenix

responses…

Rob from Employment Hero:

On R&D, I expect companies to spend roughly the same % of revenue, but ship more and faster. The winners won’t cut R&D - they’ll reinvest the productivity gains into speed and experimentation.

On close: we’re not at one-click month end, but AI already helps more than people think. The biggest wins aren’t fancy agents inside Excel - they’re upstream. Auto-recs, anomaly detection, variance explanations, draft commentary. If your data is clean (you put sh*t in you get sh*t out), AI saves a ton of time. If it’s messy, no agent is saving you.

AI doesn’t fix broken finance hygiene - it just exposes it faster.

Matt from Superhuman:

In the medium term, I think R&D spending as a percentage of revenue will stay about the same, but output will keep growing. Competition will drive this.

AI tools make every software development team more productive. You could take that to the bottom line, but in competitive markets, the real move is to reinvest in more experiments, shortened feedback loops between product, sales, and customers, and bolder roadmaps. These productivity gains will lead to way more software getting created.

To the finance angle specifically, IMO we’re still early. At Superhuman, we’ve been experimenting with a small set of packaged tools - for example, shifting from FloQast to Numeric - and general-purpose productivity (Claude, ChatGPT, etc.), but I haven’t yet seen the “vibe coding moment” for month-end close or Finance/Accounting processes generally.

That said, even if we get there, I’m betting that we will continue to have some form of human-in-the-loop process - perhaps shifting away from “black-pen” work (where you do it from scratch) and more “red-pen” work (reviewing agentic outputs).

Robert from BillGO:

Part 1: While I do expect the innovation and product release cycle to speed up, I also believe there will be some increase with cloud usage which may partially offset the ROI. Still early days on innovation, but likely the expectations across any market participant, in order to effectively compete, is to leverage AI tools. 

R&D % may come down initially (less incremental headcount required), but I believe this will likely have to increase as all companies will gravitate towards the new innovation paradigm, and eventually will require additional investment to generate a competitive advantage (whether that be lowest cost or product value). These added costs may come in the form of incremental cloud (likely COGS allocation) but may also find themselves with AI licensing (yes, I do expect these subscriptions to go up with the billions being poured into the sector) and a retrained middle management layer that will manage junior engineering and AI team members.  

Part 2: I have yet to find an AI tool that can effectively manage a close. Not to mention leveraging any AI tool within Finance requires clean, high-quality data that would minimize any errors with accounting.

That being said, automation plays a critical role with shortening our monthly close process. For us, revenue accounting estimates are usually conducted at month-end after aggregating all upstream data files (i.e. not enough rows in Excel) that have been received through the last day of the month and reconciling this data to our cash balances with our partner banks; this often spills across several days post close to synthesize the data and accrue for any estimates. We are now beginning to employ transaction level matching and cash reconciliation on a daily basis to truncate monthly close - the tool we employee is called Trintech.  

So automation can still play a huge role with speeding up the monthly close. However, I have yet to see AI deliver month-end financial statements, as producing financials still requires accounting judgement based on management decisioning within GAAP.

Question #5:

When you think about how much money the company puts into R&D, what % goes to keeping the lights on vs improving existing products vs innovating net new stuff?

And, do I have those buckets right?

How do you split it up?

Joseph, PA

Rob from Employment Hero:

I think about R&D as Run, Win, Expand.

  • Run: keep the lights on - compliance, security, reliability

  • Win: make the core product better - retention, expansion, GTM leverage 

  • Expand: new bets that grow TAM

At scale, Run is usually ~40%, Win ~40%, Expand ~20% (give or take). If Expand gets too big without proof, returns fall off a cliff. If Run gets too big, velocity dies. The CFO’s job isn’t to starve Run - it’s to keep pushing it down over time so you can fund Win and Expand without wrecking margins.

Matt from Superhuman:

I loosely follow a 70/20/10 rule that I’ve borrowed from my time around Google-style operators.

  • 70%: The Core: This isn’t quite “maintenance;” it’s where your economic engine already works.

  • 20%: Emerging Growth: This is where you’ve found signal and now need scale. You’re still iterating, but the unit economics are trending in the right direction.

  • 10%: Net-New, Speculative Bets: This is where you buy optionality, especially in an AI-native world. Small, focused teams exploring new product surfaces, models, or GTM plays. This is where you tolerate ambiguity but insist on fast learning cycles.

Protect the 70, rigorously curate the 20, and time-box the 10.

Robert from BillGO:

Ultimately, you want to get towards an effective balance were 50%-60% goes into keeping the lights on and 40%-50% placed on innovation. Many companies, particularly within FinTech, have amassed complex tech infrastructure and cumulated significant technical debt along the way; thus having to allocate 70%-80% of R&D with maintaining platforms. Not where you want to be.

Question #6:

How do you determine which members of the management team present at each board meeting? Is it predetermined at the start of the year, or more of a flavor of the week, depending on what's going on? We want to give the right people face time. Also should the CRO present at all of them? What about the CFO?

Shauna, Texas

Rob from Employment Hero:

CEO and CFO every meeting. Non-negotiable.

CFO provides continuity across performance, and capital - boards expect that. CRO should present when GTM, efficiency, or growth motion is changing, not just by default. Other leaders should present when there’s a decision, risk, or inflection point - not for visibility.

Boards don’t want airtime, they want the truth on what’s relevant at that moment. Simple test: if you’re not asking for input or alignment, you probably shouldn’t be presenting.

Matt from Superhuman:

I don’t begin with a set schedule or speaker rotation. Instead, I focus on what the board meeting needs to accomplish. A good board meeting does three things, in this order:

  1. It forces a clear narrative. It pushes our team to get their story together around our strategy, how it’s working, and what we are doing next.

  2. It arms the Board as advocates. If they understand the story, they can then sell it to investors, candidates, and the market.

  3. They can pressure‑test a short list of decisions. The management team runs the business, but the Board can be helpful in pattern-matching for a small number of key decisions (e.g. < 3).

Once you see it that way, who presents becomes a design choice rather than a template.

Robert from BillGO:

I typically see the CEO and CFO in all sessions (excluding CEO debriefing with the Board).  The CFO will present Financial snapshot of where the company is (performance and cash), current outlook, and known risks & opportunities. The COO may come in to present updates around key OKRs and discuss customer pipeline. 

Ultimately, the presenters are up to the CEO, but my recommendation is to keep the attendees consistent with an emphasis on transparency and objectivity in order to build trust and cultivate the right level of dialogue.    

Wishing you a define your expansion ARR the right way,

CJ

Reply

Avatar

or to participate