Why this is in the vault
Tuesday Office Hours mailbag, three reader questions: negotiating your own raise while running a tight budget, picking the handful of KPIs that actually matter, and how an FD should operate after a PE buy-and-build acquisition — kept for the third answer's board-reporting and platform-CFO-relationship playbook.
Issue contents
- Growing Resentment (UK) — How does a CFO who built the budget ask for their own raise when cash is tight? Answer: separate fair pay (market benchmark, independent of affordability) from affordable pay (phasing, retention bonus, equity/LTIP), and reframe the ask as "permission to spend 30 minutes on my own position" rather than a confrontation. TLDR: agree what you're worth first, then negotiate timing.
- BackToBasics (NY) — How do you choose the "at-a-glance" metrics for a business when there's no obvious cash-health equivalent outside VC burn/runway? Answer: three-question framework — (1) are customers buying and staying (NPS, retention, churn), (2) can you make money doing it (contribution margin, unit economics), (3) can you finance the journey (burn, runway, working capital) — with the metric set evolving into a fuller scorecard as the business matures.
- First Time PE (UK) — An FD at a £30m company being bought into a £100m PE buy-and-build platform asks how to keep making a good impression, especially on board reporting. Answer: understand the underwriting/value-creation case first rather than contesting it; own delivery (not just reporting) against it; keep board reporting to four blocks — performance scorecard vs. plan, revenue bridge (opening recurring revenue → renewals/churn/upsell/new business → closing), value-creation-plan progress, and risks/actions; align KPI definitions with the acquiring group's; and treat the platform CFO (not the PE sponsor directly) as the critical relationship.
Mapping against Ray Data Co
The genuine throughline is narrow: it's the PE buy-and-build answer (#3), not the salary or KPI-framework questions. The "align metric definitions with the acquiring group, standardize the board scorecard, make the platform CFO's life easy with consistent numbers" pattern is a concrete instance of the Organizational Intelligence problem this vault already tracks under the retired-CAF/OI framing (Org Platform → Org Map, Intelligence Platform → IMA) — see project_caf_pm_role — namely: when ownership or org structure changes, the hard problem isn't producing a report, it's reconciling definitions and data lineage across newly-combined units so numbers from different sides of the acquisition mean the same thing. That's exactly the kind of cross-entity metric-standardization work an org-intelligence layer would exist to automate.
That said, honesty check: RDCO itself is dormant (project_rdco_dormant_phdata_main) and not pursuing CAF/OI as an active build, so this is evidence filed for a thesis currently on ice, not a live roadmap input. The KPI-selection answer (#2) is generic good practice (customer value → unit economics → liquidity) but doesn't sharpen any specific RDCO decision — no sort-order argument, no tool shape. The salary-negotiation answer (#1) is pure personal-career material with no RDCO angle. Filed primarily for the PE-platform-reporting pattern; the rest rides along because it's the same issue.
⚠️ Sponsorship
The issue opens with a paid placement for Numeric's free "Finance Engineer Course" (five modules: data foundations, Claude skills, AI-era control, tech stack), tagged utm_source=secret_cfo&utm_medium=paid-newsletter&utm_campaign=finance-engineer. Numeric is a recurring CFO Secrets sponsor (confirmed in the existing rotating pool: Campfire, Zip, Pulley, Stuut, Una, Ledge, Summation, Nominal, CloudZero, Aleph, Numeric, Airwallex). Bias implication: minimal here — the sponsor content is cleanly separated from the mailbag Q&A and doesn't touch the three editorial answers, but note Numeric sells finance-automation tooling adjacent to the "finance engineer" framing this same newsletter has promoted editorially in other issues — mild soft-advertorial alignment to watch for, not present as a conflict in this specific issue's advice content.
Related
- [[2026-06-16-cfo-secrets-jumping-ship-pe-sponsor]] — prior mailbag on vetting/surviving a PE sponsor relationship; directly complements this issue's "make the platform CFO's life easy" advice.
- [[2026-09-29-secret-cfo-too-good-for-pe-fund-mailbag]] — another recent PE-ownership mailbag answer from the same author; useful to track how the PE-operator advice is evolving issue to issue.
- [[2026-09-22-secret-cfo-secret-salary-cyber-security-mailbag]] — prior mailbag with a compensation-conversation question, for comparing how the author's salary-negotiation framing has been consistent across issues.
- [[project_caf_pm_role]] — the retired-CAF/Organizational Intelligence framing this issue's PE-platform answer is mapped against.