Finance
Spend review
Review a card or bank export: categorise every line, flag duplicates, new subscriptions and price rises, and total spend against last month.
Add in the app
Finance · For your bots
Revenue snapshot
Summarise revenue for a period (new, expansion, churn, refunds, failed payments) against the last period, with a chart. Read-only.
In Lobstack: Skills › Library › Add
Download LobstackWhen to use it
Someone wants to know what came in over a week, month or quarter and why it moved — usually from Stripe or a billing export.
What your bot will do
- 01
Fix the period, timezone and currency first, and state them at the top. Most arguments about revenue are arguments about where a day ends.
- 02
Read only. Never refund, cancel, retry a charge or edit a customer, even when the connection would allow it.
- 03
Pull each figure for this period and the last:
- total collected, and recurring revenue if there are subscriptions;
- new customers and what they brought in;
- upgrades and downgrades;
- cancellations and the revenue lost with them;
- refunds and disputes;
- failed payments still unpaid.
- 04
Show every figure beside last period's, with the change. Put the main series in a chart fence.
- 05
Explain the biggest moves, including dull causes: a billing date that moved, an annual renewal, a batch of refunds, a price change.
- 06
Mark a figure "missing" when you could not get it. Never estimate one to fill the gap.
- 07
Post it as a document, headline first. Offer to repeat it on a schedule, and ask before saving the routine.
Leave individual customer names out unless the person asks for them.
The file
---name: revenue-snapshotdescription: "Summarise revenue for a period (new, expansion, churn, refunds, failed payments) against the last period, with a chart. Read-only."metadata: title: "Revenue snapshot" category: finance tags: [finance, revenue]--- ## When to use this Someone wants to know what came in over a week, month or quarter and why itmoved -- usually from Stripe or a billing export. ## How 1. Fix the period, timezone and currency first, and state them at the top. Most arguments about revenue are arguments about where a day ends.2. Read only. Never refund, cancel, retry a charge or edit a customer, even when the connection would allow it.3. Pull each figure for this period and the last: - total collected, and recurring revenue if there are subscriptions; - new customers and what they brought in; - upgrades and downgrades; - cancellations and the revenue lost with them; - refunds and disputes; - failed payments still unpaid.4. Show every figure beside last period's, with the change. Put the main series in a chart fence.5. Explain the biggest moves, including dull causes: a billing date that moved, an annual renewal, a batch of refunds, a price change.6. Mark a figure "missing" when you could not get it. Never estimate one to fill the gap.7. Post it as a document, headline first. Offer to repeat it on a schedule, and ask before saving the routine. Leave individual customer names out unless the person asks for them.