Al Maktoum Airport's Automation Push: A Practical Guide for Insurance Companies in UAE

Direct answer: Al Maktoum Airport is building what is being reported as the world's largest automated people-mover system, and that single infrastructure decision creates a wave of new insurable risk — construction, cyber-physical, liability, and travel-related — that UAE insurance companies are not yet fully set up to underwrite or process claims against. The practical response isn't waiting for the airport to open; it's building modular underwriting and claims software now so your systems can price and handle these exposures as they emerge, rather than retrofitting legacy policy admin platforms under pressure later.

According to UAE infrastructure reporting from August 2026, Al Maktoum International Airport's ongoing redevelopment includes an automated people-mover system that is being described as the largest of its kind anywhere in the world. Automated people-movers are driverless transit systems that shuttle passengers between terminals and concourses without a human operator — a category of infrastructure that major hub airports increasingly rely on once terminal footprints grow too large for walking connections within normal transfer times. A precise capacity figure, completion date, or cost estimate for this specific system isn't publicly available at the time of writing, so this piece reasons from the general pattern of what large-scale automated transit builds mean for the industries around them, rather than inventing numbers that haven't been reported. For UAE insurance companies, that pattern matters more than any single statistic: a signature automation project of this scale reshapes what "insurable risk" looks like across construction, aviation, cyber, and travel lines for years around it, and the carriers that build the technical capacity to underwrite it well end up setting the pricing and product standard the rest of the market follows.

What Al Maktoum's Automation Push Actually Is

Strip away the "world's largest" framing and the underlying decision is a familiar one in airport engineering: when a terminal complex gets physically too large for passengers to walk between gates within a normal connection window, the fix is to automate movement itself rather than ask people to walk faster. Automated people-movers (APMs) are already standard at several of the world's biggest hubs — driverless, rail-guided or rubber-tired vehicles running on a fixed loop, controlled by centralized software rather than a human driver, typically integrated with the airport's broader operational technology so that scheduling, safety interlocks, and maintenance alerts all run through connected systems rather than manual oversight.

What UAE infrastructure reporting from August 2026 confirms is that Al Maktoum is building this kind of system at a scale being called the largest deployment of its type globally. That claim alone tells you two things worth acting on even without further detail: first, the system will be genuinely complex from an engineering and software standpoint, meaning more vendors, more integration points, and more places something can go wrong during construction and commissioning. Second, a project positioned as a world-first draws attention — from regulators, from insurers looking to write reference business, and from every contractor and systems integrator in the region who wants their name attached to it. That attention is exactly why UAE insurers should be thinking about this now rather than after the ribbon-cutting.

It's worth being precise about what isn't known yet, too. Public reporting at this stage confirms the scale claim and the fact of the build, but doesn't yet give a firm passenger-capacity figure, a completion date, or a disclosed budget for the people-mover specifically — and this piece deliberately doesn't guess at any of those. What can be reasoned honestly from the general pattern is that projects of this description, once operational, tend to run for decades with continuous maintenance, periodic hardware refreshes, and an expanding software layer as operators add monitoring and automation on top of the original build. That multi-decade operating life is itself relevant to insurers, because it means the risk this project creates isn't a one-time construction-phase event — it's a long-running exposure that will need policies renewed, re-priced, and re-underwritten for as long as the system runs.

Why People-Movers Are Becoming Central to How Big Airports Get Designed

The broader trend behind this single project is that airport automation is no longer a convenience feature bolted onto a terminal — it's becoming part of the core design logic for any hub competing at global scale. Once an airport commits to automated transit as core infrastructure, that decision cascades into procurement (specialized hardware imported and installed under tight tolerances), workforce planning (fewer transit-operations staff, more systems-maintenance staff), and risk management (a transit system that used to be "a bus and a driver" is now a software-controlled asset that behaves more like an industrial control system than a shuttle service). None of that is unique to Dubai — it's the same shift airports from Singapore to Denver have made — but doing it at a record scale means the risk profile scales with it.

Why This Matters Specifically to Insurance Companies in the UAE

A project like this generates insurable exposure in layers, and most of those layers touch insurers who will never write a policy for the airport operator directly. During construction, the system needs contractor's all-risk and engineering cover for the specialized rail, vehicle, and control hardware being imported and installed — exposure that sits with UAE-based marine and cargo insurers moving the equipment, and with engineering-risk underwriters covering the installation itself. During commissioning and testing, product liability questions start to matter: if a driverless vehicle malfunctions during test runs, is that the manufacturer's exposure, the systems integrator's, or the airport operator's, and which UAE-licensed carrier is holding that liability line? Once the system is operational, the exposure shifts again toward public liability, business interruption if a fault halts terminal transit during peak travel periods, and — increasingly — cyber-physical risk, because a driverless mass-transit system is fundamentally software and sensors wrapped around moving hardware, connected to the same operational technology network as the rest of the airport.

There's also a liability question sitting underneath all of this that current policy language doesn't answer cleanly: if an automated vehicle malfunctions and causes an injury, is that the airport operator's exposure, the hardware manufacturer's, or the software vendor's that wrote the control logic making routing and safety decisions? Traditional liability wording was written assuming a human driver or operator somewhere in the chain of responsibility; a fully automated system removes that person and spreads the decision-making across a manufacturer, an integrator, and a software team, none of whom fit neatly into a single existing policy category. UAE insurers writing liability cover anywhere near this project need to work through that allocation question before an incident forces the answer, not after.

Dubai's insurance market is structured around exactly this kind of hub-economy risk: aviation, trade, marine cargo, and reinsurance capacity are concentrated here precisely because so much of the region's commercial activity flows through its airports and ports. A reference project of this visibility becomes something other GCC infrastructure buyers point to when shopping for cover on their own automation builds — a new terminal in Riyadh, a port automation project in Abu Dhabi, a rail system elsewhere in the Gulf. Underwriting teams that can speak fluently and specifically about automated-transit risk today build credibility that extends well past this one airport.

New Exposure Classes Underwriting Teams Haven't Fully Priced Yet

The categories worth naming specifically are ones that don't map cleanly onto existing policy wordings. Autonomous-system liability — who is responsible when a control algorithm, not a human, makes the decision that leads to an incident — sits awkwardly between product liability, professional indemnity for the software vendor, and general liability for the operator. Cyber-physical convergence risk is another: a breach of the control network for a people-mover isn't just a data-privacy event, it's potentially a safety event, which changes how it should be priced and how claims should be investigated. Insurers that treat these as edge cases within existing aviation or engineering lines will underprice them; insurers that build dedicated intake and pricing logic for them will have a real product advantage as more of this infrastructure gets built across the region.

What Changes in Practice for Insurers' Websites, Apps, and Internal Systems

Once the underlying risk categories diversify the way described above, a single generic quote engine stops being adequate. Underwriting workflows need to branch by risk type — construction and engineering risk, cyber-physical risk, general aviation liability, product liability for systems vendors — each with its own data fields, document requirements, and approval routing. A policy administration system built around one-size-fits-all commercial lines forms will either force underwriters back into spreadsheets and email for anything unusual, or worse, push them to approve applications without collecting the information they actually need to price the exposure correctly.

Claims intake needs the same rethink. An incident involving an automated transit system generates evidence types that a standard claims portal — built around a written description, a couple of photos, and a police report — simply isn't set up to ingest: sensor and telemetry logs, maintenance and inspection records, video footage from onboard or platform cameras, and system-fault codes that only make sense with vendor documentation alongside them. Claims teams that can't accept and organize that evidence digitally end up doing it over email threads and shared drives, which slows down every claim tied to this category of risk and makes fraud or liability disputes harder to resolve cleanly.

From Templated Quote Forms to Modular Underwriting Software

The practical fix isn't a bigger form — it's underwriting software built in modules, where a new risk category can be added as its own intake flow, scoring logic, and document set without rebuilding the whole platform. That's a different kind of build than most insurers have historically commissioned, and it's the kind of work that off-the-shelf policy admin platforms weren't designed to flex around, since their data models assume a fixed, known set of risk categories rather than ones still being defined as new infrastructure comes online. This is precisely where Custom Software Development earns its cost over a templated platform: it lets an insurer's underwriting logic evolve at the same pace as the risk landscape it's pricing, instead of waiting for a vendor's next release cycle.

There's a customer-facing side to this too. As Al Maktoum becomes a larger part of how people move through and around Dubai, product teams selling travel-related cover have an opening to sell it where the actual booking decision happens, rather than as a separate add-on days later. That's the same integration logic covered in our piece on Travel Booking App Development — insurance quoting embedded directly inside a booking flow converts at a meaningfully different rate than sending a customer to a separate insurance site after they've already committed to a flight. And when an infrastructure story like this draws new attention to your brand — a broker researching who covers automation risk, a contractor comparing carriers before a bid — your public quote pages need to hold up under that scrutiny. A slow-loading quote form on mobile is a lost lead regardless of how good your underwriting is behind it, which is exactly the kind of problem addressed in our guide on how to pass Core Web Vitals in WordPress & Shopify.

Managing the New Risk Surface: Data, Cyber, and Shadow AI

Automated transit infrastructure is, underneath the branding, an operational technology (OT) network merged with conventional IT — every sensor, control loop, and scheduling system is a potential attack surface, and airport operators are increasingly layering AI-assisted anomaly detection on top to catch faults before they become incidents. Underwriting that kind of exposure well requires an insurer's own data pipeline to handle telemetry-style inputs responsibly: audit trails on who accessed what, clear data retention rules, and access governance that doesn't assume every underwriter needs to see every raw sensor feed from every insured asset.

That governance discipline matters just as much inside the insurer's own walls. Underwriting and claims teams evaluating cyber risk for airport-linked automation exposures are, at the same time, running their own stack of SaaS tools for triage, fraud detection, and document processing — and unmanaged AI tool adoption inside that stack is precisely the blind spot described in our piece on Shadow AI in 2026. An insurer that can't account for which AI-powered tools its own underwriters are feeding sensitive client telemetry into has a governance gap that undercuts its credibility when it's simultaneously trying to assess a client's cyber-physical risk posture. Getting your own house in order isn't a side project here — it's part of being able to underwrite this category of risk with a straight face.

Building the Underwriting and Claims Stack: What to Actually Do

The realistic path forward has five parts. First, map the new exposure classes relevant to your book — construction and engineering risk tied to automation hardware, cyber-physical risk for operational technology, autonomous-system liability, and travel products tied to airport growth — so you know which ones deserve dedicated intake logic versus which can stay inside existing lines for now. Second, build or extend underwriting software as modular components rather than patching a legacy form, so each new risk category can be added without a platform rebuild. Third, expand claims intake to accept telemetry, video, and maintenance-record evidence types natively rather than through email attachments. Fourth, invest in an integration layer that can pull data from external sources — a contractor's monitoring system, a systems integrator's fault logs — instead of relying on annual paper renewals to catch what's changed. Fifth, put security and governance controls around all of it from day one, given how sensitive OT-adjacent data tends to be.

What This Kind of Work Typically Falls Under

Most insurers don't need to build all five pieces at once, and the right starting point depends on where the gap is most urgent. The table below reflects how this kind of work typically maps to project scope, not a fixed quote — actual pricing depends on integration complexity and data volume.

Tier	Typical scope for an insurer	Starting at
Essential	Refreshed public quote page or landing experience built for speed and mobile conversion	$1,000
Growth	A modular underwriting intake portal or expanded claims document handling for one new risk category	$2,000
Enterprise	Full custom underwriting engine with external data integration, multi-line risk branching, and governance controls	$4,000+

An insurer that starts at the Essential tier to fix a slow-converting quote page isn't locked out of the Enterprise-level underwriting rebuild later — the two are separable pieces of the same direction of travel, and starting small is a reasonable way to build internal confidence before committing to the bigger integration work.

Key Takeaways

• Al Maktoum's automated people-mover, reported as the world's largest of its kind in UAE infrastructure coverage from August 2026, creates new insurable risk across construction, liability, cyber, and travel lines — even for insurers who never write the airport operator's own policy.
• Generic policy admin platforms and quote forms aren't built to flex around new, still-forming risk categories like autonomous-system liability or cyber-physical convergence risk; modular custom software is the more durable fix.
• Claims intake needs to evolve to accept telemetry, video, and maintenance-record evidence natively, not through email threads, as more automated infrastructure enters the region.
• Your own governance around AI-powered underwriting and claims tools matters as much as the client risk you're assessing — shadow AI inside your own stack undercuts your credibility on cyber-physical risk.
• Embedding travel insurance quoting directly into booking flows, and making sure public quote pages perform well under new attention, are the customer-facing side of the same trend.
• Start with the highest-urgency gap — a quote page, a claims portal, or a full underwriting engine — rather than waiting for the airport to open before modernizing.

Automation projects at this scale don't wait for insurers to catch up, and the carriers that treat this as a technology decision now will be pricing these risks more accurately than the ones that wait. If you want help figuring out where your underwriting or claims systems need to change first, book a meeting with our team.

Frequently Asked Questions

What is an automated people-mover system, in plain terms?

An automated people-mover is a driverless transit system — usually a rail-guided or rubber-tired vehicle running on a fixed loop — that shuttles passengers between terminals or concourses without a human operator. It's controlled by centralized software that manages scheduling, safety interlocks, and routing, which is what makes it fundamentally a software-and-sensor system rather than a simple shuttle bus.

Why is Al Maktoum Airport's automated people-mover being described as the world's largest?

UAE infrastructure reporting from August 2026 describes the system as the largest deployment of its kind globally, though a precise capacity figure or technical benchmark behind that description isn't publicly available yet. What matters practically is the scale claim itself, which signals a genuinely complex, high-visibility engineering project with more vendors and integration points than a typical airport transit build.

Is Al Maktoum Airport replacing Dubai International Airport?

Al Maktoum is part of Dubai's longer-term aviation expansion, and the automated people-mover build is one piece of its ongoing redevelopment. Specific timelines for any transition of primary hub status aren't part of the reported trend this piece is grounded in, so it's better to treat the automation build as a standalone signal rather than assume a firm handover date.

Why should a UAE insurance company care about an airport construction project at all?

Because the risk generated by a project like this doesn't stay contained to the airport operator — it spreads across contractors, systems integrators, hardware importers, and eventually travel and consumer products tied to the airport's growth. Any UAE insurer writing construction, marine cargo, engineering, aviation, or cyber lines is likely to touch some piece of that exposure whether or not they ever underwrite the operator directly.

What types of insurance are typically involved in a large automated-infrastructure project?

Contractor's all-risk and engineering cover during construction, product liability during commissioning and testing, and public liability, business interruption, and cyber-physical cover once the system is operational. Marine and cargo cover also applies to the specialized hardware being imported and installed.

Does this change aviation liability insurance specifically?

It adds a layer that traditional aviation liability wording doesn't cleanly address: liability arising from a software-controlled transit system rather than an aircraft or a human-operated vehicle. Underwriters working in this space need to think through whether existing aviation liability language actually covers an automated ground-transit incident or leaves a gap.

Who is liable if an automated transit system malfunctions and causes injury?

That depends on where the fault originates, and current liability wording often doesn't answer it cleanly — it could sit with the airport operator for maintenance and oversight, the hardware manufacturer for a mechanical failure, or the software vendor if a control-system decision caused the incident. UAE insurers writing liability cover touching this kind of infrastructure need to work through that allocation question in their policy language now, rather than leaving it to be litigated after a real incident.

What is cyber-physical risk, and why does automation increase it?

Cyber-physical risk is the exposure created when a breach or fault in a digital control system causes a real-world physical consequence, not just a data loss. Automated people-movers increase this risk because the same network that schedules and routes the vehicles also manages safety interlocks, meaning a cybersecurity failure can become a physical safety incident rather than staying contained to data.

How does this affect cargo and marine insurers in the UAE?

Specialized rail, vehicle, and control-system hardware for a project of this scale has to be imported and installed under tight engineering tolerances, which is squarely marine cargo and engineering-risk territory. Any delay, damage in transit, or installation failure involving that hardware is a claims scenario marine and engineering underwriters should be prepared to price.

What is business interruption insurance, and why does it matter here?

Business interruption cover compensates for lost income when an insured event halts normal operations. For an automated people-mover, a fault that stops terminal transit during peak travel periods could trigger business interruption claims from the airport operator or affiliated commercial tenants, which is a new scenario for underwriters used to pricing simpler transit disruptions.

Will insurers need to underwrite the airport operator directly to be affected by this trend?

No. Contractors, systems integrators, hardware suppliers, logistics vendors, and even travel companies building products around the airport's growth all generate insurable exposure that UAE carriers may end up covering, regardless of who holds the airport operator's own policy.

How does this project affect UAE-based reinsurers?

A signature project of this visibility and complexity is exactly the kind of risk that primary insurers look to reinsurance markets to help absorb, particularly for cyber-physical and engineering exposures that are still being defined. UAE-based reinsurance capacity is likely to see more inquiries tied to automation risk as similar projects follow across the Gulf.

What is "engineering all-risk" insurance and when is it used?

Engineering all-risk cover protects against physical loss or damage during the construction, installation, and testing of complex infrastructure like an automated transit system. It's typically the primary policy type covering the people-mover build itself before the system becomes operational.

How should underwriting teams start pricing new automation-related exposure classes?

Start by mapping which specific risk categories — autonomous-system liability, cyber-physical convergence, product liability for software vendors — actually appear in your current book, then build dedicated intake questions and scoring logic for each rather than folding them into existing lines. Treating them as edge cases within old wordings is the most common way insurers underprice this kind of risk.

What kind of data does an insurer need to underwrite automated transit risk properly?

Beyond standard engineering and construction documentation, underwriters increasingly need access to system telemetry, maintenance schedules, and cybersecurity posture information for the control software involved. Building a data pipeline that can ingest and organize that information is a technical project, not just a policy-wording update.

Can existing policy administration software handle these new risk categories?

Most off-the-shelf policy admin platforms assume a fixed, known set of risk categories and struggle to flex around ones that are still being defined, like autonomous-system liability. That's usually the point where insurers start looking at custom or modular software rather than trying to force new risk types into old forms.

What does "modular underwriting software" mean?

It means building the underwriting platform out of separate components — one per risk category — so a new risk type can get its own intake flow, data fields, and scoring logic added without rebuilding the entire system. This is the opposite of a single monolithic quote form that tries to cover every scenario with the same fields.

Why would an insurer need custom software instead of an off-the-shelf platform?

Off-the-shelf platforms are built around risk categories that already exist and are well understood; a project like Al Maktoum's automation build is generating risk categories that are still being defined in real time. Custom software lets underwriting logic evolve at the same pace as the risk landscape instead of waiting on a vendor's release schedule.

How long does it typically take to build a custom underwriting portal?

Timelines depend heavily on scope — a single new risk-category intake flow is a much smaller build than a full multi-line underwriting engine with external data integration. Scoping the highest-priority gap first, rather than trying to build everything at once, is the more realistic way to get something usable in a reasonable timeframe.

What does Scult's Custom Software Development service actually include?

It covers building underwriting workflows, claims intake systems, and data integration layers tailored to an insurer's actual risk categories and internal processes, rather than adapting a generic template. Details and scope options are outlined on the Custom Software Development page.

How much does a project like this typically cost?

It depends on scope: a focused improvement like a faster public quote page typically starts around $1,000, a modular underwriting or claims intake build for one new risk category typically starts around $2,000, and a full custom underwriting engine with external data integration and governance controls typically starts at $4,000 and up.

What's the difference between the Essential, Growth, and Enterprise tiers?

Essential covers a focused improvement like a public-facing quote page rebuild. Growth covers a modular underwriting or claims intake addition for a specific new risk category. Enterprise covers a full custom underwriting engine with multi-line risk branching, external data integration, and governance controls built in from the start.

Can an insurer start small and scale up the software later?

Yes — starting with an Essential-tier improvement like a quote page doesn't lock you out of a larger underwriting rebuild later. Many insurers use a smaller first project to build internal confidence in a technology partner before committing to a bigger integration effort.

What new evidence types show up in claims tied to automated systems?

Sensor and telemetry logs, system-fault codes, maintenance and inspection records, and platform or onboard video footage are all evidence types that come up in incidents involving automated transit systems. Standard claims portals built around written descriptions and photos generally aren't set up to ingest or organize these natively.

How should a claims portal be redesigned to accept telemetry or sensor data?

It needs structured upload fields for machine-generated log formats, not just free-text descriptions and image attachments, along with a way to tag and organize that evidence against the specific incident and vendor documentation it relates to. This is a data-architecture decision as much as a UI one.

What is Shadow AI, and why does it matter to an insurance company's own operations?

Shadow AI refers to employees using AI-powered tools that haven't been vetted or approved by IT and security teams, often to handle sensitive work faster. For an insurer, that risk is described in more depth in our piece on Shadow AI in 2026, and it matters because underwriting and claims staff may be feeding sensitive client data into ungoverned tools without anyone tracking it.

How does Shadow AI relate to underwriting cyber risk for a client like an airport project?

An insurer trying to assess a client's cyber-physical risk posture has less credibility if its own underwriting team is running unmanaged AI tools against sensitive telemetry data. Governance has to be consistent on both sides of the underwriting relationship for the risk assessment to hold up.

What security controls should an insurer put around a new underwriting data pipeline?

At minimum, audit trails on who accessed which data, clear retention policies for sensitive telemetry or OT-adjacent information, and access governance that limits raw sensor-level data to people who actually need it for pricing decisions. These controls should be built into the software from the start, not added after a data-handling issue occurs.

Does data protection law apply to telemetry data from insured infrastructure?

Telemetry and operational data from insured infrastructure can carry sensitivity depending on what it reveals about safety systems, personnel, or operations, even if it isn't classic personal data. Insurers should treat it with the same governance discipline as any other sensitive commercial data rather than assuming it falls outside data protection considerations.

Why does website performance (Core Web Vitals) matter for an insurance company?

When an infrastructure story like Al Maktoum's automation build draws new attention to your brand — a broker or contractor researching who covers this kind of risk — a slow-loading quote page loses that lead regardless of how strong your underwriting is behind it. Our guide on passing Core Web Vitals in WordPress & Shopify covers the practical fixes.

How does slow quote-page performance actually cost an insurer business?

Visitors comparing carriers typically have several tabs open and little patience for a slow-loading form; a page that lags on mobile pushes them to the next option before they've even seen your pricing. That's a lost lead that never shows up as a rejected quote — it just never converts.

Should insurers integrate insurance quoting into travel booking apps?

As airport-driven travel volume grows, embedding insurance quoting directly inside a booking flow generally converts better than sending customers to a separate site after they've already committed to a flight. Our piece on Travel Booking App Development covers how that kind of integration is typically built.

What does embedded travel insurance inside a booking flow look like in practice?

It means the insurance quote and purchase option appears as a step inside the same flow where someone is already booking a flight or transfer, rather than as a separate product they have to seek out afterward. The technical work involves integrating the insurer's quoting API directly into the booking platform's checkout flow.

Is this trend specific to Dubai, or does it apply across the UAE and GCC?

The specific project is in Dubai, but the pattern of large-scale airport automation driving new insurable risk applies wherever similar infrastructure gets built across the UAE and wider Gulf region. Insurers that build the capability to price this kind of risk well have a template they can reapply as comparable projects appear elsewhere in the GCC.

What is the realistic timeline for Al Maktoum's automation buildout?

A specific completion timeline for the automated people-mover system isn't publicly available at the time of writing, so it's better for insurers to treat this as an ongoing, multi-year build rather than a fixed near-term deadline. Preparing underwriting and claims systems now avoids being caught unprepared whenever specific milestones are announced.

Should smaller UAE insurers worry about this, or only the large national carriers?

Smaller insurers that write construction, cargo, engineering, or specialty lines touching contractors and suppliers around a project like this are exposed just as much as large national carriers, sometimes more, since they may have less existing capacity built for unusual risk categories. Scale doesn't exempt a carrier from needing updated intake and claims processes for this kind of exposure.

What happens to insurance demand during the construction phase versus after the airport opens?

During construction, demand concentrates in engineering all-risk, contractor's liability, and marine cargo cover for imported hardware. After the system opens, demand shifts toward public liability, business interruption, and cyber-physical cover tied to ongoing operations — which means underwriting priorities should shift along a similar timeline.

How does this affect workers' compensation or contractor liability lines?

Installing and commissioning a large automated transit system involves specialized labor working around active machinery and testing procedures, which is standard territory for workers' compensation and contractor liability underwriters. The novelty here is less the coverage type and more the technical documentation needed to price the specific installation risk accurately.

What's the risk of waiting to modernize underwriting systems until the airport actually opens?

Waiting means pricing and processing this risk reactively, likely under time pressure, once claims or new business inquiries tied to the project start arriving. Building modular underwriting and claims capability now means those systems are ready before demand spikes, rather than being assembled under deadline pressure.

How does an insurer decide which risk categories to prioritize first?

Start with whichever category already shows up most in your current book — if you write significant marine cargo or engineering risk, prioritize that intake flow first; if cyber is a bigger part of your portfolio, start there. The goal is matching the build to your actual exposure rather than building every category speculatively.

What role does AI-assisted anomaly detection play in underwriting automated infrastructure?

Airport operators are increasingly using AI-assisted monitoring to catch faults in automated systems before they become incidents, which is relevant to underwriters because it can factor into risk scoring and premium calculation for the operator's cyber-physical exposure. It also means insurers need governance frameworks for evaluating AI-driven monitoring claims made by clients.

Can a custom underwriting system integrate with an airport operator's own data feeds?

Yes, that kind of integration is exactly what a modular, custom-built underwriting platform is designed to support — pulling relevant data from an insured client's monitoring or maintenance systems rather than relying solely on periodic manual reporting. This is more feasible with purpose-built software than with a rigid off-the-shelf policy admin platform.

What's the difference between IT risk and OT risk in this context?

IT risk generally concerns data systems — records, databases, customer information. OT (operational technology) risk concerns the systems that control physical processes, like the sensors and control loops running an automated transit vehicle. A people-mover blends both, which is why it needs risk assessment that spans traditional cyber underwriting and physical engineering risk together.

How should an insurer's product team think about new travel insurance products tied to Al Maktoum?

As airport-driven travel volume grows, product teams have an opportunity to design travel cover that's sold at the point of booking rather than as an afterthought, ideally integrated directly into booking platforms. The product design question is less about new coverage types and more about distribution — meeting travelers where they're already making a purchase decision.

Do insurers need a new customer-facing quote flow, or just backend underwriting changes?

Most insurers need both, but they don't have to happen simultaneously. A backend underwriting change that isn't matched by a customer-facing flow that can actually collect the right information from applicants will still create friction, so the two should be planned together even if built in phases.

What's a realistic first project for an insurer that wants to start now?

A focused first step — rebuilding a public quote page for speed and clarity, or adding a modular intake flow for one new risk category — is more realistic than attempting a full underwriting platform rebuild immediately. It also gives internal teams a working example of the new approach before committing to a larger build.

How does this fit into the broader pattern of UAE infrastructure driving software demand?

Major UAE infrastructure projects consistently create downstream demand for custom software among the businesses and service providers connected to them, because generic platforms rarely match the specific new processes those projects require. Al Maktoum's automation build is one instance of a pattern insurers should expect to see repeat as the region continues large-scale infrastructure investment.

What happens if an insurer's competitors move on this first?

A competitor that builds dedicated underwriting and claims capability for automation-related risk first is likely to win reference business and pricing credibility on similar projects going forward, since brokers and clients tend to default to carriers who can speak specifically to a risk category. Being early here is a genuine competitive advantage, not just operational tidiness.

How does Scult typically start an engagement like this?

Engagements typically start with a scoping conversation to identify which risk category or workflow gap is most urgent, followed by a proposal scoped to the appropriate tier of work rather than a one-size-fits-all package. The Custom Software Development page has more detail on how that process works.

What should an insurance company's leadership ask their tech team before greenlighting this kind of project?

Leadership should ask which specific new risk categories the business is already exposed to, whether current systems can actually collect and process the data needed to underwrite them, and what the cost of waiting looks like if a competitor moves first. Those three questions usually clarify whether the right starting point is a small fix or a larger platform investment.