What exactly are Bonsai AI Workers?
An AI Worker is a piece of software with a single task. It reads an input, such as a PDF, an email, or a file, extracts the relevant fields, compares them with what is in your system, and prepares a proposal or notification for the employee who approves it. No broad platform, no configuration screen full of options. A Worker has one task, one input, and one output. That makes it fast to build, easy to audit, and straightforward to replace when circumstances change. It works alongside your existing ERP, TMS, or WMS without needing access to your full data model.
What problem does an AI Worker concretely solve?
The pattern we encounter time and again: every morning, an employee opens a stack of documents, re-keys data into the system, and sends a confirmation back. That work takes time but requires almost no judgment. An AI Worker reads those documents automatically, parses the fields, and prepares a draft entry. The employee reviews and approves, but their attention goes to the exceptions, not the routine. The same principle applies to customs document checks, matching invoices to purchase orders, assigning transport jobs based on fixed rules, or drafting a first Quote. Every time, the same idea: repeatable work that requires no real human decision but produces human errors when it stays manual.
Where do teams get stuck during implementation?
The biggest obstacle is not the technology but the task definition. Teams working with AI Workers for the first time tend to broaden the scope: can we also include X, and Y? Understandable, but it makes a Worker unmanageable. A Worker performs well when the task is sharp: one input, one output, one decision point. A second common problem is source data quality. If the documents you process are inconsistent in format or completeness, the Worker will also be inconsistent. That is not solved with better AI but with agreements with suppliers or customers about document formats. A third point: integrating with the existing system takes more time than expected, especially when the package's API is limited or absent.
When are AI Workers the wrong choice?
If your core system is itself the problem, a Worker will not solve it. A Worker is a layer on top of an existing system. If that system is slow, error-prone, or fundamentally unsuited to your current operation, you are applying a fix to a problem that runs deeper. In that case, it is more honest to consider whether you should rebuild the core system from scratch, purpose-built, with AI built in. That is what we call the Bonsai AI Digital Twin. Beyond that, Workers are not the right choice when the task you want to automate is substantially different every time and therefore requires judgment that cannot be captured in rules or recognisable patterns. AI is good at recognising and applying patterns. It cannot assess situations that fall outside those patterns unless it has been explicitly trained to do so with sufficient examples.
How do Bonsai AI Workers relate to Dottle and Quote?
Dottle and Quote are ready-made Workers for two specific tasks: document processing and quote automation. They are faster to implement because the core is already built and you configure them for your documents or pricing logic. We build custom AI Workers when the task is too specific for a standard product or when the integration with your system requires more tailoring. The choice is practical: start with a product if it fits, choose custom when the context is too different. We help you make that choice, including when the answer is that nothing needs to be built.