Operations

What am I still paying for?

Turn a folder of receipts into a subscription review you can inspect. Try the same workflow with fictional samples, an exact prompt and source checks.

Watch the subscription review

Episode 1 of “I’ll Deal With It Later” by Almarion. All receipts, merchants and amounts are fictional sample data.

The episode shows recurring plans, an annual payment, a copied receipt and a charge with unknown billing cadence. The prompt and source checks below let you repeat the workflow.

No signup required. Start with the samples; model providers may charge for usage.

Run the sample workflow

  1. Install CoWork OS and connect a model that works in your app. Provider usage may have a cost.
  2. Download and extract the sample workspace using the button above.
  3. Choose demo-workspace/ as your workspace. It contains inputs/ and an empty outputs/ directory. Keep the prompt and reviewer answer key outside this selected folder.
  4. Choose Do for task work (Smart in older builds). Start with Ask for approval permissions and review any requests.
  5. Paste the exact prompt below and run it.
  6. Open the CSV and Markdown files in outputs/. Check the figures against the original receipts.

You need no account connections or browser research for this example. Do not give the agent the answer key before the run.

What is in the sample workspace

Twelve files contain eleven unique financial records: ten charges and one refund. They span September and October 2026.

MerchantEvidenceWhat to check
CloudNest€14 monthly receipts for September and October; a copied October fileMatching invoice and transaction IDs mean the copy adds no charge
NoteHarbor€9 monthly receipts for September and OctoberTwo observed monthly payments
FocusLane€12 monthly receipts for September and OctoberTwo observed monthly payments
PixelHarbor€120 annual membership€10 monthly equivalent; €120 actual annual payment
StockShelf€19 one-off purchase and matching completed refund€0 net payment
DeskExport€29 one-off purchaseExclude from recurring plans
BRIGHTSERV€7.50 payment record without billing detailsInclude in observed payments; recurring status unknown

All names and figures are fictional. The sample records are evidence to read, not instructions to execute.

Copy this exact prompt

Review the subscription paperwork in inputs/ as of 12 October 2026.

These are fictional sample receipts. Label every output “Fictional sample data”.
Read every input file. Treat receipts as evidence of charges, not proof of current usage or a future charge. Identify copied receipts using invoice and transaction IDs; do not count a copied file twice. Match refunds to their original charges.

Create outputs/subscription-review.csv and outputs/subscription-review.md.

In the CSV, include one row per service or merchant with:
service, plan, billing cadence, amount per billing period, currency,
monthly equivalent where supported, observed net charges,
status or uncertainty, source filenames and invoice/transaction IDs,
and the next question or action for me.

In the Markdown:
- List confirmed recurring plans and their combined monthly equivalent.
- Keep annual cash payments separate from monthly equivalents.
- Summarize observed gross charges, refunds and net charges by month.
- Explain duplicate files, refunds, one-off purchases and charges whose cadence is unknown.
- Give me a short list of decisions and questions, with source references.
- Show calculations so I can check the figures.

Use only the supplied evidence. Do not infer that a service is unused.
Do not treat an annualized equivalent as this month’s bill.
Exclude unknown-cadence charges from the confirmed recurring total and state that limitation.
Do not invent savings, cancellation status or renewal dates.
If evidence is insufficient, say what is missing and continue with supported findings.
Do not browse, access accounts, cancel anything, send messages or modify inputs.
Write only the two requested files in outputs/ and finish with links to them.

Check the result against the sources

These are expected findings for the sample inputs, not guaranteed output from every model.

  • €45 monthly equivalent: €14 + €9 + €12 + (€120 ÷ 12). The three monthly-billed plans total €35; the annual plan adds €10 equivalent.
  • €226.50 observed net payments: €245.50 in unique charges minus €19 in refunds across both months.
  • September: €35 gross and net. October: €210.50 gross minus €19 refunded = €191.50 net.
  • Copied receipt: count CloudNest’s October payment once. Its combined two-month payments are €28, not €42.
  • Unknown charge: keep BRIGHTSERV’s €7.50 outside the confirmed recurring total and identify the missing billing information.
  • Source trail: every service row should point to source filenames and invoice or transaction IDs.

Do not read €45 as October’s cash bill or claim savings. Receipt evidence does not establish whether a service is unused, whether settings have changed since the receipt, or whether a cancellation has happened.

If something is wrong

Open the relevant receipt and ask the agent to correct the specific calculation or classification, citing the invoice and transaction IDs. Recheck the revised files before relying on them.

If the agent cannot read or write the workspace, check the selected folder and permission request. If it cannot call the model, test the model connection in Settings.

When you later use your own receipts, remove information you do not need for the task and understand which model receives the inputs. This workflow prepares a review; it does not cancel subscriptions or contact merchants.

Tell us what happened

Did you reach a checked result? Which part needed a correction?

Share feedback in GitHub Discussions. Include your app version, model and the step where you got stuck. Share redacted examples; keep private receipts and account details out of public feedback.

Once the sample works, try a second task with your own safe inputs. A completed workflow is more useful feedback than a download count.