This template applies the four-block method — THE THINGS, THE LINKS, THE STATES, THE NUMBERS — to an artisan craft brewery. It's filled in for a brewery that sells kegs to bars, bottles to bottle shops and cans at its own taproom: the example shows how to describe batches, packaging formats and clients, without ever describing a screen.
The trade carries a production calendar that spreadsheets too often ignore: a batch goes through brewing, fermentation and packaging BEFORE it becomes sellable stock. The template separates the recipe (what doesn't change from one batch to the next) from the batch itself (a dated production run, with its status and stock per format).
Filled with your vocabulary, this text briefs a developer — or is submitted as-is to Blueprint Maker, which turns it into an application plan you validate, then a generated application: database, screens, dashboard and demo data.
The template to copy
My business: artisan craft brewery, regular and one-off special batches, sold in kegs, bottles and cans. THINGS tracked: - Batches (recipe, brew date, production status, stock per format) - Recipes (name, beer style) - Clients (name, category — bar / bottle shop / individual, price) - Orders (client, batch, format, quantity) LINKS: - A batch follows a recipe. - An order concerns a batch, a format and a client. STATES of a batch: brewing, fermenting, packaged, available. NUMBERS to see every day: - Remaining stock by batch and format - Batches currently fermenting - Orders to prepare - Revenue per channel (bars / bottle shops / taproom)
Adapting this template to your brewery
- The production status is not a detail: without it, a batch still in the tank can show up as available to sell. Describing the stages (brewing, fermenting, packaged, available) is what stops you promising a bar a beer that isn't ready yet.
- One batch, several formats: if you package into kegs AND bottles AND cans, describe stock PER FORMAT rather than one overall figure — that's what lets you answer "how many kegs of the latest IPA are left" without counting by hand.
- Trade prices differ by channel: if your bar/bottle-shop prices differ from taproom pricing, describe your client categories with their prices — they become structuring fields on client records and orders.
- What the application does NOT do: it doesn't file anything with regulators (excise duty, statutory declarations) — those stay on their own dedicated tools. The application covers your production and sales tracking, whose structured data makes those filings easier all the same.
- Special recipes and collaborations are still batches like any other: describe them as a distinct batch type if you want to track them separately from regular batches.
