Workflow, users and records
Describe how work arrives, who reviews it, which decisions need approval and what closes the task. Identify the current systems and repeated manual steps. This produces a workflow and role map before a screen list.
(✦) — Web Apps
Build software around the work your team needs to complete. We define users, permissions, records and integrations, then agree a first release with reviewable acceptance criteria.
Built around how your business actually works.

A web application built around agreed workflows, permissions and operating requirements.
See the work(01) — Selected work
(✦) — The problem
When your operations don't fit the software, the software wins — and your team adapts, works around it, copies data between systems, and builds manual processes that break under growth. The cost isn't just inefficiency. It's compounding drag on every part of the business that touches that tool.
When critical data lives in a Google Sheet that three people edit simultaneously, you have a reliability problem masquerading as a process.
Five tools, three different logins, manual data transfer between them, no single view of your business. Every gap is a mistake waiting to happen.
Your current tools cover part of the workflow but leave important manual gaps.
The tool that worked at 100 users breaks at 10,000. Rebuilding under pressure, at scale, with live customers depending on the system — that's the worst time to do it.
Workflow
Your operating process
Roles, states and exceptions defined together
Scope
Itemised proposal
Requirements and dependencies reviewed first
Access
Documented handover
Repository, accounts and third-party terms clarified
(✦) — What you get
The metrics your team needs, in the layout that makes sense for how they work. Not a standard report nobody reads.
Authentication, roles and permission boundaries are defined for the application. SSO, MFA and audit requirements are included where agreed and tested.
Data models designed around your actual business logic. Clean, normalised schemas that perform at scale and are easy to extend.
Live dashboards, instant notifications, and reactive interfaces that keep your team informed without manual refresh.
Connect to your existing tools — ERP, CRM, accounting, logistics — so the app fits into your ecosystem rather than replacing it.
We define which status updates, approvals and data transfers can be automated, with error handling and human review where the workflow requires them.
Capacity planning and load tests use agreed user counts, data volumes and response requirements. Later growth is reviewed against the measured limits.
The proposal defines architecture notes, API documentation, setup guidance and handover sessions so the receiving team understands the system and dependencies.
Scope and delivery
Describe how work arrives, who reviews it, which decisions need approval and what closes the task. Identify the current systems and repeated manual steps. This produces a workflow and role map before a screen list.
Choose the essential journeys and record what is deferred. Screens, roles, reports and integration limits belong in the accepted scope. An internal tool and a customer-facing multi-tenant product have different access and operating requirements.
Review migration fields, permitted actions, tenant boundaries, audit events and restore requirements. Test access restrictions with representative roles and data. A technical control is tested against its stated requirement; it is not a general compliance certification.
Agree user acceptance scenarios, pilot users, training owners and a release plan. The contract identifies repositories, documentation, accounts, licences and support. Changes to workflows after acceptance are assessed for price and timing.
(03) — How we approach it
We start by mapping your workflow, then build software that removes the friction — secure authentication, real-time data, clean dashboards and APIs that connect your tools. Built on a robust stack with room to scale, so the app grows with your business instead of holding it back.
(04) — What's included
— Pricing
Custom software is the service most often quoted by the hour and least often finished on budget, so we scope it first and publish both ends of the range instead.
AED 15,000 – 40,000
One workflow done properly — records, roles, reporting and an admin view your team runs without us.
AED 45,000 – 100,000+
Multiple user roles, live data and integrations into the systems you already run. Scoped and specified before a price is quoted.
Paid against milestones: a deposit to start, a payment at specification sign-off, and the balance on handover.
The accepted proposal defines the price, deliverables and exclusions. Changes, usage rights, third-party charges and support terms are agreed explicitly.
(05) — Delivery checkpoints
Each stage has a deliverable and an approval point. The proposal assigns responsibilities and the schedule.
Identify roles, records, approval steps and existing tools.
What you review
Checkpoint: Confirm the first-release boundary.
Implement agreed screens, permissions and integrations.
What you review
Checkpoint: Review the tasks with representative users.
Check migration, role boundaries, error paths and recovery.
What you review
Checkpoint: Confirm expected behavior for each user role.
Agree a pilot, training, operating owner and release plan.
What you review
Checkpoint: Approve the pilot before wider rollout.
(✦) — Why NxFold
Good software starts with understanding the workflow before writing the first function.
We map your actual operations before designing anything. The software removes friction in how your business works — not how we assume it should.
We document expected load, growth assumptions and likely bottlenecks, then review capacity using the agreed test plan.
Authentication, input validation, API security, and dependency auditing are built in — not added when something breaks.
We agree source access, documentation and the handover session in advance, including dependencies and any ongoing operational responsibilities.
Arabic-language requirements and local payment systems — we understand the integrations UAE businesses actually need.
(✦) — Industries
Fleet management, route optimisation, driver tracking, and client portals — unified in one platform.
Lead management, property tracking, document workflows, and CRM integration for property teams.
Patient management, appointment scheduling, clinical records, and staff portals.
Invoice platforms, payment reconciliation, financial reporting, and client document portals.
Inventory management, supplier portals, purchase order workflows, and multi-location visibility.
Public-facing portals, internal tools, case management, and document processing systems.
Student portals, enrollment management, course scheduling, and fee collection platforms.
Employee onboarding, leave management, performance tracking, and payroll integration.
(✦) — Where we deliver Web Application Development
(✦) — Explore next
Custom ERP or off-the-shelf? An honest build-vs-buy guide for UAE companies: real cost ranges, the e-invoicing mandate, and when custom actually pays.
A practical guide to building appointment booking systems in Dubai for clinics, salons, consultants, events, fitness, and service teams.
What UAE rental operators need from fleet software — Salik, traffic fines, contracts and multi-branch — and the point where building beats buying.
(06) — FAQ
Everything you need to know before we start.
Dashboards, customer portals, booking systems, internal operations tools, marketplace platforms, SaaS products, admin panels, data visualisation applications, and custom business platforms — anything tailored to your specific workflow that you cannot buy off the shelf.
We begin with 2–3 discovery sessions that map your existing workflow, identify where friction and manual work accumulate, and define the minimum viable feature set. We then produce a detailed specification document with user flows, data model, integration requirements, and a fixed-price proposal before any code is written.
Yes. We connect to your existing tools via APIs — ERP systems, CRM platforms, accounting software, payment providers, logistics platforms, and communication tools. We document all integration requirements during scoping and test every integration in a staging environment before launch.
We agree the access model, authentication, validation, secrets handling and security checks for the application. MFA, SSO, encryption configuration and independent penetration testing depend on the system and scope. No system is described as risk-free.
We design against stated load assumptions and agree performance tests before launch. Growth may require indexing, caching, infrastructure or code changes. Capacity claims are supported by test results for the specified workload, not a universal 10× promise.
A focused internal tool or dashboard typically takes 6–10 weeks. A full business platform with complex data models, authentication, integrations, and multiple user roles runs 12–24 weeks. We confirm timelines after scoping and deliver against agreed milestones.
We define the administrative tasks your team needs, such as updating records, managing permissions or exporting data, and include the agreed screens in scope. New workflows or structural changes may still need development.
Yes. NxFold also develops iOS and Android apps through our mobile app development service; Superior and Halaly are existing examples. This service focuses on applications used in the browser. We scope a companion mobile app and any shared backend or APIs separately when the product needs both.
The handover scope lists the source repository, architecture notes, API documentation, deployment instructions and walkthrough sessions. The agreement defines deliverable rights, third-party licences and any ongoing support; credentials are transferred through an agreed secure process.
Internal tools and dashboards typically start from AED 15,000–40,000. Complex business platforms with multiple user roles, integrations, and custom logic range from AED 45,000 to AED 100,000+. We provide fixed-price quotes after a scoping session — not open-ended hourly billing.
Yes. Leadora is a multi-tenant CRM product, and Vara Fleet is an operational rental platform built by NxFold. For a new SaaS product, we define the core workflows, account boundaries, user permissions and integrations before scoping the MVP and later phases. Subscription and billing requirements are agreed during scoping.
Yes. Full RTL Arabic interfaces with proper typography, RTL-aware data tables, bilingual user preferences, and Arabic date/number formatting. We design both language interfaces simultaneously so each feels native — not like a translated version.
Real-time updates can be scoped with WebSockets, server-sent events or polling according to the use case. We agree expected concurrency, reconnect behaviour and tests; offline, delayed and failed updates need explicit handling.
We primarily use PostgreSQL for relational data — reliable, performant, and well-supported. For specific requirements we also use Redis for caching and session storage. We design database schemas carefully to perform well at scale and stay easy to extend.
Ongoing support and feature work can be covered by a separately scoped retainer. The agreement identifies the support period, covered issues, response arrangements and change process; no continuation or fixed duration is assumed.
(✦) — Ready to build the right tool?
Send the requirements, existing systems and target date. We will review the scope, dependencies, price and delivery schedule with you.
Dubai · Abu Dhabi · Sharjah · GCC · International
(✦) — Contact
Tell us about your project and we'll get back to you within 24 hours.
Senior designers and engineers are your project team, from brief to launch. You'll always talk to the people actually building it.
Your project brief
Talk to us directly