Where AI is worth doing in Cape Town
Suppose an importer in the Netherlands writes to your estate in the Winelands in the middle of harvest. She wants a technical sheet, your prices and what is available, set out the way her own office keeps them. You copy the figures into her layout, check the stock and reply after the day's pressing. If she orders, each document asks again for details you have already typed. The same week a couple who tasted with you in February write from Hamburg wanting another case, and their address is somewhere in last summer's email. Every step falls to you, and none of it is winemaking.
Here is the same enquiry after our work. Her format is filled from your master sheets and price list, and any gap is marked, so you check one page and send it. The order's documents are prepared from the order itself. The February visitors' address is on record, so their reorder is a single message. Where an importer writes in German or Dutch, the reply is drafted in that language, and you read it over before it is sent. Prices, allocations and anything the software is unsure of come to you. Not everything is switched on together: the sheet or the availability list, whichever your cellar office is asked for most, goes first, and a second job waits until you have seen what the first gives back. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job.
Wine is one case among many in Cape Town: a Sea Point guesthouse is asked about arrival all summer, and a Salt River clothing workshop is asked where each order stands. The change is clearest from the far end. An importer in Germany receives the sheet in the layout his office expects. A restaurant in Johannesburg reorders with one line. A wine shop in the United States, the market we work in ourselves, deals with the person who makes the wine and gets as complete an answer as a larger producer's export desk would send.



