In the first three editions of Intelligence inside, Elias and Kevin explained the foundations: why the bar for AI in finance and tax is higher than in almost any other software category, how we built the Intelligence Core and its trust architecture, and how the Data Platform and semantic layer give our agents a governed, grounded single source of truth to reason over.
That bar, trustworthy on day one, traceable on day two, defensible in front of an auditor on day three, is not just a design principle. It is the filter every product decision in my team goes through.
This edition is about what that filter produced: a year of intelligent features already live across our CFO Solution Platform. Not announced, not in beta, not on the roadmap. Shipped, in production, and in use.
The rule we apply to every feature: does it earn the right to be there?
Kevin described the division of labor clearly: deterministic logic does the calculation, intelligent reasoning does the interpretation. That distinction is not just a technical choice. It is a product discipline that we apply before a feature gets built.
The question I ask before any intelligent capability gets close to a customer is simple: does this deserve to be in a CFO's workflow? Not “is it technically impressive?” Not “does it work in a demo?” Does it solve a specific, named problem in the way a finance or tax professional would want it solved, with full visibility, full control, and no surprises?
Every feature I will describe below passed that test. Each one takes on the repetitive, judgment-heavy, or expertise-dependent work that slows teams down, and hands the result back to the professionals for review.
The intelligence does the work. A human approves it. That is not a constraint, it is the design.
What that looks like in practice varies by solution. But the principle is consistent across all of them.