06-reference

cfosecrets finance stack of the future unbundled erp

2026-04-28·reference·source: CFO Secrets·by The Secret CFO
cfotech-stackunbundled-erpfinance-operating-layerharness-engineering-cluster

Building Blocks: The Future Tech Stack - CFO Secrets Mailbag

Why this is in the vault

A Mailbag-format reply to a UK manufacturing CFO ("Bob") asking whether to replace his legacy Sage 200 ERP. The Secret CFO's response goes well past the question: the future finance tech stack is unbundled, best-of-breed, and connected via APIs, not a single monolithic ERP replacement. The post is a direct extension of the Buy / Build / Borrow framework from AI-for-CFOs III, applied to legacy ERP migration. RDCO files this because (a) the unbundling argument is the buyer-side mirror of the harness-engineering thesis (composable substrate + specialist applications), (b) the response models how to read tech-stack questions through a workflow-decomposition lens rather than a vendor-comparison lens, and (c) it surfaces two new tracked-author candidates (Shaka Nestoris and "Mark from Munich") who pitched their own writing publicly in the Mailbag.

The argument

The historical bet was the unified ERP - one system of record for accounting, manufacturing, inventory, payroll, and CRM, with everyone tolerating the worst-of-each in exchange for "one source of truth." That bet is breaking. Modern API-connected best-of-breed tools beat the monolith on every functional axis. The decision frame is: decompose the workflow into atomic units, find the best vendor at each unit, and treat the integration layer as the strategic asset. "Break the problem into accounting and manufacturing... find the best option at each atomic level."

For Bob specifically: don't replace Sage 200 with another monolith. Pick a modern accounting core (Campfire-class, AI-native) and pair it with a specialist manufacturing system, integrated via API.

Operational specifics

Mapping against Ray Data Co

Against the harness-engineering thesis cluster

This is the buyer-side mirror of the harness-engineering thesis. The argument is structurally identical to [[06-reference/concepts/2026-05-10-harness-moat-two-layers-portability]]:

The CFO seat and the AI-builder seat are independently arriving at the same architectural conclusion. This is the second strong cross-validation of the harness-engineering thesis from CFO Secrets (the first being the AI-for-CFOs III Buy/Build/Borrow framing).

Against MAC

Indirect: the unbundling argument implicitly assumes a layer that watches data quality across all the unbundled components. That layer does not exist for most mid-market finance stacks. MAC is the data-quality substrate that makes the unbundled stack safe to operate. Worth a Sanity Check angle: "If you unbundle your ERP, you also unbundle your data-quality assumptions. Here's what fills the gap."

Against Sanity Check (voice / cadence study)

Two notes:

Tracked-author candidates surfaced

Sponsorship

Summation sponsored this issue (top-of-newsletter + embedded demo CTA). Campfire is referenced in the editorial body as an example of the AI-native accounting layer Bob should consider, but is NOT the paid sponsor of this issue - separate disclosure. Worth noting: the author treats Campfire as an editorial example even when not being paid, consistent with his stated investor/user position from the AI-for-CFOs series. Sponsor entity to tag forward: Summation.

Related