Custom software
What you cannot buy ready-made, we build
Some businesses work in a way no off-the-shelf system understands. Others have an old system that works perfectly well and needs connecting to the rest of their tools rather than replacing. Either way it starts with a session where we watch how the work actually runs.
What we build
We start from the thing that is slowing your business down, then decide what shape the answer takes.
Mobile apps
An app for Android and iPhone, published to both stores under your own name and your own developer account. One shared codebase where that is enough, and a separate native app per platform where the camera, the maps or the responsiveness need it.
Management systems in the browser
A system your team opens from any device with nothing to install: dashboards, a portal for your customers, a different level of access per member of staff, several branches under one roof. It usually replaces ten spreadsheets nobody can tell apart.
Websites and online shops
A site for your business, or a shop that actually sells. Built to open fast on a phone before a desktop, to be found in Google in both Arabic and English, and laid out right-to-left from the start rather than mirrored from an English design.
Programs that run on a PC
A Windows program with its own icon that runs inside your premises with no internet when that is what the work needs. With an installer a member of staff double-clicks once, not a sequence of steps read off a sheet of paper.
Hosting and cloud operations
Servers, daily backups, and the monitoring that tells us before it tells you. On a public cloud or on a machine you own in your own office, and the choice is yours once we have explained what each one costs and who carries the risk.
Connecting your systems to each other
Your accounting package, your payment gateway, government e-invoicing, SMS, and anything else you use that has an interface. The point is that a number is entered once instead of being carried by hand between three programs.
Repetitive work that runs itself
The report somebody prepares every morning, the reminder somebody forgets, the data moved between two systems by hand. All of it can run on its own and arrive finished.
Moving your existing data
We take your data out of your current system or out of years of spreadsheets, clean it and reconcile it before it goes in. You get a report of everything we could not accept and why, so you never start on an incomplete system without knowing what is missing.
The technologies we work in
The language and the stack are an engineering decision taken after we understand your business. We do not sell one language to everybody.
We choose the stack after we understand the work
We ask how many people will use it, how many years it has to keep running, and who maintains it after us. If your own team already knows a language well, that is a strong reason to pick it, because a system your team cannot maintain becomes your burden within a year.
On the device it will actually be used on
Phone, tablet, desktop, a reception screen, a point-of-sale terminal. We try the interface on the device your staff will hold every day, because what feels comfortable on a large screen can be unusable on a phone in a busy hand.
Arabic from the first line
Right-to-left layout, Arabic typefaces that are genuinely readable, and correct dates and numerals. This is harder than it looks and it surfaces late in projects that treated Arabic as a translation added at the end.
A written way of working
Every change goes through automated tests and a review before it reaches you, and every release can be rolled back within minutes if something is wrong. It is the same method Mibsal builds its own systems with, and you are welcome to ask about it at any point.
The technologies we build with
A technical team working across every area of software. We pick from these to suit your project, rather than starting from a tool and making your project fit it.
Web and interfaces
- JavaScript
- TypeScript
- Vue.js
- Nuxt
- React
- Angular
- Svelte
- Tailwind CSS
Servers and back end
- PHP
- Laravel
- Node.js
- Python
- Django
- FastAPI
- Go
- Rust
- OpenJDK
- Spring Boot
Mobile apps
- Flutter
- Dart
- Kotlin
- Swift
- Android
- Apple
- Ionic
Desktop programs
- .NET
- Blazor
- Electron
Databases
- MySQL
- MariaDB
- PostgreSQL
- SQLite
- Redis
- MongoDB
Operations and hosting
- Docker
- Linux
- NGINX
- Git
- GitHub
- Cloudflare
Ready-made platforms
- WordPress
- WooCommerce
- Figma
How we work with you
Five stages, and each one ends with something real in your hands.
We learn your business
We sit with you and watch the work as it actually happens, not as it is supposed to. We leave with a written description of what will be built and what will not, and that description is what we both return to whenever we disagree later.
Scope, price and duration
A written offer stating exactly what we will hand over, what it costs and how long it takes. Anything added later is possible and carries a price you see before we start it, so no invoice reaches you with something on it you did not expect.
We build in stages
You receive a working version at the end of every stage rather than at the end of the project. That way you correct the direction early, while correcting it is still cheap, instead of seeing the system for the first time four months in.
We hand over everything
The system, the project source files, the credentials, and a document explaining how it works, where it is deployed and what it does when something fails. Handover here means another developer could carry on from where we stopped.
We stay after handover
A warranty period during which we fix any defect at no cost, then a maintenance agreement if you want one. You are not tied to it, because the system is yours and any team can pick it up.
What you own at the end
This is the difference between buying a program and having one built for you.
The project source files
The code is yours, handed over and explained. You can develop it inside your own team or with anybody else, without coming back to us and without asking permission.
Your data, exportable
Your data comes out in a format any other system can read. Export is part of the handover itself, not a service you pay for later.
A document that explains it
How it works, where it is deployed, and what it does when something breaks. Written for whoever comes after us, not attached as a formality.
No dependence on us
We do not build deliberate reliance on ourselves. If you decide to stop working with us the system keeps running and your team carries on with it, and we treat that as a successful handover.
Questions people ask before signing
Direct answers, including the ones you may not like.
What does custom software cost?
There is no fixed price, because no two systems are the same. The cost follows the size of the work, which is why we begin with an understanding session and then give you a written offer with a price and a duration before any work starts. We will not ask you to decide before you have seen the number.
How long does a project take?
That follows the size of the work too, but you will not wait until the end to see anything. You receive a working version at the end of every stage, and the schedule is written into the offer and reviewed with you as each stage closes.
Is a ready-made system better than one built for me?
Ready-made is faster, cheaper and more settled when it fits you, which is why we also sell Mibsal ERP. Custom becomes the right answer when your way of working is your advantage over your competitors, or when nothing ready-made exists in your field at all. We will give you our honest view even when the answer is to buy a cheaper ready-made system.
We have an old system that works. Should we replace it?
Not necessarily. Replacing is a risk and an expense, and connecting is usually faster and cheaper. We look first at whether what you have can be joined to what you need, and if replacing really is the right answer we will say so and give you the reason.
What if we stop working with you?
You own the project source files, the data and the documentation from the moment of handover, so any other team can continue. That is deliberate in how we hand over, not a concession granted to whoever asks for it.
Where will our data be stored?
Wherever you decide. On a public cloud, on a server rented in your own name, or on a machine inside your office with no internet at all. We discuss it during the understanding stage, because it changes the design of the system rather than a setting changed later.
Something we have not answered?
Before you commission a custom system
If your business is a clinic, or anything that manages customers, appointments and invoices, there may already be a ready-made system that fits and saves you both time and money.
Look at Mibsal ERP
A complete management platform delivered as a system built for one sector at a time: customers, appointments, invoices, payments, expenses, team and reporting, in Arabic and English. The dental clinic system runs today.
See the ready-made sectors
Choose your sector to read what its system covers and what it costs.
Tell us the problem and leave the solution to us
The best opening is a description of what is slowing your business down today and who it costs. Working out whether the answer is an app, a system, or simply wiring two programs together is our job.