Pour5

What it is

Software for the bar owner who is also the buyer, the counter, and the bookkeeper. Pour5 connects to the register, reads the menu that is already there, and watches what deliveries do to the cost of every pour built on them. When a drink drifts off the margin its owner set, it shows them the new cost, the price on the menu now, and what the price would have to be.

Then it stops. Pour5 can rename, restructure, reprice and remove things in a register, and it does none of it until someone says yes. That is a product decision rather than a technical limit, and it is the one we would defend hardest: an operator who cannot predict what the software will do next stops using it, whatever it saves them.

Why a software studio

Pour5 started with a text message, at dinner with friends who own a bar outside Denver. Their bartender said they were out of something. They knew they were not, because they remembered ordering it, and they told the bartender where to find it — from memory, in the middle of dinner.

What followed was an hour on what running a bar actually takes. Prices keyed into the register one at a time. Costs chased through spreadsheets. Every tool they had tried did part of it and left them as the glue between the parts. They were not complaining about software; they were describing their evenings.

We were not at that table looking for a business idea. The question stuck anyway: why do they have to do any of this? We built an inventory prototype to help them, and it grew from there into a company.

What it changed about how we build

Everything else we have built is a screen someone opens by choice, usually a developer at a desk with time to learn it. Pour5 gets used standing up at the end of a shift, by someone who would rather not be looking at a screen at all. So the rules change. Twenty seconds a developer would not notice is twenty seconds a bar owner does not have after close.

Pour5 also forced the shape question. Most software is built in the shape that was convenient to write, and the person using it spends the rest of their life translating between that and their actual work. A bar is not an alphabetical list, and counting it as one means walking the room in one order while reading the screen in another. So Pour5 learns the shape that is already there — their layout, their menu, their names — and the code carries the translation instead of the operator.

Neither of those is a feature. They are both decisions about who absorbs the awkwardness, and we have been wrong about them often enough to know they are worth arguing over.

Where it stops

Pour5 can keep the cost side honest, because cost comes off an invoice. It cannot see the spout. If the pours going across a bar are heavy by a quarter ounce, the pour cost it calculates is arithmetically correct and still not what the night cost. Somebody has to watch that, and it is not us.

Pour5 does not walk the room and count the bottles either. It tells you what should be on the shelf, which turns a count into a check rather than a survey, and a person still has to go and look.