AR\TI/FI · THESIS · v1 · MAY 2026 · FOUNDER-AUTHORED

Software is disappearing. Finance is next.

The durable layer is not the UI. It is the ledger and the open logic that runs on top of it. Whatever AI tool the user is in today renders the surface they need. Everything else is execution.

THE PATTERN, BEFORE FINANCE

The work moves up the stack. The interface collapses.

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 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
01
Finance work is 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. Exactly the inputs LLMs handle best.
02
The artifacts are deterministic
A journal entry is right or it is wrong. 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.
03
Country and industry logic is encodable
Estonian VAT thresholds, US revenue recognition, German chart-of-accounts conventions — complexity that lives in PDFs, consultant heads, and paid customisation layers. It is the kind of expertise that wants to be code.
04
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 finance natively inside Claude, not wrap an LLM around a fixed UI.
WHAT CHANGES WHEN FINANCE LIVES INSIDE CLAUDE
The interface collapses.

There is no “finance app.” The user types or speaks; the result renders as an Artifact, a table, a filing, or a conversation. The screens that used to be the product become artifacts produced on demand.

Customisation becomes code.

Country rules and industry logic ship as Plugins — versioned, forkable, reviewable, owned by the people closest to the work: accountants and controllers, not vendors.

Operator becomes validator.

AI executes. The accountant reviews, signs, and owns judgement — the central labour-economic shift, and the wedge for the firm channel: a substrate firms can wrap services around.

THE BET, IN ONE PARAGRAPH

If software is disappearing, someone builds the financial infrastructure layer for businesses operating inside AI tools. That layer doesn't look like a faster ERP or a better UI. It looks like a stable ledger, an open logic layer, and a thin surface into whatever AI tool the user is in. 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, founder of Artifi
ANDREW RUDCHUK · FOUNDER · TALLINN, ESTONIA
WHO'S BEHIND THIS

Built by the person who had to close the books.

Artifi is founded and built by Andrew Rudchuk. Not as a thought experiment — as the answer to work he was doing himself: running finance operations across entities and countries, and watching every automation attempt either fork into unmaintainable custom code or die as a demo.

The platform's internals are published, not pitched. The block engine, per-org patches, dry-run mode, and the effect-guard design are all documented in the Building the Agent Platform series — real architecture, real confidence thresholds, and the incidents that shaped them. Comments and disagreement are welcome at hello@ar-ti-fi.com.

The company is Arfiti Technologies OÜ — Tallinn, Estonia. Small by design: the product is the leverage, and the discipline is written into it — capability only after containment, dry-run before live, evidence before autonomy.

Disagree with the thesis?

Good. Write to us — or watch it run on your own books first.

Book a working sessionSee the product →