Basheer Albashir · Riyadh

I build operations that hold under load.

Warehouse and e-commerce systems, and AI put to work inside daily operations, for teams whose growth has outrun their process.

See what I build Work with me

Engineer · Operator · Builder

Basheer Albashir
200 → 3,000Daily orders carried through one operation's scale-up
1,639SKUs under a live counting system used by a warehouse team
6+Operations tools running in production, not slideware
0 SARMonthly API spend on the warehouse bots. The models run on our own hardware.

01 · The problem I solve

Growth doesn't break companies. Unwritten process does.

Orders climb, headcount climbs, and the thing holding it together is four people who remember how it works. Nothing is documented, every exception is a phone call, and the numbers in the system stopped matching the shelf months ago. That is not a people problem or a software problem. It is an operations design problem, and it is fixable.

02 · Fit

This is for you if

  • You run e-commerce, retail or warehouse operations in the Gulf
  • Your volume grew faster than your process did
  • Inventory on the screen no longer matches inventory on the shelf
  • Your team is capable but spends its day firefighting
  • You want AI doing real daily work, not producing demos

This is not for you if

  • You want a strategy deck with no change to the floor
  • You want AI adopted for the announcement
  • You want someone to blame rather than a system to fix
  • You need a vendor who agrees with you

03 · How I work

Read the operation. Reframe the problem. Leave a system behind.

01

Read

I walk the actual process (the floor, the exports, the exceptions) until I can see the pattern under what people tell me. The stated problem is rarely the real one.

02

Reframe

I name the constraint underneath and turn the problem until it becomes workable. Most 'we need a new system' turns out to be three decisions nobody made.

03

Build

I ship the smallest thing that changes the number, put it in the team's hands, and iterate on what they actually do with it. Working software beats a recommendation.

04

Hand over

Documented, owned by your team, running without me. A dependency on the consultant is a failed engagement.

04 · Selected work

Systems in production, with the teams still using them.

Warehouse

Cycle-count system

1,639 SKUs counted blind from the floor, discrepancies escalated by rule

Ops automation

Operations bots

Document, receiving and cost workflows handled in chat, on local models

Client intelligence

Account briefing engine

Daily Arabic client-news briefing, delivered automatically

See all work →

05 · Work with me

Three ways in. All of them start with a conversation.

01

The conversation

45 minutes · no charge

You describe the problem as you see it. I ask what I would ask on your floor. You leave knowing whether I can help and what to do first.

02

The diagnostic

Two weeks · fixed scope

I read the operation and hand you a written, scored picture of where it stands, and the one constraint to fix first.

03

The build

Scoped after the diagnostic

The smallest working system that changes the number, in your team's hands, documented, running without me.

How an engagement works