Building the brew and packaging schedule
Turns your sales forecast, tank capacity and release dates into a brew schedule and a packaging plan, and rebuilds both when one date moves instead of someone redoing the spreadsheet.
This page lists the work around the beer in a UK independent brewery that Claude can take on, by function and by the size of the brewery. It starts with getting production, stock and barcodes off spreadsheets, and it includes a brewery that has already done it.
In a small brewery the founder brews, sells, drives the van and does the duty return in the evening. A growing craft brewery has a canning line, a small sales team, a taproom and an operations manager holding it all together. An established brewery has departments, a dray fleet, supermarket accounts and a board pack. Pick the one closest to yours and the rest of the page follows it, from where the time goes to the calculator.
These are the tasks that land on the founders and a small team, usually after the brewing is done.
These are the tasks that come round every week in a brewery of 10 to 50 people, grouped by the kind of work they are.
These are the tasks that come round every week in an established brewery, where the admin has a department rather than a founder.
This is the point of the whole page. The work in the left column is why people drink your beer and why pubs put it on the bar. The work in the right column has grown up around it, and none of it needs a brewer.
This is the point of the whole page. The work in the left column is why people drink your beer and why pubs put it on the bar. The work in the right column has grown up around it, and none of it needs a brewer.
This is the point of the whole page. The work in the left column is why people drink your beer and why pubs put it on the bar. The work in the right column has grown up around it, and none of it needs a brewer.
The use case for AI is taking away the time that gets spent on the work sitting around the beer, and freeing your people up to do the work only a human can do. The work that grows the brewery, and the work they enjoy the most.
Vault City is a modern sour beer brewery in Penicuik, just outside Edinburgh. It releases new beers every month and sells to pubs, bottle shops, supermarkets, export partners and drinkers online. As it grew, more of the operation was running on spreadsheets and documents filled in by hand, and the same information was being typed into several systems. The senior team has worked with Get AI Powers since July 2026, building the tools below with Claude on top of their brewery system rather than replacing it.
Steve Smith-Hay, the managing director, set one test for anything we built: it had to fix a problem for the team rather than create more work for them. The production app passed it, and he describes it as easy to use. The canning line controller replaced a document his team filled in by hand on every packaging day, which he called an immediate saving. Because the tools sit on Vault City's own data, when something needs to change he asks Claude to change it rather than paying a developer.
“It isn't the way to do it.”
“The application works and it does what it needs to do.”
“Continue to grow without hiring more people to put the same information in 5 different times.”
Quotes are from Steve Smith-Hay, Managing Director and Co-Founder of Vault City Brewing, on calls with Get AI Powers between August and October 2026. The times on the use cases are our estimates, not Vault City's measurements.
The times are our own estimates for a typical task in a UK independent brewery. Nobody has published measured times for this work, so where a source gives a figure we say who published it. Every use case assumes a business plan whose terms keep your content out of model training. The highlighted use cases either take the most hours or make the biggest difference to the business, and the ones marked Built at Vault City are running there now.
The brew schedule, the tank plan and the packaging plan.
Turns your sales forecast, tank capacity and release dates into a brew schedule and a packaging plan, and rebuilds both when one date moves instead of someone redoing the spreadsheet.
Checks the plan every morning against what is actually in tank, booked on the line and in the warehouse, and tells you which beers will miss their packaging or release date while there is still time to act.
Writes the day's board from the plan: what is being brewed, transferred, dry hopped, crashed and packaged, which tanks are free and who is on, ready for the handover.
Shows which fermenters and conditioning tanks are booked, for how long, and where the gaps are, so you can see whether there is room for a collaboration brew or a rush order before you say yes.
Builds a forecast by beer and pack format from sales history, pre-orders, supermarket promotions and the release calendar, so the brew plan starts from demand rather than from last month's spreadsheet.
Works through what a collaboration or a contract brew needs: tank time, raw materials, who pays the duty, how it counts towards your Small Producer Relief, labels and who sells what.
When a batch is dumped or held, works out the knock-on effect on tanks, packaging days, releases and customer orders, and drafts the new plan and the list of people to tell.
Run sheets, fill weights, pallet sheets and line checks.
Pulls can size, pack format, batch, allergens, best before rule and pallet layout from your brewery system and writes the run sheet, instead of someone filling in a document by hand on the morning.
Calculates the target gross weight for a can of each beer from its gravity and the can and lid weights, so the checkweigher is set to the declared volume and the average quantity rules.
Prints a pallet sheet for every finished pallet with the beer, batch, best before, case count and a QR code, so the warehouse books it in by scanning rather than copying numbers.
Checks the packaging plan against cans, ends, sleeves or labels, carriers, cases and CO2 in stock and on order, and tells you what will run short and when.
Writes the booking and the brief for a mobile canner or contract packer: beer, volumes, can size, labels, dates and what has to be ready on the day.
Turns the sensory, clarity, dissolved oxygen and seam check results into a tidy record against the batch, and flags anything outside your limits.
What you have, where it is, and the barcode on every pack.
Builds a branded availability list from the brewery system showing what is in stock, what is coming and what is nearly gone, so buyers order from the list rather than emailing to ask.
Checks every new product in your brewery system against your barcode registry, allocates numbers for the can, the multipack and the case, checks them and tells the team what was created.
Compares the count sheets with the brewery system, the webshop and the taproom, and explains each difference before anyone adjusts stock.
Matches kegs sent out against those returned, from your own records, delivery notes and the keg rental report, and lists the accounts holding kegs for longer than they should.
Answers stock questions from sales and the taproom from the live system, including what is allocated, what is in the cold store and what is due off the line.
Reconciles the reports from third party warehouses, distributors and contract packers with your own records, so beer you own but do not hold is counted once and only once.
Lists stock getting close to its best before date or the shelf life your trade customers need, and suggests where it could go: the taproom, a webshop offer or a buyer who takes short dated beer.
Product sheets, set-up, the release calendar and the trade mailer.
Writes the product sheet for a new beer from the brew sheet and the brief: name, style, ABV, allergens, formats, prices, release date, tasting notes and the story behind it.
Takes the product sheet and sets the beer up in each place it has to exist: brewery system, webshop, trade marketplace, beer rating apps and the taproom menu, so nobody types the same facts six times.
Keeps the release calendar in step with the production plan, the artwork deadlines and the trade mailer dates, and tells you when one of them slips.
Writes the trade mailer for the next release from the product sheets: what is coming, formats, prices, allocation rules and the date orders close.
Works through pre-orders and requests for a limited beer against what will be packaged, using the rules you set, and shows who gets what and why.
Writes the brief for the label designer with every mandatory element listed, the sizes and the deadline, so the first proof comes back with the legal text already right.
Keeps one record for each new product as it moves from idea to pilot batch to launch, with the decisions, dates, costings and who owns the next step.
Orders from every channel, invoices, returns and credits.
Reads orders that arrive by email, text, voicemail note or messaging app and drafts the sales order in your brewery system, checking each line against stock and the customer's prices.
Brings orders from trade marketplaces and wholesaler portals into one list, matches them to your products, and flags collection dates and minimum shelf life rules.
Checks the day's invoices against the delivery notes, the customer's price list and any deal agreed by the rep, and lists the ones that look wrong before they reach the customer.
Works out what each returned keg or damaged case means: the credit note, the stock adjustment and the duty you can reclaim, so the same return is not credited twice.
Writes the order confirmation with the delivery day, anything substituted or short, and the keg collection due, in the same friendly tone every time.
Winning free houses and bottle shops, and keeping them.
Looks at order history to find accounts that have gone quiet or are ordering less, separates those who have just switched to buying through a wholesaler, and drafts a message in the rep's own voice.
Reads a pub's website, menu, reviews, social posts and what is on the bar, and writes a short brief on who they are, what they pour and why your beer would fit.
Builds a list of free houses, bottle shops and restaurants within a drive of the brewery that are likely to take your beer, using public information and the accounts you already have.
Turns a voice note after a visit into a CRM entry, the follow up email and any task for the office, such as a price, a sample or a keg collection.
Works out what a discount, a free case or a volume deal does to gross profit across trade and the webshop, so the rep knows the floor before the conversation.
Writes the letter that explains a price change after the duty uprating or a cost rise, with the new price list and a short version for reps to use face to face.
Pulls new accounts, lost accounts, volumes against target by rep and the open opportunities into one page for the Monday sales meeting.
Range reviews, product data, depot bookings, claims and export.
Pulls your rate of sale, distribution, promotions and the category trends into a pitch for a range review, written for a buyer who has thirty suppliers to see.
Fills in the product data each retailer or wholesaler asks for, from dimensions and case configuration to allergens and barcodes, from your one product record.
Reads supermarket and wholesaler purchase orders, checks them against stock and lead times, and drafts the depot booking and the pallet labels needed.
Matches remittances against invoices and lists every deduction a retailer or wholesaler has taken, with the promotion or claim it relates to and whether it looks right.
Drafts the paperwork for an export order from the order and the destination's rules: commercial invoice, packing list, label requirements and the duty documents for beer leaving in bond.
Drafts the answers to a tender or supplier questionnaire from your standard answers, accreditations and product data, and lists the questions that need someone senior.
Van runs, couriers, picking lists and the parcels that go missing.
Groups the week's local deliveries and keg collections into runs by area and day, with the order of drops, the load and the cut-off for adding more.
Books couriers and pallet collections for the day's orders, prints the labels and marks the orders as dispatched, which is the moment the duty becomes due.
Writes picking lists by location and delivery notes for each drop, with batch codes recorded so a recall can be traced to the pub.
Gathers the tracking, photos and order details for a lost or damaged parcel, files the claim with the courier and drafts the reply to the customer.
Brings driver hours, vehicle check sheets and loading errors into one weekly view, and flags drivers near their limits and checks that were missed.
Release days, customer emails, the beer club and the taproom.
Sets up a webshop release: product pages, limits per customer, the email to your list, the social posts and the fulfilment plan for the first weekend.
Drafts replies to webshop customers about delivery, broken cans, age checks and subscriptions, using the order history so the reply is about their order.
Plans each month's subscription box from what is in stock and coming, writes the tasting notes card and the email, and lists members whose payment failed.
Writes the tap list and the board from what is on and coming, with ABV, allergens and prices worked out from your margin rules and the minimum price after duty.
Plans an event from date to clear up: the beers, the staffing, the extra stock, the ticketing page, the posts and the checklist for anything your licence requires.
Matches the kegs sent to the taproom with the till sales by pint, so the stock and the duty records agree and you can see the yield from each keg.
The monthly return, relief, losses and the records HMRC expects.
Builds the month's duty figures from what was dispatched, split by strength band, draught and non-draught, with Small Producer Relief at the rate for when each batch was made, and spoilt beer reclaimed.
Works out your relief rate for the production year that starts on 1 February from your estimate of output, and keeps the record HMRC asks for of how and when you made the estimate.
Checks each product against the draught relief rules, at least twenty litres, under 8.5% and made for dispense, and flags anything claimed as draught that went out for take-away.
Writes the loss record HMRC expects when beer is destroyed or lost, with date, time, volume, strength, vessels, method and reason, and drafts the advance notice where one is needed.
Checks your brew records, packaging records, stock takes, losses and movements against the list HMRC publishes, and finds the gaps before an officer does.
Lists every movement of duty suspended beer that has not been receipted, how long it has been, and drafts a chase to the receiving warehouse before the deadline turns it into duty on your next return.
Reads the Budget on alcohol duty, such as the one on 28 October 2026 that sets the February 2027 rates, and works out what the new rates mean for each product and channel.
Label checks, allergens, food safety, recalls, deposits and packaging data.
Checks a label proof against the rules: name, strength, allergens in bold, net quantity, batch and best before space, your address, and the barcode, before thousands are printed.
Keeps one allergen record for every product from the recipes, including milk in lactose sours and gluten from barley and wheat, and checks it against every place the beer is listed.
Updates your food safety plan and procedures when a process changes, such as a new canning line or a fruited range, and lists the records you need to keep for each control point.
Builds a recall procedure that traces a batch from brew to every customer who received it, and drafts the notices, so a recall takes an hour rather than a week.
Lists every can product that will need a registered barcode and the scheme logo when the deposit return scheme starts on 1 October 2027, and plans the label changes and registration.
Works out the weight of packaging you placed on the market by material from your sales and pack specifications, for the packaging data return and the fee.
Keeps the taproom licence conditions, personal licence dates, age check training and refusals log in one place, and reminds you before anything lapses.
Raw materials, packaging, supplier bills and input prices.
Works out what the brew plan needs in malt, hops, yeast and adjuncts against what is in stock and on contract, and drafts the orders with lead times allowed for.
Reads supplier invoices, matches them to orders and deliveries, codes them and prepares them for the accounts package, with the PDF attached.
Lays quotes from packaging suppliers side by side on price per unit, minimum order, lead time and terms, so the cheapest headline price is not the only thing compared.
Tracks what you pay for CO2, energy, cans and malt against what you paid before and what the trade press is reporting, and flags the contracts to renew.
Credit control, cash forecasting, costing and the month end.
Lists overdue accounts by age and value, checks for disputes and credits, and drafts the chase for each in a tone that fits how good a customer they are.
Builds a rolling cash forecast from the bank, debtors, creditors, the duty payment on the 25th, payroll and planned purchases, and shows the weeks where cash gets tight.
Works through the month end checklist: bank reconciliations, taproom and webshop takings, stock valuation, accruals and the duty account, and lists what does not reconcile.
Builds the cost of each beer from recipe, yield, packaging, duty with your relief and labour, so you know the margin per pint, can and case in each channel.
Brings till and webshop takings into the accounts with the fees, refunds and tips split out, so the bank reconciliation matches.
Social posts, festivals and awards, reviews and consumer email.
Plans a month of posts from the release calendar, taproom events and what the brewers are doing, written in your voice with the facts checked against the product sheets.
Fills in festival and competition entry forms from your product records, and keeps a calendar of deadlines, deliveries and what each festival needs.
Reads ratings and reviews on beer rating apps and your webshop for each release, and sums up what people liked, what they did not, and any quality complaint worth checking.
Writes the weekly email to webshop customers and segments the list by what people have bought, so sour drinkers hear about the next sour.
Knowing your numbers, from a Monday note to the board pack.
Builds a sales dashboard from your brewery system, till and webshop that shows sales, margin and stock by channel, account and beer, and that you can change by asking Claude rather than paying a developer.
Writes a one page note every Monday with sales by channel, the biggest accounts, stock running low, cash and what is due this week.
Drafts the board pack from the accounts, the brewery system and the sales data, with sales, margin by channel, volume, cash, debtors and the key risks, and the commentary started.
Works out what each channel, account and beer really makes after discounts, delivery, keg losses and duty, so you can see which business is worth more of.
Produces the monthly KPI report for production, packaging, logistics and sales from the systems, instead of each manager copying numbers into a template.
Rotas, procedures, hiring and new starters.
Builds the rota from the production plan, the packaging days and the taproom opening hours, with holidays and skills taken into account, and flags any shift with no one trained to cover it.
Turns how your best people do a job, from a recorded walk through or their notes, into a step by step procedure for cleaning, packaging, cellar work or the till.
Writes the advert, the job description and the interview questions for a role, from what the job really involves rather than a template.
Builds the first two weeks for a new starter: the training they need, the procedures to read, who shows them what, and the records to keep.
Time is the easy part to count. For a brewery the other parts are keeping the accounts you fought to win, being easier to buy from than the next brewery, and owning the tools that run the place. Each has published evidence behind it, and each has a limit that we state next to it.
Most pubs near an independent brewery are closed to it, so the free houses and bottle shops that do take your beer are worth defending. It is easy to lose one over something that has nothing to do with the beer, such as a wrong order or an email nobody answered.
The detailCloseWe do not claim that Claude keeps any number of accounts, because nobody has published why pubs and shops drop a brewery or how often. We have not found a survey that measures it. Nothing Claude drafts reaches a customer until someone at the brewery has read it.
A buyer with thirty breweries to choose from orders from the one that makes ordering easy: a stock list they can trust, a confirmation that arrives, a product sheet with the right allergens and a delivery that turns up when promised.
The detailCloseWe do not claim that a stock list or faster paperwork wins a listing or a line, because nobody has published a number we would defend. The beer, the price and the relationship still decide it.
Brewery software is priced by volume, users and add-ons, and it still leaves gaps that people fill with spreadsheets. The planning views, the canning controller, the stock list and the dashboard Vault City built with Claude belong to Vault City, and they sit on top of its brewery system rather than replacing it.
The detailCloseThis covers internal tools, workflows and the connections between systems. It does not replace your brewery system, your accounts package or your till. Someone has to maintain what is built, and we agree who in writing. Anything that touches the duty return is checked by a person before it is submitted.
Every figure names who published it. Where nobody independent has published one, we leave the number out. Stories published by companies that sell software to breweries are vendor material and we say so. Vault City is our client.
Nobody independent has published how many hours a week brewery staff spend on this work, so put in your own.
Costed at £32 an hour. An hour is costed from that salary plus employer National Insurance and pension, over 1,740 hours. No overhead is added.
This values the hours at what they cost you and nothing more. In a small brewery the biggest cost is the founder's time away from brewing and selling, which is worth more than any salary.
This is arithmetic on your own numbers and not a claim about what Claude will do. Put in a year of sales to pubs, shops and wholesalers, and the share of it that you keep the following year from the same customers.
The starting figures are our own assumption for a typical brewery of each size, not a benchmark, because nobody has published one for UK breweries. Put in yours.
We do not claim that Claude changes retention. This only shows what each point is worth on the figures you entered.
Not a bigger brewery. The same brewery, with most of the work on the right hand side of that list gone.
Not a bigger brewery. The same brewery, with most of the work on the right hand side of that list gone.
Not a bigger brewery. The same brewery, with most of the work on the right hand side of that list gone.
Pick one use case from this page. Thirty minutes on a call, no slides, and you keep whatever we build.
Book a call