A prototype we built for an insurance operation in Thailand. 2026.
An insurance operation in Thailand keys its forms into SAP by hand from scans in two languages, with stamps and handwriting across them. Gemini 2.5 Pro reads the form and returns the fields as JSON, and the recorded walkthrough shows it happening on the real form.
A Thai and English insurance form, read into named fields
Screens from this system are being added.
The operation's forms arrive as scans in two languages, with stamps and handwriting across them, and the fields are keyed into SAP by hand. Most extraction demos run on a clean English invoice. This one was built to behave on the real forms, and to show the team what the SAP entry stage would take once the fields were out.
The operation saw its own form read into named fields on video rather than a clean English invoice, and had the SAP entry stage mapped well enough to decide on.
A prototype we built for wholesale order desks
An email becomes order lines against a catalogue, stock moves to reserved, and a quotation drafts itself. 3 quantities per stock item: on hand, available and reserved.
A prototype we built for ads-ops teams
The CSV or JSON export an ads-ops person opens every morning, aggregated per campaign, compared against the previous day, with what to look at first pulled to the top. 40 minutes of a person's morning, and a spreadsheet, before the prototype.
A prototype we built for a manufacturing prospect
Workbook upload, validation rules, transforms, reports and notifications, with a simulated marketplace upload as the worked example, built in February 2026 for a prospect whose order workbooks were rejected by hand. 5 required fields checked on every row: order, customer, mobile, city and quantity.
Elsewhere on the site
Where to next
Say so in a few sentences. The reply comes from the person who built this one.