"Your AI product has a fake mustache..."
Why this is in the vault
Three Q&As — AI-washed revenue classification, standard-costing governance discipline, and long-range planning inside a quarter-to-quarter culture — plus a new-sponsor signal (Aleph, pitching packaged Claude Skills for finance teams) that's directly adjacent to RDCO's own skills-over-commands practice.
⚠️ Sponsorship
Aleph (getaleph.com) — finance-ops AI platform, promoting a "Claude skills for finance" guide (Budget Pressure Tester, Model Sanity Checker, Board Pack Prepper) via a clean paid placement with UTM tracking (utm_source=secretcfo&utm_medium=email&utm_campaign=082026_secretcfo_playbook). No disclosed author relationship. This is a NEW, tenth distinct sponsor in CFO Secrets' rotating pool (prior confirmed members: Campfire, Zip, Pulley, Stuut, Una, Ledge, Summation, Nominal, CloudZero). Notable for RDCO specifically: the product being sold is a packaged set of Claude Skills for a vertical function — the same wedge shape as RDCO's own skills-over-commands practice, aimed at a buyer (CFO/finance team) adjacent to phData's client base.
The core argument
Q1 — AI-in-name-only revenue classification (US reader): A services company is bundling mostly-non-AI services (80-90% of the bundle) into a product marketed as "AI," and the exec team wants all revenue booked as AI revenue end-to-end (opportunity through GL), collapsing the component-level breakout. The Secret CFO's answer: marketing packaging and internal classification are separate decisions — finance's job is to preserve atomic, component-level revenue tagging at the sales-opportunity/contract/invoice/GL level regardless of how the business chooses to present the bundle externally. Aggregation for a board deck or investor narrative is fine later; losing the underlying breakout is not recoverable. He also flags the deeper tell: finance being told how to classify rather than driving the classification design suggests a broader influence gap worth interrogating.
Q2 — Standard costing governance maturity (manufacturing, US reader): Follow-up to the 2026-07-07 BOM/standard-cost issue (2026-07-07-cfo-secrets-bom-standard-cost-governance.md), this time framed as "what does mature governance look like end to end." The Secret CFO's answer organizes it into three buckets: (1) annual rollover — a controlled, once-a-year reset with a formal timetable, clear owners, materiality thresholds, pre-roll simulations, error reports, and sign-off across BOMs, routings, scrap %, labor/overhead rates, and active/inactive part reviews; (2) live changes — kept to an absolute minimum, reserved for genuine business-reality shifts (new products, new plants, material errors), explicitly NOT for absorbing normal operational variance into the standard (which would hide the very performance signal standard costing exists to surface); (3) major circumstance changes — rare, high-bar resets (extreme input-cost inflation, structural sourcing shifts) treated as a formal governance event, gated on whether the performance bridge would otherwise become materially misleading. Explicit warning against building "fat" into standards — keep them lean so misses stay visible.
Q3 — Long-range planning in a quarterly-execution culture (Eli, US reader): A business targeting 10x revenue over 5 years (~60% CAGR) delivered almost nothing in year one and wants to know how to introduce long-range planning into a culture that only operates quarter-to-quarter. The Secret CFO's answer: don't reach for a longer planning document — that makes the same execution problem "bigger and more beautifully formatted." Instead, assign single-name ownership of the 10x goal, define what has to be true in the next 12 months to keep the 5-year goal credible, and break that into a nearer-term milestone (e.g., 2-2.5x in 12 months) the execution culture can actually act on. Stretch the planning horizon only as the organization demonstrates it can hit nearer milestones. Long-range planning's real value surfaces later, when it forces visibility into resourcing trade-offs (e.g., is growth capital being diverted from a contracting core business).
Mapping against Ray Data Co
The Aleph sponsor placement is the sharpest signal in this issue: a vendor is productizing "Claude Skills for finance" as a lead magnet, using the exact skills-over-commands framing already codified in RDCO's own harness (~/.claude/skills/ format, MEMORY.md "Skills over commands"). This is a competitive/positioning data point, not just a sponsor to disclose — a third party is packaging the same wedge (vertical-specific Claude Skills as a sales asset) for a CFO/finance buyer, which overlaps with phData's client base. Worth a look at what Aleph's actual skill files contain before assuming it's marketing-only.
Separately, the AI-in-name-only Q&A is a direct mirror of a governance question RDCO should be asking about its own artifacts: does "AI-branded" revenue/positioning ever risk collapsing a real component breakdown the way this reader's exec team is doing? The standard-costing governance answer (three-bucket cadence: annual rollover / rare live changes / rare major resets) is a reusable pattern for RDCO's own "keep the reference point stable, gate exceptions behind formal review" instinct — applicable anywhere a scoring rubric or baseline (e.g. the newsletter-output-invariants schema, or a pricing/cost baseline for a client engagement) needs the same discipline against silent drift.
Related
[[2026-07-07-cfo-secrets-bom-standard-cost-governance]] — prior standard-costing governance issue this Q2 directly follows up on [[2026-08-18-cfo-secrets-nobody-bid-whose-fault]] — same Tue Mailbag cadence, most recent prior CFO Secrets sponsor-rotation data point (Nominal) [[feedback_skills_over_commands]] — the RDCO skills-over-commands practice Aleph's sponsor pitch directly parallels