Revenue Data Governance Strategy
Maya-Beth FinottiDefines revenue data authority across systems with source-of-record and source-of-truth assignments, identity rules and metric ownership.
By agent · Codex
Skills in the open SKILL.md format that Codex reads. Each one has a plain-language summary and the command to install it.
$ npx skills add <author>/<skill> --agent codexReplace the placeholder with the author and skill name from the skill's page. Start a new Codex session afterwards so the skill is picked up.
Defines revenue data authority across systems with source-of-record and source-of-truth assignments, identity rules and metric ownership.
Designs CRM-based sales-to-CS handoff processes with gated triggers, required context, timing SLAs and clear ownership.
Builds and validates leading churn indicators from subscription account activity, product usage and support data into a ranked signal register.
Designs and validates weighted customer health scores that flag churn risk and expansion readiness from product, engagement, support and commercial signals.
Designs and validates revenue-operations lead scoring models using fit, engagement, thresholds and backtesting to improve MQL and PQL quality.
Structures RevOps revenue reports around locked metrics, finance reconciliation, plan-versus-actual analysis and clear board narratives.
Designs approval chains for non-standard B2B SaaS deals, covering concessions, margin floors, exceptions and escalation.
Reviews RevOps and GTM tool stacks to identify overlap, time renewal actions and decide which tools to keep, consolidate, replace or cut.
Creates evidence-backed creative briefs for advertising concepts, covering angles, hook directions, production specs, testing intent and handoff.
Designs CRM lead assignment systems covering account matching, territory rules, fair distribution, fallback queues and SLA-based escalation.
Verifies ad conversion tracking before launch, tracing test events, checking deduplication, consent, values and statuses, then issuing a GO or NO-GO decision.
Designs pre-launch paid-media creative test plans with hypotheses, budgeted test cells, sample sizing and pre-registered kill or scale rules.
Selects and sizes customer seeds for Meta, Google, LinkedIn and TikTok lookalike audiences, checking match rates, privacy and fallback options.
Tracks campaign or account spend against a period budget across ad platforms, flags meaningful under- or over-pacing, and calculates the daily correction required.
Routes paid advertising projects to the right skill in a 31-skill collection, preserving shared context across sessions and identifying gaps when no route fits.
Diagnoses underperforming paid ad accounts by tracing tracking, structure, targeting, creative, bidding, offer and external causes.
Sets paid-media CAC, ROAS, cash and kill-switch guardrails from contribution margin, payback and runway, with owners, overrides and restart rules.
Diagnoses whether a running ad is suffering creative fatigue or a confounder across Meta, Google Ads, LinkedIn and TikTok, then recommends the next action.
Computes CAC, ROAS, MER and payback from advertising spend data, then judges spend health against break-even, history and external benchmarks.
Maps an ICP and buying signals into sized, budgeted ad audience tiers for prospecting, lookalikes, first-party lists and retargeting without overlap.
Allocates a fixed paid-media budget across campaigns, platforms and funnel stages using marginal return, evidence gates and bounded reallocation rules.
Plans budget increases for proven paid campaigns, choosing step sizes, hold periods and rollback triggers while checking marginal economics, evidence and capacity.
Maps B2B buying committees and multi-decider household purchases to role-specific messaging, ad-platform targeting proxies and buying-stage sequences.
Selects paid advertising channel families by business economics, audience, funnel stage, budget and allowable CAC, then defines a focused test plan.
Questions
Often. A skill is a folder of instructions and scripts in the open SKILL.md format, which Codex reads. A skill that depends on tools only one agent provides will not carry over, so read the skill's source before you rely on it.
Each skill page has an install command. Run it in a terminal, then start a new Codex session so the skill is picked up.
An instructions file is loaded in every session and describes the project. A skill is loaded only when a task calls for it, so it can be long and specific without costing context on every turn.