Nearly nine hours a week of admin, handed to software the brewery already paid for
Goldmark ran its orders, invoices and dispatch out of an old desktop system while Breww and Xero sat paid for and unused. In one week I moved the business onto Breww, connected it to Xero, and took nine recurring admin jobs off people's desks. No new software was bought.
Start here: this one is mine too. Goldmark Craft Beers is a business I own, and I led this implementation myself. Read it as a worked example rather than an independent reference. What you get in exchange is the full picture: the hours it took and the hours it saves.
At a glance
- The business
- Goldmark, cask beer brewed in Poling, near Arundel, since 2013
- What it replaced
- ViewPlan, a desktop brewery system running orders, dispatch and invoicing
- What it moved to
- Breww for brewery management, connected to Xero for the accounts
- Software bought
- None. Breww, Xero and Microsoft 365 were already licensed
- Implementation week
- 28 September to 4 October 2026
- Live
- Monday 5 October 2026, 11 days ahead of the planned cutover
- My time
- About 48 hours across that week
Who they are
Goldmark has brewed cask beer in Poling, near Arundel, since 2013. Draft Pick, a keg brand, is brewed alongside it. The team is small: Ethan runs the brewery, Marta runs customer engagement, and I run the business side.
The challenge
Breww and Xero were both paid for. Neither was doing the job. On Monday 28 September, Breww held a floor plan and a brew kit and nothing else, and Xero had never raised an invoice. Every order, dispatch note and invoice still came out of ViewPlan, an old desktop system on one PC at the brewery.
So the work happened around the software instead of inside it. Invoices were raised in one system and keyed into another, emailed by hand, and never followed by a reminder or a statement. Supplier bills were typed into Xero. Casks went out to pubs and were tracked on paper and memory. Marta built her call lists from spreadsheets. Every call to the brewery went to one mobile.
None of that is unusual. It is what a small business looks like when the software has been bought but never implemented.
What I built
Breww is now the system of record, and everything else hangs off it.
- Off ViewPlan. Customers, products, price books and casks exported, cleansed and loaded into Breww. ViewPlan no longer invoices or dispatches.
- Breww to Xero. Invoices, credit notes and supplier bills arrive in Xero as drafts, and payments sync in both directions. The invoices still open in ViewPlan were brought across and the balances checked to match.
- Invoices and payment. Invoice emails go automatically once an order is delivered, from a verified accounts address. Payment reminders are on, and monthly statements start in November.
- Supplier bills. A bill emailed to the accounts inbox becomes a draft bill in Xero.
- Casks. Every cask is a tracked record, and the pubs holding them sit on a monthly uplift list.
- Sales. Five lists in Breww create Marta's tasks each week: overdue payments to chase, casks to collect, customers with missing details, regulars due to order, and lapsed customers to win back.
- Phones and inbox. An unanswered call goes to voicemail and raises an alert in Teams. A daily sweep checks junk folders for customer emails, and caught a trade order on its first day.
- Bookkeeping in one place. A short stretch of bookkeeping kept in FreeAgent was cleared into Xero, and FreeAgent is now switched off.
- Trade marketing. Customers marked for marketing in Breww sync to Klaviyo. It does one job today, and it is the base the brewery's marketing will grow from.
- Where to drink. The map of pubs pouring Goldmark and Draft Pick on the brewery's website now updates itself overnight from Breww. Tag a pub in Breww and, once it has had a delivery in the last four weeks, it appears. A rosette shows how often it pours the beer: gold for a permanent line, silver for a delivery every fortnight, bronze otherwise. Each beer's page shows where it was recently sent. The website only reads from Breww, never stores a contact name, phone number or order detail, and a pub that asks not to be listed stays off whatever Breww says.
- Duty. October's alcohol duty is set up in Breww.
- Process. Seven SOPs rewritten around Breww and Xero, replacing a quality system written around ViewPlan.
Breww's own onboarding checklist was 85% complete at go-live.
What I did
Breww publishes a sound onboarding checklist and more than 350 help guides, and I followed the checklist. What made the difference was not knowing something the guides leave out. It was the order, and the checking.
Get the ledger agreeing first. The invoices still open in ViewPlan went into Xero, and the balances were checked to match, before the new system was trusted with anything. If the books do not agree on day one, they never quite agree again.
Prove each automation end to end. An invoice raised, emailed and sitting in Xero is proof. A setting switched on is not. The first three live orders went through the whole chain before I called the integration done.
Log every configuration mistake. I kept a running log of every setting that turned out to be wrong, and fixed them before the team relied on them. The few still open are being closed out. That log is the part a first-timer does not keep, and it is where most of the cost of doing it yourself hides.
Rewrite the process with the software. The SOPs changed in the same week. New software with procedures that still describe the old way puts a team back on the old way within a month.
How it runs day to day
An order goes into Breww. When it is delivered, Breww raises the invoice, emails it to the customer and puts it in Xero. When the customer pays, both systems know. If they do not, the reminder goes without anyone writing it, and the order appears on Marta's overdue list.
Marta starts the week from her Breww lists rather than a spreadsheet. Ethan works from the SOPs. Supplier bills land in Xero as drafts for checking, not typing. When a delivery is marked complete in Breww, the pub's place on the website's Where to drink map is updated that night, without anyone opening the website.
The accountant still approves what goes into the books. Nothing here took a decision away from a person. It took away the typing that sat in front of the decision.
The outcome
What changed
Breww is the live system from Monday 5 October 2026, eleven days ahead of the planned cutover on 16 October.
These are the jobs it took off people's desks, with my estimate of what each was costing a week:
- Raising and keying sales invoices, 2 hours a week. Now: Breww invoices on dispatch and uploads to Xero.
- Emailing invoices and chasing payment, 1.5 hours a week. Now: automatic invoice emails, reminders and statements.
- Keying supplier bills into Xero, 1 hour a week. Now: bills emailed to the accounts inbox become Xero drafts.
- Building call and chase lists, 1 hour a week. Now: Breww lists create Marta's tasks each week.
- Tracking casks on paper and memory, 1 hour a week. Now: tracked casks and the uplift list.
- Checking voicemail and missed calls, 0.5 hours a week. Now: a Teams alert, once the phone line switch completes.
- Checking junk folders for orders, 0.5 hours a week. Now: a daily sweep.
- Printing invoices, 0.25 hours a week. Now: automatic printing.
- Keeping the Where to drink map current, 1 hour a week. Now: a nightly feed from Breww.
Total: about 8.75 hours a week.
They are estimates, and I would rather say so than dress them up. They get checked against October, the first full month live, and this page will carry what the month shows.
The Where to drink feed went live on the morning of 5 October. The hour is the smaller part of what it fixes. A list kept by hand drifts: a pub that stopped pouring the beer stays on it, and a regular gets left off. Either one lands on a relationship the brewery has spent years building, in public, on its own website. A feed taken from the deliveries themselves does not drift that way.
By the numbers
Four questions to ask of your own site
- Which software are you paying for that nobody has finished setting up?
- How many times is each invoice typed, and by whom?
- When a customer does not pay, who notices, and how long after?
- If you set it up yourself, at the hours you can really spare, when would it be finished, and what does the old way cost you until then?
What this was, as a service
- Workflow Automation
Get your systems talking to each other and cut out the double entry and the manual reports that come with it.
- Business Health Check
A clear look at where your time and money are really going, with a ranked plan for what to fix first.
Want results like these?
Tell me what's going on and we'll talk through what's possible for your business. The first call is free.