Need smarter insights in your inbox? Join our weekly newsletters to get solely what issues to enterprise AI, knowledge, and safety leaders. Subscribe Now
In all places you look, persons are speaking about AI brokers like they’re only a immediate away from changing whole departments. The dream is seductive: Autonomous techniques that may deal with something you throw at them, no guardrails, no constraints, simply give them your AWS credentials and so they’ll remedy all of your issues. However the actuality is that’s simply not how the world works, particularly not within the enterprise, the place reliability isn’t non-compulsory.
Even when an agent is 99% correct, that’s not all the time ok. If it’s optimizing meals supply routes, which means one out of each hundred orders finally ends up on the unsuitable deal with. In a enterprise context, that type of failure fee isn’t acceptable. It’s costly, dangerous and exhausting to clarify to a buyer or regulator.
In real-world environments like finance, healthcare and operations, the AI techniques that truly ship worth don’t look something like these frontier fantasies. They aren’t improvising within the open world; they’re fixing well-defined issues with clear inputs and predictable outcomes.
If we maintain chasing open-world issues with half-ready expertise, we’ll burn time, cash and belief. But when we give attention to the issues proper in entrance of us, those with clear ROI and clear boundaries, we are able to make AI work right this moment.
This text is about chopping by way of the hype and constructing AI brokers that truly ship, run and assist.
The issue with the open world hype
The tech business loves a moonshot (and for the document, I do too). Proper now, the moonshot is open-world AI — brokers that may deal with something, adapt to new conditions, study on the fly and function with incomplete or ambiguous info. It’s the dream of common intelligence: Methods that may not solely purpose, however improvise.
What makes an issue “open world”?
Open-world issues are outlined by what we don’t know.
Extra formally, drawing from analysis defining these complicated environments, a completely open world is characterised by two core properties:
- Time and area are unbounded: An agent’s previous experiences might not apply to new, unseen eventualities.
- Duties are unbounded: They aren’t predetermined and may emerge dynamically.
In such environments, the AI operates with incomplete info; it can’t assume that what isn’t identified to be true is fake, it’s merely unknown. The AI is predicted to adapt to those unexpected modifications and novel duties because it navigates the world. This presents an extremely troublesome set of issues for present AI capabilities.
Most enterprise issues aren’t like this
In distinction, closed-world issues are ones the place the scope is understood, the foundations are clear and the system can assume it has all of the related knowledge. If one thing isn’t explicitly true, it may be handled as false. These are the sorts of issues most companies truly face on daily basis: bill matching, contract validation, fraud detection, claims processing, stock forecasting.
Function | Open world | Closed world |
Scope | Unbounded | Effectively-defined |
Information | Incomplete | Full (inside area) |
Assumptions | Unknown ≠ false | Unknown = false |
Duties | Emergent, not predefined | Mounted, repetitive |
Testability | Extraordinarily exhausting | Effectively-bounded |
These aren’t the use instances that usually make headlines, however they’re those companies truly care about fixing.
The chance of hype and inaction
Nevertheless, the hype is dangerous: By setting the bar at open-world common intelligence, we make enterprise AI really feel inaccessible. Leaders hear about brokers that may do every part, and so they freeze, as a result of they don’t know the place to start out. The issue feels too large, too imprecise, too dangerous.
It’s like making an attempt to design autonomous automobiles earlier than we’ve even constructed a working combustion engine. The dream is thrilling, however skipping the basics ensures failure.
Resolve what’s proper in entrance of you
Open-world issues make for excellent demos and even higher funding rounds. However closed-world issues are the place the true worth is right this moment. They’re solvable, testable and automatable. They usually’re sitting inside each enterprise, simply ready for the best system to deal with them.
The query isn’t whether or not AI will remedy open-world issues finally. The query is: What are you able to truly deploy proper now that makes what you are promoting quicker, smarter and extra dependable?
What enterprise brokers truly appear to be
When individuals think about AI brokers right this moment, they have an inclination to image a chat window. A person sorts a immediate, and the agent responds with a useful reply (perhaps even triggers a device or two). That’s effective for demos and shopper apps, however it’s not how enterprise AI will truly work in apply.
Within the enterprise, most helpful brokers aren’t user-initiated, they’re autonomous.
They don’t sit idly ready for a human to immediate them. They’re long-running processes that react to knowledge because it flows by way of the enterprise. They make selections, name companies and produce outputs, constantly and asynchronously, with no need to be instructed when to start out.
Think about an agent that screens new invoices. Each time an bill lands, it extracts the related fields, checks them in opposition to open buy orders, flags mismatches and both routes the bill for approval or rejection, with out anybody asking it to take action. It simply listens for the occasion (“new bill acquired”) and goes to work.
Or take into consideration buyer onboarding. An agent may look ahead to the second a brand new account is created, then kick off a cascade: confirm paperwork, run know-your-customer (KYC) checks, personalize the welcome expertise and schedule a follow-up message. The person by no means is aware of the agent exists. It simply runs. Reliably. In actual time.
That is what enterprise brokers appear to be:
- They’re event-driven: Triggered by modifications within the system, not person prompts.
- They’re autonomous: They act with out human initiation.
- They’re steady: They don’t spin up for a single process and disappear.
- They’re principally asynchronous: They work within the background, not in blocking workflows.

You don’t construct these brokers by fine-tuning a large mannequin. You construct them by wiring collectively present fashions, instruments and logic. It’s a software program engineering drawback, not a modeling one.
At their core, enterprise brokers are simply trendy microservices with intelligence. You give them entry to occasions, give them the best context and let a language mannequin drive the reasoning.
Agent = Occasion-driven microservice + context knowledge + LLM
Accomplished properly, that’s a robust architectural sample. It’s additionally a shift in mindset. Constructing brokers isn’t about chasing synthetic common intelligence (AGI). It’s about decomposing actual issues into smaller steps, then assembling specialised, dependable elements that may deal with them, identical to we’ve all the time completed in good software program techniques.
We’ve solved this sort of drawback earlier than
If this sounds acquainted, it ought to. We’ve been right here earlier than.
When monoliths couldn’t scale, we broke them into microservices. When synchronous APIs led to bottlenecks and brittle techniques, we turned to event-driven structure. These have been hard-won classes from a long time of constructing real-world techniques. They labored as a result of they introduced construction and determinism to complicated techniques.
I fear that we’re beginning to neglect that historical past and repeat the identical errors in how we construct AI.
As a result of this isn’t a brand new drawback. It’s the identical engineering problem, simply with new elements. And proper now, enterprise AI wants the identical ideas that bought us right here: clear boundaries, unfastened coupling and techniques designed to be dependable from the beginning.
AI fashions are usually not deterministic, however your techniques might be
The issues price fixing in most companies are closed-world: Issues with identified inputs, clear guidelines and measurable outcomes. However the fashions we’re utilizing, particularly LLMs, are inherently non-deterministic. They’re probabilistic by design. The identical enter can yield totally different outputs relying on context, sampling or temperature.
That’s effective while you’re answering a immediate. However while you’re working a enterprise course of? That unpredictability is a legal responsibility.
So if you wish to construct production-grade AI techniques, your job is easy: Wrap non-deterministic fashions in deterministic infrastructure.
Construct determinism across the mannequin
- If you understand a selected device ought to be used for a process, don’t let the mannequin resolve, simply name the device.
- In case your workflow might be outlined statically, don’t depend on dynamic decision-making, use a deterministic name graph.
- If the inputs and outputs are predictable, don’t introduce ambiguity by overcomplicating the agent logic.
Too many groups are reinventing runtime orchestration with each agent, letting the LLM resolve what to do subsequent, even when the steps are identified forward of time. You’re simply making your life more durable.
The place event-driven multi-agent techniques shine
Occasion-driven multi-agent techniques break the issue into smaller steps. While you assign every one to a purpose-built agent and set off them with structured occasions, you find yourself with a loosely coupled, totally traceable system that works the best way enterprise techniques are speculated to work: With reliability, accountability and clear management.
And since it’s event-driven:
- Brokers don’t must learn about one another. They only reply to occasions.
- Work can occur in parallel, rushing up complicated flows.
- Failures are remoted and recoverable through occasion logs or retries.
- You possibly can observe, debug and take a look at every element in isolation.
Don’t chase magic
Closed-world issues don’t require magic. They want stable engineering. And which means combining the flexibleness of LLMs with the construction of excellent software program engineering. If one thing might be made deterministic, make it deterministic. Save the mannequin for the elements that truly require judgment.
That’s the way you construct brokers that don’t simply look good in demos however truly run, scale and ship in manufacturing.
Why testing is a lot more durable in an open world
Probably the most neglected challenges in constructing brokers is testing, however it’s completely important for the enterprise.
In an open-world context, it’s practically unattainable to do properly. The issue area is unbounded so the inputs might be something, the specified outputs are sometimes ambiguous and even the factors for fulfillment may shift relying on context.
How do you write a take a look at suite for a system that may be requested to do virtually something? You possibly can’t.
That’s why open-world brokers are so exhausting to validate in apply. You possibly can measure remoted behaviors or benchmark slender duties, however you may’t belief the system end-to-end except you’ve one way or the other seen it carry out throughout a combinatorially giant area of conditions, which nobody has.
In distinction, closed-world issues make testing tractable. The inputs are constrained. The anticipated outputs are definable. You possibly can write assertions. You possibly can simulate edge instances. You possibly can know what “appropriate” seems to be like.
And when you go one step additional, decomposing your agent’s logic into smaller, well-scoped elements utilizing an event-driven structure, it will get much more tractable. Every agent within the system has a slender duty. Its habits might be examined independently, its inputs and outputs mocked or replayed, and its efficiency evaluated in isolation.
When the system is modular, and the scope of every module is closed-world, you may construct take a look at units that truly offer you confidence.
That is the muse for belief in manufacturing AI.
Constructing the best basis
The way forward for AI within the enterprise doesn’t begin with AGI. It begins with automation that works. Meaning specializing in closed-world issues which might be structured, bounded and wealthy with alternative for actual impression.
You don’t want an agent that may do every part. You want a system that may reliably do one thing:
- A declare routed appropriately.
- A doc parsed precisely.
- A buyer adopted up with on time.
These wins add up. They scale back prices, unlock time and construct belief in AI as a reliable a part of the stack.
And getting there doesn’t require breakthroughs in immediate engineering or betting on the following mannequin to magically generalize. It requires doing what good engineers have all the time completed: Breaking issues down, constructing composable techniques and wiring elements collectively in methods which might be testable and observable.
Occasion-driven multi-agent techniques aren’t a silver bullet, they’re only a sensible structure for working with imperfect instruments in a structured manner. They allow you to isolate the place intelligence is required, include the place it’s not and construct techniques that behave predictably even when particular person elements don’t.
This isn’t about chasing the frontier. It’s about making use of primary software program engineering to a brand new class of issues.
Sean Falconer is Confluent’s AI entrepreneur in residence.