Computer Systems & Software Design
Design and build work for systems that have to survive real users, real volumes of work and a real audit, whether or not there is any AI inside them.
Systems built to be operated day to day.
- Your operation runs on spreadsheets that only two people understand.
- You have an ERP nobody trusts, so half the business keeps its own private records on the side.
- A previous supplier built something your team cannot maintain or add to.
- You need a system that will pass an audit rather than one that only looks good in a demo.
A large part of our work has no AI in it at all. It is ERP, joining separate systems together, and custom software for organisations in Abu Dhabi and across the UAE whose operations have outgrown the spreadsheets holding them together.
The largest example is a 35-module ERP running projects, finance, HR and procurement for an engineering consultancy that works in several countries. More than 150 people use it every day across four countries, and it stays up 99% of the time. Alongside it, software that reads drawings and documents took structural beam design from four hours to under five minutes, and automated drafting now saves 100 to 200 hours on a typical project. Both sit inside AutoCAD and Revit, the software the engineers already use all day, because anything that asks people to work somewhere new gets ignored.
The hard part of this work is almost never the new system. It is connecting it to the systems your business actually runs on: the ERP, the CRM, and the internal database nobody wants to touch and nobody fully understands. We plan for that from the start instead of walking into it in the final weeks.
Everything is built on your own systems, in technology your team can hire for, with the tests running automatically on every change from the first day of coding. When we leave, your engineers run it. If they cannot, the job is not finished.
What you get
The design, written down
How information moves through the system, where it meets your other systems, who is allowed to see and do what, and the ways it can fail. Written down rather than carried around in somebody's head.
Working software
Built on your systems, in technology your team can maintain, with tests that run automatically on every change from the first day of coding rather than the last week.
Connected to the systems you run on
The ERP, the CRM and the internal database nobody wants to touch. Usually the hardest part of the project, and the part most estimates ignore.
Handover pack
How to release changes, how to keep an eye on it, what it is allowed to cost, and what to do when it breaks at two in the morning. Written for whoever inherits it, not for us.