Ask Lumen: an AI that asks before it touches your books

The fastest way to lose trust in business software is to let it change numbers nobody asked it to change. So Ask Lumen draws a hard line between answering and acting.

Answers are instant. Actions are proposals.

Ask "which items are below reorder level?" or "how did Outlet B do this month?" and you get the answer straight away, from your live records — nothing is written, nothing moves.

Ask it to do something — draft an invoice for Karim Traders, create payroll for May, log a call and set a follow-up — and Lumen prepares the work and puts it on the agent board as a task. Someone with permission to approve sees exactly what it is about to do, down to the line items, and approves or rejects it.

Why a board and not a chat message

A proposal sitting in a chat log gets lost. A task on a board has a state: waiting, approved, rejected, done. It also has an audience — the person whose permissions actually allow the change, which is not always the person who asked. That is the difference between an assistant and an autopilot.

What it is good at today

• Finding things. Questions that would otherwise be a report you have to build: slow-moving stock, overdue receivables, this month against last.
• Drafting. Invoices, quotations, proposals and payroll runs, pre-filled from records that already exist, for you to check rather than type.
• Remembering. Logging calls, notes and follow-ups against the right customer without you navigating there first.

What it will not do

It will not post an entry you did not see, it will not act outside the asker's module permissions, and it will not reach data the asker cannot open. Every change is written to the owner-only audit log, whether a person or the assistant proposed it.

Used this way, the AI stops being a risk to your books and becomes the fastest way to get work into them.