ENES
One conversation
Agents/CamelliaClient agent · Kombucha lab

Camellia

A kombucha lab runs on precision: every jar, every reading, every recipe. We built the operating system around her process, not the other way around.

ClientGolden Sands, Los Cabos
IndustryKombucha and fermentation
RebuiltSeptember 2026
What it isGolden Sands OS and Camellia
[ 01 ] WHY A LAB NEEDS THIS

Fermentation forgives nothing.

Kombucha is alive. Every batch moves through stages, from day zero to first fermentation, harvest, cold crash, flavouring and carbonation, and each stage has its own readings, its own limits and its own timing. Miss a reading, skip a baseline or lose track of which starter went into which jar, and a whole batch can be lost.

On top of the lab sit the recipes, the cleaning and tasting logs, the stock of bottles and ingredients, and the customers waiting on the next delivery. A notebook and a spreadsheet can hold some of it. None of it talks to the rest.

[ 02 ] BUILT AROUND HER

Her rules, her recipes, her jars.

Our first pass modelled a factory. Big tanks, dozens of tables, a process that looked right on paper. Her lab is glass jars on shelves, and her process is her own. So we started over, by asking.

Golden Sands OS is built on her standard operating procedures, the ones she uses across every recipe and every batch. Each stage carries her limits, each reading is checked against them the moment it is entered, and the system adapted to the way she already works.

It adapted to her. She did not have to adapt to it.

[ 03 ] HOW LONG IT TOOK

About two weeks for the rebuild.

  1. August 2026A first version. Built ahead of the business, so we stepped back and listened.
  2. Early SeptemberRebuilt with Camellia around her real lab: jars, stages and her own limits. Live within days.
  3. Mid SeptemberCleaning, tasting and temperature logs, then stock that updates itself as she produces.
  4. Late SeptemberOrders and customers in the same system, and a brand system for the business.
[ 04 ] WHAT SHE HAS NOW

A lab that knows itself.

01Every jar on one map

The lab drawn the way it really is, each jar with its stage and its last reading.

02Readings, checked as entered

Each measurement compared with her own limits for that stage, instantly.

03Her SOPs, built in

The steps she follows for every recipe, so the process is the same every time.

04Camellia, the agent

Walks her through measurements, tracking and the day, short and in her language.

05Stock that keeps itself

Ingredients and bottles update as batches move.

06Orders and customers

Who ordered what and when, next to the lab that makes it.

[ 05 ] WHAT CHANGED

The process lives in the system, not in memory.

Readings in a notebook→Readings checked against her limits
Process held in memory→Process held in the system
Stock counted by hand→Stock that updates itself
Software that expects a factory→An OS that fits her lab
[ 06 ] WHERE IT GOES NEXT

For anyone who makes things in batches.

What we learned in this lab carries to every small producer with recipes and batches: breweries, bakeries, chocolate and coffee roasters, cosmetics and skincare makers. Interview the maker before modelling anything, lock the facts into the data, keep the agent short and practical, and let the system follow the recipe, not the other way around.

MORE STORIES
[ NEXT ] ONE CONVERSATION

Bring the business as it is.

We'll tell you, honestly, what we would build first and what we wouldn't. No deck, no pitch.

Start in 30 seconds