Al KabeerFood & beverage manufacturing · Sharjah
Oracle NetSuiteA group close that took three weeks now takes four days
4 daysGroup close
100%Batch traceability
Proscape ERP case study
5,000 man hours a year,
handed back to the site teams.
Proscape, a Dubai landscaping and contracting company, replaced spreadsheets and disconnected software with a single Odoo ERP covering estimation, procurement, site progress, payroll and accounts. The implementation ran 14 weeks from discovery to go-live and returned more than 5,000 man hours a year to operations, with real-time project visibility for the first time.
- Client
- Proscape
- Industry
- Contracting & landscaping
- Location
- Dubai, UAE
- Platform
- Odoo ERP
- Engagement
- Full ERP implementation
- Duration
- 14 weeks to go-live
- Users
- 120 across office and site
- Status
- Live, on support
The outcome
What changed, in numbers
5,000+Man hours returned to operations every year
14 weeksFrom first discovery workshop to go-live
100%Of projects visible in real time, from any device
The challenge
Three systems, forty spreadsheets and no single number anyone trusted
01Costs arrived a month late
Site supervisors recorded labour and materials on paper, which reached the office days later and the accounts system days after that. By the time a project cost was known, the work it described was already finished and the money spent.
02Procurement ran on memory
Material requests moved by phone call and WhatsApp. Nobody could say what had been ordered against which project, so the same items were bought twice on some sites and ran out on others.
03Every report was rebuilt by hand
Management reporting meant one person exporting from three systems and reconciling them in a spreadsheet. It took several days a month and the answer changed depending on who built it.
The engagement
How the fourteen weeks were spent
A fixed scope agreed before any configuration started, then four phases with a named consultant on site through each of them.
Weeks 1–3Discovery on site
We walked three live sites and the head office, mapped how a job actually moves from enquiry to final invoice, and wrote it down. The gap between the documented process and the real one is where most of the savings were found.
Weeks 4–8Configure and migrate
Odoo configured for estimation, procurement, inventory, project costing, timesheets and accounts. Three years of historical project and supplier data migrated and reconciled against the closing trial balance.
Weeks 9–12Train where the work happens
Office staff trained in the boardroom, supervisors trained on site on their own phones. Site adoption is where contracting ERP projects usually fail, so that is where we spent the training budget.
Weeks 13–14Go-live and hypercare
Cutover over a weekend, then a consultant on site daily for two weeks and on call for a month. Every issue raised in that window was closed before the engagement ended.
The result
What the numbers mean day to day
Cost visibilityMonth end → same day
Material duplicationEliminated on live projects
Management reportingThree days → one dashboard
The 5,000 hours are not a single dramatic saving. They are the sum of a supervisor no longer writing the same timesheet twice, a buyer no longer chasing which site ordered what, and a finance team no longer rebuilding the same report every month. Each is small; together they are more than two full-time people returned to doing the work rather than recording it.
The change the management team cares about more is the visibility. Project cost against budget is now a live number rather than a monthly post-mortem, which means an overrun gets caught while there is still time to do something about it. That is the difference between reporting on a loss and preventing one.
“The transformation QZ Infomatics delivered changed how we run our entire operation. We recovered thousands of hours our teams were losing to manual processes every year, and for the first time our management has a real-time view of every project. We run a tighter, faster and more efficient business because of this implementation.”
In scope
The modules that went live
Every module below has a page of its own explaining what it does and where it fits.
Frequently asked questions
What people ask about this project
How long did the Proscape ERP implementation take?
Fourteen weeks from the first discovery workshop to go-live, followed by two weeks of on-site hypercare and a month of on-call support. That is typical for a single-entity contracting business of this size on Odoo. See how we run implementations.
Why was Odoo chosen over Microsoft Dynamics 365 or NetSuite?
Proscape is a single UAE entity that needed strong project costing and procurement without enterprise licence cost. Odoo covered that at a fraction of the price and its project module maps cleanly onto how contracting work is actually run. A multi-entity group with consolidated reporting would have pointed us at NetSuite instead. Compare the platforms.
What did the implementation cost?
We do not publish individual client fees, but an implementation of this shape — single entity, six modules, three years of data migrated, 120 users — sits in the AED 30k to 120k band we quote openly, with Odoo licences billed separately by user. See Odoo pricing in the UAE.
How were the 5,000 hours measured?
By counting the manual steps removed. Duplicate timesheet entry, manual purchase order chasing, monthly report rebuilding and site-to-office paperwork were each timed before go-live and re-measured six months after. The figure is the annualised total of those savings across office and site staff.
Do you support the system after go-live?
Yes. Proscape moved onto an annual support and maintenance contract after hypercare ended, which covers user support, minor enhancements and version upgrades. Most of our clients do the same. See support and training.