The platform

Twenty-four modules. Take the ones that are your business.

None of this is a roadmap. Every module below is running in production today, which is a different claim from most of what you will read on a page like this. The engagement starts by deciding which of them are actually yours.

Five groups

Organised around the day, not around your store's database.

A platform organised around objects gives you Orders, Products, Customers. A platform organised around the day gives you what has to happen before tonight, what needs deciding this week, and who is doing it. The second one is what people actually open in the morning.

How it actually works

Three mechanisms, running.

Each one is the mechanism itself, running — not a picture of it. The data is invented; the behaviour is not.

One warehouse, every shopfront

A sale on one store has to reach every other one, and it has to count exactly once — however many routes it arrives by.

The same sale, counted once.

A rule changed at three in the afternoon

The person who noticed the problem raises the acceptance line themselves. No ticket, nothing to wait for — the held orders re-check themselves against the new line.

WHEN

acceptance score below6075

THEN

Hold + raise a CS task

SAVED

Held for review

24
  • #41902Giza54
  • #41917Nasr City58
  • #41928Alexandria66NEW
  • #41931Heliopolis71NEW
Written on screen by the person who noticed.

Supplier photos in, a product page out

Whatever arrived on WhatsApp becomes a gallery in your house style and copy in your store's voice — then waits for a person to approve it.

DRAFTAWAITING APPROVALEGP 1.40 · cached
  1. 01Photos received
  2. 02Cut out
  3. 03House packshot
  4. 04Copy written
  5. 05Draft created
Nothing generated reaches a customer unapproved.

02 / The core

Everything below the waterline is already built.

A new brand does not start from an empty repository. The foundation — the part that is expensive, slow and invisible — already exists and is already running. What we build for you sits on top of it.

Your store is a plugin, not the foundation

The core of the system does not care which platform you sell on. Every sales channel plugs into the same place, so adding another storefront, a different platform or a new courier is a part we add — not a system we rebuild.

Built for more than one business from the first day

Every record is scoped to its owner and isolated at the database level. Your data is not a folder in someone else's system.

Your rules are settings, not code

Thresholds, review rules, the scoring formula, the stale-order age, the categories, the automation switches. If it is a business rule rather than a new feature, your manager changes it — not a developer, not a support ticket.

Permissions to the individual

Roles are a starting bundle, then every permission is set per person. Who sees revenue, who sees HR, who can write back to the store, who can approve payroll.

One design system, held to a written constitution

Colour appears only when it carries information. One motion curve. Four corner radii. It is why thirty-five screens built over a year still feel like one product — and why yours will.

On the phone, without a second app to build

The same system ships to iOS and Android as a real app with biometric sign-in, push and camera. Every web release is on every phone the moment it deploys.

04 / Depth

Five things a generic tool cannot do for you.

This is the honest answer to “why not just install an app.” Each of these is built, running, and took long enough that it is a reason to talk to us rather than start over.

I

A score for whether the order will actually be accepted

In cash-on-delivery, the first question about an order is not whether it was placed — it is whether it will be taken at the door. We compute, for every buyer, the share of their settled orders that were actually delivered, merging the duplicate profiles that are really one person behind a single phone number and address. It updates the moment anything happens to an order, and it appears everywhere that buyer does.

Every threshold in it is yours to change.

II

Rules your manager writes, not your developer

When this is true, hold the order and do that. Buyer scored below your line. A genuinely first-time buyer, checked against phone and address so a returning one cannot hide behind a new email. Value above a limit. Four orders from one number inside ten minutes. A name that is really a phone number. The conditions compose without code, and what happens next — a task, a message to the agent on duty — is a choice, not a rebuild.

Written in the interface, at three in the afternoon, by the person who noticed the problem.

III

Every shopfront telling one truth

One warehouse behind several stores, none of which knows the others exist. The happy path takes an afternoon. What takes months is everything else: one sale reaching you by more than one route and having to count exactly once, a level below zero meaning an oversell rather than a delivery, a restock counted again the next morning, an archived product that still holds real stock. Every movement is written down permanently and nothing is ever quietly edited, so you can replay any day and see what really happened — because these records are about money.

Anyone can build the happy path. You are buying the edge cases.

IV

Photos in, listing out

Supplier photographs — usually whatever came through on WhatsApp — become finished galleries in your house style and listing copy in your store's voice, categorised and drafted into the store. Style templates are measured from your existing catalogue, not guessed. Spend is capped monthly, identical work is never paid for twice, and nothing generated reaches a customer without a person approving it.

For a brand adding products weekly, this is the difference between a person's week and a batch job.

V

It works in the language your team writes in

English and Arabic throughout, including the Franco-Arabic your staff actually type into a free-text field. Not a translation layer over an English product: the release notes, the expense descriptions, the assistant and the interface all work in both, and each person picks their own.

Software people avoid using is software you did not buy.

Is this the part you need?

The fastest way to find out is to tell us what this part of your operation currently costs you in people and mistakes.

Start a conversation