MAYDAN
Memberships, class booking, gradings and kids' terms across two branches — with five interfaces, two of them entirely inside WhatsApp.
AI agents · Automation · Products · IT delivery
Software that carries out the work.
BASES builds AI agents that take real steps inside your systems, automation that removes the manual handoffs between them, and mobile and web products people use every day. Five of our own products are live below. Open one and use it.
Both channels reach the same people — the ones who would do the work.
We work across several markets. An engagement is delivered in your working hours, under your rules, into your environment.
- Delivery follows your working day
- Your data stays inside your perimeter
- Handover is part of the scope, not an extra
MAYDANSports club platformMASARFleet and parcel operationsNABDClinics and laboratory platformSIDRAFine-dining guest platformMALAMEHSalon group platform
What we build
Five kinds of work. One team behind them.
The list is short on purpose. Each of these is something we have built end to end, not a service line we are willing to attempt.
AI agents
Systems that read what comes in, decide inside limits you set, act in your software, and hand the case to a person when they should.
AI agents in detailAutomation
The manual steps between systems: intake, matching, approvals, reconciliation, the report someone rebuilds every morning.
Automation in detailMobile and web products
Products that hold up in daily use — Arabic first, right-to-left as the default, fast on a mid-range phone.
Mobile and web products in detailWhatsApp systems
Threads where a booking, a payment or a reschedule actually completes, writing to the same records as the app.
WhatsApp systems in detailIT delivery
Integration with what you already run, deployment into your environment, and operating the system after launch.
IT delivery in detail
Our work
Five finished products. All of them open.
We designed and built each of these ourselves, end to end — the domain model, the seeded world, every screen, both languages. They are not screenshots and not videos. Every control does something.
Sports club platform Fleet and parcel operations MASAR
An own-fleet, cash-on-delivery parcel network across merchant, driver and operations — with cash tracked as an object from the door to the payout.
Clinics and laboratory platform NABD
Five clinic branches and their own laboratory: booking, live queue, a lab worklist from accessioning to validated release, and critical-value callbacks.
Fine-dining guest platform SIDRA
A guest layer over an existing point of sale: booking against real table availability, an allergen passport, coursing, split bills, and the floor.
Salon group platform MALAMEH
Three branches where the specialist is the bookable unit, privacy is machinery rather than a promise, and at-home service is a mode of the same calendar.
These are our own product builds, shown as our work. We do not name businesses and we do not present them as client engagements.
Narrow first, then wider.
We would rather put one small thing into real use than deliver a document about six large ones.
Read the operation
The spreadsheet, the phone calls, the paper receipt. What the work is now, before any talk of a model.
Agree what done means
Acceptance criteria written and signed before the first line of code. If we cannot state them, the scope is not ready.
Build the first slice
One narrow piece, working, inside your systems. Fixed scope, fixed price, a date.
Hand over the keys
Code, documentation, and the training to run it without us. Your team should be able to change it.
Where an agent stops
An agent is only useful if you can see it and stop it.
Autonomy is not the goal. A bounded system that a supervisor trusts is worth more than a clever one nobody switches on.
It acts from a written list
Permitted actions are enumerated. Anything outside the list halts and asks rather than improvising.
Every action leaves a record
Input, decision, output, and who or what approved it. Readable months later by someone who was not there.
A person owns the irreversible step
Money moving, a contract sent, a record deleted — those pass through an approval gate by design.
You can switch it off
Per capability, without a deployment, by someone who is not an engineer.
A thread that finishes the transaction.
Most WhatsApp work in this market is a notification pipe. It sends a message and then sends the customer somewhere else. That is where the drop-off happens.
It completes, it does not announce
Booking, rescheduling, paying, confirming a delivery address — done inside the thread, in the customer's own words.
It writes to the same records
A booking made in a thread is the same record the app lists and the staff screen prints. One ledger, not a parallel one.
Staff use it too
In one of our products, two of the five interfaces are WhatsApp: the member's and the coach's. Rosters, attendance and cover are handled without opening an app.
Notes
What we think, written down.
Short pieces on the parts of this work that decide whether a system survives contact with a real operation.
Why the pilot never becomes a system
On the distance between a demo that impressed the board and something the operations team depends on.
WhatsApp is an interface, not a notification channel
On why most WhatsApp automation quietly becomes a person typing.
Arabic is not a translation layer
On what breaks when Arabic is added at the end of a project.
Tell us what the manual step is.
One message is enough to start. If it is not something we should build, we will say so.
Our WhatsApp line is being connected. Email reaches us today.