We built BatchDash to run our own production.
BatchDash is designed and built in Toulouse, out of the work of taking a hot sauce of our own from formula to production. Every part of it answers something that work needed, and it is engineered by people whose trade has been software for twenty years.
We went looking for a system to run the workshop on. What we found either treated making as assembling parts out of bins, or carried the weight of software written for a plant, with an install project to match. We needed the formula, the batch and its real cost to belong to one record. So we built that.
It started at the bench.
Most of the work turned out to be development. A trial, one percentage moved, another trial, a tasting weeks later once the ferment had shifted. That is where the time goes, and it is exactly the part no production software had anything to say about.
So that is where we started. BatchDash has a bench sheet because we needed somewhere to write down what we had actually weighed. Every version of a formula stays readable, because a version you cannot read back is a result you cannot repeat. Tastings are scored, experiments are kept, and a trial batch can be undone and give its ingredients back to stock. Most of ours were trials.
Production followed. Once a recipe works you have to buy for it, make it twenty times bigger, and afterwards prove which lot went where. Each part was built at the point the work reached it.
The founders.
Pierre
Tech & Product
Twenty years in software engineering, and the architect of BatchDash. The data model, the costing engine and the stock ledger are his design. The parts of this product that have to be exactly right are engineering problems before they are food problems, and he builds them as such.
Antoine
Customer Success
A career industrial drafter: years of describing a thing precisely enough that somebody else can build it from the drawing. A formula is that same document for food. He runs the bench and the production work, and he leads customer success: getting a workshop running on BatchDash, and carrying what it needs back into the product.
We own what it runs on.
BatchDash runs in the European Union, on machines we administer ourselves, on infrastructure we assembled rather than rented one service at a time. Your records are never somewhere we would have to open a ticket to go and look.
That is a choice about control. When someone asks where a batch record is stored, who can read it, or how far the backups go back, we answer with a fact, because we built that part too.
Toulouse, and two languages.
We are in Toulouse, and BatchDash exists in English and in French. Neither version is a translation of the other: a French maker finds the words a French maker uses.
Write from the contact page and it reaches someone who builds BatchDash. There is no queue and no first line to get past.