AI USE CASES YOU CAN REUSE.English edition · Individuals, independents, small businesses
Spotted on the web

Create a voice input vinification monitoring application with the AI alone for 36 vats

Use described publicly by Vitisphere (8 October 2026), summarised by the desk. Not tested by iadujour.

The result to aim for

Joannès Violot Guillemard, a winemaker in Pommard, has designed himself with Claude and Glide an application where his team dictates the temperature, density and acidity of each tank, and calculates product additions and sends alerts.

What was done

According to Vitisphere (8 October 2026), the estate operates 8 hectares of vines and one trading activity, i.e. 36 wine vats. The application, tested during harvests 2026, records and sorts dictated measurements over the phone, calculates the quantities of products to be added and displays alerts on a touch screen installed in the cellar. The winemaker explains that she replaced scattered Excel tables and poorly written notes. He developed it in July, about three hours a day, at a cost of about EUR 1 000 between subscription to Claude and subscription to Glide, while, according to him, equivalent market tools cost around EUR 100 000. He seized his own vinification criteria; The tool works in a closed circuit without going to search for protocols elsewhere, and the final decision is up to it.

Before you start

Tool cited by the source: Claude; other tools cited: Glide. Gather the information the prompt asks for. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.

The method, in three steps.

  1. Gather the context

    Gather the information described in the prompt.

  2. Adapt the prompt

    Copy the prompt below, replace the bracketed items, then paste it into Claude.

  3. Reread before using

    Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.

Your starting point.

Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.

The prompt to customise
Help me design a small tracking application for my operation, without being a developer.

What I want to catch (to the voice if possible):
My calculation rules:
Alerts intended:

1. Proposed the data structure (table).
2. Describe the screens, with a no-code tool of type Glide.
3. Write the calculation rules and a list of tests with unknown values to verify the results.
Not to add any oenological rules I didn't give.

What deserves your attention

An erroneous dosing calculation can damage a tank: test the application on known cases before harvest, keep a manual track of critical additions, and plan who maintains the tool.
Origin of the case. Use described publicly by Vitisphere (8 October 2026).
Proof level: Testimony published by an identified source. Source checked on 10 November 2026. Use described by the source, not tested by the desk. Original summary written by iadujour.fr: figures and claims are the source’s; the prompt is a desk proposal, not a quotation.
TO GO FURTHER

Other ideas to put to work.

The whole Dev theme
Dev

Make a pull request by an agent before the human review

A first automated passage to identify probable bugs, missing tests and safety risks, so that the human review focuses on the essentials.

Tool: Claude CodeType: Practical case
DISCUSSION

Comments.

A field note, a question, a precision on this use case? Comments are reviewed before publication.

Published comments

Loading comments…

    Leave a comment

    Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.