Pricing
Book a Demo Register for a Trial
LEDGE Operator · Command Centre

Query your data. Draft the email. Send it.
All from one chat.

The AI operations assistant that lives in your Command Centre - search entities, query procurement data, draft supplier emails and take action without leaving the conversation. LEDGE reads your data, understands the context and helps you act on it.

Book a Demo Watch Reels
Read + write
Capabilities
Draft in chat
Review & send
Entity search
Built in
LEDGE Operator
Command Centre persona
Online
Draft a follow-up to Bidfood about the late delivery on PO-000142.

Drafted a follow-up referencing PO-000142 (£1,247.20, originally due 2 May). Review before sending.

The action layer

One interface. Query, draft, send.

Where CFO LEDGE reads and analyses, Operator LEDGE reads and acts. Same data access, plus the write tools that finish the job - without you ever leaving the conversation.

1
Interface
Data query, email compose and entity search - one chat window
<10s
Draft to send
Ask LEDGE to draft → review → send, without leaving the conversation
Zero
Context switching
No jumping between analytics, email and supplier screens
AI
Draft assist
LEDGE writes the email - you just approve it
Two personas, one engine

LEDGE comes in two flavours.

Same Anthropic Claude under the hood, same data access, same multi-turn architecture - but the personas are tuned for different jobs. Pick the one that matches what your team needs to do.

LEDGE CFO
Intelligence
Read + analyse

The finance-focused intelligence layer. Reads procurement, spend, supplier and accounting data, returns analysis and live charts. Active anomaly alerts injected into every conversation.

  • ✓Natural language queries · 108 endpoints
  • ✓Live charts (bar / line / pie / area / stacked)
  • ✓Multi-turn context · 6 pairs
  • ✓Insight Alert injection
  • ·Email draft assist
  • ·Direct email send
  • ·Entity search
LEDGE Operator
Command Centre
Read + act

The operations-focused assistant that lives inside the Command Centre messaging hub. Same read access - plus AI-drafted supplier emails, direct send and entity search built right into the chat.

  • ✓Natural language queries · 108 endpoints
  • ✓Live charts (same chart-spec model)
  • ✓Multi-turn context · 6 pairs
  • ·Insight Alert injection (operational focus)
  • ✓Email draft assist
  • ✓Direct email send · via AWS SES
  • ✓Entity search · POs / invoices / suppliers / docs
Three write tools

The capabilities that turn "can someone send this?" into "done".

Three explicit tools layered on top of the read engine. All three flow through pending actions - LEDGE drafts, you confirm, the platform executes. No autonomous send.

Tool 01

Email compose + send

Ask LEDGE to draft a supplier email. The draft returns as a pending_action with subject, HTML body, recipient and entity references already embedded. Review inline. Click Send. Email dispatched via AWS SES with a branded template, reply-to set to your address.

POST /v0/command-centre/draft-assist
Tool 02

Direct supplier email

Single-step compose-and-send for quick messages - recipient, subject, HTML body, optional entity references. Creates the message record, dispatches via SES, returns the sent message in the same call. Useful for short ad-hoc messages without the draft step.

POST /v0/command-centre/emails/send
Tool 03

Entity search

Search any entity in OmniPATH - purchase orders, invoices, suppliers, documents - to reference in messages or follow-up queries. Returns the entity type, ID, label, detail and a deep-link URL. Used by the compose UI's entity picker, by LEDGE for context enrichment and inline for message references.

GET /v0/command-centre/entity-search
Entity search

Find any record. Reference it in seconds.

One search box, four entity types, deep-linked results. Type a supplier name to surface every related PO, invoice and document. Click any result to drill into the record, or use it as context in your next LEDGE question.

  • Four entity types · purchase orders, invoices, suppliers, documents
  • Deep links returned · click any result to open the underlying record
  • Context for LEDGE · search results enrich the next conversation turn automatically
  • Used by the compose UI · the entity picker for embedding references in outbound messages
  • Auth-scoped · only entities in your active org, only what your role allows
bidfood
Results7 matches · 4 types
Supplier
Bidfood Foodservice Ltd
Co.no.03873787 · 24 active accounts
PO
PO-000142 · Bidfood
£1,247.20 · due 2 May · overdue
PO
PO-000148 · Bidfood
£892.00 · due 4 May · overdue
Invoice
INV-08823 · Bidfood
£1,847.50 · posted 28 Apr · paid
Document
Bidfood-Statement-Apr2026.pdf
supplier statement · uploaded 03 May
Workflows in action

Three real jobs. One conversation each.

The most common operator workflows - chase a late delivery, query and share, look up and act. Each one collapses what was three browser tabs into a single thread.

Chase a late delivery
Workflow 01
You
Which orders from Bidfood are overdue?
LEDGE
2 orders overdue: PO-000142 (£1,247) and PO-000148 (£892).
You
Draft a follow-up about PO-000142.
LEDGE
Pending action · supplier email
You
[Send]
LEDGE
Email sent to orders@bidfood.co.uk. Saved in your sent items.
Query, then share
Workflow 02
You
Credit note ratio for Fresh Direct this quarter?
LEDGE
Fresh Direct: 8.4% credit ratio (concerning). 12 credits totalling £2,840 against £33,810 in invoices.
You
Draft an email to the ops director summarising this.
LEDGE
Pending action · internal email
You
[Edit] add Q1 comparison [Send]
LEDGE
Sent. Includes Q1 comparison and the trend chart inline.
Look up & act
Workflow 03
You
Find the invoice from Brake Bros last week.
LEDGE
Found INV-09221 from Brake Bros · £3,420.80 · posted 29 Apr.
You
Email Brake Bros about a disputed line item.
LEDGE
Pending action · invoice reference embedded
You
[Send]
LEDGE
Sent. Reply will arrive at your email.
The Command Centre · beyond LEDGE

The messaging hub LEDGE lives in.

LEDGE Operator is one piece of a wider Command Centre. Compose freely, save drafts, preview rendered HTML, browse sent items, filter by status - the messaging fundamentals are all there, AI-assisted or not.

Compose & send

Recipient, subject, body, entity refs. Save as draft, edit, discard, dispatch - same fields whether you wrote it or LEDGE did.

Drafts & preview

Render the full HTML email before you send. Edit, polish, ask LEDGE to rewrite. Drafts never auto-send.

Sent items

Full history of every outbound message · status (draft / sent / failed) · sender · SES message ID · timestamps.

Filters & threads

Filter by status, by sender, by entity reference. Threading via reply_to_id for outbound message chains.

Before vs after

From three open tabs to one chat thread.

Most operators are juggling analytics, the email client and the supplier directory all at once. LEDGE Operator collapses them into one interface where the question, the answer and the action live together.

×
Without LEDGE Operator
Three tabs, two screens, copy-paste
  • Query data in one tab, compose email in another, look up PO references in a third
  • Draft emails manually - copy-paste figures from reports
  • Entity references typed by hand - easy to get wrong, breaks deep links
  • No AI assistance - every email written from scratch
  • No conversation context - each interaction starts fresh
  • Sent and unsent state lives across multiple tools
✓
With LEDGE Operator
One thread, query → draft → send
  • One chat interface - query, draft, send, no tab switching
  • AI drafts the email with correct figures, PO numbers and formatting
  • Entity references auto-embedded from search
  • Multi-turn context · "now send that to the ops director" works because the prior turn is still in scope
  • Pending actions - review before send, never autonomous
  • All outbound messages tracked in the Command Centre with full audit
Frequently asked

The practical details.

Which AI model is behind LEDGE Operator - and what happens to the email content I run through it?
LEDGE is powered by Anthropic's Claude, accessed via the LEDGE pipeline (a separate service in front of OmniPATH's API). The arrangement with Anthropic includes a no-training, no-retention agreement for the API tier we use - so the email drafts, supplier names, PO references and prompts you run through LEDGE aren't used to train the underlying model and aren't retained beyond the immediate request lifecycle on Anthropic's side. The drafted email and the conversation it lives in are stored in your OmniPATH org as you'd expect, but nothing leaks outside that boundary.
Does LEDGE ever send an email by itself?
No - never. Every email LEDGE drafts surfaces as a pending_action object that a human has to confirm. The "Send" button is the trigger; LEDGE prepares the content but the dispatch only happens when you click. There's no autonomous mode where LEDGE sends on your behalf without an explicit confirmation step. This is a deliberate design choice for an AI in the finance/operations workflow - drafting fast, sending only when you approve.
When the supplier replies, does the reply come back into the Command Centre?
No - replies are routed to your business email address, not back into OmniPATH. The outbound email is sent via AWS SES with the reply-to header set to your email, so when a supplier hits reply, the response lands in your inbox. We send mail out of OmniPATH but we don't run a full inbound mail server. If you want the reply context inside OmniPATH, the typical pattern is to forward the response back into the platform manually or via your inbox's forwarding rules.
Can LEDGE approve orders or invoices from the chat?
Not currently - write tools are scoped to email only. Order approval, invoice approval, supplier approval and the rest of the platform's write flows still happen through the normal UI with their own audit and authority rules. We've kept LEDGE deliberately narrow on the action surface - drafting messages is a low-risk write operation; modifying financial state needs the controls baked into the existing approval flows.
Can I attach files to an outbound message?
Outbound messages are text and HTML only - no file attachments today. If you need to send a document like a remittance or a statement, the typical pattern is to share a link to the document inside OmniPATH (entity search returns deep links) rather than attach the file. The supplier follows the link and authenticates if needed.
Can I save email templates for repeat use?
No saved-template library today - each message is composed fresh, either by you or by LEDGE. In practice, asking LEDGE to "draft the standard chaser for an overdue PO" works very well because LEDGE has the context already - the supplier, the PO, the amount, the due date. Effectively the prompt becomes the template.
Can I schedule an email for later?
Not currently - emails dispatch when you click Send. There's no "send at 9am tomorrow" feature today. If timing matters, the draft can sit in your drafts list until you're ready to send, but there's no automatic scheduled dispatch.
Can I see if a recipient opened my email?
Open and click tracking aren't built today. SES handles delivery, returns a message ID and tracks bounce/complaint events at the protocol level - but no open-pixel tracking or click-through reporting in the Command Centre UI. If a delivery fails (bad address, hard bounce), the message status flips to failed with the SES error attached.
Can I CC or BCC additional recipients?
Single recipient per outbound message today. If you need to copy multiple people, the typical pattern is to send the same message to each recipient individually (which keeps the threading clean) or to forward your sent copy to additional recipients via your normal email. CC/BCC support and multi-recipient threading would be a substantial feature - happy to discuss if it's a deal-breaker for your workflow.
Does LEDGE Operator have the same data access as CFO LEDGE?
Same read-side endpoints (108 of them) - procurement, financial, cash flow, budgets, suppliers, categories, products, processing, transactions, accounting. Same chart-spec model, same multi-turn context window (6 question/answer pairs). The Insight Alert injection that CFO LEDGE uses is the one piece not shared - Operator's context is more focused on operational state (overdue orders, pending approvals, open invoices) than on the broader anomaly-detection surface. Auth is identical: bearer token forwarded, role-gated, org-scoped.
Ready when you are

Watch LEDGE draft a real supplier email.

Bring an email you'd usually write manually - a delivery chaser, a credit query, a statement reconciliation - and we'll have LEDGE draft it on the demo. Sub-five-second response, ready to review, ready to send.

Book a Demo Watch Reels
No card needed · 30-min demo · Bring an email you'd usually write