How it works

You do not file anything.

The premise is that the filing already happened, badly, in email, and that reading it is a job software can now do.

The parts

Everything on this list is live today.

Sign inBy emailed link. No passwords to choose, remember or leak. The link expires after fifteen minutes and works once.
Mailbox connectionThrough Google's own consent screen. Read and draft permissions only. Send, delete and modify were never requested, so they cannot be switched on later without a new consent screen you would see.
Question answeringConversational rather than a search box. It chooses which mailboxes to search, runs the searches, opens the attachments that look relevant, and answers while streaming its working so you can watch it think.
Document readingPDFs, scans and photographs of paperwork. It extracts supplier, document number, dates, VAT and amounts, which is what makes a second question fast.
SourcesPreview in the conversation or download. Nothing is asserted without the document behind it, and if it cannot find a source it says so rather than filling the gap.
DraftingReplies land in Gmail drafts with the document attached. A person presses send, always.
Handing work outDocuments bundled to somebody outside the company at a link that expires after fourteen days, pinned to those exact documents, sent only to a recipient the account holder approved in advance.
Cost trackingEvery question records who asked and what it cost, with an optional monthly ceiling per person.

And here is what is not

What happens in one question

What answers you is an agent, not a search box.

A search box takes your words and matches them. This decides on an approach, carries it out, changes its mind when the approach is not working, and shows you all of that while it happens. The difference matters most on the questions where the answer is not sitting in one obvious email.

It decides where to lookNot every mailbox, and not everything in the ones it picks. It reads the question, works out which mailboxes and which date range could plausibly hold the answer, and starts there.
It runs its own searchesSeveral, usually, and it changes them when the first ones come back thin. You watch this happen rather than waiting at a spinner.
It chooses what to openAttachments cost money and time to read, so it opens the ones that look like the answer rather than all of them. Eleven attachments, not four hundred.
It answers, or says it cannotWith the document attached to the claim. When the mail does not contain the answer it says the mail does not contain the answer, which is the behaviour that makes the other answers worth anything.

What goes in, what comes out

The shape of it, in one picture.

  connected mailboxes          Panorithm            what you get
  ────────────────────         ─────────            ────────────
  contracts, quotes            searches             an answer
  invoices, MOUs         ──▶   reads          ──▶   the document behind it
  site lists, reports          extracts             a draft reply
  scans and photographs        answers              a bundle for your bookkeeper

And then what

Reading is the start of the engagement, not the whole of it.

Everything above is what the software does on its own. The reason it is worth connecting is what happens next: the reading tells us which repeated jobs are eating your people, and those become agents that own the job rather than answering questions about it.

We read before we build

A diagnostic runs for four to six weeks and produces a findings report: what is unchased, what is leaking, and which repeated jobs are worth taking over.

An agent is scoped against one job

Not a category. One job, with a beginning and an end, quoted against what the diagnostic said it is worth.

It runs, and it keeps changing

Partners change their formats, edge cases turn up, and the underlying models get better. The monthly fee is for that, not for keeping the lights on.

Then the next one

Because the person freed by the first agent moves up to work that is often partly repeatable too.

See it read your own mail.

A demo is a live look at the product on real documents. A diagnostic is the version that produces something you can act on.

Start with a diagnosticBook a demo