About
Built by operators, in Arizona
Handbook is built by people who run the kind of business it is built for, which is most of the explanation for why it works the way it does.
Why it exists
Small businesses do not usually lose to competitors. They lose to drift: the standard that slipped, the training that never quite happened, the count nobody did. None of it is dramatic, and all of it compounds.
The tools that promise to fix this tend to solve one slice and add another login. So the recipe lives in one place, the checklist in another, and the inventory in a spreadsheet, and none of them know about each other. Handbook exists because the connections between those things are where the value actually is.
Who builds it
The Handbook Company is owned and developed by Beanchain Coffee LLC, in Arizona.
We run a coffee business. Handbook started as the system we needed for our own team, which is why it is opinionated about things like counting inventory in the order you walk the shelf, and why the AI assistant will not write to your data without asking.
How we decide what to build
The product direction is practical rather than visionary. If a feature does not make an expectation easier to find, easier to teach, or easier to keep current, it tends not to get built.
That is also why the public pages here use plain language about training, SOPs, checklists, recipes, inventory, and suppliers, instead of describing a category. It is easier to tell whether the product fits when the description is literal.
Getting in touch
Email [email protected] and a person will read it. Feature requests, bug reports, and questions about whether it fits your operation are all welcome.
See whether it fits
The trial is free and the demo is a conversation, not a pitch deck.