Gulf shops pay for software, then reach for the notebook

In small shops across Oman, the UAE, Qatar, Kuwait and Bahrain, a sale is still recorded in a paper notebook at the moment the customer pays. Incoming stock goes onto paper too: what arrived, how much arrived, when. At day-end and month-end, staff review the pages and tick off entries to catch mistakes.

The notebook is not a side record. It is the operating record for stock and cash, kept by the people who handle both. That makes it hard to displace with a tool that lives in a different routine.

Many of these businesses have already bought inventory or sales software. Some paid for it and still keep the notebook within reach. The software is used little, or not at all. Across the Gulf, a business can pay for a tool without adopting it. The distance between purchase and use is the market’s real opening, and most of the market looks past it.

That gap is easy to miss from the outside. A purchase looks like adoption in a vendor’s spreadsheet. Inside the shop, adoption is a daily action: someone has to open the tool, enter the sale and trust the number that comes back. If the notebook is faster, the notebook wins.

The mismatch shows up in small moments: a delivery arrives, a customer pays, a staff member needs a number before the shop closes. A system that adds steps to those moments asks the shop to absorb the cost of the software’s design.

The competitor is not another dashboard. It is a pen, a page and a habit that needs no explanation. Paper asks nothing of a shop assistant beyond writing down what happened. Software asks for a new routine before it has proved it can carry one.

Why paper survives

Paper’s advantages are ordinary and hard to copy. A pen and a page need no training. The record is visible and belongs to the user. The notebook does one job, reliably, and finding an old entry means flipping pages. Software that replaces it has to match that simplicity, trust and reliability. Being more powerful is not enough.

Much software in the Gulf is sold by building a product, advertising it and closing a sale. A sale is not use. A company building for these shops has two jobs: develop the product, and build a culture and habit of use. Helping users adapt is part of building software use, not an after-sales extra. A product alone is insufficient for adoption.

The sales motion rewards the signature. The shop lives with the tool afterward, and that is where the work begins.

Many customers had tried similar software before. What determined the outcome was implementation, observation and the work of making use easier. Inventory workflows, from ordering to buying to stock entry to accounting, are hard in most systems. Cutting inventory steps to the fewest lets untrained shop workers use the tool, and leaves them happier using it.

Implementation is not a handover document. It is the point where the product meets the shop’s existing routine, and where a feature either removes work or adds it.

An engineer in the shop

Omid Pirdehi, a co-founder, spent long stretches inside one customer’s shop, sometimes 8–10 hours a day. He watched the activity, the paper records and the WhatsApp notes staff wrote to themselves. He taught staff how to enter data and entered many products himself. Watching an engineer use the tool showed the workers that it was simple to learn.

The point was not to demonstrate the product. It was to see where the working day broke, and to fix the tool around that.

Working inside the shop revealed needs that people had not mentioned or been asked about. It showed, firsthand, where the tool could improve. A feature passes only if a user can walk the path easily without extra cognitive load. Placing an engineer inside a business is an old practice. It matters more with AI, because an embedded engineer can watch real behaviour, design for it and build solutions for other customers if they work.

That feedback loop is slow and specific. It also produces a product that can be used without a trainer standing nearby.

Entry, reach and trust

Software has to make information entry simple through a dashboard or an AI chat. It has to keep information reachable from a phone, a laptop or a tablet, through a dashboard or chat. Reachable information makes a system feel reliable. The software must return data exactly as it was entered. Seeing an entered sale appear correctly in a report is where trust starts.

Reliability here is plain: the number on the screen has to match the number on the page, or the page keeps its authority.

Trust cannot be forced. It takes time. Products that push sales through advertising rarely wait for it. Products that help build culture, knowledge and trust over time gain more than a sale. Trust leads to loyalty, which builds slowly and is hard for competitors to buy. A sale can be bought with advertising. A habit cannot.

That is a different measure of success from a launch or a licence count. It is also harder to fake.

AI becomes useful to owners once data is entered correctly. Owners use it only for decisions that would otherwise take more thinking or more clicks. An owner about to write a cheque can ask an AI assistant what date to use. The assistant can look at past sales: if the 15th is usually the biggest sales day, the 16th is safer because the money will be in the bank. No accountant’s report is needed for that date decision. The advice depends on sales having been entered correctly.

The notebook test

Founders building for Gulf small businesses should treat the notebook as the benchmark. Data entry should be as simple as writing. Data should always be within reach and shown exactly as entered. Judging a product should look past how many businesses bought it and ask how many still open the notebook.