Skip to content

List · reads subscription

Subscriptions

Recurring costs & renewals.

One row per item, the plainest possible view.

The "used" column is what makes this actionable rather than merely depressing.
  • Design suite€59/mo
  • Project tool€32/mo
  • Email marketing€110/mo
  • Stock photos€290/yr

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

The total at the bottom is the point. Individually every line looks reasonable, and the annual figure is the one nobody has looked at.

Records how recently each was actually used, which turns an audit from an opinion into a list.

Renewal dates are surfaced before they charge rather than after, which is the only moment cancelling is easy.

Annual and monthly costs are normalised, so a 290-a-year service is comparable with a 32-a-month one.

How it works

  1. 1

    Subscriptions are recorded as they are noticed, usually while looking at a statement.

  2. 2

    Costs are normalised, so a yearly service compares against a monthly one.

  3. 3

    Renewal dates surface before the charge rather than after.

  4. 4

    The used column is asked about explicitly, because nobody volunteers that they stopped using something.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
ServicerequiredtextWhat is being paid for, as it appears on the statement.
CostrequiredmoneyWhat it costs per period, normalised so annual and monthly compare.
RenewsrequireddateThe next charge. The only moment cancelling is easy.
UsedrequiredtextHow recently it was actually used. What turns an audit from an opinion into a list.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • Nothing detects a subscription automatically; they are entered.
  • Usage is self-reported and therefore optimistic.
  • No cancellation — this tells you what to cancel, it does not do it.
  • Per-seat pricing is a single figure here, so a team that grew is not tracked.

Before it works

What you have to provide, if anything.

  • Do it in one sitting from a statement. Piecemeal, the total never appears.
  • Pair with Expenses so the recurring and the one-off are visible together.

In practice

A five-person agency that had been adding tools for four years.

What are we actually paying for every month?
What was said to the agent

What the agent built

Eleven services with costs, renewal dates and last-used notes gathered over a fortnight of conversation.

What changed

Two were unused since May and one had been used twice ever. Cancelling those three was 4,900 a year, decided in one meeting.

Questions

What data does the Subscriptions page use?

It reads subscription records the agent has collected. Recurring costs & renewals. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ