All services

Web & platforms

Custom software and CRM systems

We build CRM, ERP and internal systems around the way your company already works, one module at a time. You end up with a documented schema, an audit trail and a way out.

Atlas Properties, a concept build: a listings dashboard showing 1,240 live listings, filtered results for Business Bay, Dubai Marina and JLT with AED asking prices, a map panel, and an English–Arabic language toggle.

Concept build — Atlas Properties, engineered in-house

<48h

Brief to fixed proposal

1

Module demoed at a time

100%

Data exportable, open formats

30 days

Warranty after cutover

What we build

Eight pieces of the job, quoted separately

Eight things a custom system has to get right.

How we build it

Three decisions we make early

Three rules that keep a long build from drifting.

We follow the work first

Before anything is modelled we sit with the people doing the job and follow one case end to end — the forms, the WhatsApp messages, the spreadsheet nobody admits to. What comes back is a process map you can correct. Software built from an org chart automates a process that only exists on paper.

One module at a time

The unit of delivery is a working module, not a milestone date. Each one is demoed on a preview environment, accepted or sent back by you, and invoiced only once accepted. If a module turns out to be unnecessary the moment you see it running, you simply do not buy the next one.

An exit is part of it

The schema is documented, the repository is handed over in full at every milestone, infrastructure is Terraform in your own cloud account, and one command exports every table in open formats. Nothing depends on a layer we own. If you replace us, the next team reads the repository and keeps going.

What you get

What a finished system leaves behind.

  • A documented schema you can hand to anyone
  • Roles, permissions and a searchable audit log
  • Workflows that match your real process, not a template
  • Migration from the spreadsheets you run on today
  • Single sign-on, with multi-factor enforced
  • Reporting your finance team accepts
  • One-command exports in open formats
  • Infrastructure defined in code, in your cloud account
  • The full repository, history included, handed over
  • Thirty days of warranty after cutover

Stack

What this work actually runs on

The stack behind a system that has to last five years.

APIs, workers and the boring parts that matter.

10 tools

  • Node.js
  • NestJS
  • Fastify
  • Express
  • Python
  • FastAPI
  • Django
  • Go
  • PHP
  • Laravel

A drawing of a table filling up: a header row, then five order rows inserting one at a time, each with a reference, an amount and a status.

Names, not logos. Everything listed is something we build with or integrate, not a category page we copied.

Where it lands

Six sectors this work is bought in

Where a system replaces a wall of spreadsheets.

All ten sectors we build for

Process

Five stages, and what you hold at each

Five stages, and one module accepted at a time.

  1. 01

    Scope

    We follow the work through your business and write it down.

    Process map

  2. 02

    Prototype

    The first module clickable, with your own data in it.

    Module prototype

  3. 03

    Build

    One module at a time, each demoed and accepted by you.

    Accepted module

  4. 04

    Launch

    A rehearsed cutover, training, then the old system read-only.

    Cutover runbook

  5. 05

    Run

    Changes, monitoring and a quarterly review against real usage.

    Quarterly review

How we quote it

We quote module by module, so each phase is priced as its scope firms up and you can stop after any one of them.

  • Phase by phase, so you can stop after any module
  • The schema and the code are yours, in writing
  • Defects found in the first thirty days are fixed free

Quoted as custom system / crm: roles, workflows, integrations, reporting, migration. We publish no bands — pick the pieces you need and one itemised quotation comes back within 48 hours, free either way.

Get a quote

Questions

Before you send the brief

Should we buy something off the shelf instead?

Often, yes, and we will say so before you spend anything with us. Off-the-shelf wins when your process is ordinary and the product is mature — most sales pipelines and most accounting is exactly that. Custom wins when the process is the business, when three products would be needed to cover one workflow, or when the licence cost per seat overtakes the build cost within about two years.

What happens to our existing data?

We profile it first, agree with you what is authoritative, and clean duplicates with the people who created them rather than guessing. It then imports into a staging environment repeatedly until the totals reconcile against your own reports. The final migration is a rehearsed script run twice — once as a dry run with a rollback, once for real — so cutover weekend is boring by design.

How do you handle PDPL and data residency?

Purpose, legal basis, retention and deletion are recorded per data category during scoping, not retrofitted. Access and deletion requests run through a routine we test before launch. Where residency genuinely matters, the system runs in a UAE region — AWS and Microsoft both operate one — and we map which systems actually need it, because pinning everything onshore costs more than it protects.

Can we move the system somewhere else later?

Yes, and the build is arranged so you can. The schema is documented, the whole repository is handed over at every milestone with nothing withheld at the end, infrastructure is defined in Terraform inside your own cloud account, and one command exports every table in open formats. Nothing depends on a proprietary layer of ours. If you replace us, another team can read the repository and keep going without a discovery phase.

How do you keep a long build from drifting?

By making the unit of delivery a module rather than a milestone date. Each module is demoed on a preview environment, accepted or sent back by you, and invoiced only once accepted. Scope changes are priced as they arrive instead of accumulating into an argument at the end. If a module turns out to be unnecessary once you see it working, you simply do not buy the next one.

Related

Where this shows up

Two systems of ours with the same moving parts.

  • Property listing platform

    Atlas Properties

    A bilingual property portal: 1,240 listings, faceted search and an agent-facing CMS.

    LCP on a filtered results page
    0.9s
    Lighthouse performance
    100
  • Clinic booking system

    Nadra Clinics

    A four-branch booking system with held slots, WhatsApp confirmations and a front-desk console.

    Lighthouse accessibility
    100
    LCP on the slot picker
    1.1s

Bought alongside

The pieces a system usually arrives with.

  • Web development

    Marketing sites and web apps in Next.js, ready for Arabic.

    Explore
  • Mobile apps

    iOS and Android from one codebase, shipped to both stores.

    Explore
  • IT & networking

    Office networks, cloud infrastructure, and support that answers.

    Explore

Map your process with us.

Bring us the spreadsheet everything runs on. We will map the workflow, scope the first module and quote exactly that.