The pattern, before finance
Business users already run marketing inside Claude. They run sales inside Claude. They run operations inside Claude. The pattern is consistent: when the AI tool is good enough to do the work, the standalone SaaS app it replaces stops being the place the work happens.
The work moves up the stack. The interface collapses. The vendor logos that used to live in a sidebar become workflows that live in a conversation. None of these companies disappeared in a single quarter. They disappeared as the place where the work happens.
Why finance is the next domain
The reasons are structural, not speculative.
Finance work is overwhelmingly text and structured data. Journal entries are text. Reconciliations are structured data. Bank statements are CSV. Invoices are PDFs. Payroll is a deterministic calculation against a tax table. These are exactly the inputs LLMs handle best.
The artifacts of finance are deterministic outputs. A journal entry is right or it is wrong. A statutory filing matches the schema or it does not. A trial balance balances or it does not. The validation layer is the entire game. AI doesn't need to be creative; it needs to be correct, and a human needs to sign the correctness.
Country and industry logic is fundamentally encodable. The complexity in any ERP is rules: Estonian VAT thresholds, US revenue recognition timing, German chart-of-accounts conventions, industry-specific accruals. This complexity has historically lived in PDFs, in consultant heads, and in customisation layers that vendors charge separately for. It is the kind of expertise that wants to be code.
The capability stack is finally complete. Skills, Artifacts, Plugins, Connectors, Managed Agents, MCP — before October 2025, the pieces were not all assembled. After, they are. The primitives now exist to build a finance system that runs natively inside Claude rather than wrapping an LLM around a fixed UI.
What changes when finance lives inside Claude
Three things at once.
The interface collapses. There is no "finance app." The user types or speaks; the AI tool renders the result as an Artifact, a table, a filing, or a conversation. The screens that used to be the product become artifacts produced on demand.
The customisation layer becomes code. Country rules and industry logic ship as Plugins. They are versioned. They are forkable. They are reviewable. They are owned by the people closest to the work — accountants and controllers — not by vendors.
The accountant's role shifts from operator to validator. AI executes. The accountant reviews, signs, and owns judgement. This is the central labour-economic shift. It is also the wedge for the firm channel — firms see the disintermediation risk in pure-play AI-ERPs and prefer a substrate they can wrap services around.
Why this is infrastructure, not a feature
Every AI-finance product currently shipping is built on the assumption that the UI is the value. They wrap an LLM around a fixed set of screens and call it AI-native. We are building on the opposite assumption: that the durable value is the ledger and the composable logic layer underneath the AI interface. Whatever AI tool the user is in today — Claude, Cursor, eventually others — renders whatever surface they need.
Defensibility comes from being the substrate others build on, not from feature parity with traditional ERP.
The bet, in one paragraph
If software is disappearing — and the evidence across marketing, sales, and operations says it is — then someone builds the financial infrastructure layer for businesses operating inside AI tools. That layer doesn't look like a faster ERP. It doesn't look like a better UI. It looks like a stable ledger, an open logic layer, and a thin integration surface into whatever AI tool the user is in today. The competitors who win features won't win the category. The category goes to whoever owns the substrate.
If we're right about the AI-interface bet, the gap between us and the AI-ERP camp is structural — they have to rewrite from scratch to catch up. If we're wrong, we're wrong. There's no middle position. That's the bet, and it's why being early on the capability stack matters more than any individual feature.
Everything else is execution.
Andrew Rudchuk
Comments and disagreement welcome at hello@ar-ti-fi.com.