Automated Spendesk Subscription Reviews
Every Monday, WebRun opens Spendesk, lists every active subscription card with its supplier, cardholder, budget, and the recurring amount last charged, posts the review to Microsoft Teams grouped by owner, and texts the finance lead the weekly recurring total through Twilio.
How do I review recurring subscription spend before the next charge?
WebRun reviews your recurring spend every Monday. It opens Spendesk, lists every active subscription card with its supplier, cardholder, budget, and last recurring charge, posts the review to Microsoft Teams grouped by owner, and texts the finance lead the weekly total through Twilio before the next charges land.
- Unused tools get cancelled before they renew
- Every recurring charge has a named owner in the weekly review
- The finance lead sees the recurring total without opening a dashboard
Built for finance leads · controllers · operations managers · startup founders
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.spendesk.comin a real browser with your saved login - no setup, no API keys. -
1
Spendesk - list active subscription cards
WebRun opens Spendesk to list active subscription cards. - Open Spendesk and go to the subscription cards list
- Capture each active card with its supplier, cardholder, and the budget it draws from
- Note the last recurring payment amount and the date it was charged
- Work out roughly when the next charge is due from the recent payment pattern
- Never pause, cancel, or delete a card. WebRun only reads and reports
Done when Every active subscription card is captured with its supplier, owner, budget, and last charge.
-
2
Microsoft Teams - post the review by owner
WebRun opens Microsoft Teams to post the review by owner. - Post this week's recurring spend review to your finance channel in Teams
- Group the cards by cardholder so each owner sees what they are responsible for
- Sort within each group by recurring amount, largest first
- Flag cards whose next charge falls in the next seven days and any supplier that is new since last week
Done when The finance channel has this week's recurring spend review, grouped by owner.
-
3
Twilio - text the finance lead the total
WebRun opens Twilio to text the finance lead the total. - Send a short text to the finance lead's own number with the weekly recurring total
- Include how many cards are active and how many charge in the next seven days
- Name any subscription whose amount rose since the last review
- Keep the message internal. WebRun never contacts a supplier
Done when The finance lead has this week's recurring total and renewal count on their phone.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it cancel a subscription card?
No. WebRun reads the subscription cards in Spendesk and reports them. Pausing, cancelling, or deleting a card stays a human decision, so no supplier relationship changes without someone in finance acting on it.
How does it know who owns a subscription?
From the cardholder and budget on each Spendesk subscription card. The Teams review is grouped by that owner, so each person sees the recurring charges sitting under their name.
Will it contact suppliers?
No. Everything it sends is internal: a Teams post to your finance channel and a text to the finance lead's own number through Twilio. Cancelling with a supplier is always done by a person.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.