A daily business summary email is one short message that arrives at the same time every morning, usually around 7, listing the few things that need attention today: invoices that have gone overdue, today's jobs or bookings, payments due out, and anything that went wrong overnight. It pulls those lines from the systems you already pay for (Xero or QuickBooks, your calendar or booking system, a spreadsheet, your inbox) so you read one email instead of logging into six places. It's built either with your software's own scheduled emails, when one system holds everything, or with a small flow that runs every morning and stitches several systems together.
I'm building one for my own business at the moment. The idea is that every morning at 7, everyone gets an email listing that day's jobs. That's it. Nothing clever, no charts, and in actual fact it's the first thing I wanted automated because it's the first thing I check every day anyway. Yours will have different lines in it, but it's the same kind of build.
What should a daily business summary email include?
Whatever you currently check first thing, in the order you'd want to act on it. That's different for every business, which is why there's no universal template, but the shape repeats. A few examples:
The owner of a small business. Three invoices are overdue, you owe one supplier on Friday, and the Screwfix delivery is booked for 10. One message instead of logging into Xero, your inbox and the supplier's site before the kettle's boiled.
A salon. Today's bookings per stylist, any gaps that could still be filled, and the clients who cancelled yesterday so someone can offer the slot. On a Monday, the free slots for the week, so nobody's scrolling the calendar while a customer waits on the phone.
A trades business. Today's jobs and who's on them, quotes that have gone quiet for a week, and materials due on site.
A finance team. Cash in the bank across accounts, what came in yesterday, what's going out this week, and the debtors who've just tipped past 60 days. Not the full aged debtors report (that's a different job, covered in an aged debtors report people act on), just the movement since yesterday.
Here's how those lines typically map to sources. The middle column is the list of systems the email will read from, and the last column is the test every line has to pass.
| Line in the email | Source system | Why it's there |
|---|---|---|
| Invoices that went overdue yesterday | Xero, QuickBooks or Sage | Someone needs to chase them today, and yesterday's new ones are the easiest to collect |
| Bills due out this week | Accounting system | So a payment run is never a surprise |
| Cash position | Bank feed via the accounting system | One number that tells you whether today is a normal day |
| Today's jobs or bookings, by person | Calendar, booking system or job management tool | People turn up in the right place without asking |
| Gaps and cancellations | Booking system | An empty slot at 9am is still sellable at 7am |
| Quotes with no reply after seven days | CRM, quoting tool or a spreadsheet | A nudge today is cheaper than a lost job |
| Deliveries expected | Supplier emails or a shared inbox | Someone is there to sign for them |
| Anything that failed overnight | Website, payments or the email's own checks | You hear about a problem before a customer tells you |
You won't want all of those. Four or five lines is plenty, and the right four or five are the ones that change what someone does before 9.
What makes a morning email get read instead of ignored?
A summary email that people stop opening after a fortnight is worse than none, because everyone assumes someone else is reading it. Four rules, and honestly they matter more than anything about how it's built.
Keep it short. If it doesn't fit on a phone screen without much scrolling, it's too long. The point is that it's read in the queue for coffee, not printed out.
Exceptions first. Lead with what needs a person: the overdue invoice, the cancelled booking, the failed payment. Things that are on track go underneath, or don't appear at all. An email that opens with "Sales yesterday: £4,212" and buries "Card payments failed overnight" at the bottom has its priorities upside down.
Same layout every day. Same subject line format, same sections, same order. After a week, the reader's eye goes straight to the bit they care about. Change the layout deliberately and rarely.
Nothing when there's nothing. If no invoices went overdue, that section disappears rather than saying "Overdue invoices: none". If nothing at all needs anyone, the email can say so in one line, or not send. A message that's the same length every day trains people to skim it; a message that's short on a quiet day and longer on a busy one tells them something before they've read a word. It feels safer to show everything, but the email is useful precisely because it's selective.
Where does the data come from?
From wherever it already lives. A daily summary doesn't need a new system, and it shouldn't involve anyone typing numbers into a spreadsheet so the email can read them, because then you've automated the easy half and kept the hard half.
The usual sources are:
- The accounting system for overdue invoices, bills due and the bank balance. Xero, QuickBooks and Sage all have APIs that an automation can read.
- Calendars and booking systems for today's jobs and appointments. Outlook and Google calendars are easy to read; booking systems vary, and some only offer an export.
- Spreadsheets that someone already maintains, like a quote tracker or a job list in Excel on SharePoint. These are fine as sources as long as they're kept up to date for their own sake.
- Inboxes for things that only arrive by email, like supplier delivery confirmations. A flow can look for them and pull out the line that matters.
Where a system has no way in except a scheduled export to a mailbox or folder, the automation reads the export instead. Less elegant, but it works.
Can my existing software send this for me?
Sometimes, and it's worth checking before paying anyone.
QuickBooks Online can email a group of saved custom reports on a recurring schedule, to people who don't need a QuickBooks login, with the report attached as an Excel file if you want it. Intuit says report groups and scheduled emails aren't available on the Simple Start plan. If everything you'd put in a morning email is already in QuickBooks, set up a custom report group and schedule it. Done, no build.
Xero reports are built to be run rather than sent. Automatic scheduled report emails have been a long-standing request on Xero's own product ideas forum, so for a Xero-based summary you'd normally use something outside Xero to do the sending.
Power BI, if your numbers already live in a Power BI report, can email a snapshot of a report page on a schedule (hourly, daily, weekly, monthly, or after the data refreshes). Subscribing other people needs a paid Power BI Pro or Premium Per User licence. It's good for a numbers summary, less good for "who's on which job today", because what arrives is a picture of a page rather than a list someone can act on.
Booking and job management systems often have their own notification settings. Look there first for a day sheet before building one.
The honest test is simple: if one system already does it, switch it on and keep your money. A built automation earns its keep when the email needs lines from three different places, because none of those systems knows about the other two.
How is a daily summary email built?
For a business on Microsoft 365, usually with Power Automate. The plain version is a flow that runs every morning at, say, 6:45. It reads each source in turn: the overdue invoices from the accounting system, today's entries from the calendar, the open quotes from the spreadsheet. It applies the rules (only invoices that went overdue yesterday, only quotes older than seven days, drop any section that's empty) and then builds one email and sends it from a shared mailbox to the people who need it.
A few practical things worth knowing:
- Microsoft 365 already includes Power Automate for flows that use standard connectors, which covers Outlook, Excel, SharePoint and Teams. Connecting to an accounting system is usually a premium connector (the Xero one in Power Automate is premium and published by a third party), and premium connectors need a paid licence. That's covered properly in whether Power Automate is included in Microsoft 365.
- One email can differ per person. The office manager gets the full list; each engineer gets just their own jobs. Same flow, same sources, a filter per recipient.
- It runs alongside the old way first. For a week or two, someone still does their usual morning checks and compares them with the email. When the two agree every day, the manual checks stop. That's the step that makes people trust it, and skipping it is how you end up with an email nobody believes.
- It should tell you when it breaks. If a source can't be read, the email says so in a line at the top, rather than quietly sending a shorter email that looks like a quiet day.
How is this different from a daily sales report?
A daily sales report answers "how did we do yesterday?" with sales against target, by product or region, compared with last week; it's covered in the daily sales report that builds itself. A daily business summary answers "what needs me today?" and is mostly lists of things to act on. A sales headline can be one line in the summary, but making one email do both jobs is how it ends up too long to read.
If you're still working out whether this is the right first thing to automate, what a small business can automate goes through the wider list. The morning email is a good candidate for a first one, though, simply because it gets used every single day, so you find out quickly whether it's right.
Anyway, if you'd like one built over the systems you already have, that's what I do on the business automation page. An automation check is £295 and comes off the build in full, a summary email from one or two sources is from £950 fixed, and upkeep is an optional £95 a month.
Common questions
What is a daily business summary email?
It's a short, automated email that arrives at the same time every morning listing what needs attention that day: overdue invoices, today's jobs or bookings, payments due and anything that failed overnight. It reads from the systems the business already uses, so nobody has to log into each one to find out.
What time should a daily summary email be sent?
Before the first person starts work, so it's read before the day takes over. A trades team on site at 7:30 might want 6:30; an office might want 7. Keep it the same time every day.
Can Xero or QuickBooks send a daily summary email?
QuickBooks Online can email a group of saved custom reports on a recurring schedule, though not on the Simple Start plan. Xero's reports are designed to be run rather than sent on a schedule, so a Xero-based summary is usually sent by something outside Xero, such as Power Automate. Both have built-in invoice reminders to customers, which is a different job.
What should I leave out of a morning summary email?
Anything that doesn't change what someone does today. Month-to-date trends, charts and long tables belong in a report. Sections with nothing in them should disappear on the days they're empty, so the length of the email itself tells people whether it's a busy day.
Do I need Power BI to send a daily summary email?
No. Power Automate can build and send the email directly from the source systems. Power BI subscriptions are useful when the numbers already live in a Power BI report, but they send a snapshot of a report page, which is better for figures than for lists of jobs or invoices to chase.
How much does a daily summary email cost to build?
If one system already holds everything and can schedule an email, nothing beyond setting it up. A built one that joins one or two sources is from £950 fixed with me, with an optional £95 a month for upkeep. Pulling from an accounting system through Power Automate usually needs a premium licence on top of Microsoft 365.