What you start with
- The same export, from the same system, with the same problems in it
- Last month’s report, which you will mostly be copying
- A distribution list that has not changed in two years
- A quiet dread on the last working day of the month
Use cases · The monthly report
Do it once.
Then never again.
Recurring reporting is the same work, on new numbers, forever. The first time is a job. The twelfth time is a tax. LumenQube is built so the first run teaches it the second.
What you say
Clean this export the way we did last month, rebuild the dashboard, write the summary, and send me the PDF to check.
One message. LumenAgent plans the run, asks before anything leaves your machine, and shows each step as it happens.
What it does
-
1
It cleans the export the same way every time
The same column mapping, the same de-duplication, the same currency handling — because it is following the run you already approved, not guessing again.
-
2
It rebuilds the dashboard
Charts, totals and the comparison against prior periods, in a real spreadsheet you can open and interrogate.
-
3
It writes the summary
What moved, by how much, and against what. Reading off the sheet it just built.
-
4
It prepares the distribution
Exports the PDF and drafts the message — and stops there. Anything that leaves your machine waits for you to approve it.
-
5
You save it as a flow
One click turns the run you just watched into a LumenFlow with a schedule.
-
6
Next month it runs itself
On the first, on time, with the new export. You get the finished PDF and the draft, and you decide whether to send.
What you are left holding
Real files, in the formats other people expect. Open any of them and keep working — nothing here is a screenshot of an answer.
- Monthly-dashboard.lumensheetThe model and the charts, rebuilt on the new numbers
- Monthly-summary.lumendocThe written narrative, reading off that sheet
- A PDFThe version you actually distribute
- A saved LumenFlowThe whole thing, on a schedule, from now on
The whole run is one undo. If it took a wrong turn, one click puts every file back the way it was. Nothing is committed anywhere until you say so.
Then stop doing it by hand
This is the page where the automation is the point rather than the postscript. A LumenFlow watches for its trigger without spending any AI credits — the meter only moves when the work runs. That is what makes it reasonable to automate something that fires twelve times a year.
Questions
Does the automation send things without me?
Not unless you set it up that way. Anything outward-facing — email, publishing, sharing — passes an approval gate, and the safest setting keeps a human on every send.
What does it cost to have an automation waiting?
Nothing. Watching for a trigger spends no AI credits; only the run itself does. That is asserted by a test, not just a promise.
What if the export format changes?
The run fails visibly rather than producing a confidently wrong report. You fix it once, re-save the flow, and it carries on.
Can it pull the export automatically?
If the source is one of the 108 connected apps — Drive, Outlook, Dropbox, Slack and the rest — yes, with the scope you granted and nothing more.