Skip to content

mbfinotti/advertising-skills / skills/cac-roas-benchmark

cac-roas-benchmark

Verified

Compute a business's CAC and ROAS family metrics from real spend and outcome data, then judge whether the spend is healthy against three references - the business's own break-even, its own trailing history, and provenance-labelled external benchmarks - returning healthy, watch, unhealthy, or insufficient evidence. Use whenever the user asks whether their CAC is too high, whether a ROAS is good, what ROAS to aim for, whether ads are profitable, or mentions MER, blended CAC, payback period, or a spend health check - even if they never say 'benchmark'. Covers B2B/SaaS (cost per SQL, cost per closed-won, cohort lag) and B2C/ecommerce. Do NOT use to set those thresholds as policy - use mbfinotti/advertising-skills@ad-spend-guardrails instead.

FileKindSize
SKILL.mdskill md29.7 KB
evals/evals.jsonconfig35.7 KB
references/benchmark-sources.mdmarkdown15.6 KB
references/worked-examples.mdmarkdown8.5 KB

evals/evals.json

View on GitHub
{
  "skill_name": "cac-roas-benchmark",
  "evals": [
    {
      "id": 1,
      "prompt": "I run Ferndale Goods, a DTC home-fitness-gear brand. July numbers: net revenue from our order system $240,000, paid media spend $96,000, plus about $14,000 in agency fees and creative production. Contribution margin after COGS, shipping and payment fees is 38%. Our Meta + Google dashboards show a combined ROAS of 4.6, which beats the 4:1 industry standard, and I read the ecommerce median is only around 2. Monthly MER since January if it helps: 2.62, 2.55, 2.48, 2.41, 2.33, 2.24, and then July. Are we healthy? Thinking about scaling next month.",
      "expected_output": "A spend health report that recomputes the money-anchored figures (blended ROAS 2.5, MER ~2.18), sets break-even at ~2.63 from the 38% margin, treats the 4.6 as platform-reported claim, names 4:1 as folklore, and returns an unhealthy verdict resting on break-even and the deteriorating trend, with scaling refused and the budget decision handed off.",
      "files": [],
      "expectations": [
        "Computes blended ROAS as 240,000 / 96,000 = 2.5 and labels it as the blended variant, distinct from the dashboard figure",
        "Computes MER as approximately 2.18 (240,000 / 110,000), with the denominator explicitly including the $14,000 of agency and creative spend",
        "Computes break-even ROAS/MER as 1 / 0.38, approximately 2.63",
        "Treats the dashboard 4.6 as platform-reported/attributed ROAS - a claimed figure, not the number judged against break-even",
        "Names the 4:1 rule as folklore with its origin: no traceable author, often misattributed to a 2016 Nielsen study that says no such thing",
        "States that 4:1 is simply break-even at a 25% contribution margin, and places this business's own 2.63 break-even next to it",
        "Returns an unhealthy verdict because MER (and blended ROAS) sit below the business's own break-even by arithmetic, not a healthy verdict",
        "The verdict rests on break-even (rung 1) and the trailing history (rung 2); the ~2 ecommerce median is used only as context, never to set the verdict",
        "Runs or explicitly requests a mix-shift check before treating the January-July MER decline as a real trend",
        "Reads the MER history as a sustained multi-period deterioration rather than a one-off dip",
        "Every reported figure carries a variant label, a window, and a data source",
        "Any external median cited carries publisher, year, sample, and the variant it measured",
        "Refuses to endorse scaling in this run and hands the pause/reallocate decision off to a spend-guardrails or budget-allocation workflow rather than prescribing budget moves itself"
      ]
    },
    {
      "id": 2,
      "prompt": "Ostrava Systems here - B2B compliance SaaS, ACV $18,000, gross margin 75%, sales cycle averages about 4 months. In April we spent $60,000 on paid (media plus agency), got 500 leads, 40 of them became SQLs, and only 2 deals closed that month. That's a $30,000 CAC against the published $239 B2B SaaS benchmark from First Page Sage. My cofounder wants to kill paid entirely before May. Our historical lead-to-close rate is 1.5%. Can you confirm the numbers?",
      "expected_output": "A run that refuses the $30,000 in-period CAC as a cohort-mixing artifact, withholds the verdict as insufficient evidence because the window is shorter than the sales cycle, exposes the First Page Sage variant mismatch, and supplies labeled interim reads (CPL $120 vs break-even CPL $270, cost per SQL $1,500) plus a cohort measurement plan.",
      "files": [],
      "expectations": [
        "Rejects $30,000 as a valid CAC because April's 2 closed deals came from earlier lead cohorts while April's spend bought a cohort that closes months later - in-period division mixed two cohorts",
        "Names the window being shorter than the ~4-month sales cycle as an explicit evidence-gate condition",
        "Returns insufficient evidence as the verdict state, not unhealthy or catastrophe",
        "Flags the First Page Sage $239 as a combined organic-plus-paid figure from a sample the agency itself discloses as roughly 75% organic-weighted, making it a variant mismatch against paid-only spend",
        "Does not endorse killing paid on the strength of the benchmark comparison",
        "Computes CPL as 60,000 / 500 = $120, labeled with variant, window, and source",
        "Computes break-even CPL as ACV x lead-to-close rate: 18,000 x 1.5% = $270",
        "Computes cost per SQL as 60,000 / 40 = $1,500",
        "Labels the CPL and cost-per-SQL reads as interim signals while the cohort is immature, explicitly not verdicts",
        "Proposes cohort measurement: group leads by month generated and measure revenue at 90/180/365 days",
        "Computes the allowable first-year CAC ceiling as ACV x gross margin: 18,000 x 0.75 = $13,500, for use once the cohort matures",
        "Explicitly distinguishes in-period CAC from lagged/cohort CAC",
        "Names exactly what would unlock the verdict: the April cohort reaching maturity"
      ]
    },
    {
      "id": 3,
      "prompt": "Loopwell here - project-management SaaS, self-serve. Two plans: Basic $15/month and Pro $99/month, gross margin 70% on both. Last month marketing spend was $93,000 and billing shows 300 'new customers,' but our billing counts plan reactivations and annual renewals as new - about 60 of the 300 are those. So CAC is $310. David Skok says payback should be under 12 months - where do we stand? Roughly two-thirds of new signups are Basic.",
      "expected_output": "A per-plan payback analysis on a corrected new-customer CAC of ~$388 (renewals excluded), computed with the gross-margin term kept (~37 months Basic, ~5.6 months Pro), the 12-month rule named as Skok's 2011 rule of thumb, and separate per-segment readings instead of one blended verdict.",
      "files": [],
      "expectations": [
        "Excludes the 60 renewals and reactivations from the denominator and recomputes new-customer CAC as 93,000 / 240, approximately $387-388, instead of accepting $310",
        "States that counting renewals as acquisitions inflates the denominator and flatters every verdict built on it",
        "Computes payback per plan rather than presenting a single blended payback figure",
        "Keeps the gross-margin term in the payback formula: monthly gross profit per customer is $10.50 on Basic (15 x 0.70) and $69.30 on Pro (99 x 0.70)",
        "Reports Basic payback at approximately 37 months",
        "Reports Pro payback at approximately 5.6 months",
        "Does not report the margin-free figures (~26 months Basic, ~3.9 months Pro) that come from dividing CAC by the raw subscription price",
        "Names the 12-month payback rule as David Skok, 2011 - a rule of thumb tied to that era's fundraising conditions, never empirically validated",
        "Puts the business's own per-plan economics next to the quoted folk target instead of deleting or simply endorsing it",
        "States that one blended number describes neither plan, since the same CAC means order-of-magnitude different payback at $15/month versus $99/month",
        "Delivers a separate reading per plan segment (Basic problematic, Pro comfortable) rather than a single verdict",
        "Every figure carries a variant label, window, and data source",
        "Flags that raw payback assumes the customer survives the payback window, and asks for retention or applies a discounted-payback view given the ~37-month Basic figure"
      ]
    },
    {
      "id": 4,
      "prompt": "Our ecommerce brand Bramblewick lost TikTok Ads reporting for the last three weeks of October (expired API token). TikTok is historically about 8% of our paid spend. My analyst put $0 for TikTok in the October sheet so the totals still add up. October: order-system net revenue $520,000, Meta spend $130,000, Google spend $95,000, TikTok $0 per the sheet. Contribution margin 44%. MER April through September was 2.35, 2.31, 2.34, 2.30, 2.28, 2.26. Can you compute October MER and tell me if the downtrend is real?",
      "expected_output": "A run that refuses the zero-filled denominator, renormalises total spend using the known ~8% TikTok share (~$245K, MER ~2.13), notes withholding as the fallback, checks mix shift before reading the trend, and judges October against the ~2.27 break-even using the corrected figure.",
      "files": [],
      "expectations": [
        "Refuses to compute the verdict from the zero-filled $225,000 spend total, naming the $0 TikTok line as silently corrupting the blend",
        "Renormalises the spend total using the known ~8% TikTok share, arriving at roughly $245,000 total spend and an October MER of approximately 2.1",
        "States that renormalising is the right move here because the missing channel is small and its size is known, with withholding the blended figure named as the fallback",
        "Computes break-even MER as 1 / 0.44, approximately 2.27",
        "Judges October against break-even using the corrected MER (at or below 2.27), not the zero-filled ~2.31 that would sit above it",
        "Runs or explicitly requests a mix-shift check before declaring the April-October downtrend real",
        "Reads the history as a multi-period deteriorating trend pending the mix-shift confirmation",
        "The verdict (unhealthy or watch) rests on the business's own break-even and trailing history, with no external median setting it",
        "Every reported figure carries variant, window, and data source labels",
        "Names restoring TikTok reporting as a concrete next step or next-period question",
        "Does not zero-fill, average around, or silently ignore the missing channel anywhere in the calculation"
      ]
    },
    {
      "id": 5,
      "prompt": "Prepping the Series B board deck for Nivara Health, our B2B scheduling SaaS. Marketing wants a slide saying CAC improved 35%: Q1 CAC was $95, Q2 came in at $62. Digging into the sheet: the Q1 figure was paid spend $190,000 divided by 2,000 paid-attributed customers. In Q2 the team switched to total marketing spend $217,000 divided by all 3,500 new customers, because organic took off after a PR hit. Q2 paid numbers were $185,000 spend and 1,850 paid-attributed customers. Can we run with the 35% improvement?",
      "expected_output": "A refusal of the 35% claim as a silent variant switch (paid Q1 vs blended Q2), a like-for-like recomputation showing paid CAC actually worsened to $100, both variants presented labeled side by side, and a recommendation to build fully-loaded CAC for the board with finance owning the definition.",
      "files": [],
      "expectations": [
        "Refuses the 35% improvement claim because Q1 is paid CAC and Q2 is blended CAC - two different variants that cannot be compared",
        "States that blended CAC is always lower than paid CAC when organic acquisition exists, so part of the apparent improvement is purely definitional",
        "Recomputes the like-for-like comparison: Q2 paid CAC = 185,000 / 1,850 = $100, meaning paid CAC worsened roughly 5% quarter over quarter",
        "Presents both Q2 variants side by side, each labeled ($62 blended, $100 paid), rather than silently picking one",
        "Names the silent variant switch as the failure: CAC appears to improve with nothing actually changing",
        "Recommends fully-loaded CAC (S&M including salaries, tooling, agency, creative) as the variant a board or investor audience expects",
        "Warns that a fully-loaded figure shown to a board becomes a reported number finance has to own, and redefining it later is a restatement - so the definition must be agreed with finance",
        "Does not let the already-available blended number decide the variant choice for a finance-facing audience",
        "Notes the organic surge is a mix shift, so any blended CAC trend cannot be read without a mix-shift check",
        "Withholds or gates any health judgment on break-even inputs and history rather than judging health from the CAC levels alone",
        "Does not present $95 to $62 as a single continuous trend line or average the two figures",
        "Every figure carries a variant label, window, and data source"
      ]
    },
    {
      "id": 6,
      "prompt": "I run Tessellate Prints, a custom-poster ecommerce shop. Everyone gives me a different ROAS target: our agency says aim for 4x minimum, a podcast said MER should be above 4 and 5-8 at scale, and a blog said median ecommerce ROAS is around 2 so anything above that is fine. Our contribution margin after COGS, shipping and payment fees is 55%. What ROAS should we actually be aiming for?",
      "expected_output": "An answer anchored on the business's own break-even of ~1.82 (1/0.55), with each quoted target named and traced to its origin rather than adopted, the margin-dependence of ROAS profit made explicit, history requested as the second reference, and the policy-setting of an actual target handed off to a guardrails workflow.",
      "files": [],
      "expectations": [
        "Computes break-even ROAS as 1 / 0.55, approximately 1.82",
        "Names the 4:1 rule's status: no traceable author, often misattributed to a 2016 Nielsen study, and mathematically just break-even at a 25% margin - not this business's 55%",
        "Names 'MER above 4, 5-8 at scale' as a Taylor Holiday / Common Thread Collective stated heuristic never measured across a sample",
        "Shows that the same ROAS means different profit at different margins (for example 4x yields about $1.40 profit per ad dollar at 60% margin and $0.00 at 25%, or the equivalent computation at 55%)",
        "Does not adopt the ~2 median as the target, and any median quoted carries publisher, year, sample, and the variant measured",
        "Explains that an external median cannot know this business's margin or price point - which is why it cannot set the verdict",
        "Positions the 1.82 break-even as the non-negotiable arithmetic floor: below it the spend loses money whatever any benchmark says",
        "Hands off setting the actual target or floor as written policy to a spend-guardrails workflow instead of declaring a policy number itself",
        "Recommends the business's own trailing history (4-8 prior periods, same definition) as the second reference and asks for it",
        "Names each quoted folk target with its origin instead of deleting or ignoring it",
        "Does not average the three quoted targets into a single number",
        "Distinguishes blended ROAS from MER by their denominators (total paid spend versus total marketing spend) when discussing the quoted 4x targets"
      ]
    },
    {
      "id": 7,
      "prompt": "CFO of Corvid Analytics, a B2B data-quality SaaS - ACV around $30K, gross margin 78%, NRR 118%. I've collected three published CAC payback medians - 16, 18 and 20 months - so let's just call the benchmark 18. Ours is 21 months, computed the same way each quarter for the last two years: 21.5, 21, 20.5, 21, 20.5, 21, 21, 21. Also our LTV:CAC is 2.7 and the rule says 3. Board meeting Thursday - how bad is it?",
      "expected_output": "A run that refuses to average the conflicting medians and presents them as a conflict with provenance, names the 3:1 rule as Skok's self-admitted guess, prefers payback over LTV:CAC, reads the stable 8-quarter history as rung 2, weighs the 118% NRR before flagging the 21 months, and refuses to declare the business unhealthy from the benchmark gap.",
      "files": [],
      "expectations": [
        "Refuses to average the 16, 18 and 20-month medians into one benchmark and presents them as a conflict instead",
        "Explains the medians disagree because the panels and definitions behind them differ",
        "Attaches publisher, year, and sample to any published payback median it cites",
        "Names the 3:1 LTV:CAC rule as David Skok's own figure from the early 2010s, a self-admitted guess, worth at most a secondary check",
        "Prefers payback over LTV:CAC as the affordability lens, giving at least one stated reason (LTV:CAC inherits whichever CAC variant fed it, hides per-plan variance, or never asks when the cash comes back)",
        "Reads the 8 quarters of same-definition history as the business's own trailing reference, noting the trend is flat/stable and that direction and volatility matter more than the level",
        "Weighs the 118% NRR before flagging the 21-month payback: high net revenue retention can justify a longer acquisition payback",
        "Computes the monthly gross profit per customer as roughly $1,950 (30,000 / 12 x 0.78) and/or the implied CAC of roughly $41,000, labeled",
        "Asks which CAC variant and spend lines feed the payback figure before comparing it to any external median",
        "Reports external benchmarks as ranges or quartiles rather than a single point estimate",
        "Sizes the gap to external medians as context only, never as the basis of the verdict",
        "Does not declare the business unhealthy on the grounds of being above the averaged or individual published medians",
        "Any verdict offered rests on the business's own economics and history, with the missing rung-1 inputs (allowable CAC versus actual CAC) either computed from the given ACV and margin or explicitly requested"
      ]
    },
    {
      "id": 8,
      "prompt": "Harbor & Pine, coastal-home-decor DTC. November: Meta Ads Manager reports $310,000 in attributed revenue on $80,000 spend; Google Ads reports $265,000 on $60,000. So combined ROAS is (310+265)/(80+60) = 4.1 and we're planning to push spend up 30% for December. The order system shows $390,000 net revenue for November in total, 3,800 new customers, AOV around $78, contribution margin 42%. Sanity-check the 4.1 for me?",
      "expected_output": "A rejection of the summed platform ROAS (platforms jointly claim ~147% of actual revenue), a blended ROAS of ~2.79 anchored on the order system, break-even at ~2.38, blended CAC ~$37 flagged as above the ~$33 first-order contribution (verdict contingent on repeat rate), history requested for rung 2, seasonality respected, and the December scale-up handed off.",
      "files": [],
      "expectations": [
        "Flags that Meta and Google jointly claim $575,000 of attributed revenue against $390,000 of actual revenue - roughly 147% - so the platforms are double-counting",
        "Refuses to sum platform-attributed revenue across platforms, stating platform-reported ROAS is non-additive",
        "Anchors revenue on the order system's $390,000 net figure, not on platform-attributed value",
        "Computes blended ROAS as 390,000 / 140,000, approximately 2.79, labeled blended with the November window",
        "Computes break-even ROAS as 1 / 0.42, approximately 2.38",
        "Judges spend health against the business's own break-even (2.79 versus 2.38), not against the 4.1 platform composite",
        "Labels the platform figures as claimed/attributed rather than caused revenue, and any attribution-inflation evidence cited carries its provenance",
        "Computes blended CAC as 140,000 / 3,800, approximately $37, labeled",
        "Computes first-order contribution as AOV x margin (78 x 0.42, approximately $33) and explicitly states the verdict is contingent on the repeat-purchase rate because CAC exceeds it",
        "Requests 4-8 prior periods of the same metrics as the trailing-history reference before finalizing the verdict",
        "Notes that December must be compared against a prior December, not against November, because seasonality alone can invert a verdict",
        "Declines to make the 30% December increase decision in this run and hands the budget move off to an allocation, scaling, or guardrails workflow",
        "Every reported figure carries a variant label, a window, and a data source"
      ]
    },
    {
      "id": 9,
      "prompt": "Meridian Straps, we sell premium watch straps online. Our Meta CAC went from $38 to $46 over the last two months - about a 20% jump. Team consensus is that Meta is saturated and we should immediately move 30% of the budget into TikTok and Pinterest to diversify. Contribution margin is 52%, AOV $95. Does the CAC jump confirm it's time to diversify?",
      "expected_output": "A margin-first read: $46 still sits under the ~$49 first-order allowable CAC, so the rise is not automatically a problem; the new-channel test is gated on the current channel's marginal CAC exceeding what the next channel could deliver; two months of decline earns at most a watch with a named question, and the reallocation itself is handed off.",
      "files": [],
      "expectations": [
        "Does not endorse immediately moving budget into untested channels on the strength of the 20% CAC rise alone",
        "Checks contribution margin first: judges the $46 against the business's own allowable CAC before treating the rise as a problem",
        "Computes first-order allowable CAC as AOV x margin (95 x 0.52, approximately $49) and notes $46 still sits under it, with thin headroom",
        "States the decision rule for diversifying: test a new channel only once the current channel's marginal CAC exceeds what the next channel could realistically deliver - and marginal CAC has not been measured here",
        "Establishes the variant of the $38-to-$46 figure as platform-attributed paid CAC and treats it as claimed rather than causal",
        "Names reacting to a CAC bump by spreading spend into untested channels as the more common failure, compared with staying too long in a working channel",
        "Notes that measuring marginal CAC takes a quarter and deliberate unrecoverable test spend, and that it serves scaling decisions rather than health verdicts",
        "Requests longer trailing history and a seasonality check before reading two data points as a trend",
        "Returns at most a watch state with a named next-period question, not an unhealthy verdict and not a reallocation instruction",
        "Hands the actual budget reallocation decision off to an allocation or channel-selection workflow",
        "Every reported figure carries a variant label, a window, and a data source"
      ]
    },
    {
      "id": 10,
      "prompt": "Head of growth at Verdala, a CRM for property managers. The CEO wants a spend health verdict by Friday for Monday's exec review. Problem: nobody has ever computed our contribution margin - finance is mid-audit and can't help until next month. What I do have: 6 months of blended CAC on a consistent definition (total marketing spend / all new customers): $410, $395, $402, $398, $405, $400, and MER for the same months: 3.1, 3.2, 3.1, 3.15, 3.1, 3.1. B2B, sales cycle about 5 weeks, monthly windows, so lag is covered. Give me the verdict.",
      "expected_output": "A run that says at intake that the verdict will be withheld without contribution margin, presents the labeled blended figures and the stable history as context, refuses to assume a typical margin or substitute a benchmark for break-even, and returns insufficient evidence naming the margin as the exact unlock.",
      "files": [],
      "expectations": [
        "States up front, at intake, that without a contribution margin the verdict will be withheld - not discovered at the end of the run",
        "Returns insufficient evidence as the final state, not healthy, despite the stable history",
        "Names contribution margin as the exact missing input and finance's margin number as what would unlock the verdict",
        "Names the Friday deadline's effect on scope: the run stays on the near-zero-effort variants (blended CAC, MER) and any fully-loaded CAC or margin rebuild is deleted from this run and said so",
        "Still computes and presents the blended CAC and MER figures, each labeled with variant, window, and source",
        "Presents the 6-month history as direction and volatility context (stable/flat) while explicitly not issuing a health verdict from the trend alone",
        "Does not substitute an external published benchmark to stand in for the missing break-even",
        "Explicitly distinguishes insufficient evidence from unhealthy: unknown is not the same as failing",
        "Does not assume or invent a margin figure (for example a 'typical SaaS' 75-80%) to force a verdict out",
        "Recommends the standing investment: contribution margin costs real effort once and near-zero every period after, scheduled for when finance frees up",
        "Includes a definitions record covering the intake answers and naming the variants this run deleted or deferred",
        "Frames what happens next: the named missing input, who provides it, and when the verdict can be issued"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Is our CAC too high?", "should_trigger": true },
    { "query": "Our blended CAC jumped from $180 to $240 this quarter - should I be worried?", "should_trigger": true },
    { "query": "Is a 3.2 ROAS good for an ecommerce store?", "should_trigger": true },
    { "query": "What ROAS should we aim for given our margins?", "should_trigger": true },
    { "query": "Are our Facebook ads actually making us money?", "should_trigger": true },
    { "query": "MER came in at 2.4 this month - healthy or not?", "should_trigger": true },
    { "query": "CFO wants to know whether our paid spend is efficient. Can you run the numbers?", "should_trigger": true },
    { "query": "We spent $50k on ads and got 130 customers. Good or bad?", "should_trigger": true },
    { "query": "What's a healthy CAC payback period for a SaaS at our price point?", "should_trigger": true },
    { "query": "Sanity-check our unit economics on paid acquisition", "should_trigger": true },
    { "query": "Can you do a spend health check on our ad accounts?", "should_trigger": true },
    { "query": "Is $420 cost per customer acceptable for a $79/month product?", "should_trigger": true },
    { "query": "Our agency says 4x ROAS is the industry standard - is that true for us?", "should_trigger": true },
    { "query": "How do I know if we're overpaying to acquire customers?", "should_trigger": true },
    { "query": "Benchmark our CAC against the industry", "should_trigger": true },
    { "query": "Is our LTV to CAC ratio of 2.5 a problem?", "should_trigger": true },
    { "query": "Judge whether our Google Ads returns are sustainable", "should_trigger": true },
    { "query": "The platform says ROAS 5.1 but the bank account disagrees - are we actually profitable?", "should_trigger": true },
    { "query": "Is a $900 cost per SQL reasonable for enterprise software?", "should_trigger": true },
    { "query": "Our payback period is 19 months - too long?", "should_trigger": true },
    { "query": "Here's our spend and revenue by month - tell me if the ads are worth it", "should_trigger": true },
    { "query": "Is 2.8 MER enough to keep scaling or are we treading water?", "should_trigger": true },
    { "query": "What does a good ROAS look like for a 35% margin business?", "should_trigger": true },
    { "query": "Boss asked if our customer acquisition cost is out of line. Help?", "should_trigger": true },
    { "query": "Are we losing money on every customer we acquire?", "should_trigger": true },
    { "query": "Evaluate whether our paid social spend is healthy this quarter", "should_trigger": true },
    { "query": "I keep hearing 3:1 LTV:CAC - are we failing at 2.2?", "should_trigger": true },
    { "query": "ROAS dropped from 3.5 to 2.9 - is that still okay?", "should_trigger": true },
    { "query": "Compare our cost per acquisition to what's normal for DTC brands", "should_trigger": true },
    { "query": "$14k spend, 200 orders, $68 AOV - is this working?", "should_trigger": true },
    { "query": "Is our cost per closed-won deal defensible?", "should_trigger": true },
    { "query": "Should our ecommerce ROAS target really be 4?", "should_trigger": true },
    { "query": "How healthy is a 24-month CAC payback for enterprise SaaS?", "should_trigger": true },
    { "query": "Give me a verdict on our blended ROAS of 2.1", "should_trigger": true },
    { "query": "Check if our ad spend clears break-even", "should_trigger": true },
    { "query": "An investor asked about our CAC efficiency - what do I tell them?", "should_trigger": true },
    { "query": "We're at 1.9x return on ad spend. Panic or fine?", "should_trigger": true },
    { "query": "Are these acquisition costs normal for fintech?", "should_trigger": true },
    { "query": "Did our ads make money after refunds and fees?", "should_trigger": true },
    { "query": "Is my cost per lead of $85 too high for B2B?", "should_trigger": true },
    { "query": "How much profit are we really making per ad dollar?", "should_trigger": true },
    { "query": "My cofounder says our CAC is fine, I think it's a disaster - settle it with the numbers", "should_trigger": true },
    { "query": "Run our January-June spend and revenue through a profitability check", "should_trigger": true },
    { "query": "Is 6:1 ROAS on brand search actually as good as it looks?", "should_trigger": true },
    { "query": "Assess our customer acquisition economics before the board meeting", "should_trigger": true },
    { "query": "The dashboard says we're at 380% return - believe it?", "should_trigger": true },
    { "query": "What CAC payback should I expect at a $12K ACV?", "should_trigger": true },
    { "query": "Marketing efficiency ratio has been sliding for three months - how bad is it?", "should_trigger": true },
    { "query": "Is spending $110 to get a $95 first order ever okay?", "should_trigger": true },
    { "query": "Do our numbers justify what we spend on paid acquisition?", "should_trigger": true },
    { "query": "Grade our paid marketing performance: spend $210K, new revenue $560K", "should_trigger": true },
    { "query": "Am I reading it right that we're below break-even on ads?", "should_trigger": true },
    { "query": "Is a blended CAC of $61 good for a subscription box?", "should_trigger": true },
    { "query": "Everyone quotes different ROAS benchmarks - which one applies to us?", "should_trigger": true },
    { "query": "Our new VP says anything under 3x ROAS should be cut. Is that right?", "should_trigger": true },
    { "query": "Quick gut check: $32 CAC, $54 AOV, 41% margin - healthy?", "should_trigger": true },
    { "query": "Tell me if our ad economics survive contact with the actual margin data", "should_trigger": true },
    { "query": "Is our cost to acquire a customer sustainable long-term?", "should_trigger": true },
    { "query": "Set a maximum allowable CAC policy for the marketing org", "should_trigger": false },
    { "query": "Write our ROAS floor and kill-switch thresholds into a formal policy", "should_trigger": false },
    { "query": "Define who can override our spend guardrails and when", "should_trigger": false },
    { "query": "Derive spend limits from our runway and codify them", "should_trigger": false },
    { "query": "We need documented rules for when to shut off a campaign automatically", "should_trigger": false },
    { "query": "How should I split $60K between Meta, Google and TikTok next quarter?", "should_trigger": false },
    { "query": "Reallocate our budget from prospecting to retargeting", "should_trigger": false },
    { "query": "Which campaigns should get more money this month?", "should_trigger": false },
    { "query": "Move spend toward the channels with the best marginal return", "should_trigger": false },
    { "query": "Are we on track to spend the full monthly ad budget?", "should_trigger": false },
    { "query": "Project our month-end spend from the first ten days", "should_trigger": false },
    { "query": "Flag campaigns that are underspending against their budgets", "should_trigger": false },
    { "query": "Why did our CPA double in March?", "should_trigger": false },
    { "query": "Figure out what's wrong with our ad account - performance fell off a cliff", "should_trigger": false },
    { "query": "Diagnose why conversions dried up after the account restructure", "should_trigger": false },
    { "query": "Our ads stopped working - find the root cause", "should_trigger": false },
    { "query": "Meta says 400 conversions, our CRM says 220 - reconcile them", "should_trigger": false },
    { "query": "Explain the gap between GA4 revenue and Shopify revenue", "should_trigger": false },
    { "query": "Classify the discrepancy between platform and order-system numbers", "should_trigger": false },
    { "query": "Should I switch to target ROAS bidding on Google?", "should_trigger": false },
    { "query": "What tROAS value should I enter in Google Ads?", "should_trigger": false },
    { "query": "Manual CPC or maximize conversions for a new campaign?", "should_trigger": false },
    { "query": "When is it safe to double this campaign's daily budget?", "should_trigger": false },
    { "query": "Design a ramp plan for scaling our winning campaign", "should_trigger": false },
    { "query": "How fast can we scale spend without breaking performance?", "should_trigger": false },
    { "query": "Verify our pixel and Conversions API are deduplicating before launch", "should_trigger": false },
    { "query": "Check whether the purchase event fires twice on checkout", "should_trigger": false },
    { "query": "Which ad platforms fit a B2B startup with a $10K monthly budget?", "should_trigger": false },
    { "query": "Should we advertise on LinkedIn or Google first?", "should_trigger": false },
    { "query": "Is my winning ad wearing out? Frequency is climbing", "should_trigger": false },
    { "query": "CTR is dropping on our best creative - fatigue or seasonality?", "should_trigger": false },
    { "query": "We have 40 campaigns - which should we merge?", "should_trigger": false },
    { "query": "Mine our search terms report for negative keywords", "should_trigger": false },
    { "query": "Ads get clicks but no conversions - audit our landing page", "should_trigger": false },
    { "query": "Rank these five video hooks before we put budget behind them", "should_trigger": false },
    { "query": "Write ad copy variations for our spring sale", "should_trigger": false },
    { "query": "Build a layered targeting plan from our ICP", "should_trigger": false },
    { "query": "Which customers should seed our lookalike audience?", "should_trigger": false },
    { "query": "Design a retargeting sequence for cart abandoners", "should_trigger": false },
    { "query": "Map the buying committee for our enterprise deals", "should_trigger": false },
    { "query": "Set up an A/B test plan for our new ad concepts", "should_trigger": false },
    { "query": "Draft a creative brief for our UGC campaign", "should_trigger": false },
    { "query": "Should this campaign use carousel or video format?", "should_trigger": false },
    { "query": "Organize competitor ads into a swipe file", "should_trigger": false },
    { "query": "What should I ask when interviewing a media buyer?", "should_trigger": false },
    { "query": "How do I move from PPC specialist to growth lead?", "should_trigger": false },
    { "query": "Which paid-media newsletters and podcasts are worth following?", "should_trigger": false },
    { "query": "Where do I start with paid advertising for my new store?", "should_trigger": false },
    { "query": "Is our monthly churn rate of 4% healthy?", "should_trigger": false },
    { "query": "Benchmark our email open and click rates", "should_trigger": false },
    { "query": "Is our organic traffic growth in line with the industry?", "should_trigger": false },
    { "query": "What's the average CPC for legal keywords right now?", "should_trigger": false },
    { "query": "Build the LTV model for our fundraising deck", "should_trigger": false },
    { "query": "Is $99/month the right price for our pro plan?", "should_trigger": false },
    { "query": "Do we have enough pipeline coverage for the Q4 number?", "should_trigger": false },
    { "query": "Calculate contribution margin per SKU from these COGS numbers", "should_trigger": false },
    { "query": "Compare our website conversion rate to ecommerce averages", "should_trigger": false },
    { "query": "Forecast next quarter's revenue from current ad spend", "should_trigger": false }
  ]
}
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall