KML Decision Intelligence · 2026

We don’t decorate intelligence.
We architect it.

KML designs executive intelligence systems that connect fragmented operational data to clarity, performance insight and better decisions — across hospitality, real estate and complex business operations.

BUSINESS → STRUCTURE → INTELLIGENCE → DECISION
2M+BUSINESS RECORDS ANALYZED
16MONTHS OF HOTEL OPERATIONS
10EXECUTIVE DASHBOARDS
10+CONNECTED OPERATIONAL MODULES
UNDERSTAND KML IN 90 SECONDS
Executive Overview

KML begins where conventional reporting usually stops.

KML combines operating knowledge, analytical structure and executive design to turn fragmented information into a decision environment. The dashboard is only the visible interface.

WHAT KML UNDERSTANDS

The operating system.

How the business creates value, where work flows, where control matters and which relationships explain performance.

WHAT KML ARCHITECTS

The intelligence system.

Data structure, KPI relationships, management hierarchy and the analytical path from signal to action.

WHAT MANAGEMENT RECEIVES

Decision clarity.

A coherent management environment designed around attention, accountability and the next decision.

THE KML QUESTION

What does management need to understand today that the current reporting environment still cannot explain clearly?

SEE ARAZ CASE MANAGEMENT COVERAGE BEHIND THE INTERFACE START A CONVERSATION
01KML SIGNATURE
UNDERSTAND THE METHOD
01

Understand the business.

Map how the operation creates value, how work moves, where revenue is generated and where control can be lost.

OPERATING REALITY
02

Structure the truth.

Connect sources, clean inconsistencies and model relationships so performance has one coherent analytical language.

DATA ARCHITECTURE
03

Expose the signal.

Separate meaningful performance signals from reporting noise — targets, gaps, patterns, drivers and accountability.

DECISION INTELLIGENCE
04

Design the decision.

Build the executive layer around what leadership needs to understand, challenge and act on next.

MANAGEMENT ACTION
OPERATING REALITY → INTELLIGENCE ARCHITECTURE → MANAGEMENT ACTION
FROM METHOD TO PROOF

The principles above matter only if they survive real operating complexity. Araz is where the KML method becomes a working management system.

ARAZ / CASE DEPTH
0%
02ARAZ CASE
ARAZ / OPERATING CONTEXT

Araz imagery is used as operating context for the case study. KML’s focus remains the intelligence architecture, decision structure and management system behind the operation.

SEE THE SYSTEM IN PRACTICE
Proof / Araz Five-Star Resort

One hotel.
One operating language.

Araz is the clearest expression of the KML method: a large-scale five-star resort operation translated into an interconnected management intelligence environment. With more than 475 rooms, eight café-restaurants, approximately 110,000 m² of built area and 30 floors, the analytical challenge extends far beyond visual reporting. The chapters below are not isolated dashboard concepts; they belong to one operating system.

475+ROOMS
8CAFÉ-RESTAURANTS
110K m²BUILT AREA
30FLOORS
At this scale, management intelligence has to connect accommodation, food & beverage, commercial performance and operational control across a complex resort environment. The significance of the KML work is therefore not the number of dashboards produced, but the ability to translate a large operating system into one coherent management language.
2M+BUSINESS RECORDS
16MONTHS OF OPERATIONS
10+OPERATIONAL MODULES
10EXECUTIVE DASHBOARDS
01ARAZ / KML
EXECUTIVE COCKPIT
EXECUTIVE COCKPITEXECUTIVE INTELLIGENCE SYSTEM
WHY THIS EXISTS

Cross-functional management view connecting the hotel’s major operating and commercial signals.

MANAGEMENT TAKEAWAY

Unify management attention across the operation so leadership sees the same performance language.

WHAT MANAGEMENT SEES

A condensed cross-functional view of the hotel’s most important performance signals, designed to direct leadership attention before detail.

VISIBLE INTELLIGENCE LAYER
WHAT THE SYSTEM CONNECTS

Executive priorities with the departmental and commercial realities that explain the headline result.

ANALYTICAL RELATIONSHIP LAYER
WHAT DECISION IT SUPPORTS

Where leadership should investigate, challenge ownership or intervene across the operation.

EXECUTIVE → SIGNAL → OWNER → ACTION
02ARAZ / KML
REVENUE INTELLIGENCE
REVENUE INTELLIGENCEEXECUTIVE INTELLIGENCE SYSTEM
WHY THIS EXISTS

Revenue, target and contribution logic structured to explain performance — not only report it.

MANAGEMENT TAKEAWAY

Explain why revenue moved, where the gap sits and which driver management should challenge next.

WHAT MANAGEMENT SEES

Revenue performance, targets, contribution and movement arranged to make the commercial result interpretable rather than simply visible.

VISIBLE INTELLIGENCE LAYER
WHAT THE SYSTEM CONNECTS

Headline revenue outcomes with the business drivers, comparisons and operating context that influence them.

ANALYTICAL RELATIONSHIP LAYER
WHAT DECISION IT SUPPORTS

Which revenue gap matters, what is driving it and where commercial attention should move next.

REVENUE → DRIVER → GAP → RESPONSE
03ARAZ / KML
ROOMS DIVISION INTELLIGENCE
ROOMS DIVISION INTELLIGENCEEXECUTIVE INTELLIGENCE SYSTEM
WHY THIS EXISTS

Rooms economics, demand and operating performance translated into a management layer.

MANAGEMENT TAKEAWAY

Connect demand, rooms economics and operating performance into a management-ready view.

WHAT MANAGEMENT SEES

Rooms performance in a structure that connects demand, room economics and operating performance.

VISIBLE INTELLIGENCE LAYER
WHAT THE SYSTEM CONNECTS

Accommodation performance with the operating and commercial relationships behind room results.

ANALYTICAL RELATIONSHIP LAYER
WHAT DECISION IT SUPPORTS

Where rooms performance is strengthening or weakening and which factor deserves management attention.

DEMAND → ROOMS → PERFORMANCE → ACTION
04ARAZ / KML
F&B INTELLIGENCE
F&B INTELLIGENCEEXECUTIVE INTELLIGENCE SYSTEM
WHY THIS EXISTS

Outlet, guest and target performance connected to the commercial reality of hotel F&B.

MANAGEMENT TAKEAWAY

Translate outlet performance, guest behavior and targets into commercial and operational decisions.

WHAT MANAGEMENT SEES

Food & Beverage performance through outlet, target and guest-facing commercial signals rather than isolated sales totals.

VISIBLE INTELLIGENCE LAYER
WHAT THE SYSTEM CONNECTS

Outlet performance with operational execution, guest behavior and the contribution of F&B to the wider hotel system.

ANALYTICAL RELATIONSHIP LAYER
WHAT DECISION IT SUPPORTS

Which outlet or performance relationship needs attention and whether the issue is commercial, operational or control-related.

OUTLET → PERFORMANCE → DRIVER → DECISION
CASE STUDY DEPTH

The approved dashboard image remains untouched. Open Decision Anatomy under any chapter to see the management logic behind the interface: what is visible, what the analytical system connects and what decision the view is designed to support.

03SCALE INTO INTELLIGENCE
UNDERSTAND THE SCALE
Araz / Scale Into Intelligence

Complexity is not solved by adding more charts.

A resort of this scale produces different operational realities at the same time: accommodation, food & beverage, commercial performance, purchasing, inventory, finance and management control. The analytical challenge is to connect those realities without losing their individual meaning.

KML approaches Araz as an operating architecture first and a reporting environment second.

01

Property Scale

475+ rooms, eight café-restaurants, 30 floors and approximately 110,000 m² of built area create a large operating footprint.

PHYSICAL COMPLEXITY
02

Operational Complexity

Departments do not operate in isolation. Revenue, service delivery, purchasing, cost and control influence one another.

BUSINESS COMPLEXITY
03

Data Complexity

More than two million records across sixteen months and multiple operational modules must be transformed into consistent analytical logic.

INFORMATION COMPLEXITY
04

Intelligence Architecture

Executive and departmental views are structured around hierarchy, relationships, targets and the questions each management level must answer.

KML ARCHITECTURE
05

Management Action

The objective is not visualization. It is faster recognition of performance gaps, stronger control and clearer management intervention.

DECISION LAYER
WHAT THE DASHBOARD SHOWS

The visible layer.

Executive KPIs, trends, targets, departmental performance and analytical comparisons presented through a consistent visual hierarchy.

WHAT THE SYSTEM REPRESENTS

The intelligence underneath.

A connected understanding of how the hotel operates, how performance is generated and how information should move toward management decisions.

The dashboard is the interface.
The operating intelligence is the product.
SEE WHO THE SYSTEM SERVES
Araz / Management Coverage

One intelligence system.
Different management responsibilities.

The Araz environment is not designed for one user or one department. It supports different levels of management across the hotel — each with a different decision responsibility, but all connected to the same operating truth.

EXECUTIVE

Direction & intervention.

High-level visibility for leadership roles responsible for overall performance, priorities and intervention.

  • Owner
  • CEO
  • General Manager
COMMERCIAL

Revenue & market performance.

Commercial views focused on demand, contribution, sales performance and revenue-related decisions.

  • Sales Management
  • Revenue-oriented management views
  • Commercial performance monitoring
OPERATIONS

Execution & service performance.

Operational intelligence focused on how hotel departments perform and where execution needs attention.

  • Front Office
  • Food & Beverage
  • Departmental operating views
FINANCE & CONTROL

Discipline & visibility.

Management layers focused on financial control, cost visibility and the operational disciplines behind performance.

  • Finance
  • Cost Control
  • Warehouse
  • Purchasing
KML PRINCIPLE

Information hierarchy should follow management hierarchy. The owner should not need the same level of detail as a departmental manager, and a departmental manager should not be limited to an executive summary. KML structures one analytical system with the right depth for each decision owner.

01SAME TRUTH

One analytical foundation across management levels.

02RIGHT DEPTH

Different information depth for different responsibilities.

03CONNECTED VIEW

Departmental performance remains connected to executive context.

04ACCOUNTABLE ACTION

Insight is tied to the person who can act on it.

CONTENT INTEGRITY

Case-study figures and operating facts shown on this site are limited to information confirmed for the Araz project. Unverified claims and speculative KPIs are intentionally excluded.

04BEHIND THE INTERFACE
LOOK BEHIND THE INTERFACE
Behind the Interface

The visible dashboard is the last layer.

A KML system is built through business understanding, process mapping, analytical modeling and management logic before visual design begins.

This is what separates an intelligence environment from a collection of charts.

01

Operating Model

Understand how the business creates value, where responsibilities sit and which processes influence performance.

BUSINESS MAP
02

Data Reality

Identify sources, inconsistencies, manual workflows, missing relationships and the actual quality of the information layer.

SOURCE ARCHITECTURE
03

Performance Logic

Define the KPI relationships, targets, comparisons and drivers that describe the business correctly.

METRIC SYSTEM
04

Decision Hierarchy

Separate executive signals from departmental detail and assign the right level of information to the right decision owner.

MANAGEMENT LAYER
05

Visual Architecture

Design the interface around attention, hierarchy and action so the important signal is visible before the detail.

EXECUTIVE EXPERIENCE
05DOMAIN INTELLIGENCE
SEE THE DOMAIN LOGIC
Domain Intelligence

Why Hospitality
and Real Estate?

Because KML’s advantage is not generic BI knowledge. It is the ability to read the operating and commercial systems behind the numbers in industries where that experience already exists.

The analytical model becomes stronger when the business language is understood before the data is modeled.

01 · HOSPITALITY

A hotel is one economic system.

Rooms, F&B, rate strategy, purchasing, cost, finance and guest-facing operations are analytically connected. Measuring one area without understanding its relationship to the others creates partial intelligence.

REVENUERate, occupancy, RevPAR, channels and demand.
OPERATIONSRooms, outlets, guest flow and service productivity.
CONTROLPurchasing, inventory, cost and financial discipline.
EXECUTIVEOne management view across the operating system.
02 · REAL ESTATE

A pipeline is a commercial system.

Lead source, geography, project, agent behavior, stage progression and conversion must be read together to explain why sales performance changes.

MARKETLocation, segment, project and pricing context.
PIPELINELead quality, stage movement and conversion.
SALESAgent, team and project productivity.
EXECUTIVEWhere attention, capital and commercial effort should move.
06ENGAGEMENT MODELS
UNDERSTAND HOW KML ENGAGES
Engagement Models
07FOUNDER
UNDERSTAND THE ORIGIN
Founder / Kemal Soleymani
Built from operations,
analysis and architecture.
“A number without context is not intelligence.”

KML was shaped through hands-on work across retail, real estate and five-star hospitality — not from a software-only background. That operating exposure informs how performance systems are designed and which questions are asked before a dashboard is built.

An architectural education adds another layer to the method: structure before decoration, hierarchy before detail, proportion before density, and clarity before complexity.

RETAILSystematic sales, revenue and cost analysis developed inside operating businesses.
REAL ESTATEAnalytics systems for Istanbul-based real estate operations and Dubai market analysis.
HOSPITALITYPurchasing, commercial operations, analysis and strategy inside a five-star hotel environment.
KMLThese disciplines converge into Decision Intelligence: business understanding translated into analytical architecture.

The next step is not another dashboard.
It is a better question.

If management is receiving more reports but still needs too much time to understand what changed, why it changed and where to act, the problem is no longer visualization. It is decision architecture.

08CONVERSATION
START THE CONVERSATION
Start With The Decision

What does management need to see
that it cannot see today?

Share the operating context, the decision problem and the current reporting gap. The first conversation is about understanding the business — not selling a dashboard.

The brief opens your email client with the context already structured. Nothing is uploaded or stored by this page.
↑
01 / 09 KML Signature

Understand the method behind the visible dashboard.