BOST Business of Smart Things
BOST Briefing

ذكاء اصطناعي استراتيجي وتشغيلي، وبنية تحتية ذكية

أكبر من مورّد جاهز. وأدقّ من استشاري عام.

ندمج فرقا ميدانية صغيرة داخل الجهات السعودية، ونسلّم أنظمة ذكاء اصطناعي وبنية تحتية ذكية يستخدمها الناس فعلا. فريق صغير من كبار الخبراء ينجز كأنه فريق كبير، لأن وكلاء الذكاء الاصطناعي يحملون العبء.

ابدأ موجزا
36+ years of business and technology lineage
1986 IIT business information company established
2020 BOST formed around AI, IoT, Smart Cities, and Professional Services
Positioning

A Saudi delivery partner for operational AI and smart infrastructure.

نحن لسنا مورّد برمجيات بمقاس واحد. نقع بين الاستراتيجية والهندسة ومنظومة الشركاء والتسليم الميداني، ونُسلّم داخل بيئة المؤسسة نفسها.

نعمل عبر القطاعين العام والخاص. ونموذج تسليم واحد يخدم الجهات الحكومية، والشركات الخاصة، والمجموعات العائلية، ومطوّري العقار، ومقدّمي الرعاية الصحية، وفِرَق اللوجستيات، وقادة التقنية المؤسسية.

Company

Mission, vision, and operating values.

The current BOST site frames the company around attracting technology partners, innovators, investors, leaders, and professionals, then realizing that work through experience, technology, and services.

01

Our Mission

Create an environment and business vehicles that attract partners, innovators, investors, visionaries, leaders, and professionals who can create customer value together.

02

Our Vision

Realize business ambitions through years of experience, innovative technology, and services delivered to customers.

03

Strategy

Planning and delivery, branding and marketing, image and networking, and technologies that matter.

Growth Leadership Trust Inclusive Teamwork Performance
The BOST model

Forward-deployed engineering is how delivery happens.

BOST teams work close to the people who own the operation. They observe the reality, model it, integrate what already exists, and ship systems in usable increments.

01

Embed

Sit with leadership, operators, IT, field teams, and partner teams to understand the real constraints.

02

Model

Map assets, devices, people, locations, events, decisions, and systems into one operating picture.

03

Build

Create integrations, dashboards, applications, automations, and AI assistants around the workflow.

04

Operate

Measure usage, capture decisions, improve the system, and transfer knowledge to the client team.

كيف نعمل

فريق صغير. بإنتاجية فريق كبير.

فريق بوست صغير وكبير الخبرة بالتصميم. وكلاء الذكاء الاصطناعي، عبر محرّك التنفيذ الخاص بنا، ينجزون العمل الكثيف، فيُسلّم فريق صغير ما كان يتطلب إدارة كاملة.

خبراء كبار، لا هرم وظيفي

لا جيش من المبتدئين يحتسب الساعات. من يحدّد نطاق العمل هم من ينفّذونه.

الوكلاء يحملون العبء الثقيل

البحث والنمذجة وتحليل المستندات والصياغة والمراقبة يتولاها وكلاء الذكاء الاصطناعي داخل محرّك بوست بإشراف الفريق.

كل شيء قابل للتتبع

كل استنتاج وقرار ومؤشر يعيش في المحرّك، فيبقى العمل بعد التسليم بدل أن يرحل مع الاستشاريين.

كيف نتقاضى أتعابنا

ثلاث طرق للدفع. نختار ما يناسب المشكلة.

أحيانًا تدفع مقابل العمل، وأحيانًا مقابل النتيجة، وأحيانًا ترخيصًا لما بنيناه. وغالبًا يكون مزيجًا، يُتفق عليه مسبقًا في الموجز.

أتعاب استشارية

تدفع مقابل ارتباط محدد النطاق: سبرنت أو فريق مدمج. نطاق واضح وسعر واضح.

أتعاب النجاح

نضع خط أساس لمؤشر معك ونتشارك في القيمة التي نحققها. لا نربح إلا حين تربحون، مع خط أساس وتتبع في محرّك بوست.

أتعاب الترخيص

حين نسلّم منتجًا أو منصة، مثل نظام ذكاء اصطناعي حواري، ترخّصها ونبقيها تعمل.

أول محادثة موجز عمل، لا عرض سعر. ومع ذلك ستغادرها وأنت تعرف تمامًا كيف سنتقاضى أتعابنا.

محرّك بوست

محرّك واحد يدير الارتباط بأكمله.

من أول موجز حتى آخر مؤشر، يعيش ارتباطك في نظام واحد، فلا يضيع شيء بين الشرائح، ويمكنك رؤية العمل وهو يجري.

يبدأ بموجز

يقرأ الذكاء الاصطناعي مشكلتك ويكتب قراءة منظمة: ما الذي يحدث على الأرجح، وأول خطر يجب اختباره، والأسئلة التي سنطرحها في الميدان.

يدير التنفيذ

التشخيص والخيارات ودراسات الجدوى والمبادرات والمؤشرات وحزم المجلس تُولّد جميعها وتُتتبّع في مكان واحد عبر وكلاء الذكاء الاصطناعي بإشراف الفريق.

يضع خط الأساس لمؤشراتك

المؤشرات التي تحدد النجاح، ومعها أتعاب نجاحنا، تُحدّد ويُوضع لها خط أساس وتُتتبّع هنا، أمامك.

تحصل على حساب دخول

يسجّل العملاء الدخول إلى بوابة خاصة لمتابعة ارتباطهم وملفاتهم ولوحة مؤشراتهم.

ادخل إلى محرّك بوست ابدأ موجزًا
Operational layer

From fragmented systems to one working operational picture.

The BOST approach connects physical devices, existing enterprise systems, data, AI, and daily workflows without forcing the client to start from zero.

Physical layer Cameras, sensors, facilities, vehicles, field teams
Data layer ERP, CRM, IoT platforms, CCTV, apps, databases
Operational model Assets, locations, incidents, patients, shipments, services
AI and automation Detection, prediction, recommendations, copilots, alerts
Workflow layer Dashboards, approvals, case management, field apps
Governance Access control, auditability, cybersecurity, compliance
How we frame the work

Three operating lenses. One delivery doctrine.

Marsad, Maydan, and Mashhad are not systems or service lines. They are named lenses BOST uses to structure a field engagement: what must be observed, what action must change, and what must survive handover.

01 · LENS · THE OPERATING PICTURE

Marsad

Marsad is the operating-picture lens. We design the ontology of assets, devices, people, locations, events, and decisions, and connect it to your existing systems so the operator can see, query, and reason over the work as one model. Not twelve dashboards.

  • Ontology of assets, devices, people, places, events
  • Connectors to ERPs, CRMs, IoT platforms, CCTV, cameras, sensors
  • Pipelines, lineage, governance, observability
  • Arabic-native search and natural-language query
02 · LENS · FIELD ACTION

Maydan

Maydan is the field-action lens. We turn the picture into action: incidents, dispatches, approvals, case workflows, alerts, decisions captured in audit, and a tablet-grade field experience for people working under pressure.

  • Real-time alerting, incident workflows, and case management
  • Field apps for operators, inspectors, dispatchers, and patrols
  • Decision logs, after-action reviews, knowledge transfer
  • Hijri-aware scheduling and prayer-time-aware dispatch
03 · LENS · OPERATING CONTINUITY

Mashhad

Mashhad is the operating-continuity lens. We version, release, observe, remediate, and hand over the work with AI copilots and a clear operating contract between BOST engineers and your team.

  • Continuous delivery, versioned environments, instant rollback
  • Operational observability: usage, decisions, model behaviour
  • AI copilots and automation, scoped by role
  • Knowledge transfer and operating-handover artifacts

Marsad observes. Maydan acts. Mashhad keeps both alive in the field. The forward-deployed engineer is the human who runs the loop.

The operating model

A Saudi operating ontology. Not a generic one.

An ontology is the set of objects, people, places, events, and decisions an operator actually reasons about. And the relations between them. Click any node to see how Marsad, Maydan, and Mashhad would shape the work around it.

ONTOLOGY · LIVE -- OBJECTS · -- RELATIONS
Process Entity Person Event Device Illustrative graph. Real engagements model their own ontology.
Solutions

Seven problems. One delivery doctrine.

Every tile below starts with a problem we hear in the room, then the operating system we put in its place. Same doctrine, different domain.

Smart cities and public safety

Your city's cameras, incidents, and patrols do not speak to each other. We give you one operating picture and field action on the same reality. Start a brief

Enterprise and sovereign AI

The board approved an AI strategy. Eighteen months later, nothing has changed. We deliver operating systems, not slideware. Start a brief

Smart health and hospital ops

Three systems, one patient, and no single operating picture. We build a governed clinical operating picture across them. Start a brief

Logistics and supply chain

You can see the truck on a map but not the decision it is about to miss. We deliver decisions and field action, not just visibility. Start a brief

Financial services and sovereign institutions

The data exists. The fee income it should unlock does not. We govern the data and AI that move the number. Start a brief

Energy, industrials and petrochemicals

Sensors everywhere, signal nowhere. We build an operating ontology that turns telemetry into decisions. Start a brief

Enterprise data and operations

Reports, not decisions. We invert that: decisions first, instrumented and audited. Start a brief

Services and solutions

Our full portfolio, organised around how we deliver.

Our offer divides into Services and Solutions. Each entry below names a specific operational engagement we run inside the client's environment, interpreted through the Marsad, Maydan, and Mashhad lenses where useful.

AL ḤIJĀZ → KSA → REGION PROJECTION · EQUIRECTANGULAR / WGS-84
MADINAH 24.467° N · 39.611° E الرياض 24.700° N · 46.700° E JEDDAH 21.490° N · 39.190° E YANBU 24.090° N · 38.060° E DAMMAM 26.430° N · 50.100° E NEOM 27.900° N · 35.000° E ABHA 18.210° N · 42.500° E 0 ≈ 200 KM
Saudi Arabia map showing Madinah as the operating base with routes drawn to Yanbu, Riyadh, Jeddah, Dammam, NEOM, and Abha.
Go to market

Madinah first. Saudi-wide second. Beyond Saudi where the mission fits.

Madinah is the center of gravity: close enough to build reference deployments, operational trust, and public-sector credibility. The same delivery model then scales across the Kingdom and into regional opportunities without turning away strong private-sector demand.

Madinah operating base Saudi national rollout Regional expansion
Partner ecosystem

We assemble the right ecosystem for the mission.

We orchestrate across AI, cloud, data centre, telco, cybersecurity, software, and device partners. We name ecosystem categories openly. Specific official partnerships appear here only when they are confirmed.

ECOSYSTEM CATEGORIES · DIRECTIONS OF WORK

Saudi data centers

Where workloads land first. Residency by default.

Telco operators

Connectivity, edge, and field comms in places without uniform coverage.

Cloud platforms

Compute, AI services, hosted databases for workloads that can leave the on-prem floor.

Cybersecurity

SOC, identity, posture, and NCA-aligned controls wired into delivery.

Device OEMs

Cameras, sensors, gateways, and ruggedised hardware for the field.

Software vendors

ERPs, CRMs, ITSM, and the long tail of systems we connect into the operating picture.

NAMED ECOSYSTEM · COUNTERPARTS WE WORK WITH OR INTEGRATE

HUMAIN

Saudi-built AI, named in the operating ecosystem we orchestrate around.

Microsoft

Azure, Microsoft 365, Power Platform. Common substrate for enterprise IT.

Oracle

Database, OCI, and applications that already run inside Saudi enterprises.

SAP

ERP, finance, and supply-chain systems we integrate into operating workflows.

Categories describe the directions we orchestrate. Named counterparts appear here as the ecosystem we work with or integrate against. Specific official partnerships are reserved for confirmed agreements.

Use cases

The conversations we want to start.

Every entry point invites a specific operating problem, not a generic software demo.

City command center

Unify cameras, alerts, incidents, patrol workflows, and executive visibility.

Smart district operations

Connect facilities, mobility, energy, safety, tenant services, and maintenance workflows.

Hospital operations and remote care

Support patient flow, telemedicine, ambient biometric data, and flexible local plus cloud deployment.

Logistics exception management

Track inventory, fulfillment, transport events, distribution issues, and partner handoffs.

Enterprise AI assistant

Answer questions over approved internal knowledge, policies, tickets, data, and operational workflows.

IoT asset monitoring

Observe devices, sensor readings, outages, maintenance needs, and field response in one view.

Why BOST

لماذا تتصل المؤسسات ببوست.

ليست الجهة صاحبة أكبر فريق أو أطول عرض تقديمي، بل الجهة التي تنفّذ من داخل عملياتكم، بلغتكم، وتسلّم أنظمة تستمر في العمل.

مدمجون، لا عن بُعد

ننفّذ من داخل عملياتكم، إلى جانب من يديرونها، لا من بعيد.

فريق صغير كبير الخبرة، مضاعَف بالذكاء الاصطناعي

فريق صغير من كبار الخبراء ينجز كأنه فريق كبير، لأن وكلاء الذكاء الاصطناعي يحملون العبء تحت إشراف بمستوى الشركاء.

العربية أولًا بالتصميم

مبنيّ لمن يؤدّون العمل، بلغتهم، لا ترجمة لاحقة.

بيانات سعودية، أنظمة سعودية، أرض سعودية

إقامة البيانات داخل المملكة، متوافقة مع نظام حماية البيانات والهيئة الوطنية للأمن السيبراني وسدايا وهيئة الاتصالات والفضاء والتقنية.

نُسلّم أنظمة عاملة

لا عروضًا تقديمية. مقرّنا المدينة وموصولون بالرياض، على نفس المنطقة الزمنية والأنظمة واللغة.

Field Notes from the Kingdom

Dispatches from the embed.

These are not case studies. They are illustrative patterns from how forward-deployed engagements tend to begin. We will replace each one with named work as engagements ship and clients agree to be quoted.

SMART HEALTH DAY 04 · FROM THE FIELD

"Day 4 at a Saudi public-health authority. Three ERPs. One mission."

By Tuesday it was clear that nobody in the room could answer the question "how many patients did we transfer last week, by referring district?". Not because the data was missing, but because it lived in three different ERPs that nobody was paid to reconcile. We started with a single Marsad object: patient transfer event. By Friday we had a working operating picture for one director.

Read the dispatch →
SMART CITIES DAY 02 · FROM THE FIELD

"The dispatch room had three screens. None of them showed the same incident."

The supervisor used the screen on the left for cameras, the centre screen for incidents, and the right screen for vehicles. The screens did not talk to each other. The supervisor's brain did. We did not replace the screens. We modeled the supervisor's brain as a Marsad ontology, then turned the centre screen into Maydan. The right screen became evidence; the left became context.

Read the dispatch →
ENERGY WEEK 03 · FROM THE FIELD

"One sensor on a substation became an incident, then a policy."

A vibration anomaly fired off a Maydan alert. The operator dispatched a crew. The crew found a transformer about to fail. Six weeks later, the same anomaly pattern had been turned into a policy: any reading above this threshold in this region in this season triggers a pre-emptive inspection. That policy is captured in version control. It will outlive everyone who wrote it.

Read the dispatch →
HAJJ OPERATIONS 04:12 AST · FROM THE FIELD

"What a Hajj operations centre looks like at 4am."

Four people in a room that was very quiet for the first time in eighteen days. The wall behind them showed a Marsad picture of the previous twelve hours: pilgrim movements, hospital intake, accommodation status, security touchpoints. They were not talking. They were reading. The next morning's plan would be written from the wall, not from a deck.

Read the dispatch →
DOCTRINE WEEK 02 · FROM THE FIELD

"Why we threw away the dashboard we built in week 2."

The dashboard was beautiful. The supervisor opened it twice. Both times he closed it within thirty seconds and went back to his three screens. We watched him for two more days, then deleted the dashboard and rebuilt the workflow as a single sticky alert in his existing tool. Adoption: 100% by Friday. The dashboard had not been wrong. It had been the wrong unit.

Read the dispatch →

Patterns drawn from how forward-deployed work tends to begin. Not named engagements yet, and not promises. As real engagements ship and clients agree to be quoted, these will be replaced with named work.

Sovereignty & posture

Built for Saudi data, Saudi rules, Saudi operating ground.

We engineer the work to align with the Kingdom's data-protection, cybersecurity, and AI-ethics frameworks. We do not claim certifications we do not hold; we do declare the posture we operate from on day one.

Posture statements describe how BOST designs and delivers. Formal certifications, attestations, and audit reports are issued only against confirmed engagements.

Insights

Long-form analysis on what operating in the Kingdom actually takes.

The Strategic Research Series is published, in Arabic and English: long-form analytic readings on the operating problems Saudi institutions face.

  1. DOSSIER№ 01
    BANK SCOREBOARD

    $295 Billion Hiding in Plain Sight.

    A scoreboard of the Kingdom's banks, read the way an operator reads a balance sheet: where the value sits, and where it is quietly leaking.

    EN + AR · CITATIONS
  2. DOSSIER№ 02
    CONSULTING

    The Future of Consulting.

    Why the deck-and-invoice model is ending, and what forward-deployed delivery replaces it with inside Saudi institutions.

    EN + AR · CITATIONS
  3. DOSSIER№ 03
    SOVEREIGN AI

    Who Governs the Output? Sovereign AI and the Saudi Trust Layer.

    When AI writes the answer, who is accountable for it. A reading of the trust layer Saudi institutions need before they deploy.

    EN + AR · CITATIONS

Read all insights

Operations Watch · live

A small window into how we are operating right now.

An honest forcing function. These numbers are public because public commit counts force the team to ship. As real engagements land, the field-deployed and operating-window counters become real.

OPERATING WINDOWS · NEXT QTR 3 Madinah · Riyadh · Eastern Province
MEDIAN TIME-TO-USEFUL-DEPLOY 90d target · subject to mission
UPTIME · MASHHAD ENVELOPE 99.9% illustrative target · audited at engagement

Numbers marked "illustrative" are operating commitments we are willing to be measured against. They are not historical data. As soon as engagements ship, the same fields will surface live counts.

The Forward-Deployed Engineer

The bridge that lets the system cross the river.

Marsad observes. Maydan acts. Mashhad keeps both alive. The FDE is the human who runs the loop. We do not staff engagements without one. We do not promote engineers who cannot do this job.

WHO

Who an FDE is

  • An engineer first. Code, systems, data. Fluent.
  • Lives in the field for the duration of the embed, not in a hotel near the airport.
  • Speaks Arabic at operator grade. Or works with someone who does, and treats that person as a peer.
  • Has skin in the operating outcome, not just the codebase.
  • Writes more in field notebooks than in Slack.
THE CHARTER

What every BOST FDE signs

  1. I optimize for what survives my handover.
  2. I do not present what I have not operated.
  3. I write the decision log my replacement will read.
  4. I show up when the operator does. Including 3am.
  5. I refuse engagements whose only deliverable is a deck.
SIGNED ON ENGAGEMENT START · COUNTERSIGNED BY THE OPERATING DIRECTOR
HOW THE EMBED RUNS

The engagement, week by week

W 0–2
EMBED. Sit with leadership, operators, IT, partner teams. Observe. Take notes. Do not propose.
W 2–6
MODEL. Operating ontology drafted through the Marsad lens, validated with operators, instantiated against real data.
W 6–14
BUILD. Decision workflows, integrations, alerts, and field apps shipped through the Maydan lens in operator-visible increments.
W 14+
OPERATE. Release, observability, rollback, and handover cadence shaped by the Mashhad lens. Default handover by week 26 unless otherwise contracted.
CURRENTLY HIRING · MADINAH & RIYADH

Apply with a one-page operating problem you have already solved. We do not read CVs cold. fde@bost.sa

Open roles: Junior FDE · Senior FDE · Principal FDE · Operating Director · Arabic-Native Operator Liaison
First principles

Twelve principles of forward-deployed engineering in the Kingdom.

We do not have a process manual. We have twelve principles. Everything else is a question of judgement applied to the operating reality in front of us.

  1. 01

    We start in Arabic. Translation is a degradation, not a feature.

    If the operator's first language is Arabic, the system's first language is Arabic. English is the mirror, not the master.

  2. 02

    The first deployment is in the field, not in the cloud.

    Cloud is where the platform lives. The field is where the test is. We sit with the people who will be woken up by the alerts.

  3. 03

    A dashboard is what the wall shows. The operating picture is the model in the engineers' heads.

    We build for the picture, not the screen. Screens are optional. The picture is mandatory.

  4. 04

    We declare the posture we operate from. We do not claim certifications we do not hold.

    Posture is honest. Certification is earned. Mixing the two is how vendors lie to ministries.

  5. 05

    We forward-deploy where Vision 2030 needs to land. Not where it is easiest to bill.

    Madinah first. Saudi-wide second. The mission picks the geography, not the procurement cycle.

  6. 06

    Ontology before automation.

    You cannot automate a process you cannot name. Marsad first. Maydan and Mashhad afterwards. Always.

  7. 07

    The decision is the unit of work. Not the meeting. Not the dashboard. The decision.

    Every decision a system asks an operator to make is recorded with a one-line reason. That is how institutional memory survives a transfer.

  8. 08

    We optimize for the operator at 3am, not the executive at 10am.

    If the system is unusable when the lights are dim and the stakes are high, it is unusable. Period.

  9. 09

    We measure ourselves by what survives our handover.

    A successful BOST engagement is one where the BOST engineer can leave the room and the system keeps operating. That is the only success worth claiming.

  10. 10

    We refuse projects whose only deliverable is a deck.

    Strategy without operating proof is theatre. We are not a theatre company.

  11. 11

    Hijri and Gregorian dates are equal first-class citizens.

    Schedules, deadlines, audit trails. All of them carry both. The Kingdom does not bend its calendar to ours.

  12. 12

    The forward-deployed engineer is the bridge. Without the bridge, the system does not cross the river.

    No FDE means no engagement. The bridge is not a phase. It is the design.

Team

The people behind field delivery.

تنشر الملفات الشخصية من ملخصات معتمدة وروابط لينكدإن موثقة. تظهر أسماء جديدة هنا مع نمو الفريق.

Bring us your operational problem

The first conversation is a working brief. Not a discovery call.

We do not run scoping calls. We start from a real operating problem, ask the sharper FDE questions, and turn the answers into a one-page operating brief with initial readings, artifacts, and diagrams.

FDE consultant lens

Start with the operating problem in plain language. The lens will update as you answer.

  1. 01 · PROBLEM

    Describe the broader operating problem.

  2. 02 · WHERE

    Where does the problem live?

    Sector
    Scale of the first deployment
  3. 03 · HOW IT WORKS NOW

    What systems and people own this work today?

  4. 04 · THE CONSTRAINT THAT HURTS MOST

    If you could break one constraint, which one?

  5. 05 · WHEN & WHO

    By when, and who runs it after we hand it over?

    Useful first deployment by
  6. ٠٦ · كيف يبدو النجاح

    أي الأرقام تثبت أن هذا قد نجح؟

    سمِّ المؤشرات التي تهم. نضع خط الأساس لها معك في البداية، ويمكننا ربط جزء من أتعابنا بتحريكها، فلا نربح إلا حين تربحون.

    تصبح هذه خط الأساس لخيار أتعاب النجاح في موجزك: أتعاب استشارية، أو أتعاب نجاح على الأرقام أعلاه، أو ترخيص، أو مزيج بينها.

  7. 07 · أنت

    Where should the brief go?