Skip the Export: Connecting Claude and ChatGPT Directly to Your Brewery Data

On today's Craft Beer Professionals webinar, Dustin, the VP of Product for Ekos and Ollie at Next Glass, walked brewers through how he uses AI. Most of it I agree with. Pull a report you already use, drop it into Claude, write a specific prompt instead of a vague one, and once it works, save it as a skill so you never type that prompt again. Check the numbers against your own totals the first few times. Treat a skill like an SOP.

That is good advice, and the timing is right. In the survey Next Glass shared, 22% of about 100 breweries use AI regularly and another 27% are experimenting. Claude was the most popular tool.

I've been brewing for 15 years, and I build FermentIQ, so I'm going to push on one step in that workflow: the export.

Where the export workflow wears thin

The first time you export a packaging report and get a clean cost breakdown back from Claude, it feels like magic. The tenth Monday you do it, it feels like a chore with extra steps. In the demo, taproom margins meant exporting from the ERP, exporting from Toast, uploading both and asking Claude to stitch them together.

Three things come with that:

The answer is only as current as the file. Pull it Friday, ask on Tuesday, and you're reading Friday.
Every system is another export. ERP, POS, accounting, each one a separate download.
The AI can only read. When Claude spots a $0 invoice or a keg deposit set up wrong (both happened in the demo), you still go fix it by hand.

What a connector changes

An MCP connector lets Claude or ChatGPT talk to your brewery software directly. No download, no upload. Next Glass showed the one they're building for Ekos, starting with sales data and adding production later.

FermentIQ's connector has been live since August. Once it's connected, you can ask things like:

"Pull this week's production summary and add it to my status sheet."
"What's low in stock? Give it to me in order sheet format."
"Log an SG reading of 1.012 at 66°F for the IPA in FV3."

That last one is the difference. The connector writes as well as reads: fermentation readings, inventory adjustments, tasks, customer interactions, and (if an admin allows it) sales orders and invoices. Taproom sales come in through the built-in Toast sync, so the margin question is one system, not two exports.

Don't hand your AI your passwords

Dustin's warning about agents was the best part of the talk. Don't give an AI anything you wouldn't give a new hire on day one. I'd add: don't give it a login at all. Give it a key.

FermentIQ connector keys work like that:

Each key acts as one role, never above the person who made it, and only reaches the data areas you tick.
Payroll and financial writes can only be granted by an admin.
Deletes and batch state changes are not available through the connector at all.
Keys revoke instantly, and every call is logged.

One thing to know going in: data pulled through the connector goes to the AI service you connect it to, Anthropic for Claude or OpenAI for ChatGPT. That's your call, which is why the sensitive scopes are admin-only.

The data problem a chat window can't fix

The errors Claude caught in that demo were data-entry errors. AI analysis is only as good as what got typed in, and in most breweries the typing happens at the end of a long day from a clipboard.

That's the part I built FermentIQ around. You log readings, transfers and additions out loud at the tank, so the number goes in when it happens. FermentIQ checks every 30 minutes for a gravity that's been flat for 48 hours, a fermenter overdue for CIP, or an ingredient running short with a brew day coming. You don't have to write a skill to get warned.

Where I agree completely

Don't let AI sign off on your TTB report. FermentIQ builds the 5130.9 from your production data so you're not assembling it by hand, and it still stops for your review before anything is filed. That's the right order: AI does the assembly, you do the signing.

Start small, like they said

Pick one report you pull every week. Ask one specific question. Check the totals. If you're tired of the export step by week three, that's when a connector earns its keep.