← All demos
Working prototype · Order entry

The email becomes the order.

Your inbox is full of orders that arrive as paragraphs — half-remembered part names, quantities buried in the third sentence, a due date in the P.S. Someone retypes all of it into the system by hand. This prototype does the retyping. Press run and watch it read.

Inbox → Order · press run
Structured order Waiting
— no order parsed yet —
CustomerPrecision Dynamics — Mike Torres
Line 140× Mounting bracket · PD-1104 rev C
Material6061-T6 · black anodized
Line 212× Heatsink plate · PD-2210
MaterialAluminum 5052
Need-bySept 14
FlagCustomer admits the date is tight — confirm capacity before promising
QuestionIs plating included at last order's price? Reply before the PO
HistoryPD-1104 run 3× before — last at $86/ea, 9-day turn
What it hands back
0Typical retyping time per emailed order — reading, interpreting, keying it in, double-checking.
0Transcription errors. The order the system holds is the order the customer actually wrote.
0Things a busy reader would have missed — caught and surfaced before you commit.
How a real build works
01

It reads your actual inbox

Orders arrive however they arrive — email, a forwarded thread, a photo of a fax. The system pulls out what matters: parts, quantities, materials, dates.

02

It knows your history

"Those brackets from last month" only means something if the system remembers last month. A real build matches against your past jobs, parts, and pricing.

03

It asks before it guesses

Ambiguity gets flagged, not invented. You answer the two questions it raises; everything else lands in your system already structured.

Where this pattern fits

What arrives in your inbox that someone retypes?

That's usually the first thing worth automating. This demo's parsing is simulated — a real build connects to your actual inbox and order system, and learns your customers' habits.

Tell me what you'd automate →