home / use cases / data, spreadsheets and reporting / scheduled-reports

Weekly reports that write themselves

Every Monday at seven, an Aivell queries your own database — Postgres, Oracle, SQL Server, whatever you run — builds the weekly report, writes it into the management sheet and mails a plain-words summary to the team. No copy-paste, no BI project, and the numbers never leave your office.

Watch the demo

starts when: Monday, 07:00 — the schedule fires

The problem

Somewhere in your company there is a Monday ritual: export from the management system, paste into a spreadsheet, repair the columns that broke, redo the same comparisons as last week, write three lines of commentary, hit send. It eats someone’s best hours on the busiest morning of the week — and when that someone is on holiday, there simply is no report.

The absurd part is that the numbers already exist, correct and current, in your database. The work is not analysis; it is transport. And transport between systems is precisely the kind of work that keeps 62% of employee time stuck in repetitive tasks.

How your Aivell does it

  1. The schedule fires. Monday, 07:00. Nobody exports anything, nobody remembers anything.
  2. The database answers, read-only. The Aivell queries your systems directly — sales, support, whatever the chore names. A guardrail makes the connection physically read-only, so a report can never modify a record.
  3. The comparisons are computed, onboard. Same week last year, budget line, the 15% threshold you wrote into the chore. The reasoning runs on the box; your revenue figures never cross your firewall.
  4. The report reads like a colleague wrote it. A plain-words summary on top — what moved and why it matters — with the tables underneath. The sheet keeps every past week, so the history builds itself.
  5. It lands before the coffee does. The management list gets the summary, Elena gets the detail, and anything the Aivell couldn’t verify is flagged rather than papered over.

The interesting rules stay yours: what counts as “worth mentioning”, who gets which version, what joins the monthly rollup. You change them by editing a sentence, not a report template — and the guardrails make sure the chore can read your data but never rewrite it.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · send monday sales report ● active

every monday at 07:00, query last week's orders from the sales database

break revenue down by product line and by region

compare with the same week last year; call out anything off by 15% or more

pull open complaints from the support sheet and add a short section

write a five-line summary in plain words on top — no jargon

update the weekly tab in the management sheet, keeping past weeks intact

mail the report to the management list; Elena gets the detailed version

first monday of the month, append the monthly rollup too

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule starts the report run every Monday
Database runs the queries, read-only
Spreadsheets writes the report tab, keeps history
Email delivers the summary to the team

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Database Read-only on the reporting schemas. No insert, update or delete can run, however the query is phrased.
Email May send only to the management list and named colleagues. External addresses are blocked.
Spreadsheets Writes only the weekly tab it owns; every other tab in the workbook is read-only.

Questions, answered.

Do I need a BI tool or a data warehouse for this? +

No. The Aivell talks to the database you already have — Postgres, Oracle, SQL Server, anything with a standard driver — and to Google Sheets. The report is described in plain language, not in a dashboard builder.

Our figures are commercially sensitive. Where are they processed? +

On the box, in your office. The queries run against your database over your own network, the reasoning happens onboard, and the mail goes out through your own mail server. No analytics cloud ever sees a number.

Can I change what's in the report without calling IT? +

Yes. The report is a chore written in sentences. Add "include a table of the ten slowest-paying customers" and next Monday it's there.

What happens if a query fails or a number looks impossible? +

It says so. Rather than mailing garbage, the Aivell flags what it couldn't verify — a failed query, a revenue figure ten times the usual — and asks before sending.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee