Why this is in the vault
Part III of the "Inheriting a Shitshow Finance Function" series — the operating model for running a broken finance function while still repairing it, directly useful vocabulary for any RDCO client engagement that lands mid-turnaround.
The core argument
A newly-inherited, broken finance function can't pause operations to fix itself — month-end, year-end, and Board asks keep landing mid-repair. The prescribed fix is a deliberate "Repair Mode" operating model: ring-fence legacy balance-sheet issues into one controlled cleanup rather than scattering fixes across the org, then sequence effort inward (core transactional processes) and backward (reliable monthly reporting) before earning the right to invest in forward-looking forecasting, upward business partnering, and outward stakeholder management. Governance centralizes even when execution doesn't; forecasting fidelity should deliberately lag actuals fidelity; stakeholder messaging must stay singular and consistent to preserve trust and buy time. The author frames it as "bailing water out of the hull" while the ship keeps moving.
⚠️ Sponsorship
Stuut (AI-powered AR/collections calling tool) sponsored via a case-study callout (HiBid CFO Chris Stiegal; 21-day time-to-live, ~7,000 accounts, $4.9M collected, halved write-offs) plus a "Book a demo" CTA and a footer "Thank you to our sponsor: Stuut" block. Disclosure is soft — a "Sponsor" banner image and footer thank-you line, no explicit "paid advertisement" language.
Series-sponsor pattern now at 3 of 3: Stuut has sponsored Parts I, II, and III of "Inheriting a Shitshow Finance Function" — matching the confirmed pattern already seen with Summation/Man Utd and Summation/"Building FP&A." Treat Stuut as the de facto standing sponsor for this series specifically; the broader CFO Secrets rotating-pool framing (Campfire, Zip, Pulley, Stuut, Una, Ledge, Summation, Nominal, CloudZero, Aleph) still holds for Sat Playbook/Tue Mailbag/Boardroom Brief issues outside this series. Watch the teased Week 4 (transitioning out of repair mode) to confirm whether Stuut closes out the full series 4-for-4.
Mapping against Ray Data Co
The inward→backward→forward→upward→outward sequencing is a reusable diagnostic for any RDCO/phData engagement that inherits a broken function (finance or otherwise): don't let stakeholder-facing deliverables (forecasts, business partnering) outrun the reliability of the underlying transactional layer — a direct echo of RDCO's own "instrumentation before targeting" discipline in the [[project_targeting_system_prioritization_filter]] four-layer filter. The "ring-fence legacy issues into one controlled cleanup" move also maps to how RDCO should scope any inherited-mess client statement of work: isolate the cleanup as its own workstream rather than letting it bleed into ongoing delivery commitments.
Curation section
- Week 1 (Part I): "how to spot a broken finance function" — https://www.cfosecrets.io/p/inheriting-broken-finance
- Week 2 (Part II): "Bring Out the Dead" (balance sheet colonoscopy) — see [[2026-09-12-cfo-secrets-bring-out-the-dead-ii]]
- Tangential YouTube embed (firecracker-under-a-pot) used only as a metaphor, not a resource recommendation
- Week 4 (teased, not yet published): transitioning out of repair mode
Related
- [[2026-09-05-cfo-secrets-inheriting-shitshow-finance-function-i]]
- [[2026-09-12-cfo-secrets-bring-out-the-dead-ii]]
- [[project_targeting_system_prioritization_filter]]