Who it fits, and who it does not
The shape of operation this suits, and four where something else is the better tool.
Hawi is built for an operation where one person is doing the operational work of three: orders arriving from more than one place, stock that has to be watched rather than counted once a quarter, and a customer inbox nobody has time to keep on top of. Roughly two to forty people, though the number matters less than the shape.
The shape it fits
- Work arrives continuously from systems you already run, rather than being entered by hand into one place.
- The same handful of exceptions repeat every week — late supplier, wrong address, damaged item, oversell.
- Somebody could describe each of those exceptions to a new starter in two sentences.
- There is a person who would read a morning summary and act on it.
Where something else is the better tool
- A single high-value negotiation
- One deal a month, each one different, each one worth arguing about. Nothing here beats a person with a phone, and the setup cost is not recovered.
- Work with no external system
- If the orders live in a spreadsheet on one laptop and nothing else, there is nothing to connect. Get the data somewhere addressable first; that is a bigger win than any agent.
- A compliance process that must be identical every time
- A deterministic workflow tool is the right shape for something where the same input must always produce byte-identical output. Agents are for judgement against messy input.
- Customer-facing chat on your storefront
- There is no shopper-facing widget. Agents work the inbox and the board behind it; they are not a front-of-house chatbot and adding one is a different product.