Build
Grow
Our products
Case studies
Blog
More
Six principles we have worked by since 2017, and the eight phases every software project goes through with us, from the first conversation to support after launch. Each phase ends with something you can see and a clear decision gate.
Not a values poster. These decide how we scope, design, build and support, and you can hold us to each one.
The people who scope your software are the people who build it and support it.
Since 2017 we have worked as one team in Sharjah: design, engineering and support under one contract and one bill. There is no hand-off to a subcontractor after the proposal is signed, and no one to blame but us.
We start from how your team actually works, not from a feature list or a template.
Before any screen is designed we sit with the people who will use the system, look at the spreadsheets, paper forms and tools they rely on today, and write down the job the software has to do. A feature that no one will use is a cost, not a deliverable.
In practice
2-week sprints · a demo every sprint · a status report every week
You see working software every two weeks, so you never commit a large budget against guesses.
Work is split into short sprints, each ending with a demo on a staging environment you can try yourself. Problems surface while they are still cheap to fix, and you steer what comes next with real software in front of you.
Bilingual screens, documents and right-to-left layouts are part of the design, not an add-on.
Customers, staff and regulators in the UAE work in both languages. We design the data model, the screens and the printed outputs for English and Arabic from the first sketch, which is far cheaper than retrofitting it later.
FTA VAT, e-invoicing and sector rules are in the brief from day one.
Tax invoices, VAT treatment, record keeping and the coming PINT AE e-invoicing requirements shape how data is stored and reported, so we design around them early. Where a requirement needs a certified provider or professional tax advice, we say so plainly and help you bring them in.
We tell you what works today, what is still in progress, and we are still here after go-live.
If a timeline is unrealistic or an idea will not work, you hear it from us before you spend money on it. After launch we keep the software monitored, backed up and improving, because the weeks after go-live are when a system earns its keep.
What happens, what you get, who is involved and the sign-off that closes each phase. Durations are typical ranges for illustration; your plan sets the real ones.
Kick-offA first conversation, often the free 30-minute scoping call.
It starts with a conversation, often the free 30-minute scoping call. For a larger project we run a short discovery: workshops with the people who will use the software, a look at your current tools and data, and agreement on what success means.
You get
From your side
From EXO LOGICS
Gate: You confirm the brief describes the problem correctly.
We turn the brief into a scope: what is in the first release, what is out, and what waits for later. You get a technical proposal and a separate financial proposal, with a choice of commercial model: fixed price when the scope is well defined, or time and materials when it needs room to evolve.
You get
From your side
From EXO LOGICS
Gate: Proposal and SOW signed; the project is booked into the schedule.
We agree the data model, the key screens in English and Arabic, and how the system connects to the tools you already use. A clickable prototype lets your team try the main flows before a line of production code is written.
You get
From your side
From EXO LOGICS
Gate: Design approved: the screens and flows the build will follow.
The build runs in two-week sprints. Every sprint ends with a demo of working software on a staging environment you can use yourself; a shared board shows what is planned, in progress and done, and a short status report lands every week.
You get
From your side
From EXO LOGICS
Gate: Each sprint reviewed at the demo; release scope confirmed feature-complete.
Testing runs through every sprint; before launch we test the release as a whole, on the browsers and devices your team uses. Then your team runs user acceptance testing (UAT) on staging with realistic data, and every issue is logged, fixed and re-checked.
You get
From your side
From EXO LOGICS
Gate: UAT sign-off: your team accepts the release for launch.
Existing data is cleaned, mapped and moved, with at least one rehearsal before the real cutover. Go-live follows an agreed plan with a time window, a named contact on each side and a rollback route if something unexpected happens.
You get
From your side
From EXO LOGICS
Gate: Go-live approved, and the migrated data checked by your team.
We train the people who will use and administer the system, in English or Arabic, and hand over everything you need to own it: source code, documentation, admin access and credentials.
You get
From your side
From EXO LOGICS
Gate: Handover signed off: you hold the code, the documents and the keys.
The first weeks after launch get closer attention (hypercare) while real usage settles. After that, a support plan covers hosting, monitoring, backups, updates and fixes, with a steady backlog of improvements based on how the software is actually used.
You get
From your side
From EXO LOGICS
Gate: Regular reviews of what to improve next, and of the support plan itself.
Live + supportedRunning in production, monitored, backed up and improving.
The same habits on a four-week website and a six-month platform build, so you always know where the project stands.
A single named project manager is your point of contact from kick-off to handover. You always know who to call.
A short written update every week: what was done, what is next, what is blocked and what needs a decision from you.
Risks, assumptions and decisions are written down in one shared log, so nothing important lives only in someone’s memory.
A change to scope comes with its effect on cost and timeline, in writing, before any work starts on it.
Every two weeks you see working software, not slides. The demo is where you steer what comes next.
A staging environment runs the latest build, so your team can test it on real work between demos.
Source code, technical documentation and user guides are delivered to you as part of the project, not held back.
Accounts, domains, cloud subscriptions and data are set up in your name. You can leave with everything at any time.
A software project needs time from your team too. This is the usual split; we agree the real one, with names, at kick-off.
| Phase | You | EXO LOGICS | |||
|---|---|---|---|---|---|
| Your sponsor | Your team | Project manager | Design | Engineering | |
| 01Discovery & brief | A | C | R | C | C |
| 02Scoping & proposal | A | I | R | C | R |
| 03Design & prototype | A | C | C | R | C |
| 04Sprint delivery | I | C | A/R | C | R |
| 05Quality & UAT | A | R | R | C | R |
| 06Launch & data migration | A | C | R | I | R |
| 07Training & handover | A | R | R | C | R |
| 08Support & improvement | C | C | A/R | C | R |
Phase one goes faster when the brief is written down. Our free template walks you through the questions we ask in discovery.
Get the free templateTell us a few lines about the project. We reply within one business day with questions, an approach and a way to estimate it.
