Video wird geladen...
Video konnte nicht geladen werden
This is how we build an agentic workflow. We put each step into 4 buckets, and I was surprised how few were agentic. - Delete. After AI, this step is not necessary. - Plain code. The step follows rules and needs no judgment, for example a simple API call.... show more
11,969 Aufrufe • vor 5 Tagen •via X (Twitter)
4 Kommentare

catmanvor 5 Tagen
The quote example makes the boundary concrete: let the agent judge customer value and resource allocation, but keep approval, negotiation, signing, and payment submission with people.

TanyaZvor 5 Tagen
Same for me. I build the steps with plain rules first and add AI only where rules can't do the job. The data comes together in one place, and I still make the call.

MoonHuangvor 5 Tagen
I'd split the quote itself: plain code for fixed prices and totals, an agent for choosing the right package, a person for approving an exception. Does that match how you built it?

shobhanaivor 4 Tagen
Reserve AI agents strictly for judgment steps; handle rules with plain code and high-stakes actions with humans.
