06-reference

secret cfo mailbag pe boss title walkback

2026-09-01·reference·source: CFO Secrets (The Secret CFO, anon)·by The Secret CFO (anon)
cfo-frameworkspe-sponsorscareer-transitionstitle-levelingboard-dynamics

Why this is in the vault

Tue Mailbag, three anonymous CFO Q&As — who a PE-backed finance leader actually reports to, how to read a title walk-back after a reverse takeover, and a toxic-board horror story — kept for the title-walkback answer, which is a direct-fit lens for reading Ray's own role/title flux at phData.

The core argument

Three reader questions, answered in the anon CFO's voice:

  1. Who do you work for under a PE sponsor? (D, Toronto) — moving from VC-backed to majority-PE-owned, the sponsor hired her and expects direct access to the numbers, while the CEO is the day-to-day boss. Advice: maximum transparency, minimum side-channel politics. Force disagreements into the boardroom rather than brokering them privately. When the CEO and sponsor deadlock and the room turns to the CFO, have an independent, fact-grounded view anchored in the value-creation plan and exit thesis ("we all want the same thing") rather than sitting on the fence or taking a side clumsily. Set ground rules explicitly in induction meetings with both sides — "assume full transparency across the boardroom unless told otherwise" — so neither party can claim they were kept in the dark. TLDR: serve the business, not either parent.
  2. Title walked back after a reverse takeover (Sherlock, Europe) — ran the acquired (larger) business's finance function, expected Group CFO, got VP Finance with a dotted line to the acquirer's smaller-company CFO who kept the title; found out the CFO title had been drafted and pulled pre-announcement. Read: probably leveling mechanics (avoiding two CFOs in one org) rather than a hard ceiling signal, but the fact no one sat him down before the announcement is itself a data point — "clumsiness in the chaos" doesn't mean he shouldn't protect himself. Recommended move: don't fight for the title immediately, but professionalize the arrangement — get explicit criteria, decision rights, and timing for the CFO path in writing, and make sure the retention/comp reflects the actual scope being carried now. Keep the external market warm in parallel so a year in a lower title doesn't calcify into a market perception of his level.
  3. Board member goes to war with finance (Jiang, Singapore) — a NED joined mid-transformation, escalated over email with no real substantiation, the CEO's support evaporated within weeks, ending in a bogus misconduct investigation and termination. Answer is short: this reads as someone else's political dysfunction, not a signal on Jiang's competence. TLDR: get out.

Mapping against Ray Data Co

The title-walkback answer (Q2) is the concrete one. Ray is currently sitting inside his own version of "the title says less than the scope" at phData — role is explicitly framed as DSA + TAL, not SE ([[project_phdata_cert_escalator_path]]), and the CAF→Organizational Intelligence reframing (retired 2026-08-10, per [[project_caf_pm_role]]) is a live example of scope and naming shifting under him mid-stream, decided elsewhere, communicated after the fact. The Secret CFO's diagnostic — "leveling mechanics vs. ceiling" isn't binary, and the absence of a clear sit-down conversation is itself the real signal worth acting on, independent of which explanation turns out to be true — is a usable gut-check the next time a phData title/scope question surfaces: don't demand the fix immediately, but do get criteria, decision rights, and comp-for-scope in writing, and keep the external narrative warm rather than assuming a year at the current label is neutral. That's the same discipline as the seat-gap thread the founder already rejected the employment frame on ([[project_income_seat_gap_400k]]) — the risk isn't the label, it's letting the label go unexamined for a year.

Q1's dual-principal dynamic (PE sponsor as capital-and-hiring authority, CEO as day-to-day boss, CFO caught between) is a weaker but real echo of RDCO's own CFO-seat/finance-ops convergence thesis this sender has repeatedly reinforced: any RDCO engagement with a PE-backed or sponsor-governed client will hit the same "who do I actually answer to" ambiguity, and "force it into the room, don't broker it privately" is directly reusable proposal-stage advice.

⚠️ Sponsorship

Sponsored placement: Ledge (accounting-agent software — reconciliations, working papers, journal entries for close/audit season), presented as a short product-demo video CTA ("agents build the close," under 3 minutes) up top of the issue. Ledge is a known member of CFO Secrets' rotating sponsor pool (confirmed alongside Campfire, Zip, Pulley, Stuut, Una, Summation, Nominal, CloudZero per the standing tracker at 01-projects/process-newsletter/README.md) — no new sponsor in this issue.

Related