This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI business subscription renewal reviewer

Share subscription bills, dated usage records, contracts and the prior review. You get options, sourced notice dates and owner actions to consider.

What you give

  • Your subscription bills or card statement lines for the month
  • Renewal dates and notice periods from your contracts or vendor accounts
  • Usage evidence, such as seats in use or last login dates

What you get

  • A renewal brief that covers only what changed since last month
  • A deadline table with the last day to cancel for each renewal and the sum behind it
  • Keep, switch or cancel options, with the yearly cost and the effort to switch
  • An updated renewal register for next month

An example

A renewal is coming up and you need to know the last day to cancel.

You ask: “Share subscription bills, dated usage records, contracts and the prior review. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • renewal-brief.md. Only what changed this month, with the decision window and a recommended path for each.
  • notice-deadlines.md. The last day to cancel each renewal, the sum behind it and the contract wording it came from.
  • options.md. Keep, consolidate, switch and cancel side by side, using prices and fees you supplied.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Track your numbers

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A renewal brief that covers only what changed since last month
  • A deadline table with the last day to cancel for each renewal and the sum behind it
  • Keep, switch or cancel options, with the yearly cost and the effort to switch
  • Evidence requests for anything missing before you decide
  • An updated renewal register for next month
  • Proposed actions for each owner, none sent

How it does the job well

  • Missing usage is "unknown", never "unused". Do not recommend cancelling on a feeling.
  • Never invent a renewal date, notice period, price, fee or saving. Savings use only prices and fees the user supplied, in the contract's currency and billing period.
  • Early termination fees and minimum terms reduce a saving. Show them.
  • Do not assume a subscription auto-renews or does not. Use the contract wording; if it is missing, say so.
  • Agree the question and the decision it supports before analysing.
  • Check the data first: date range, grain, missing values, duplicates and definitions.
  • Compare like with like: same period length, definitions and segments.

Mistakes it avoids

  • Treating a missing usage report as proof of no use.
  • Giving a cancel-by date without showing how you worked it out.
  • Repeating last month's recommendation as a new finding.
  • Describing this as a running monitor. It is one review at a time.
  • Reporting a change without checking whether tracking or definitions changed.
  • Treating correlation as cause.

What a good result looks like

An example, not your task: A renewal is coming up and you need to know the last day to cancel.

  • renewal-brief.md. Only what changed this month, with the decision window and a recommended path for each.
  • notice-deadlines.md. The last day to cancel each renewal, the sum behind it and the contract wording it came from.
  • options.md. Keep, consolidate, switch and cancel side by side, using prices and fees you supplied.
  • evidence-requests.md. What is missing before a decision, who could supply it and by when.
  • renewal-register.csv. The updated register of every subscription, term, notice date, owner, usage date and decision.
  • owner-actions.md. One proposed action per owner. Drafts only, nothing sent or cancelled.

How the work is checked

  • Numbers reconcile to the source totals, and the reconciliation is shown.
  • Every chart and number states its source, period and definition.
  • Limits and next checks are listed.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

  • Read last month's register. It keeps each subscription's ID, term, notice date, owner, usage date, decision and source. The first run builds the register.
  • Find what changed. A renewal entering your decision window, a new quote or a big change in usage puts a subscription in scope. Unchanged ones are left alone.
  • Work out the deadlines. It subtracts the notice period from the renewal date and shows the sum. It follows the contract's own wording on how days are counted.
  • Fill the gaps first. If notice terms or usage are missing, it checks the contract and writes an evidence request before any advice to cancel.
  • Compare the options. For each changed subscription it sets keep, consolidate, switch and cancel side by side, using only prices and fees you supplied.
  • Propose actions and save. It lists one proposed action per owner, then updates the register. Nothing is sent or cancelled.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id monthly-subscription-renewal-decision-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/monthly-subscription-renewal-decision-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • Your subscription bills or card statement lines for the month
  • Renewal dates and notice periods from your contracts or vendor accounts
  • Usage evidence, such as seats in use or last login dates
  • The owner of each subscription, and how many days before renewal you want to decide
  • Last month's renewal register (optional on the first run)
  • Any new quote or price change from a vendor (optional)

Helpful context (optional)

  • A calendar export of known renewal dates.
  • The vendor's admin usage report.
  • Any past decision notes on why you kept a tool.

Tools and access

  • Claude, ChatGPT or Gemini with file upload: It reads bills, contract text and usage exports together and does the date sums.
  • A spreadsheet tool such as Excel or Google Sheets: Your register lives in a file you can sort by cancel-by date.
  • A chat AI that opens spreadsheet and PDF files: It needs to read your bill export and any contracts. It cannot see inside your tools, so usage notes must come from you.

Functions and deliverables

  • Business subscription renewal reviewer: Review changed bills, usage and renewal terms. Find duplicate costs and evidence gaps before proposing a renewal decision.
    • A renewal brief that covers only what changed since last month
    • A deadline table with the last day to cancel for each renewal and the sum behind it
    • Keep, switch or cancel options, with the yearly cost and the effort to switch
    • Evidence requests for anything missing before you decide
    • An updated renewal register for next month
    • Proposed actions for each owner, none sent
  • Business subscription usage auditor: Check software bills and real use. Compare keep or replace options and list renewal choices with possible savings.
    • A subscription register: each tool, its cost, owner, renewal date and status
    • Savings scenarios that count only from the date a notice period ends
    • Keep, merge or replace choices for the tools worth a second look
    • A dated action list: what to decide, by when, and who owns it
    • A hand-back summary with one next step
  • Vendor agreement status checker: Name a vendor. Get what you signed, what is missing and what expires soon. Verify against the originals.
    • A list of agreements and their status
    • Gaps in the paperwork
    • Upcoming expiry and renewal dates
    • The sources each item came from
    Source: Anthropic.
  • Software subscription terms checker: Find renewal traps, price rises, uptime promises and data exit terms in a software contract before it renews. A first check, not legal advice.
    • A bottom line on whether you can sign, or what to fight for first
    • The renewal date and the last day to cancel
    • Price rise, uptime and data exit findings, each rated for legal risk and business impact
    • AI training, liability cap and law findings
    • A record you can copy into a renewal tracker
    Source: Anthropic.
  • Metric definition writer: Share a metric, calculation and business use. Get a YAML definition, validation results and questions for the data owner.
    • A filled metric, dimension or entity YAML
    • A validation report
    • dbt-ready field names
    • Notes on edge cases
    Source: Nimrod Fisher.

Tasks you can use it for

  • A renewal is coming up and you need to know the last day to cancel.
  • A vendor sends a new quote or raises the price.
  • A team's use of a tool has dropped or jumped.
  • You review software costs every month and want to see only the changes.

Limits to check before starting

  • You want a first sweep of every subscription for duplicates. Use the Business subscription usage auditor workflow.
  • You need one contract checked in depth. Use the Vendor agreement status checker.
  • You sell subscriptions and want to know why customers cancel. Use the Subscriber cancellation and retention reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Download the pack from this page and add it to your AI. If you cannot add it, paste SKILL.md into a new chat.
  • Attach this month's bills or card lines, your contract dates and notice periods, and any usage exports. Attach last month's register if you have one.
  • Say how many days before a renewal you want to decide, and who owns each subscription.
  • Say "Find what changed and work out each cancel-by date. Do not recommend cancelling without contract and usage evidence." Your AI asks once for anything missing.
  • Open notice-deadlines.md first. Check each date against the contract wording yourself.
  • Send the evidence requests and owner actions yourself. Keep renewal-register.csv for next month.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/monthly-subscription-renewal-decision-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.