How long does it take to build custom software? For a typical UAE or India business, a professional website takes 2 to 6 weeks, a CRM or POS takes 6 to 12 weeks, a mobile app takes 8 to 16 weeks, and a full ERP covering sales, stock, accounts and HR takes 3 to 9 months. These are realistic ranges from a working studio, not marketing promises, and the single biggest variable is not coding speed but how fast decisions, content and data arrive from the client side.
Typical timelines by project type
The table below gives honest ranges for well-run projects where the client is responsive. Treat them as planning figures, not guarantees; your scope decides where in the range you land.
| Project | Typical duration | What drives the range |
|---|---|---|
| Business website (5 to 15 pages) | 2 to 6 weeks | Content readiness, number of languages, custom design |
| Landing page with WhatsApp lead flow | 1 to 2 weeks | Copy and images supplied on time |
| CRM for a consultancy | 6 to 12 weeks | Pipeline complexity, document templates, WhatsApp or email integration |
| POS for retail or restaurant | 6 to 12 weeks | Hardware mix, kitchen display, loyalty, multi-branch |
| HR and payroll with WPS | 8 to 14 weeks | Leave rules, gratuity logic, attendance devices |
| Mobile app (customer or staff) | 8 to 16 weeks | Platforms, offline use, store approval |
| Full ERP | 3 to 9 months | Number of modules, branches, data migration, integrations |
If you are weighing a build against a subscription product, read custom software vs off-the-shelf first; sometimes the right answer is to buy and save the months.
The five phases and how long each takes
1. Discovery and scope (1 to 3 weeks)
The team maps your process, lists every screen and report, identifies integrations such as your bank, WhatsApp, payment gateway or Accredited Service Provider, and agrees what is in the first version. This phase feels slow but prevents months of rework. The output is a written scope and a firm plan.
2. Design (1 to 4 weeks)
Wireframes and then visual designs for the main screens, in every language you need. Arabic right-to-left layouts take extra care. Your sign-off here is a decision point that often stalls projects.
3. Build (40 to 60% of the total)
Developers build the database, logic and screens, usually in two-week cycles with a demo at the end of each. You should see working software early, not a big reveal at the end.
4. Testing and data migration (2 to 6 weeks)
Your team tests real scenarios with real data. Customers, products, suppliers and opening balances are imported from Excel or the old system. Dirty data is the most common cause of delay at this stage; our data migration checklist shows how to prepare it.
5. Go-live and stabilisation (2 to 4 weeks)
Training, switch-over, usually at a month-end or quarter-end, and a period of fast fixes while staff settle in.
What makes projects run late
In our experience, delays rarely come from the code. They come from the following, roughly in order of frequency:
- Slow decisions. A design waiting two weeks for approval adds two weeks to the end date.
- Scope creep. Each small extra is reasonable; twenty of them are a second project.
- Missing content and data. Product lists with blank prices, customer files with duplicate names, website text that never arrives.
- Third parties. Payment gateways, bank integrations, app store reviews and ASP onboarding move at their own pace.
- One point of contact who is too busy. The owner wants to approve everything but is travelling.
The fix for most of these is to name a decision-maker with authority, agree a 48-hour turnaround for approvals, and freeze the scope of version one in writing.
Compliance deadlines you should plan around
If your software issues invoices in the UAE, the e-invoicing timeline matters for your project plan. The Ministry of Finance issued Ministerial Decisions No. 243 and 244 of 2025 on 29 September 2025 (source: mof.gov.ae). A pilot starts 1 July 2026; compliance is mandatory from 1 January 2027 for businesses with revenue of AED 50 million or more and from 1 July 2027 for businesses below that figure. Every business must appoint an Accredited Service Provider and issue invoices in PINT AE format, with electronic documents stored inside the UAE.
Under Cabinet Decision No. 106 of 2025, failing to implement the system or appoint an ASP on time carries a penalty of AED 5,000 per month of delay (source: tax.gov.ae). Work backwards from your deadline: allow time for the build, for ASP onboarding, and for a month of parallel testing. Starting a system project in early 2027 for a 1 July 2027 deadline is cutting it fine.
How to plan a realistic go-live date
- Pick the business date that matters: a new branch opening, a quarter-end, a compliance deadline.
- Subtract four weeks for stabilisation and training.
- Subtract the build range for your project type from the table above, using the upper end.
- Subtract two to three weeks for discovery.
- That is the latest date to sign off the scope. If it is already behind you, plan a phased launch.
A phased launch, where the core module goes live first and the rest follows, is almost always the better choice for an SME. You get value sooner, staff learn in stages and the risk of a big-bang failure disappears. Our services page lists the modules we usually phase in this way.
Frequently asked questions
Why do developers refuse to give an exact date at the first meeting?
Because the scope is not yet defined. An honest developer will give a range after the first call and a firm plan after a short discovery phase, when the screens, integrations and data sources are agreed. A precise date before that is a guess dressed up as a promise.
Can we speed up a project by adding more developers?
Only up to a point. Adding people to a small project adds coordination work and often slows it down. Faster results come from quicker decisions on your side, a clean data set for migration and a willingness to launch a first version before every wish is built.
What is a phased launch and should we use one?
A phased launch delivers the core module first, for example invoicing and stock, and adds payroll or a client portal in later phases. For most UAE SMEs it is the safest route: staff learn one thing at a time and you see value within weeks rather than months.
How long does UAE e-invoicing integration add?
If your system already produces compliant tax invoices, mapping them to PINT AE and connecting to an Accredited Service Provider is typically a matter of weeks, depending on the ASP's onboarding process. Start well before your deadline of 1 January 2027 or 1 July 2027 so testing is not rushed.
What happens after go-live?
Expect a stabilisation period of two to four weeks when small issues surface and are fixed quickly. After that, the project moves into maintenance, with updates, backups and support covered by an agreement. Our article on software maintenance contracts explains what that should include.
How Zaini Developers can help
We give you a written timeline after a short discovery call, build in two-week cycles with a demo at the end of each, and recommend phased launches so you see working software early. Websites, CRM, FORMA ERP, ZainiPOS, StaffManager Pro and e-invoicing integration are all quoted to your scope, never from a price list. Browse live systems at zainidevelopers.com/demo or contact us on +971 50 260 0409 with your target date and we will tell you honestly whether it is achievable.