Software for breweries and small makers
Denver makes a lot of what it drinks, and the people who drink it meet a brewery in three ways. A regular in RiNo buys a pint across the taproom bar. A restaurant in Golden expects its kegs on Thursday. A bar in Arvada has empties in its cellar that nobody has come for. Those three are served from three sets of records: what went into each batch and when, which kegs are full, out or missing, and which orders ship this week. In a brewery with a few dozen accounts that is often a whiteboard, a spreadsheet and the head brewer's memory.
What we would build joins those records. Each batch has an entry for what went in and when. Each keg is scanned with a phone, by its serial number, out and back, so the bar in Arvada appears on a list of accounts that have held kegs too long. The restaurant in Golden gets what it ordered because Thursday's delivery list is drawn from the same entries as the tanks, and the head brewer checks that list before the van is loaded. Brewery software sold off the shelf may already do enough, and we check that first. If it falls short, scope and price are fixed in a brief before building starts.
A distributor in Wyoming, New Mexico or Kansas asks one thing before taking on a Denver brewery: how much can you send, and can you keep sending it. A brewery that wanted the bars of Cheyenne once put a rep on the road with a case of samples and a notebook, and learned at the end of the month how many kegs had not come home. Today the distributor's order, the kegs that go to it and the batches that fill them sit in the record your brewer already keeps. The brewer can quote a firm figure and delivery day. A bar in Cheyenne that holds a keg too long shows on the same overdue list as the bar in Arvada. The rep's notebook has become a list kept in Denver, updated by every scan.



