Automated reporting — The weekly numbers arrive on their own, from every system you use
Automated reporting gathers figures from the systems a business runs on, such as bookings, sales, jobs and accounting. It builds the same report on a schedule and sends it by email or Slack, with a short written summary of what changed. Owners stop exporting spreadsheets to see how the week went.
By Julia Ja, Owner
Weekly report · new bookings
Sample dataSummary: Bookings were up on last week, mostly from web requests. Two large jobs are waiting on a quote.
Why it matters
The problem it solves
Many owners see their numbers only after someone exports from each system and builds a spreadsheet. That person has other work, so the report comes late or gets skipped in busy weeks.
When different people build the report, the same number gets counted different ways. Meetings turn into debates about whose figure is right instead of what to do about it.
Example · illustrative
A two-location restaurant on Monday morning
- 6 am on MondayThe weekly report lands in the owner's inbox.
- It shows sales, labor and voids for each location from Toast, next to the week before.
- The summary notes that voids at the second location ran higher than usual on Friday night.
- The owner forwards that line to the manager and asks what happened on that shift.
How it works
How automated reporting works
- Starts whenA set time each day, week or month
- 1Step 1Pull the numbersFigures are collected from each system's API or scheduled export.
- 2Step 2CalculateEach number uses the same definition every time, such as jobs booked versus completed, open quotes and overdue invoices.
- 3Step 3Write the summaryA short plain-language note says what moved since last period and what looks unusual.
- 4Step 4DeliverThe report goes out by email, Slack or a shared dashboard.
- A person decidesAct on itOwners and managers decide what to do about what the numbers show.
Before · by hand
- Someone exports from several systems into a spreadsheet.
- The report is late whenever that person is busy.
- Numbers change depending on who built the report.
With automated reporting
- The report arrives on schedule without anyone building it.
- Every number uses the same definition each time.
- A short summary points out what changed.
What we build
The parts of automated reporting
Your systems
- QuickBooks Online
- HubSpot
- ServiceTitan
- Shopify
- Toast
- Google Sheets
What we build
1Data connections
Pulls figures from each system's API or scheduled export, such as Toast, ServiceTitan, Shopify or QuickBooks.
2Metric definitions
A written definition for each number, applied the same way every time, such as what counts as a completed job or an overdue invoice.
3Report layout
Places each number next to the same period last time, grouped by location, team or service.
4Written summary
A short AI-written note on what moved and what looks unusual, always shown beside the figures it describes.
5Data checks
Flags a source that is missing or late, so a report never presents partial data as complete.
6Delivery
Sends each version to the right people by email, Slack or a shared dashboard, on the schedule you choose.
Your team decides
- Owners and managers decide what to do about the numbers.
- The business agrees on what each number means before the report is built.
Industries it fits
What automated reporting looks like in each industry
HVAC, plumbing & electrical
A Monday report from ServiceTitan shows jobs booked and completed, open quotes and revenue per technician. Callbacks and canceled jobs are counted the same way every week, so technicians compare fairly.
Everything for hvac, plumbing & electricalYour industry isn’t listed, or works differently? Describe it and get an answer in a minute.
Getting started
What you need first
We go through these with you in the audit, before anything is built.
Before we start
4 things to have ready- Access to each system the numbers come from, through an API or a scheduled export.
- Agreed definitions for each number, signed off by the owner or manager.
- A list of who gets which report, and on what schedule.
- Someone who can say when a number looks wrong and help trace it.
How a rollout runs
- 1Pick the numbersWe list the decisions the report should support, and the few figures that inform each one.
- 2Define each numberWe write down how each figure is calculated and check it against a report you already trust.
- 3Connect the sourcesWe connect each system and confirm the figures match what staff see inside that software.
- 4Run beside the manual reportThe automated report runs next to the spreadsheet version until both show the same numbers.
- 5Hand over and adjustThe manual report stops, and numbers are added or dropped as the questions you ask change.
What to measure
How to know it's working
Weekly report · automated reporting
IllustrationReports delivered on schedule
The basic test. A missed report usually means a broken connection.
Spot checks that match the source
Comparing a few figures with the source software keeps trust in the report.
Data warnings raised
Shows how often a source is late or incomplete, and which one.
Summary corrections
Each time the written note misreads a trend, the summary rules are tuned.
Decisions taken from the report
If nobody acts on a number, it may not belong in the report.
We measure the baseline before building, so the change can be compared afterwards.
When it’s not a fit
- It can't fix bad source data. If jobs or sales are recorded inconsistently, the report repeats the mess on schedule.
- Too many numbers make a report nobody reads. A short report with the right figures gets used.
- The written summary can misread a trend. The figures always come first, and the note is a pointer.
- If nobody has decided what a number means, that decision has to happen before anything is built.
Tool or custom build
Do you need a custom build?
Option A · a ready-made tool
An off-the-shelf tool may be enough
Most systems have built-in reports, and tools like Looker Studio, Power BI and Databox combine sources into dashboards. They suit teams with someone who likes building and maintaining them.
Option B · built around your systems
When a custom build is worth it
A custom build makes sense when numbers need your own definitions across several systems. It also fits when you want a written summary in email or Slack, with nobody maintaining it.
Not sure which fits?
What it typically costs
Typical ranges as of October 2026. Not a quote.
Ready-made tool, set up by us
An existing platform on your own account, configured for your business.
- Setup, one timepaid to Lorryn
- $750–$1,500
- Tool subscriptionpaid to the provider
- $15–$75 / month
Fits when your process matches what the platform already does.
Custom build
Built around how you work, with no platform subscription. You own it.
- Build, one timebasic version to full version
- $2,000–$5,000
- Running costshosting and usage, on your accounts
- ~$5–$25 / month
Fits when your systems, rules or exceptions don't match a ready tool.
Optional Automation Care: $125 · $250 · $375 / month
1, 2 or 3 hours of support a month, with monitoring and alerts included. Without it, you run it yourself after handover.
Typically works with QuickBooks Online, HubSpot, ServiceTitan, Shopify.
Booking into or writing to your field-service, practice or shop software adds up to $500 to the ready-made tool (often a built-in feature) and $500–$1,500 to a custom build.
Your price depends on volume, the systems involved and how many exceptions need a person. Our team confirms a fixed price before any work starts.
Proof and who stays in charge
Who does what
The automation does the routine steps. A person makes the call.
- 1Pull the numbersAutomated
- 2CalculateAutomated
- 3Write the summaryAutomated
- 4DeliverAutomated
- 5Act on itA person
Consent and privacy
Reports that include patient data stay within HIPAA-covered systems and vendors that sign a BAA.
FAQ
Questions about automated reporting
Yes, that's the main point. Numbers from booking, sales and accounting can sit side by side in one report.
It can misread a trend now and then, so the figures always sit right next to it. You judge the numbers, and we tune the summary rules if it misses.
No. Most owners prefer an email or a Slack message. A shared dashboard can be added if your team wants one.
Yes. Once the systems are connected, adding a number or changing the schedule is a small change.
You choose the recipients. Owners, managers and staff can each get a version with only the numbers they need.
The report says which source is missing rather than showing partial numbers as complete. It can be resent once the data arrives.
You do. The definitions, queries and report layout belong to the business and are documented.
Related use cases
Often built together
- Data & reportingSystem syncKeeps customers, jobs and invoices in step between the systems your team already uses.
- Data & reportingData cleanup and alertsFinds duplicates, gaps and odd values in your records and alerts the person who can fix them.
- Billing & paymentsBank and payment reconciliationMatches bank deposits and processor payouts to invoices and flags what doesn't line up.
Want automated reporting for your business?
Pick the step that suits you. Every path starts with how the work runs today, and we'll say honestly whether it's worth automating.
- Right now · any hour
Ask Lorryn AI
Describe your process and get a first answer in a minute: what to automate, what it connects to, and a rough estimate.
- Free · 15 or 30 minutes
Talk to our team
Bring one process to a video call. Leave knowing whether it’s worth automating and how.
- Free · 6 of 15 spots left
Get a free written plan
Free for businesses with 3 or more employees, while spots last (normally $250).
Claim a free audit9 of 15 claimed