One workflow, on purpose
The pilot is one path through the business: a lead comes in, a ticket arrives, a draft is requested, or a file needs sorting. We map that path, decide what the model may do, and decide what a person still approves.
A pilot that tries to automate the whole company in a month does not finish. The scope names the trigger, the inputs, the output, and the person who checks the result.
What gets built
The published capabilities are LLM workflows, integrations, triage, and monitoring. An integration might be the inbox, the form on the site, or a sheet the team already uses. Monitoring is there so you can see when the workflow fails, not only when it was demonstrated.
We do not train a private model as part of the pilot. The pilot uses Claude or OpenAI on the workflow we scoped. If the data cannot leave your account, that constraint goes in the brief before we start.
Where it helps a UAE company
The useful cases are ordinary: a clinic sorting appointment requests, a brokerage sending listing enquiries to the right person, a shop tagging the questions that need a human. The pilot is the same shape in each case. The words and the system change.
KAN can also build the page or the product the workflow sits on. A form that captures the right fields makes the automation smaller. That site work is a Launch Site or a Web/App Build, quoted separately.
After the pilot
If the workflow is worth keeping, we talk about a retainer for monitoring and the next workflow. If it is not, you still have the map of the process and a working version of the one we built.
We will not attach a savings figure to a pilot that has not run. The brief can name the time the task takes today. The report after the pilot can compare that with what actually happened.