BOST | Business of Smart Things

Positioning

A Saudi delivery partner for operational AI and smart infrastructure.

We are not a one-size software vendor. We sit between strategy, engineering, partner ecosystem, and field delivery, and we ship inside the operator's environment.

The website leads with public-sector mission work while staying credible for private operators, family groups, real estate developers, healthcare providers, logistics teams, and enterprise technology leaders.

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

What we deploy

Three platforms. One operating doctrine.

We do not ship shrink-wrapped software. We deliver three named service lines, each focused on one part of the operating room. Forward-deployed engineers build the work inside your environment, then transfer it to your team.

01 · SERVICE LINE · THE OPERATING PICTURE

Marsad

مَرْصَد · the place from which one observes

Our service line for the operating picture. 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 · SERVICE LINE · MISSION OPERATIONS

Maydan

مَيْدَان · the field where the work is done

Our service line for mission operations. We turn the picture into action: incidents, dispatches, approvals, case workflows, alerts, decisions captured in audit, and a tablet-grade field experience for the people standing in the rain at 3am.

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 · SERVICE LINE · DEPLOYMENT & OPERATIONS

Mashhad

مَشْهَد · the scene that is being staged and watched

Our service line for keeping the work alive. We version, release, observe, and remediate Marsad and Maydan in the field. We add 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

Built around Saudi operating domains.

Our work spans smart cities, smart health, big data, AI, applications, logistics, education, marketing, and professional services. Each domain shows up below as a specific operational engagement we can deliver.

Smart Cities and Public Safety

Computer vision, big data, real-time alerts, secure collaboration, incident workflows, and city command operations.

Enterprise AI and Big Data

Analytics, machine learning, predictive analysis, text analytics, natural language processing, and decision support.

Smart Devices and IoT

Sensors, cameras, gateways, connected assets, edge intelligence, and device data flowing into operational workflows.

Smart Health

Remote care, telemedicine, ambient biometrics, preventative health, and flexible local plus cloud architectures.

Logistics and Supply Chain

Warehousing, fulfillment, transport, distribution logistics, ecommerce, and data-flow visibility.

Applications and Integration

Custom software, mobile and web apps, data management, integrations, automation, and employee workflows.

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, supported by Marsad, Maydan, or Mashhad.

AL ḤIJĀZ → KSA → REGION PROJECTION · EQUIRECTANGULAR / WGS-84

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

Enterprise-level consulting and support, delivered close to the work.

BOST’s current site emphasizes enterprise consulting, support, highly available and secure technology platforms, and four reasons to choose the company.

People

Smart, dedicated people who directly affect delivery success.

Support

Trustworthy, experienced engineers who stay close to client issues.

Customer Service

A focus on service quality and client satisfaction.

Quality

Cutting-edge IT solutions intended to add value beyond the expected scope.

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 · ILLUSTRATIVE

"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.

SMART CITIES DAY 02 · ILLUSTRATIVE

"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.

ENERGY WEEK 03 · ILLUSTRATIVE

"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.

HAJJ OPERATIONS 04:12 AST · ILLUSTRATIVE

"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.

DOCTRINE WEEK 02 · ILLUSTRATIVE

"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.

Illustrative patterns drawn from how forward-deployed work tends to begin. Not engagements. Not clients. 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.

01 · RESIDENCY
Saudi data residency by default

Workloads target Saudi cloud regions and on-prem environments first. Cross-border movement is a deliberate exception, never a default.
02 · PDPL
PDPL-aligned data handling

Personal Data Protection Law principles. Lawful basis, minimisation, retention, subject rights. Wired into intake, storage, and audit logging.
03 · NCA ECC
NCA Essential Cybersecurity Controls posture

Architecture choices map to NCA ECC domains: governance, defence, resilience, third-party, and ICS where it applies.
04 · SDAIA
SDAIA AI ethics principles

Fairness, accountability, transparency, privacy, reliability, and human oversight applied to every model that touches operational decisions.
05 · BILINGUAL
Arabic-first capable

Arabic UX, RTL-correct interfaces, Arabic NLP and OCR, and Arabic-native operator workflows. Not afterthoughts behind English.
06 · PROCUREMENT
Public-sector procurement ready

Documentation, due-diligence packs, and engagement model designed for Etimad-style procurement and ministry technical reviews.

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

The Madinah Operating Center

A physical address for forward-deployed work in the Kingdom.

A small floor where we embed, model, and operate. Three rooms, each named for the work it holds. What you see is our operating intent for Phase I, which opens against confirmed engagements.

FLOOR PLAN · PHASE I · MADINAH AL MUNAWWARAH

01 · FIELD ROOM

Where embeds begin and field photos come back to.

Whiteboards, pin boards, real maps. The room where the FDE returns from a site visit and dumps everything onto a wall before any of it becomes a model. Designed to be loud and unfinished.

02 · MODELING ROOM

Where the Marsad ontology gets drafted.

Quiet. Big monitors. Two-pizza pairs. The ontology is sketched here, validated against real data, then promoted to a working model. No pitch decks allowed in this room.

03 · OPERATING ROOM

Where Maydan and Mashhad live, on a wall.

A video wall, six operator stations, and a 24/7-capable shift desk. The room from which BOST jointly operates with client teams during the steady-state phase of an engagement.

04 · MAJLIS

Where the conversation is bilingual by default.

A working majlis, not a conference room. Saudi-style seating, qahwa, and the assumption that the most important meeting of the week happens here, in Arabic, with the operating director from the client's side.

Floor plan is operating intent for Phase I. Phase II adds a residency for visiting FDEs, a small training room, and a hardened comms point for restricted engagements.

Dossiers

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

Dossiers are how we sell without selling: 12–20-page analytic readings, in Arabic and English, on the operating problems Saudi institutions face. Three are in flight. The first ships within sixty days.

DOSSIER№ 01

DUE · ESTIMATED Q2 / 1447 H
Hajj Logistics as a Streaming-Data Problem.

Hajj is the largest annual choreographed movement of human beings on earth. We argue it is best modeled as a streaming-data system, not a planning exercise. Pilgrim cohorts, transport segments, accommodation, medical events, and security touchpoints as one operating ontology, with the Hijri calendar as a first-class field.
≈ 18 PAGES · EN + AR · CITATIONS
DOSSIER№ 02

DUE · ESTIMATED Q3 / 1447 H
What It Takes to Deploy Operational AI Inside a Saudi Ministry.

A field-grade reading of the constraints. Procurement, data residency, NCA ECC, PDPL, language, change management, and the gap between a ministry's stated and operating practices. Written for technical leaders inside the public sector who already know the easy answers do not work.
≈ 16 PAGES · EN + AR · CITATIONS
DOSSIER№ 03

DUE · ESTIMATED Q4 / 1447 H
Operating Posture vs. Certification: An Honest Framework for KSA Technology Buyers.

Saudi technology buyers are routinely sold "compliance" by vendors who hold neither the certifications they imply nor the operating posture that would back them up. We propose a framework for separating the two and a checklist procurement teams can use the next morning.
≈ 14 PAGES · EN + AR · PROCUREMENT-FRIENDLY

Pre-register to receive each dossier the day it ships: dossiers@bost.sa

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

I optimize for what survives my handover.
I do not present what I have not operated.
I write the decision log my replacement will read.
I show up when the operator does. Including 3am.
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. Marsad ontology drafted, validated with operators, instantiated against real data.
W 6–14: BUILD. Maydan workflows, integrations, alerts, and field apps shipped in operator-visible increments.
W 14+: OPERATE. Mashhad cadence in place. Handover artifacts written. 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.

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.
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.
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.
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.
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.
06
Ontology before automation.

You cannot automate a process you cannot name. Marsad first. Maydan and Mashhad afterwards. Always.
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.
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.
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
We refuse projects whose only deliverable is a deck.

Strategy without operating proof is theatre. We are not a theatre company.
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
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.

We list only confirmed profiles, with verified LinkedIn links and CV summaries the named individual has approved. New names appear here as the team grows.

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 written down in five short fields. Fill it in. We respond within seven days with a one-page reading of how Marsad, Maydan, and Mashhad would attack it.