What Hawi is
Named agents that work orders, stock and customer messages across the systems a shop already runs, on a board a person can read.
Hawi is an operations surface for small commerce teams. You describe the jobs you repeat — chasing a late supplier, answering “where is my order”, watching stock cover on the lines that actually sell — and you give each one to a named agent. The agents read from the systems you already run, write back to them, and put what they did on a board you can read without asking anyone.
The word that does the most work in that paragraph is “named”. Hawi is not one assistant with a text box. It is several agents with separate briefs, separate tool access and separate spending ceilings, which hand work between each other and to people. Atlas takes orders, stock and suppliers. Mira takes the inbox. Vela takes calls. Those are defaults, not fixtures; you rename and rebrief all of them.
Product boundaries
- Customer messages require a channel you connect and an agent you brief. Hawi has no storefront chat widget.
- Your shop platform, accounting system and helpdesk remain the source systems. Hawi reads and writes across them.
- A new workspace starts with no connections, no agents and a per-agent spending ceiling of zero. You enable each capability from there.
- Agents use written briefs, tool lists and limits. There is no canvas of connected workflow boxes.
Who it fits
Dropshippers, marketplace sellers, vintage resellers, retailers and wholesalers — teams between roughly two and forty people where one person is doing the operational work of three. It also serves larger companies that need several teams running agents against shared connections with reporting that suits a role, which is why workspaces, roles and per-workspace connection selection exist at all.
The five stages
The product and most of this documentation follow five stages. A single order can move through all five over a week.
- Intake
- Mail, marketplace messages and stock alerts become board items carrying a source, a status and an owner.
- Watch
- Stock cover is recalculated from sales, listings are compared with the stock sheet, and supplier follow-ups are scheduled.
- Act
- A named agent with a defined brief, a model, a tool list and a ceiling does the work and hands off what is not its job.
- Approve
- The actions you chose to route to a person wait in a queue showing the current record beside the proposed change.
- Monitor
- A daily brief, and a trace of any result back through its inputs, tool calls, handoffs and decisions.