Skip to content

Why Ask Lucy

Most AI tools ask you to choose between useful and allowed. Ask Lucy is built so a bank, a fund administrator, a law firm or a public body does not have to.

Lucy runs on EU-built Mistral models, on infrastructure that keeps each organisation’s data separate. There is no third-country frontier model in the answer path, so there is no third-country transfer to explain to your DPO.

  • Reads and writes your documents. Drop in a contract, a fee schedule or a KYC file. Get back a checked spreadsheet, a one-page Word summary or a PDF.
  • Works inside your tools. Connect Microsoft 365 or Google Workspace and Lucy searches your mail, drafts replies and books meetings, as you and never as a shared account.
  • Runs code safely. Analysis and document building happen in an isolated, short-lived sandbox with no route to your network.
  • Remembers how you work. Teach Lucy a recurring process once and it follows it every time, and shows you when it did.
  • Shows its work. Every answer lists the steps taken, so a reviewer can check how a number was reached.
Your risk question How Lucy answers it
Who can use what? Roles, groups and per-feature switches. Every sensitive capability is off until an admin turns it on.
Can an assistant send mail by itself? No. Anything that reaches other people shows an approval card first.
Where does the data go? Per-organisation separation, retention you set, and a clear list of what leaves the platform. See Data handling.
Can we prove what happened? An audit log that cannot be edited, exportable, with a read-only auditor role.
What will it cost? Per-person limits in euros, a monthly organisation budget and alerts before you hit it.

Staff get a tool that is pleasant to use on day one. Admins get the controls to say yes with confidence. Both are in these docs.