Meta MuseSelf-reported $720 in about an hour, unverified; saved excerpt lists $180 first-year and $200/year items, not a complete reconciliation.Public · Free

Cut $720 of subscriptions in an hour with an agent-led bill and perk audit

Feifei QiuX · 2026-09-21

Read original

@Muse saved $720 for me tonight in an hour Google AI Pro : I have been paying $19.99/mo for a long time, while I have Verizon perk not being used (free 6 months, then $10) → ~$180 saved in the first year McAfee auto-renew for an old laptop: canceled → $200/yr avoided

Business model

The author had Meta Muse run a subscription and perk audit in a single evening. It lined up what was being charged against what the author already owned through carrier and card perks, then flagged two kinds of waste: paying for something a perk already covers, and auto-renewing for hardware that is long gone. Two items were named: Google AI Pro at $19.99 a month moved onto an unused Verizon perk (free six months, then $10) for about $180 saved in year one, and a McAfee auto-renewal on an old laptop cancelled for $200 a year avoided. The transferable part is the audit, not the specific services.

Subscription waste is rarely 'I overpaid'. It is 'I already owned this and paid anyway' and 'I stopped using it and it kept charging'. Both are invisible because the evidence sits in three different places: the bank statement, the inbox and the perks page. Putting them side by side is exactly what an assistant is good at, and the same audit works for a household or a small team.

Workflow

  1. Export everything currently being charged: service, amount, cycle, payment channel, last used date if known.
  2. List perks you already own from your carrier, bank, cards and memberships, with expiry and conditions.
  3. Have the agent cross the two lists and tag four cases: covered by a perk, dead auto-renewal, silent price rise, and barely used.
  4. Give every item one concrete action: keep, downgrade, move to the perk, or cancel, with the annual saving and the steps.
  5. Confirm each action yourself before touching anything, especially contracts, family plans or team billing.
  6. Put trial expiry, perk expiry and renewal dates on a calendar so the savings do not leak back.

Adaptation plan

The full itemised breakdown of $720 is not in the saved excerpt. Which carrier perk applied and whether it still exists is unverified. Whether the cancellations actually took effect is not shown. No build cost or token spend was disclosed. Actual savings for a different person depend entirely on their own subscription mix. The saved original is partial; absence from that excerpt does not establish absence from the full post.

Starter prompt

Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.

You are my personal spending audit assistant. I want a one-pass subscription and auto-renewal cleanup. Follow these steps.

INPUT - two lists I will paste:
List A (being charged): one row each as 'service | amount | cycle | payment channel | last used date (or unknown)'.
List B (perks I already own): one row each as 'source (carrier / bank / card / membership) | perk | expiry | conditions'.

WHAT TO DO:
1. Cross the two lists and tag four cases:
   a) Covered by a perk: I pay for it but something in list B already includes it;
   b) Dead auto-renewal: device retired, account abandoned, or unused for over 90 days but still charging;
   c) Silent price rise: renewal price clearly above the first-term price;
   d) Barely used: near-zero usage per cycle at a non-trivial price.
2. For every item give: category, the evidence (which pasted row justifies it), a recommended action (keep / downgrade / move to perk / cancel), and the estimated annual saving.
3. For anything marked cancel or downgrade, write out the practical steps and the points where I must log in myself.
4. Keep a separate 'not sure' section for items where you lack receipts or terms. Do not guess.

OUTPUT FORMAT:
First a summary table (service / category / action / estimated annual saving / needs my confirmation), then at most three lines of reasoning per item.

RULES:
- You have no access to my bills or accounts. Never invent amounts, usage or perk terms. Write 'unknown' when data is missing.
- Estimated savings must be computable from the numbers I gave you. No industry averages.
- Never claim you cancelled, downgraded or changed anything. You only produce the list and the steps.
- A perk only counts as covering a service if the pasted terms say so. Similar names are not enough.
- Flag anything with a contract term, early-cancellation fee, family sharing or team billing as needs-human-confirmation before recommending.
- Keep first-year and per-year savings in separate columns. Never merge them into one number.

[COMPLETE SMALL SYNTHETIC INPUT AND OUTPUT — not real business data; no model execution]
The JSON contains all demo inputs and a manually authored reference output. Do not invent facts from files not supplied. This reference covers only this minimal input and is not a business reproduction.
{
  "input": {
    "currency": "USD",
    "subscriptions": [
      {
        "service": "Storage Pro",
        "charge": 9.99,
        "cycle": "monthly",
        "capacity_gb": 100,
        "last_used": "8 months ago"
      },
      {
        "service": "Antivirus",
        "charge": 39.99,
        "cycle": "annual",
        "device": "retired laptop"
      }
    ],
    "perks": [
      {
        "service": "carrier storage",
        "capacity_gb": 100,
        "price": 0,
        "term": "while carrier plan active",
        "activation_required": true
      }
    ],
    "unknowns": [
      "feature equivalence",
      "cancellation fees",
      "family sharing"
    ]
  },
  "expected_output": {
    "candidates": [
      {
        "service": "Storage Pro",
        "action": "check equivalence and activate perk before considering cancellation",
        "potential_annual_avoided_gross_cost": 119.88
      },
      {
        "service": "Antivirus",
        "action": "confirm no active devices or contract penalty before cancellation",
        "potential_annual_avoided_gross_cost": 39.99
      }
    ],
    "savings_realised": 0,
    "cancellations_executed": 0,
    "needs_human_confirmation": [
      "feature equivalence",
      "cancellation fees",
      "family sharing"
    ]
  },
  "mode": "synthetic_read_only_reference_not_model_execution"
}

Running costs and pitfalls

The full itemised breakdown of $720 is not in the saved excerpt. Which carrier perk applied and whether it still exists is unverified. Whether the cancellations actually took effect is not shown. No build cost or token spend was disclosed. Actual savings for a different person depend entirely on their own subscription mix. The saved original is partial; absence from that excerpt does not establish absence from the full post. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

The breakdown and starter prompt are AgentFlow’s analysis and adaptation; results are not guaranteed.

Original text and media remain attributed to their authors.