About
Built by people who had the problem.
Procurement Control Tower was not designed in a workshop. It was built inside a working procurement department, to answer the question that department had every Monday morning: what do we need to order, and how do we know?
What it is
A planning and procurement workspace that sits alongside an ERP rather than replacing it. It reads the exports the ERP already produces, turns them into one view of stock cover, demand, open orders and supplier delivery, and keeps the reasoning behind each purchasing decision with the decision itself.
Why it exists
Every mid-sized importer and manufacturer has the data needed to plan properly and almost none of them can act on it, because it arrives as four separate reports that somebody merges by hand. The merging is where the week goes, and the reasoning is what gets lost. This software exists to remove the first problem and fix the second.
How it is developed
Continuously, in small changes, each one gated by an automated test suite that has to pass before anything can be released. The architecture is deliberately plain — static files and a managed database — so that it can be maintained for years by a small team rather than needing one.
Where it is built
In the Kingdom of Saudi Arabia, for companies that import, manufacture and distribute. The software itself is country-neutral: currency, locale, date format and working week are configured per company, not compiled in.
Who uses it
Several companies run on it today, each seeing only their own data, and it is in use every week rather than in a pilot. Access is provisioned by an administrator; there is no public sign-up.