The Cold Side

$1,250 of revenue given up by waiting — and that is the kind version, because it assumes the beer moves at all. The beer that did not sell through: a batch is ageing past its best in the tank or in the cooler, and everyone can see it. Why does nobody make the call, and what does waiting cost? Mac and Wren separate the quality call — "is this beer still good," which a brewer makes in a second off a glass — from the business decision underneath it: hold for full price, discount it and move it, blend it, or dump it, with doing nothing as the unmarked fifth door that most buildings take. Wren prices the wait on stated assumptions throughout (10 assumed barrels of packaged or brite-held beer that misses its window and eventually moves at an assumed $125 a barrel instead of an assumed $250 — 10 × $125 = $1,250 of revenue handed back), and says plainly what the number is not: it excludes the tank or cooler space the beer sat in, which may be the larger cost and which she declines to price without knowing the tank and what it displaced. Her fix — discount early and small, while the beer is still well inside its best — gets its full weight from Mac first, and then he wins the round: the arithmetic assumes a buyer for ageing beer at a lower price, the accounts who move on price are the ones whose customers will judge the brewery on that glass, and in a slow month that buyer may not exist at any price. Wren concedes it fully. What actually helps: a decision date set on packaging day, while you still like the beer, at which the hold, move, or dump conversation happens on purpose instead of when a full tank sets the date for you. Tie-in (verified against code 2026-10-23): in FermentIQ, packaged beer sits in finished-goods stock carrying the date it was packaged and how much of it is left, lot by lot, batch by batch, oldest first — so which packaged beer has been in stock the longest, and what remains of it, is a lookup instead of a walk to the cooler. No automatic staleness alerting is claimed. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "Which packaged beer has been in stock the longest, and how much of it is left?" — answered live on the capture account (org 11, Playground Brewery, is_test=true; site context "FermentIQ Brewery" single-site via the site switcher; attempt 1 of 3): the longest-held packaged beer is a Pilsner, lot 260212-125, one unit left, packaged May 5, 2026, with a best-by date of November 1, 2026 — and BrewBuddy flagged the next-oldest lots as probable opening-stock records rather than true packaging dates. Dry Hops: set the decision date on packaging day, while you still like the beer — the date you set later will be set by a full tank, not by you. And the first discount should be small and early or not at all; a large, late discount teaches accounts to wait you out. Last Call: find the oldest beer you hold today. Write down its packaging date and the date you will make the hold, move, or dump call. Put that date somewhere you will see it. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com.

Two weeks, not two months: about $2,900 a hire lost in the gap between week three and week eight. Mac and Wren argue over why a new cellar person takes two months before they can be left alone with a transfer — what "trained" even means ("can do it unsupervised and will stop when something is off"), why the confident untrained person is the expensive one, and why the thing Mac calls judgment is mostly a list he never wrote down. Mac concedes it: thirty people's worth of the list, all in his head. Tie-in (verified against code 2026-10-09): the onboarding checklist with due dates, per-employee training records (forklift, hazmat, first aid, food safety) with due dates and completion status, and every batch stage change logged as a written, timestamped sequence on the batch. SOP storage killed in verification — no customer-facing SOP feature exists in the brewery product, so the script claims nothing about one. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "Are there any training records or certifications on file for the team at FermentIQ Brewery?" — captured 2026-10-09 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, ask #2 of 3 (ask #1, "What onboarding tasks are open for the team right now?", deflected — no tool lists onboarding checklist tasks). The answer is a truthful deflection: no training records or certifications confirmed on file, no safety standards tracked on the capture org. No customer names in the answer (nothing to anonymize). Per the runbook deflection rule, the tie-in is not strengthened by the capture: the Hot Side beat claims only the code-verified mechanism, and the post-INSERT beat answers the empty record honestly ("On this site it lives where it lives at most breweries. In people's heads."). Dry Hops: have the new person write the procedure as they learn it — the gaps in their draft are the gaps in your training. And let them make the safe mistakes early and on purpose — everybody remembers the mistake they made; nobody remembers the mistake they watched you make. Last Call: write down the CIP sequence for one tank, start to finish, and hand it to somebody who has never done it. If they can follow it without asking you a question, you wrote a procedure. If they can't, you wrote a reminder — to yourself. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com.

Six stops, one truck: about $2,100 a year in recoverable driver hours, and only if the recovered time actually gets used. Mac and Wren argue over a real run sitting in the app — six accounts, $1,692 on the truck — on why a delivery day is built out of habit and the order the calls came in, why the truck costs an assumed $289 a day to roll (eight hours, $28 an hour fully loaded, $65 fuel), and why delivery is not a distance problem — it is a time-window problem. Mac wins the round: the paper-optimal route loses to the route that respects when accounts will actually take a delivery. First Runnings: the clipboard version of the real run. Dana at the Copper Mug called first Friday, so the Copper Mug is stop one — driver at eight-fifteen for a ten-to-noon window, forty-five minutes in the parking lot, engine off. Late everywhere downstream: Harbor and Rye at eleven-fifteen, after Priya — the only signer — left at eleven. Ferment and Fork at noon against an eight-to-ten window. Two stops missed, one redelivery later in the week. Two trucks for one week's beer, and the record says nothing. Hot Side: the arithmetic, assumptions throughout. Eight hours at an assumed $28/hr fully loaded plus an assumed $65 fuel: $289 a delivery day. Two days a week, fifty weeks: $28,900 a year to run the truck. Forty-five recovered minutes a day at $28/hr: about $2,100 a year in driver hours — and Wren says plainly what that number is not: not fuel, not truck wear, not revenue, unless the time gets used for another stop. Mac concedes the math outright, then wins: the optimizer's perfect loop puts the driver at Ferment and Fork at ten-thirty for a window that closed at ten, or at Harbor and Rye at one-thirty after Priya's gone. The route that ignores the windows is abandoned by stop three. Wren concedes fully. Then the real stop order, sequenced by the windows: Ferment and Fork first (eight-to-ten), Harbor and Rye for Priya before eleven, the Copper Mug ten-to-noon with Dana and the back door, the Hoppy Monk (side door after eleven, by two), Bottle Theory fifth (call twenty minutes ahead, Fifth Street dock), Cask and Craft last (flexible hours, hand-truck job down the stairs, truck at its lightest). Tie-in (verified against code 2026-10-02, corrected 2026-10-02): the route and the paperwork come off the same record — road-routed ETAs via OpenRouteService, driver signature capture, and vehicle inspection are live in the driver app. LLM stop-ordering (`POST /api/delivery/routes/optimize`) and BOL generation (`POST /api/driver/bills-of-lading/generate`) exist as backend endpoints only, with no UI calling them — not user-reachable, so not claimed as live features. Structured receiving-window modelling does not exist (free-text field only) — the windows stay a human process, and the script claims only that the software holds what you typed. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "What's on the delivery run for tomorrow, and in what order?" — captured 2026-10-02 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, attempt 3 of 3 (6 asks total, all consistent). The answer is a truthful deflection: no delivery routes created for tomorrow (2026-10-03), 0 pending deliveries on the capture org — not a technical failure. No customer names in the answer (nothing to anonymize). Per the runbook deflection rule, the tie-in is not strengthened by the capture: the Hot Side beat claims only the code-verified mechanism, and the post-INSERT beat answers the empty record honestly ("Empty is also an answer, as long as it's the true one"). Dry Hops: write the receiving window in the customer record the day you open the account — Dana's window, Priya's mornings, the back door, the side door — not the third time you get turned away. And hand the driver the windows and let him sequence the run once; buy him a beer and write down what he says. Last Call: take your biggest delivery day and write down the receiving window for every account on it. The gaps are your route problem. Every blank is forty-five minutes in a parking lot waiting to happen. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com. PRODUCTION NOTE (rewrite 2026-10-02 ~06:45 PDT): this episode was rewritten around a real delivery route built in the app the same day (org 11; 6 fictional test accounts IDs 545–550 with real receiving-window constraints, 6 invoices INV-869–874, route "Delivery 10/2/2026" PLANNED, $1,692 total; no email addresses on any record per Jacob's rule #0). The v1 script is backed up at FermentIQ_Podcast_Ep10_Script_v1.md. The rewrite's render passed the level gate cleanly (15 chunks, 0.38 dB spread, limit 1.50) — the earlier p12 waiver applied to the v1 chunking only.

Contracted hops in a flat year: $2,400 a year of hops you bought and did not brew. Mac and Wren on why the contract was the responsible thing to sign, the four ways out (priced honestly), and why the surplus market seizes up exactly when you need it. First Runnings: the contract was the responsible thing to do at the time — and that is what makes it hurt. The farm plants in spring off what you committed in winter. They can't plant on optimism. Hot Side: the arithmetic, assumptions throughout. Assume 800 lb a year of one variety at an assumed $12 a pound: $9,600 committed. Assume production comes in 25% under plan — you brew 600 pounds' worth and carry 200. Two hundred pounds at $12 is $2,400 a year of hops bought and not brewed. Over a three-year contract, that's $7,200 — and the number is not a write-off: you own the hops, sitting in a cooler, losing alpha while you decide. Ask BrewBuddy (real question, real account, whatever it says is what you hear): how much of each hop variety did we use in the last twelve months? [Capture pending — this note updates when the take lands.] Dry Hops: write the worst-year volume next to the contract volume, on the same page, before you sign — not the forecast, the worst year. And never sign a contract in the month you had your best sales week. Sign in February. Nobody's celebrating in February. Last Call: pull your hop contracts and write your actual last-twelve-months usage beside each committed volume. If the two columns don't match, you just found your two hundred pounds before you paid for it. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com.