Loading
Most businesses do not need another product subscription. They need the one system nobody sells: the thing that sits between an ERP nobody can change, a spreadsheet three people maintain by hand, and the way the business actually works. Novamind scopes that precisely, builds it, and hands over the code. The team works remotely with clients across the UAE, Saudi Arabia, Kuwait, Oman, Qatar and Bahrain.
Operations and finance leads who have run out of road with off-the-shelf software, and who can describe the process they need but cannot find a product that matches it.
The pattern is usually the same. A core system does eighty per cent of the job and refuses to do the rest. The gap gets filled by a spreadsheet, then by a second spreadsheet reconciling the first, then by one person who understands both and cannot take leave. The cost is invisible until that person leaves.
Custom software is the right answer when the process is genuinely yours, when the data already exists in systems that can be read, and when the work repeats often enough that automating it pays back. It is the wrong answer when a product already does the job and the real problem is that nobody has configured it.
We will tell you which of those two you have during discovery, including when the honest answer is that you should buy something instead. That conversation is cheaper for both of us than a build that should not have started.
Four shapes cover most of this work. Each is scoped on its own, so the quote reflects the system you need rather than a bundle.
The screens your team works in all day: job and order tracking, approvals with a record of who approved what, scheduling, inventory movements, document generation. Built on Next.js and Postgres with roles and per-record permissions, because an internal tool that everyone can edit becomes an internal tool nobody trusts.
A logged-in area where your customers, suppliers or franchisees see their own data and act on it: orders, statements, service requests, documents, renewals. Arabic and English, reading correctly right to left. The portal reads from your existing systems rather than becoming a second place the truth lives.
Reading an ERP that offers only a SQL view, pushing to an accounting package that only accepts a file, keeping two systems agreeing on the same customer. We build the integration with retries, a record of every attempt and an alert when it stops, because the integrations that cause damage are the ones that fail silently.
When the numbers people argue about come from three systems that each define revenue differently, the fix is a defined layer rather than another dashboard. We agree the definitions with finance in writing first, implement them once, and reconcile against the reports you already trust before anything goes live.
Fixed-scope work, priced from a written specification. The engagement models on the services page cover retainers and dedicated teams.
Discovery produces a written specification: the screens, the data model, the integrations, the permissions and the things explicitly out of scope. You own that document whether or not you build with us, and it is detailed enough to take to another firm.
The quote follows the specification, not the other way round. Starting prices on the services page are real starting points rather than marketing numbers, and the things that move a custom build above AED 20,000 are integration count, how much of the existing data needs cleaning, and how many distinct user roles the permissions have to express.
Scope changes are priced and agreed before they are built. The specification is what we are both holding, so a change is a visible decision rather than something discovered at handover.
On final payment, everything transfers. There are no licensing hooks and no dependency on us to keep it running.
The source code, the repository history, the infrastructure configuration and the database schema transfer to you in full. We hand over to whoever you choose, including a competitor, and we document it well enough that they can take it on.
That is a deliberate commercial position, not generosity. A client who cannot leave is a client who stops asking for improvements, and we would rather be kept because the work is good.
We build on stacks a UAE development team can hire for, which in practice means TypeScript, Next.js, Postgres and React Native, and never a proprietary page builder or a low-code platform whose export is a lock-in.
Stated plainly, because finding out later is expensive for you and bad for us.
On-site staff. Every engagement is delivered remotely over calls, a shared repository and a staging environment you can open. There is no office to visit.
Hardware, networking, or on-premise server administration. We will build against a server your IT team runs; we do not run it.
A published uptime or support-response guarantee. We have no SLA to point at, so we are not going to imply one.
ERP implementation or licence resale. If you need an ERP rather than a bespoke system, our own product Axion may fit, and if it does not we will say so.
Regulatory certification of any kind. We build to the rules that apply to your sector, and we do not hold accreditations ourselves.
Two of the clearest examples of what this team builds are our own products, because they are large, in production, and you can open them right now.
Axion is a GCC ERP with finance, people, sales, supply chain and commerce, VAT per country, WPS wage files, end-of-service gratuity to each state’s own statute, Arabic and English throughout. Ignis is a social media platform with a per-client inbox across Instagram, Messenger and WhatsApp, publishing to six platforms and an automation canvas. Both are ours, both are live, and both are bigger than most client builds.
For client work, the GSG Academy platform is published as a case study: an iOS and Android app, an indexable web platform and the admin console the academy team runs enrolment, payments and campaigns from.
We have not published a case study for an internal systems build, and we would rather say that than describe one vaguely.
The questions we hear before a custom software project starts.