Why this is in the vault
CJ + Paul Stansik (ParkerGale PE operator, who was literally acting-VP-of-Sales at a portco during the interview) lay out five concrete ways a finance leader earns trust with the sales org instead of being the receipts cop. The value for RDCO is half voice-study, half operating-model. The substantive content is a CFO-to-sales playbook that doesn't directly map to a solo-founder business, but two ideas (segment the top line so you can diagnose misses; make metrics mean something in the recipient's own terms) transfer cleanly to RDCO's client-reporting and multi-bet attribution posture. The bigger reason to keep it is voice: this is the cleanest recent example of CJ's profane-practitioner register, useful as a Sanity Check tonal reference.
⚠️ Sponsorship
Brex is the top-of-newsletter primary sponsor in a paid rotating slot (rotation set also includes Intuit / Samsara / Rivian / MLB / Abacum; only Brex appears in this edition). The placement is reinforced by CJ being a customer ("That's why I use Brex") and Mostly Metrics being named alongside Anthropic, DoorDash, and Coinbase as Brex users. The ad block is structurally separate from the article body and there is no editorial entanglement in the five-point analysis. Second-house plug at the bottom for Mostly Talent, CJ's own recruiting arm. Disclosing both as commercial placements.
The core argument
Finance leaders at startups get handed problems outside finance, and the most common ask is "how do I help sales?" CJ rejects the usual woo-woo "be a team player" answers and, with Paul Stansik, lands on five concrete moves:
- Make the budget mean something — Don't treat annual budgeting as a toll booth. It's the one moment you force leadership agreement on current state, biggest opportunities, and the next twelve months. Paul's top tip: segment the top line (by product, region, or motion). Plan bookings as a segmented number, not a monolith, so when you miss three to six months later you have scaffolding to diagnose instead of reverse-engineering what broke. The number will be wrong at first; it gets better as you collect data points.
- Help emphasize forecasting — The muscle to move a deal and the muscle to forecast accurately are different muscles; most sales leaders are great at the first, still building the second. Finance should be a pressure valve, not an interrogation light. Whiteboard the forecast model (inputs, stage definitions, progression rules, certainty per step) before the sales leader has to defend a number with the CEO in the room. Citing Dave Kellogg: help is defined by the recipient, not the giver. Interrogating slipped deals in front of the CEO just gets you a sandbagged forecast next quarter.
- Lend a hand with data and metrics — A ~$20M-revenue org has excess analytical capacity in FP&A, not in sales. Point it across the aisle: forecast support, CRM hygiene, cohort analyses, deal-cycle measurement. Frame it to your analyst as development, not a loan. Crucially, make metrics mean something in the sales team's own terms — CJ's NDR anecdote: he droned on about net dollar retention for quarters until he spent 60 minutes walking the SVP of Sales through the four levers underneath it, after which the SVP internalized it and played it back. Paul's framing: connect the metric to the multiple, the multiple to the outcome, the outcome to what each equity holder gets, so GTM builds a durable, sellable revenue engine.
- Get involved in a few key RevOps spots — Momentum often dies after the sale, not during. The front end of commercial processes is over-engineered relative to the back end: a verbal yes followed by two weeks for a quote is a terrible payoff. Paul's frame is "selling with certainty" — anything in the quote that adds doubt (an empty discount column, an unbroken multi-year cost, a vague "implementation services" line) gives the buyer's brain a reason to pause. Tangent: kill SKUs; a long menu creates rep indecision that passes to the customer. CJ's steal-able move: at a pre-IPO company fighting public competitors for enterprise logos, every above-threshold-ACV quote included a first-person one-page letter from the CFO (with a headshot) stating investors, cash in bank, runway, and growth rate — killing the unspoken "will this company still exist in 5 years" objection. At seven-figure ACVs the buyer is risking their career, not just budget.
- Build a great relationship with sales — The one "feelings" point: none of the above works without trust. If the sales leader thinks finance is building a case to fire them, the forecast comes back cooked. Paul: "You can't fix a secret." The fastest way through is relentless curiosity — asking and listening, not explaining what you think they should work on. The best CFOs CJ has interviewed have higher EQ than IQ; the job is pulling ugly things out of dark corners into conversation so management can resolve them.
Mapping against Ray Data Co
Mapping: weak-to-medium, mostly as voice-study. This is a CFO-to-sales-org piece written for companies with separate finance and sales functions, which RDCO is not. There is no sales org to align finance with. The direct operating-model relevance is limited, so the honest call is that the content itself is thin for us as a how-to.
Two transferable ideas are worth flagging for the client-reporting and finance-pulse surfaces:
- Segment the top line for diagnosability (point 1) maps to RDCO multi-bet attribution. The lesson that you can't put toothpaste back in the tube — you must track in segments before a miss so you can dissect it — reinforces the [[2026-05-19-mostly-metrics-when-to-allocate-overhead]] discipline of separating attribution lines early. For RDCO that means tracking the bets (MAC, Squarely, Sanity Check, investing) as segments from the start, not as one blended P&L.
- Make metrics mean something in the recipient's own terms (point 3) is a [[finance-pulse]] / client-reporting principle. The NDR anecdote (60 minutes explaining the four levers beats quarters of TED talks) is a direct argument for explaining the levers under a metric in any RDCO reporting artifact rather than just presenting the headline number. "Make the metric mean something" is a reporting-design rule we can lift.
Stronger value is as a Sanity Check voice reference. Per the no-derivative-Sanity-Check rule, this is not a topic to restate — but it's a useful tonal anchor for CJ's register (profane-practitioner, anecdote-forward, deflating-the-platitude). If a future Sanity Check piece touches finance/sales alignment it would need an original re-frame, with this as evidence, not source.
Related
- [[2026-05-19-mostly-metrics-when-to-allocate-overhead]] — companion CJ piece on segmenting/attributing cost lines before you need them; same "track in segments early" discipline as point 1 here
- [[2026-05-17-mostly-metrics-sector-refresh-new-nine]] — prior Mostly Metrics note; same author voice and benchmark posture
- [[2026-02-28-cfosecrets-drilling-for-insight-storytelling-cfo-iv]] — cfo-secrets parallel on making metrics legible to a non-finance audience (point 3 overlap)
- [[finance-pulse]] — RDCO reporting surface where "make the metric mean something in the recipient's terms" applies