AI Ops Audit ($500)Credited toward a build within 30 days
Book Now →
← Barrel & Beacon
A Working System

Inside a Brand Ops Brain. One brand's week, handled.

Not a demo reel and not slideware. This is the system I build for beverage brands, running on a sample brand, doing the ops work that eats your selling time. Watch the 1:49 run, or read the whole thing in text below it.

Built by someone who carried a bag for 30+ years: I know what a depletion dip should trigger, what a distributor check-in should actually say, and which states have franchise laws. That goes into the build, not into a deck.

Rather read than watch? The full run is written out below the video. Or start smaller: free 10-min call, no pitch · hello@barrelandbeacon.com

The Demo

Foxglen Bourbon Co., start to finish.

One founder's morning in the time it takes to drink a coffee. Five prompts, five answers, no cuts in between. Here is every step you will see:

  • Morning brief: calendar, overnight email, overdue follow-ups, and this week's priorities in one read.
  • Meeting prep on a named distributor contact, pulled from every past interaction on record.
  • "Who's gone quiet?" Stale relationships flagged against their cadence, check-in emails drafted in the founder's voice.
  • Content batch: a week of posts, checked against the last three weeks so nothing repeats.
  • Call logging: a spoken recap turned into a CRM entry, a next step, and a follow-up date.

Foxglen Bourbon Co. is a sample brand, not a client. Barrel & Beacon is in pilot intake, so there are no client names and no client results to show you. Every contact and every number in the demo is a fixture built for the walkthrough. The system running on top of them is the real thing, with nothing hidden behind a login.

No sound needed. Everything the system returns is written out in full in the next section.

The Same Run, In Text

Prefer to read it? Here is the whole thing.

Five prompts, and what came back for each one. This is the output from the run in the video above, set in the page's type instead of a screen recording, with punctuation tidied and nothing added.

Read these as fixtures, not results. Priya, Marcus, Val, the placement counts, the case counts: all of it is invented Foxglen data. What is worth judging is what the system did with it.

Step 1 of 5

Morning brief

morning brief

Today's calendar

  • 9:30a. Call: Marcus Hale (Bluegrass), September reset planning.
  • 1:00p. Tasting room walkthrough with Jess.
  • 3:30p. OH distributor intro call: Val Kessler, Riverbend Distributing.

Emails needing replies

  • Priya Natarajan (Cumberland Crown): fall menu deadline moved up to Aug 8. Needs cocktail spec sheets and pricing by July 25 or half the accounts get missed.
  • Tom Kowalski: Elizabethtown store 3 wants a Rye endcap in August. Needs an answer by Monday.
  • Meg (designer): two Rye gift carton label proofs, waiting on a direction call.

Overdue follow-ups (CRM)

  • Priya Natarajan: next touch was 7/8, past due. Also, you promised her a Nashville visit before menus lock, still not scheduled.
  • Val Kessler (Riverbend/OH): next touch was 7/3, past due. You also owe her volume projections and KY velocity data, promised "within a week," not sent.
  • Chef Andre Boone (The Copper Still): next touch was 6/30, past due.

This week's priorities

  • Nashville visit with Priya, needs to get on the calendar before July ends.
  • TN on-premise is at risk: 2 placements vs. the goal of 10, menus lock in August.
  • OH distributor: two stalled conversations, target is signing by end of Q3.
  • Rye check-ins with IN chain contacts.

Biggest fire: Priya's deadline moved up and you're already overdue with her twice over (spec sheets plus the visit). Want me to draft that reply now?

Step 2 of 5

Meeting prep

prep me for my meeting with Priya

Priya Natarajan, Cumberland Crown Distributing (TN)

  • Last interaction: 6/24 email. Next touch was 7/8, past due.
  • She asked for cocktail spec sheets; you promised a Nashville market visit before fall menus lock. Neither has happened.
  • Follow-up cadence for Cumberland Crown is 14 days through October (launch window). You're already past that.
  • Escalation contact if needed: Walt Freeman, GM.

Open items between you

  • Cocktail spec sheets and pricing: she now needs these by July 25, moved up from the original ask.
  • The Nashville visit: promised, not scheduled.
  • TN on-premise placements: 2 out of the 10 menu goal, menus lock Aug 8.

Talking points

  • Own the delay straight up, then give her a firm date for the Nashville visit. This is the priority item this month per your own notes.
  • Walk through the spec sheet timeline. Can you actually hit July 25? If not, tell her now, not on the 24th.
  • Ask directly which accounts are still winnable for the 10-menu push, given menus lock in less than a month.

Want me to draft the Nashville scheduling email while this is fresh?

Step 3 of 5

Who's gone quiet

who's gone quiet?

Gone quiet (past cadence)

  • Priya Natarajan (Cumberland Crown): last touch 6/24, 18 days. Cadence for Cumberland Crown is 14 days through October. Overdue.
  • Chef Andre Boone (The Copper Still): last touch 5/30 visit, 43 days. Standard cadence is 30 days. Overdue.

Marcus, Val, and Tom are all within cadence, so not on this list. Here are drafts for the two that qualify:

Draft 1 of 2: Priya Natarajan

Hey Priya,

Sorry for the gap. I know the spec sheets are overdue and the Nashville visit still isn't on the calendar. Both are on me.

I can get you cocktail spec sheets and pricing by July 25. For the visit, does the week of the 20th work? Pick a day and I'll book it.

Talk soon,
Dana

Draft 2 of 2: Chef Andre Boone

Hey Andre,

Summer's settling out on our end. You mentioned wanting to talk fall feature once things calmed down, so here I am.

Rye's been getting good traction lately. Want to grab 20 minutes next week and talk through it?

Both are drafts, not sent. Want any edits before you send them?

Step 4 of 5

Content batch

draft this week's posts

This week's posts

Checked against the last 3 weeks, avoiding rickhouse aging, corn field, and Rye cocktail repeats.

  • Post 1, family and rickhouse angle. Image idea: exterior shot of the rickhouse, golden hour. Caption: "My grandfather built this rickhouse by hand. Everything we make still ages under his roof. Some things don't need updating." #Foxglen #Bardstown
  • Post 2, Small Batch feature (balancing the recent Rye focus). Image idea: Old Fashioned with the Small Batch bottle, bar setting. Caption: "An Old Fashioned made right starts with what's in the glass. We grow the corn, we run the still, we age it once. Simple as that." #FoxglenSmallBatch
  • Post 3, farm and season angle. Image idea: hands checking corn stalks or an irrigation line, midday. Caption: "July on the farm means watching the sky more than the calendar. Every bottle starts right here, in this field." #Foxglen

Want me to adjust any angle, or pull from a different part of the story?

Step 5 of 5

Log a call

Log my call with Marcus. Settled the September reset, 20 cases Small Batch, 10 Rye, he wants updated shelf talkers by August 15. I owe him the co-op budget number by next Friday. Next check-in in two weeks.

Interactions: Marcus Hale / Bluegrass Beverage Co.

  • Date: 2026-07-11
  • Summary: settled September reset, 20 cases Small Batch, 10 Rye. Marcus wants updated shelf talkers by August 15.
  • Next step: send co-op budget number to Marcus, due Friday, 2026-07-18.
  • Next touch: 2026-07-25.

One flag: Marcus already existed in the CRM slice with a next touch of 7/22. This updates that to 7/25 based on "two weeks" from today. Want me to adjust if you meant two weeks from your original 7/22 date instead?

The system labels this one itself: the logging is simulated, because the demo project runs on a test fixture CRM rather than a live database. A real build writes to your real database. That disclosure is in the video, not added here.

One 60-minute call, then a written roadmap of exactly what to automate in your business, in what order. Not ready for that? Free 10-min call, no pitch →

The Five Workflows

What it actually does, every week.

All five are in the video and in the walkthrough above. They ship with every Brand Ops Brain. Here is what each one replaces.

"Morning brief."

Reads the calendar, scans overnight email, checks the CRM for follow-ups going stale, pulls the task list. One briefing: here's the day, here's what needs attention, here's what's slipping. An hour of morning triage becomes a two-minute read.

"Prep me for my meeting with Priya."

Every past interaction, company context, open items between you, drafted talking points. Thirty seconds instead of twenty minutes of digging through notes. It even surfaces the promises you made and haven't kept yet.

"Log my call with Marcus."

Writes the interaction to the CRM, updates the contact record, creates the follow-up task with the right date, and flags it when the new date contradicts one already on file. Nothing falls through the cracks because the system does the remembering.

"Who's gone quiet?"

Scans relationship history, flags anyone untouched past their cadence, and drafts the check-in emails with the real context of the last conversation. The founder reviews and sends. The system never sends anything itself.

"Draft this week's content."

Every draft in the brand's voice, checked against the content calendar so nothing repeats, with hard rules for what the brand will and won't say. A human approves before anything posts.

For brands with distributor depletion data: see the live sample dashboard and monthly memo that pair with this →

Straight Answers

What this actually is.

It knows your business before it writes anything. Your distributor landscape, your open accounts, your priorities, your team, your voice, and your rules are loaded in, and it reads all of that before it drafts a single line. That is why the reply comes back usable instead of generic.

Two things it is not, since both come up every time:

  • Not ChatGPT with a clever prompt
  • Not a slide deck of recommendations you have to go build yourself

It runs inside the tools a brand already uses: your notes, your CRM, your email, your calendar, your files. There is a short list of things you supply, and it's published on this page rather than saved for the call.

What It Costs

Published prices. No discovery-call ambush.

Most readers of this page are deciding between two things: the map, or the build. Both are below at the real price.

Start here

AI Ops Audit

$500

One 60-minute call plus a written roadmap: your top 10 automatable workflows, ranked by payoff, and what you already pay for that can be wired together. Delivered as a 4 to 6 page PDF within 5 business days. Credited toward any build within 30 days.

Book the audit →

Brand Ops Brain

$2,500

The system on this page, built for your brand in 3 weeks. Wired to your email and calendar. Five workflows tested on your real data. Training session recorded, plus 30 days of support.

Start with the audit, credited back →

Two more tiers, if you want the power layer or ongoing help: Full AI Operations Build, $5,000 (everything above plus custom skills, memory architecture, and automated reporting, 4 to 5 weeks, 60 days of support) and AI Ops Partner, $400/mo (optional retainer: a deliverable every month, tune-ups, new workflows, cancel anytime). See all four tiers side by side → or read a sample monthly memo →

What you supply

  • Your own Claude subscription. Pro, from $20 a month. Billed to you, not to me.
  • Google Workspace or Microsoft 365. Whichever you already run.
  • One 60 to 90 minute block a week during the build, for access and feedback.

The audit is the low-risk way in. You keep the written roadmap whether or not you hire me for the build. If you do hire me within 30 days, the $500 comes off the price. Beyond your own time and a $20 a month Claude subscription, that is the whole risk.

Before You Book

The questions people ask at this point.

Do you have client results to show me?

No, and I won't pretend otherwise. Barrel & Beacon is in pilot intake, so there are no case numbers and no testimonials yet. What there is: a working system you can watch run end to end, the same run written out in full on this page, published prices, and an audit that credits back against a build. You are judging the work, not a reference list.

What was real in that video, and what was staged?

The brand is invented. Foxglen Bourbon Co., every contact in it, and every number in it are fixtures built for the walkthrough. The system is not invented: it is a real Claude project with real context files and real connectors, and there are no cuts between a prompt and its answer.

One honest limit, which the system states on camera at step five: it logged the call against the test fixture CRM rather than a live database, because the demo project is not wired to a real one. Your build is.

What do I have to supply?

Your own Claude subscription (Pro, from $20 a month, billed to you and not to me), Google Workspace or Microsoft 365, and one 60 to 90 minute block a week during the build so I can get access and feedback. That is the full list, and it is on this page rather than saved for the call.

What if my records are a mess?

Most are. You do not need a clean CRM to start. During the three week build I load what already exists: your contacts, your distributor landscape, your account list, your current priorities, your voice and your rules. I do that loading, not you. What lives only in your head comes out in the weekly working block.

After that the system logs as you go, so every call you log is context it did not have the day before. Week one is thinner than week ten, and week one still beats the spreadsheet.

Will it send emails or post without me?

Never. It drafts, you approve. Every outbound message and every post is reviewed by a human before it leaves. That rule is built into the system, not left to discipline.

More on time, data, ownership, and what happens when the tools change: the full FAQ is on the home page.

Next Step

See what your brand's system would look like.

The audit is one 60-minute call and a 4 to 6 page written roadmap of exactly what to automate, in what order. $500, credited toward a build within 30 days.

Prefer email? hello@barrelandbeacon.com