AI agents, built around the constraint
Every industry has one rule that decides what software is allowed to do on its own. In Dubai real estate it is a permit. In UAE ecommerce it is cash on delivery. In logistics it is that the worst failure never announces itself. These pages start from that rule rather than from a feature list, because it is the rule that determines the design.
Which industry are you in?
Four industry pages so far. Each names the constraint it is built on, the systems the agent touches, what breaks, and what the work costs in AED.
Real estate
A permission problem. A listing cannot reach a portal without a valid Trakheesi advertisement permit number, so the design question is not what the agent can do but what it is forbidden to do without a person. Portal enquiries, listing consistency across Bayut and Property Finder, and Ejari renewal dates.
Ecommerce
A race and a reconciliation problem. Cash on delivery separates the moment the parcel is handed over from the moment the money arrives, so orders, courier remittances and refunds have to be matched before anyone acts on them. Confirming an order before dispatch, refunds held until the courier remits, and stock kept honest across channels.
Logistics
An absence-of-event problem. A shipment that stalls emits nothing at all: no webhook, no status change, no error. Catching it needs a clock and a threshold set per lane, not a trigger. Shipment status, proof of delivery, customs paperwork, and the shipments that went quiet.
Healthcare
A permission problem with a regulator attached. The agent handles scheduling, insurance eligibility, intake and follow-up, and nothing clinical. Health data stays where the DHA rules require it to stay, which shapes where the whole thing can run.
What if your industry is not here?
These four are the ones written up so far, and there is no longer list waiting behind them. We started here because each of the three has a constraint specific enough to explain in public without inventing anything.
The method does not change with the industry. Find the step that is irreversible or regulated, and make that the one the agent hands to a person. Find the failure that produces no signal, and give it a clock. Find the two systems that disagree, and decide which one is the record of truth before writing a line of code. That work is the same whether the systems are property portals, a Shopify store or a transport management system.
If you want the service view instead of the industry view, all services lists what we build, the use cases page starts from the problem, and how we work covers scope, fixed price and what happens after launch.
Tell us the rule your business runs on
Describe the workflow and the step nobody is allowed to get wrong. We will tell you which part an agent should handle, which part it should hand back, and what the build would cost.
hello@telora.dev