№ 530304July 2026 · Brooklyn, NY
Kings County Distillery Agent
A business analyst in Slack for New York's oldest and most awarded whiskey distillery.
Problem
I sit on the board of a small craft distillery, Kings County Distillery (New York City’s oldest and most awarded distillery). The business decisions require reconciling the story from half a dozen disconnected exports — accounting, online store, register, barrel inventory.
Solution
This agent can, with its connections, answer most important questions on the business via Slack. The next step is letting it act on my behalf (inspired by Bending Spoons' internal 'alter ego' agent).
Verifying data across different channels
How does production, aging, bottling, shipping, marketing, and admin all work together?
A distillery is several businesses sharing one set of books. Spirit is made years before it is sold, so cash sits in barrels that lose volume to evaporation while rent, insurance and excise accrue per barrel-year, and inventory has to be tracked in proof gallons by age rather than in bottles. Revenue then arrives through channels with different economics: distributors who take a margin and pay on terms, direct online orders, the tasting room's register, and events. Each lives in its own system with its own idea of a sale, a month and a product. The build scripts map every export into shared revenue segments and cost buckets, then gate on the seams: segment sums must match the ledger's monthly totals, cash rebuilt from bank transactions must land on the balance sheet, and barrel counts and proof gallons must agree with the inventory export, or the build stops and names the gap. A failing gate usually means a source changed shape, which is exactly when a hand-edited spreadsheet drifts silently.
An alter-ego agent
The direction is an assistant that holds the same permissions I do as a board member and can carry a request from question to finished work on my behalf.
The company's internal agent lives in its chat tool as each employee's artificial alter ego: it holds exactly the tool access and permissions of the person it mirrors, can be asked to do anything they could across the company's integrated systems, and folds a chain of cross-team requests into one message. A bug gets spotted, checked for spread, traced to its cause, fixed and routed for review in minutes rather than weeks. None of that is built here yet. What exists is the brain: CLAUDE.md orientation, the README data dictionary and known-issues list, and committed scripts, which already let a coding assistant answer most board questions from evidence. Next is letting it act for me, with my permissions.