← Back to the Weekly Signal

How the Weekly Signal works

The nightly loop it runs on, the five questions every Brief answers, the alerts between Mondays, and a full example on a synthetic demo brewery, walked end to end.

How it actually works

A weekly briefing that gets smarter every week

The Weekly Signal runs on a loop. Live inputs from across your business come in every night and get weighed against everything your brewery already knows. The loop turns that into a heads-up, a place to dig in, and a decision you act on. Every answer and every outcome feeds back into your brewery's knowledge, so each week starts a little sharper than the last.

1ALERT

What changed, delivered where your team already talks. A short morning video and a Slack heads-up carry the one thing worth knowing. When something looks off and no note explains it, the Signal asks you about it directly.

2ANALYZE

Dig into whatever caught your eye. Ask a question in Slack and get an answer in seconds, scoped to your data. When you want the full root cause, it opens into the Weekly Signal Brief.

3ACTION

Decide what to do, and write it down so it lives somewhere other than a meeting. Later the Signal follows up on its own: did the action actually work?

We connect and maintain the inputsWe set up and keep every connection running, so the daily data flows in on its own. It comes from three places: the transactional data your business produces every day, like POS sales, labor, and the money side; outside conditions like weather and local events; and the context your team already carries, from manager logs to the notes and past actions they mention along the way.

The goalAnyone on the team can get an immediate alert on how the business is performing, see the one thing worth acting on, and know what that action is worth, all in a couple of minutes. For brewery teams that are always under pressure, juggling a dozen things at once and moving from one fire to the next, getting there that fast is what keeps a small problem from becoming an expensive one.

Brewery Brain · The Weekly Signal

What the Weekly Signal actually says

The Weekly Signal is one brief a week that answers the five questions every operator asks, in the order they ask them. It comes to you in Slack and as a short morning video, and it opens into the full Brief when you want the root cause. Here is a full week, walked end to end.

You start where your data isMost breweries connect their POS and manager logs first, then add weather, guest reviews, and the money side over time. The Signal gets richer with each source, and it works from day one on the two you already have.

The five questions it answers

Each stage shows what feeds it, what you see, and where it lands. The example runs through Coastline Craft Co., a synthetic demo brewery, for the week of April 13.

1

What happened?

The weekThe taproom ran $206,402, about 3% under plan. Harbor beat its plan; Downtown came in light.

2

Why should I care?

The stakesIf you only have time for one thing this week, focus on Downtown evening. It's the biggest single gap at $4,084, it's a real soft spot (the other dayparts just trail a high plan), and it's been under plan for weeks. That makes it the one place your attention pays off.

3

What caused it?

The causeGuests held steady, but they ordered less food: attach down 6 points, so the average check fell 8%. One level down it is Food, $4,441 under plan, while beer and cocktails ran over.

4

What should I do?

The actionWork Downtown evening food attach: a late-night menu, servers prompting at the table. The gap to plan is $4,084; an illustrative win-back from the food fix runs about $2,000 to $2,500 over the next few weeks.

5

What's next?

The follow-upEvening has been under plan two weeks running, and 6 of the last 7. Next week's Signal checks whether the fix held.

When the Signal asks

When a number looks off and nothing in the logs explains it, the Signal asks the person who was there.

Signal

Brewery Brain

Downtown evening ran about 20% under plan Friday and Saturday, on lower food attach and smaller checks, even though traffic held. Anything you'd point to?

GM

Downtown manager

Kitchen was short a line cook both nights. We stopped pushing food after 8.

That answer turns "evening is soft" into a specific, fixable cause. It gets stored, so next week's Signal already knows to watch evening food attach and whether the new hire closes the gap. That's the loop from page one, in a single exchange. When a busy week means no one answers, that's fine: the Signal still flags the gap and keeps going, and the next answer sharpens it.

The Signal does not stop at the why. It proposes the fix, ready to hand off:

Recommended action

Work Downtown evening food attach: a late-night menu, and servers prompting at the table.

Open the fix & assign it →

One tap opens it in the app, where you can adjust the plan, assign it to someone, and log the decision. We propose the action; you decide.

It comes to you, wherever you work

The same Signal reaches you through whatever fits your day. We make it as easy as possible to get the insight and act on it without stepping out of your normal routine.

Watcha two-minute video on what changed last week

Listenlike a short podcast, on the drive in

In Slackright where your team already talks

On your phoneopen the full brief and dig in

Here is that full brief, where an operator digs in.

Weekly Signal Brief

Downtown evening pacing under plan

Coastline Craft Co. · Taproom · Week of Apr 13 · Harbor + Downtown

Summary. Taproom revenue $206,402 vs $213,764 plan (down 3.4%). Downtown carries the gap (down 8.8% vs plan); Harbor came in over plan. Downtown evening is the daypart to work: the one spot sitting below its own recent pace. The other soft dayparts are tracking their own pace under a plan that sits high.

Taproom vs plan

$206.4K

▼ 3.4% under plan

Downtown evening

−$4,084

▼ 19.6% vs plan

Evening food attach

48%

▼ 6 pts vs prior week

This week's decision

Downtown evening is the headline, $4,084 under plan. Traffic held: about as many guests as last week. The gap is check size. Guests ordered less food (attach down 6 points, and lighter tickets once the kitchen cut back), so the average check fell 8%, and Food came in $4,441 under plan while beer and cocktails ran over. The lever is evening food attach: a late-night menu, servers prompting at the table. An illustrative win-back is about $2,000 to $2,500 of the gap over the next few weeks.

Daypart	vs plan	Guests (checks)	Avg check
Downtown evening ★	−$4.1K	384 flat	$43.60 ▼ 8%
Downtown dinner	−$4.2K	826 ▼ 3%	$48.89 ▼ 3%
Harbor dinner	−$2.5K	738 ▲ 4%	$50.04 ▲ 2%
Downtown afternoon	−$1.6K	351 ▼ 3%	$49.06 ▲ 5%

Guests and avg check are versus the prior week. Downtown evening held its traffic; the gap is check size: guests ordered less food (attach down 6 points), so the average check fell 8%.

What we set aside this week

Harbor afternoon ran over plan, but Saturday alone was 40% of the week and 4x a normal afternoon ($8,437 in one day). That reads as a one-off, like a private buyout, so we set aside about $5,634 rather than count it as a real gain. The Signal filters that noise so you don't have to.

Every figure traces to the POS actuals and your sales plan, complete Mon–Sun weeks only, no projections, except the win-back estimate, which is illustrative. Avg check is net sales per check, pre-tax and after comps.

A faithful mock of the Weekly Signal Brief, on Coastline Craft Co. (a synthetic demo brewery). Real client briefs carry the same shape (live BAN cards, sparklines, and drill tables) on the brewery's own numbers.