Demos
See how a process changes
Two illustrative examples with fictional data. Each one shows the manual way, what the system does, where a person decides and the result.
Illustrative example · fictional data
Documents that come in on their own
A distributor receives purchase orders as PDFs by email.
Before
Someone opens every PDF and retypes the order into the system, line by line.
Without JavaScript, this is the walkthrough for the first sample document.
Purchase order · Brennick Supply
What the system extracts
| Field | Value | Confidence |
|---|---|---|
| Customer | Brennick Supply | 98 % · OK |
| Order number | PO 4471 | 97 % · OK |
| Order date | 2026-10-14 | 95 % · OK |
| Item | Steel shelving, 5 levels | 91 % · OK |
| Quantity | 12 | 62 % · Needs review |
| Delivery date | 2026-10-28 | 88 % · OK |
Where a person decides
Fields the system is unsure about are marked. A person checks them and approves the order.
Result
The order is created as a record, ready for the next step, and the approval is logged.
Illustrative example · fictional data
Next steps that don't depend on memory
A professional services firm keeps its requests in a shared inbox, a spreadsheet and its CRM. Connect them to see one view.
Shared inbox
- Contract renewalVantrell Co.
- Billing questionQuarrow Tile Works
Spreadsheet
- New office setupLuis
CRM
- Lindqvist & RuizNew
| Request | Client | Source | Owner | Next step | Status |
|---|---|---|---|---|---|
| Contract renewal | Vantrell Co. | Shared inbox | Dana | Send the draft on Thursday | In progress |
| New office setup | Ostmark Dental | Spreadsheet | Luis | Waiting for their signed form | Waiting for the client |
| Monthly report | Lindqvist & Ruiz | CRM | Priya | Review the figures with the client | New |
| Billing question | Quarrow Tile Works | Shared inbox | Tom | Closed, reply sent | Done |
Without a connection, each request lives in a different tool. Connected, the team sees the owner, the next step and the status in one place.