Discl: Held IRL (and debating whether to pull the pin, either in entirety or further lighten position)
@reddogaustin , that was insightful. I took the next step of asking my buddy chat the follow up question" Or do the brutal exercise: what would an AI-native accounting stack look like if Xero didn’t exist?
I also asked the follow up question at the bottom of the Chat response, which I will put in a separate post.
The stark thing is, this response from your Chat, is the EXACT OPPOSITE of what XRO presented in their session yesterday, where they are investing in in FY26 and FY27, and what they believe is going to drive XRO growth through to at least FY2028..
Even if AI doesn’t replace Xero, it can still:
- Collapse willingness to pay for:
- Reporting
- Insights
- Forecasting
- Advisory-lite features
- Push customers to expect:
- AI included
- No surcharge
- Constant improvement
My dilemma is this:
1. I really cannot see the "no XRO" scenario playing out anytime soon. BUT is this just my pure bias at play and my simply refusing to accept what now "appears possible", theoretical as it is?
2. XRO is going down a path that seems very logical, and at pace. Advancements in AI are short term tailwinds for XRO as they leverage their customer base, data, domain knowledge etc. The more finance-centric AI there is, the faster will XRO be able to use, embed and deploy AI capabilities into the XRO platform. This absolutely strengthens the moat. Similar to AIM, it makes sense to use a combo of private and public AI to embed AI capabilities in the XRO workflows.
3. What proportion of the XRO SMB customer base is (1) savvy enough (2) has the time (3) and sees the value, to actually build their own AI non-XRO accounting stack, such that they would eventually say "see you later XRO, I am outa here because I now have my own stack that replaces you completely". While this is theoretically possible, is this real at all? No disrespect to SMB owners, but the ones that I have dealt with can't even manage their operations, their books, their billings, never mind build any self-taught capability to replace their basic accounting system using Claude ... Would any spare time that they have be better spent using Claude to improve their CORE business, the reason why they are in business, instead of their back end system which costs maybe $150-$200 a month?
4. If I accept that the XRO-replacement stack isn't happening anytime soon, then the XRO aggression today to roll out AI-capabilities, the pitch around FY27 being a continuous stream of AI initiative rolled out, monetised of course makes complete sense. Its XRO playing offense to embed the use of AI, make it so integral and an uplift in the workflow capabilities of the current SMB's and also attract new SMB's. Once onboard, the stickiness and network effects take over - I think this still remains true, even in an AI-centric view.
5. I can argue till I am blue, but I can't do squat if the rest of the market does not see things the way I do. Do I just accept the value destruction playing out right now, with Mr Market being irrational and that my view will ultimately prevail over time?
I am absolutely struggling with this. I am glad I lightened my XRO 3-4 months ago. But am still unsure what I will do at this point.
--------------
Yeah — this is the right next question. If you strip Xero out of the universe entirely and ask from first principles what an AI-native accounting stack would look like today, you end up with something that looks very different from “Xero + AI features”.
I’ll answer it cleanly, layer by layer, and then land the uncomfortable implication for Xero-like incumbents.
The core premise: AI-native ≠ SaaS with copilots
An AI-native accounting stack would not start with:
- a chart of accounts
- double-entry UX
- reports and menus
- human data entry metaphors
It would start with state inference and control, not bookkeeping.
Accounting, reframed for AI, becomes:
“Maintain a legally defensible financial state of an entity, with minimal human instruction.”
Everything else is secondary.
Layer 1: The primitive is not the ledger — it’s the event graph
Traditional accounting stacks are ledger-first:
- debit
- credit
- reconcile later
An AI-native stack would be event-first.
What that looks like
- Every raw financial signal is ingested as an event:
- bank transaction
- card swipe
- invoice received
- contract signed
- payroll obligation accrued
- tax liability triggered
- Events are not immediately booked
- They sit in a probabilistic event graph:
- who
- what
- why
- confidence
- reversibility
The “ledger” is a derived artefact, continuously re-materialised from events + policy.
This is already how modern data systems work. Accounting just hasn’t admitted it yet.
Layer 2: Policy engines replace charts of accounts
Charts of accounts are a human workaround.
An AI-native stack would instead have:
- A policy layer, expressed in natural language + constraints:
- “Meals under $300 are deductible unless client entertainment”
- “CapEx over $5k depreciated over useful life unless immaterial”
- “GST applies unless foreign supplier”
- Policies are:
- jurisdiction-aware
- auditable
- versioned
- testable
The model doesn’t “categorise”.
It applies policy to events and proposes state transitions.
Humans approve exceptions — not every transaction.
Layer 3: The ledger becomes a consensus artefact
Here’s the big break from Claude-style workflow tools.
An AI-native accounting system would still need a ledger — but:
- It’s append-only
- It’s cryptographically verifiable
- It’s reconciled by construction, not after the fact
Think:
- bank feeds
- payment rails
- payroll providers
- tax offices
All acting as co-signers of financial state.
The system’s job is to:
- propose the state
- collect confirmations
- surface conflicts
- resolve with minimal human input
This is where incumbents still matter — but the UX and economics change completely.
Layer 4: AI agents replace workflows, not screens
There are no “modules”:
- no invoicing screen
- no reconciliation page
- no report builder
Instead you have persistent agents:
Examples
- Ingestion agent
- monitors inboxes, banks, cards, contracts
- asks clarifying questions only when confidence drops
- Compliance agent
- watches jurisdictional rules
- flags upcoming liabilities
- prepares filings continuously, not quarterly
- Cash agent
- models liquidity in real time
- simulates scenarios
- initiates payments with approval thresholds
- Audit agent
- maintains an always-on audit trail
- answers auditor questions instantly with evidence
The “UI” is conversation + alerts.
Dashboards exist only for regulators and auditors.
Layer 5: Reporting is free, narrative is continuous
This is where traditional SaaS value collapses.
In an AI-native stack:
- financial statements are always current
- forecasts are continuously regenerated
- commentary is ambient, not requested
You don’t “run a report”.
You ask:
“Can I afford to hire two engineers in May if churn spikes 1%?”
And the system answers — with assumptions, confidence bands, and policy constraints baked in.
This is why reporting will never be a paid feature again.
Layer 6: Liability and trust become the real moat
Now the hard part — and the reason Xero still exists today.
An AI-native accounting stack must:
- accept legal liability
- be regulator-recognised
- survive audits
- integrate directly with tax authorities and banks
- guarantee data retention and immutability
So the winning players aren’t:
- model providers
- agent frameworks
- vibe-coded SMB tools
They’re the ones who can:
- underwrite risk
- hold licenses
- embed into financial plumbing
This is where AI startups stall and incumbents slow-walk.
So… if Xero didn’t exist, who would build this?
It probably wouldn’t look like a “software company”.
It would look like a hybrid of:
- payments processor
- compliance utility
- AI systems integrator
- regulated financial institution
Think:
- Stripe + OpenAI + a tax authority mindset
- —not a prettier accounting app.
The uncomfortable implication for Xero (and why your instinct is right)
If this is the destination, then:
- Xero’s current product is not the end-state
- Its moat is execution + trust, not UX or features
- AI doesn’t kill it — but it hollows out monetisable layers
- The multiple compresses because:
- upside is capped
- pricing power weakens
- differentiation moves out of the UI
Xero survives by becoming:
boring, critical, regulated infrastructure
—not magical SaaS.
Which is survivable.
But not dreamy.
Bottom line
An AI-native accounting stack would be:
- event-driven, not ledger-driven
- policy-defined, not category-based
- agent-orchestrated, not workflow-designed
- continuously compliant, not periodically reconciled
- liability-bearing, not insight-selling
Xero isn’t dead.
But it’s staring at a future where its best move is to disappear into the plumbing.
If you want, next we can:
- map which layers Xero can realistically own
- compare Xero vs Intuit in this future
- or ask the really brutal one: where does the profit pool actually settle?