Custom business software in Egypt: when the workflow is the product
How to decide whether custom business software is justified when spreadsheets, SaaS tools, and manual approvals no longer agree.
The signal that it is time to build
Custom software is worth considering when the same exceptions repeat, the rules are important to the business, and no existing tool can show who owns the next action. The problem is not that the team lacks another dashboard. The problem is that the operating model is being reconstructed by hand.
Map the work before the code
Document roles, approvals, records, states, handoffs, and failure paths. Include the real constraints around branches, Arabic and English teams, payment reconciliation, local delivery, and reporting. A short process map is more valuable than a long feature list.
Know what to buy and what to build
Keep commodity capabilities where a stable product already does the job, and build the workflow that differentiates the operation. Accounting, authentication, messaging, payments, and analytics may integrate well; the rules that join them may be the part you own.
Shape a first release people can trust
Choose one valuable operating loop and make it observable from request to outcome. Give the team clear permissions, evidence, notifications, and an exception path. The first release should reduce a real handoff, not simply recreate every screen from the old tools.