All work

Standalone · recipe engineering

Batchmaker Studio

A lean recipe studio for recipes, raw materials, batch tickets, and glass chemistry.

Responsibility
Product architecture, full-stack development, and calculation engine.
Stack
Node.js · Express · node:sqlite · Vanilla JS · Vite · native tests
Evidence
Independently operable product

Situation

Recipe work needs the same domain core as production — but not silos, shifts, and live bookings. A full operations system is too heavy for desk-side development.

Decisions

  1. 01

    The same domain core, deliberately smaller scope.

  2. 02

    Its own server, SQLite file, and lean browser interface.

  3. 03

    Validation as a visible step, not a hidden side effect.

Evidence

Not features. Systems.

Batchmaker Studio recipe workspace.
Batchmaker Studio recipe workspace.
Validation as a dedicated step.
Validation as a dedicated step.
Configuration for redox, calibration, and oxides.
Configuration for redox, calibration, and oxides.

Decisions

The domain core as a model.

  1. 01

    Recipes

    Version, compare, import, and export.

  2. 02

    Chemistry

    Oxides, redox, physics, and traceable calculations.

  3. 03

    Tickets

    Draft, scale, preview, print-ready output.

Outcome

An independently operable tool for recipe work, glass chemistry, and print-ready batch tickets. No unverifiable efficiency claims.

Takeaway

Product boundaries are architecture. A good tool does not have to model the neighbouring process in full.

Conversation

A process that deserves better software?

Start a conversation