From answers to jobs
A chat assistant answers. You ask something, it replies, and any action that follows is yours. That is genuinely useful, and it is where most businesses have started.
An agentic system is one that takes a goal, works out the steps, carries them out across several tools, and comes back with the finished thing. The unit of work changes from a question to a job.
What that requires in practice
Three capabilities have to be present at once. It has to break a stated goal into work that can actually be done. It has to reach the places where your information lives. And it has to know when to stop and ask you.
The third is the one that is usually missing, and the one that decides whether the first two are safe to use.
A worked shape
Take "find where we are losing margin on installs". A single answer to that is a guess. The job version is: gather the install jobs and their quoted values, match actual labour and parts, compare line by line, group the pattern, then propose the quote changes — and stop before changing a live price list.
Same sentence in. Very different thing out.
Where it should stop
Preparation should be generous; action should be narrow. Drafting, gathering, comparing and summarising can run freely because they are reversible. Sending, paying, publishing and committing should not, because they are not.
When someone describes an agentic system to you, the sharpest question is not what it can do. It is what it will not do without you.
Written by the 8ORA team. We publish no customer names, figures or certifications we cannot evidence.