Why we keep to a fixed order
Software projects usually go wrong when building starts before anyone has agreed what is being built. So we map how you work, agree what will change, build it, test it, and only then switch it on.
Each project has its own details, but the steps run in that order every time.
How we run an Odoo project
The same five steps on every Odoo implementation. The fit-gap plan in step two gives you the dates.
Discovery
We map how you sell, buy, stock and account today, and where it breaks.
Fit-gap and plan
What Odoo does out of the box, what needs configuring, what needs custom code, and in what order.
Configure and build
We set up the apps and write the custom modules and integrations.
Migrate and train
We move your products, customers, balances and open documents, then train each team on its own screens.
Go live and support
We stay with you through the first closings and keep improving the system after.
How we build web and mobile apps
Four stages for web applications and mobile apps.
Planning and analysis
We agree who the application is for, the scope and the requirements, and name the risks before any design starts.
Design
We work out the screens, features and flows and check them with the people who will use them.
Build and test
We develop the application and test it against the goals agreed in planning, on real devices for mobile apps.
Delivery and maintenance
We release it for your approval, then support fixes, upgrades and new features after launch.
What working with us looks like
One team
ERP, web, mobile and hosting from the same people, so nothing falls between vendors. The people who plan your project are the people you call when something needs to change.
Arabic and English
Meetings, documents and training in either language, and software that works in both, with right-to-left layouts for Arabic.
A written estimate first
After a free discovery call we send a written estimate broken down by phase, so you know what each stage covers before it starts.
Training on your own data
Each team learns on its own screens with its own data, so the first day after go-live looks familiar.
Progress updates
[NEEDS CLIENT INPUT: how Kites reports progress during a project, for example regular calls or a shared task board]
Start with a discovery call
Tell us how your company works today and what you want to change. The first call is free.




