Case study: Budget Hub
Running Budget Hub on automation.
A small team cannot check a product by hand every day, and a problem a customer finds first is found too late. So we automated the routine, and kept the decisions.
- 3areas automated: monitoring, reporting and content
- 80scheduled runs every week
- 100%of drafts reviewed by a person before publishing
A day on autopilot.
Budget Hub is a monthly budgeting product that shows people how much they have left to spend. Most of the routine around it happens before we sit down.
-
Overnight
Health checks
Site, sign-in, security, certificates, backups and storage are checked while nobody is looking.
-
Early morning
Errors and payments
Error reports are summarised and the payment set-up is confirmed before customers arrive.
-
Morning
Numbers and news
A summary of sign-ups and conversion, and a scan of South African news that matters to household budgets.
-
Mid-morning, then midday
Drafts for review
Social posts are drafted daily and blog articles three times a week. A person reviews every one.
Eight automations, one table.
What each one is for, what it does, and what a person still does with the result.
| Automation | The problem | What it does | Runs | Our part |
|---|---|---|---|---|
| Site and security checks | Faults and weak settings go unnoticed until someone complains. | Checks the site, sign-in, security settings and certificates. | Daily | Read the summary and fix what is flagged. |
| Backup and storage checks | A failed backup is only discovered when it is needed. | Confirms backups ran and are intact, and watches storage use. | Daily | Act on any warning. |
| Payment checks | A broken payment set-up costs revenue without any visible error. | Confirms payments are configured and working. | Daily | Act on any warning. |
| Error digest | Errors pile up in a tool nobody opens. | Summarises new, recurring and spiking errors. | Daily | Decide which to fix first. |
| Daily metrics | The numbers are spread across several dashboards. | Summarises sign-ups, activity and conversion in one message. | Daily | Decide what to do with the numbers. |
| News scan | Hard to tell which news matters to people's budgets. | Picks a few South African stories and shows the budget angle of each. | Daily | Choose what is worth acting on. |
| Social drafts | Posting consistently takes time a small team does not have. | Drafts posts for social media from the news scan. | Daily | Review, edit and publish. |
| Blog drafts | The blog goes quiet when nobody has time to write. | Drafts a blog article on a budgeting topic. | Three times a week | Review and approve before it goes live. |
Where the work goes.
Scheduled runs per week, by area
Routine work that would otherwise need a person every day.
80 scheduled runs a week in total. These are runs scheduled by design, not a measure of results.
Monitoring: we hear first.
Overnight and early-morning checks on everything a customer would notice if it broke.
- Site and sign-in
- Security settings
- Certificates
- Backups
- Storage use
- Payments
- Error reports
- The problem
A fault in availability, security, backups or payments does damage while nobody is looking, and checking each by hand every day does not happen reliably.
- What it does
Runs a set of checks every day and sends short summaries. Anything that needs attention is flagged.
- The benefit
We learn about a problem before customers do, and we start the day knowing the state of the product.
- Our part
We read the summaries and act on anything flagged.
Reporting: one short read.
A morning summary of how the product is doing, and what is happening in the news that touches it.
- Sign-ups
- Activity
- Conversion
- News scan
- The problem
Knowing how the product is doing meant opening several dashboards and piecing the picture together by hand.
- What it does
Summarises sign-ups, activity and conversion, and scans South African news for stories with a household-budget angle.
- The benefit
One short read shows where the product stands and what is worth talking about today.
- Our part
We decide what to do with the numbers and which stories to act on.
Content: drafted, then approved.
AI-assisted drafts of social posts and blog articles, written for a person to review. Nothing publishes on its own.
- Social post drafts
- Blog drafts
- AI-assisted
- Reviewed before publishing
- The problem
Publishing regularly about money takes time a small team spends elsewhere, and it stops whenever nobody has the time.
- What it does
Drafts social posts from the day's news, with a Budget Hub angle, and drafts blog articles three times a week.
- The benefit
A steady flow of relevant content, written to a consistent standard, without depending on someone finding the time.
- Our part
A person reviews every draft before anything is published.