FOUNDER PHOTO

Built by a Brewer.
For Brewers.

BrewCompass didn't come from a tech startup brainstorm or a consulting firm's whiteboard. It came from a decade of early mornings, frustration with the tools that were supposed to make the job easier, and too many spreadsheets holding everything together.

The Problem I Kept Running Into

After 10 years of professional brewing — including serving as Head Brewer at multiple breweries — I'd used just about every tool the industry had to offer. Recipe software that couldn't talk to inventory. Spreadsheets for TTB reporting that one wrong cell could break. Notebooks for brew logs that got wet, lost, or left in someone's truck.

The bigger platforms were built for factories, not 7-barrel brewpubs. The smaller ones solved one piece and ignored the rest. And every single one of them felt like it was designed by someone who'd never stood in a brewery at 5 AM trying to figure out if they had enough grain for tomorrow's batch.

I didn't set out to build software. I set out to stop losing data on clipboards and spending my Sundays updating spreadsheets instead of being with my family.

So I started building the tool I wished existed. One that connected recipes to batches to inventory to packaging to compliance — the way the actual work connects in a real brewery. Not a collection of separate apps duct-taped together, but one system that understands the workflow because it was designed by someone who lived it.

From Brew Day to Build Day

The path from brewer to founder wasn't a straight line — but every step informed what BrewCompass became.

~20 Years Ago

Started Tracking Data as a Homebrewer

Even before brewing professionally, I was logging recipes, recording gravity readings, and tracking what worked and what didn't. The habit of capturing data to make better beer started long before it became a career.

Mid 2010s

Started Brewing Professionally

Began working in craft breweries, learning the trade from the ground up — milling grain, scrubbing tanks, and figuring out why the mash tun was stuck again.

Following Years

Moved Into Head Brewer Roles

Took on recipe development, fermentation management, QC programs, purchasing, and all the operational overhead that comes with running production. Started bumping into the software gaps daily.

The Pivot

Started Building BrewCompass

What started as a personal project to organize brew logs turned into something much bigger. Realized the whole industry was dealing with the same fragmented tooling problem.

2025–2026

Full-Time Development

Went all-in on building BrewCompass as a complete platform. 26 modules live, covering everything from recipe building to TTB reporting to keg tracking. Now onboarding beta testers.

What Makes BrewCompass Different

There's no shortage of brewery software out there. What's rare is brewery software built by someone who actually ran a brewery. That's not a marketing angle — it's the reason the details are right.

It's why grain is measured in sacks and hops ship in 11, 22, and 44-pound increments instead of generic "quantity" fields. It's why the sensory panel uses WSET-aligned methodology with BLIC scoring, not a thumbs-up emoji. It's why TTB reporting pulls directly from your production data instead of asking you to re-enter numbers you already logged.

Every field, every dropdown, every workflow was built by someone who's used the real-world version of that tool and got frustrated enough to build a better one.

How We Build

🎯

Domain First

Every feature starts with how breweries actually work — not how software companies think they should.

💰

Honest Pricing

Volume-based flat pricing. All features at every tier. No per-user fees, no module upsells, no surprises.

🔗

Everything Connected

Data flows through the whole system. Your recipe feeds your batch, your batch feeds your inventory, your inventory feeds your purchasing.

Want to See What 10 Years of Brewing Built?

Join the beta to get hands-on with BrewCompass and help shape the platform from the inside.