BOST | Business of Smart Things

Positioning

A Saudi delivery partner for operational AI and smart infrastructure.

We are not an off-the-shelf software vendor. We sit between strategy, engineering, the partner ecosystem, and field delivery, and we ship inside the organisation's live environment.

We work across the public and private sectors. One delivery model serves government, large enterprise, and the institutions that run the Kingdom's infrastructure.

Company

Mission, vision, and operating values.

What we exist to do, where we are headed, and the principles that govern how we deliver.

01

Our Mission

Put operational AI and smart infrastructure into the hands of Saudi institutions, and hand over systems they own and run.

02

Our Vision

Critical operations across the Kingdom, run on systems built in the field, in Arabic, and owned by the institutions that depend on them.

03

How We Operate

Strategy first, then build. We model the operating picture, ship decision workflows in usable increments, and transfer the system and the skill.

Strategy-led Arabic-native Outcome-aligned Field-deployed Owned by you Ontology-first

The BOST model

Forward-deployed engineering is how delivery happens.

A BOST team works next to the people who run the operation. They learn how it actually works, map it, build on the systems already in place, and ship in increments the team can use right away.

ATHR · أثر · the methodology

Sector-neutral delivery, applied across eight industries.

Six phases from first value to lasting proof. Each phase answers one question, and ends only when the answer is real.

01 2 to 6 weeks

Align

Where is the value, and what is it worth?

Before any build, we agree the outcome that matters, the real constraints, and where engineering will change the outcome most.

02 1 to 2 weeks

Commit

What exactly are we both signing up to?

Scope, charter, and approval gates locked on both sides, so everyone knows exactly what we are signing up to.

03 2 weeks

Discover

How does the work really happen today?

We sit with the leadership, operators, IT, and field teams who run the operation, and learn where it really breaks.

04 3 to 4 weeks

Design

What will change, and who will own it?

We map the assets, people, locations, events, and systems into one shared operating picture, and name who will own it.

05 8 to 10 weeks

Deliver

Is it working inside the business?

We build the integrations, dashboards, apps, automations, and AI assistants the workflow needs, shipped in increments the team uses right away.

06 90-day proof

Sustain

Does it last without us?

We track real usage, keep improving the system, and hand full ownership to the client team.

Eight commitments

What you can hold us to.

Not values on a wall. Eight promises that shape every engagement, each one we expect to be measured against.

01

Decisions before dashboards

We build to change a decision, not to add another screen. If a dashboard does not move a choice, we do not ship it.

02

Work inside your operation

Our engineers sit with your operators, in your building, on your systems. We learn the work by doing it, not by interviewing about it.

03

No baseline, no fee

We measure where you start before we begin. If we cannot establish a baseline, you do not pay.

04

Close the say-do gap

We track what the system promises against what it does in the field, and we report the gap honestly.

05

Arabic is the working language

Interfaces, documentation, and training are Arabic-native, not translated after the fact.

06

What survives handover is what was delivered

The deliverable is the system still running after we leave, not the deck that describes it.

07

Your people own it from day one

Your team holds the keys, the code, and the credentials from the first commit. No lock-in.

08

Fees follow your results

A meaningful share of our compensation is tied to the outcomes you measure, not the hours we bill.

Trust and accountability

Four controls that keep us honest.

Verified trust over claimed capability. These four controls run on every engagement.

C1

Engagement charter

One signed document that fixes scope, owners, baseline, and the definition of done before any build begins.

C2

The Record

A complete audit trail of every decision, change, and KPI, owned by you and readable without us.

C3

Approval gates

Work advances only when you sign off at each gate. No silent scope creep, no surprise invoices.

C4

Pay on proof

Where fees are tied to an outcome, payment releases against a proven result, not a date on the calendar.

How we work

A small team. The output of a large one.

A BOST team is small and senior by design. AI agents handle the volume work through our delivery engine, so a small embed ships what used to take a department.

Senior operators, not a pyramid

No junior army billing hours. The people who scope the work are the people who do it.

Agents do the load-bearing work

Research, modelling, document analysis, drafting, and monitoring run on AI agents inside the BOST engine, directed by the team.

Everything is traceable

Every finding, decision, and KPI lives in the engine, so the work survives handover instead of leaving with the consultants.

How we charge

Five commercial models. We pick the one that fits the problem.

Sometimes you pay for the work, sometimes for the result, sometimes to licence what we built. Often it is a blend, agreed up front, in the diagnostic.

01

Fixed fee

A scoped engagement at a clear price. You know the cost before we begin.

02

Retainer

An embedded team on a monthly basis, for operations that need a standing capability.

03

Usage-based

Metered to what the system processes, so the cost tracks real load.

04

Success fee

We baseline a metric with you and share the upside we create. We win when you do.

05

Licensing

Annual licensing for a product or platform we hand over, kept running after the 90-day proof.

Fixed fee and retainer cover standing capability. The success fee is the part that gates on proof. Most engagements blend the two, agreed up front. The first conversation is a diagnostic, not a quote, and you will leave it knowing exactly how we would charge.

The BOST engine

One engine runs the whole engagement.

From the first diagnostic to the final KPI, your engagement lives in one system, so nothing gets lost between slides, and you can see the work as it happens.

It starts with a diagnostic

The diagnostic agent reads your problem and writes back a structured reading: what is likely happening, the first risk to test, the questions we would ask on the ground.

It runs the delivery

Diagnosis, options, business cases, initiatives, KPIs, and board packs are all generated and tracked in one place by AI agents under the team's supervision.

It baselines your KPIs

The metrics that define success, and our success fee with them, are set, baselined, and tracked here, visible to you.

You get a login

Clients log in to a private portal to follow their engagement, files, and KPI cockpit.

Log in to the BOST engine Start a diagnostic

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 holds the scene together over time: release, observability, rollback, handover. The forward-deployed engineer runs the loop across all three.

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 diagnostic

Enterprise and sovereign AI

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

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 diagnostic

Central to everything we do

Enterprise data and operations

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

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 diagnostic

Financial services and sovereign institutions

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

Energy, industrials and petrochemicals

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

Applied across eight industries

Government
Telco & smart cities
Real estate
Energy & petrochemical
Banking & finance
Health
Industrials
Logistics

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

Go to market

Madinah HQ. Riyadh-connected. Saudi-wide 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.

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 · SYSTEMS WE INTEGRATE WITH AND ORCHESTRATE AROUND

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 are systems we integrate with or orchestrate around, not declared partnerships.

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.

Document intelligence

Extract, classify, and reason over contracts, policies, records, and correspondence, in Arabic and English.

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.

Agentic process automation

AI agents that run back-office workflows end to end under human approval: intake, checks, routing, and decisions.

Why BOST

Why institutions call BOST.

Not the firm with the biggest team or the longest deck. The firm that delivers from inside your operation, in your language, and hands over systems that keep running.

Embedded, not remote

We deliver from inside your operation, alongside the people who run it, not from a distance.

Small and senior, multiplied by AI

A small senior team that delivers like a large one, because AI agents carry the load under partner-level judgement.

We hand over working systems

Not decks. Madinah-based and Riyadh-connected, on the same timezone, regulations, and language as you.

Paid on outcomes, not hours

Success-fee and outcome-based models available. We tie our upside to systems that work and the results they deliver, not the time we bill.

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

We hire forward-deployed engineers and Arabic-native operator liaisons who can do this work in the field.

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 are biased to Arabic delivery, not bolted-on translation.

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.