# Custom software | Octacer: Saudi Arabia / GCC

> Custom operational software, portals, SaaS products, internal tools, mobile applications and ERP extensions, for workflows that off-the-shelf tools cannot support. The fourth answer, not the first.

- **HTML:** https://octacer.com/sa/en/custom-software
- **Arabic-default:** https://octacer.com/sa/custom-software
- **Arabic markdown:** https://octacer.com/sa/custom-software.md

## Problem

Building is the most expensive and most permanent option. It is worth doing only after process change, automation on platforms you own, and integration have been honestly ruled out.

## Architecture

Decision test: build when the workflow is commercially important, persistent, differentiated, and not reliably expressible using existing systems plus integration and automation. Do not build when a licence already covers it, the requirement is still moving, the pain is a missing connection, or nobody will own it.

## Outcome

Operational products people use all day, built around one operational object and the states it moves through, instead of showcase projects.

## Related

- [Arabic custom software](https://octacer.com/sa/custom-software)
- [Operations review (EN)](https://octacer.com/sa/en/operations-review)
- [Product engineering architecture](https://octacer.com/architecture/product-engineering)
- [Saudi English home](https://octacer.com/sa/en)