Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The problem
What is usually behind this search
We do not have an office in Makkah
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
Custom software is the right answer less often than software firms suggest. If a packaged product fits, buying it is almost always cheaper across the system's life. The case for building is when the process being supported is genuinely how the organisation competes, or when the required integration between existing systems is the actual product.
The second problem is that most failed custom projects did not fail technically. They failed because the requirement was written by people who do not do the work, the scope grew without the timeline moving, or the system was delivered to a team that had never seen it before go-live. Those are process failures, and they are avoidable.
Capabilities
What we actually deliver
Enterprise applications
Operational systems built around a specific business process — case management, field operations, project control, scheduling, approvals.
Systems integration
Making existing systems work together reliably — interface design, message handling, reconciliation and the error paths most integrations skip.
API and platform engineering
Interfaces designed to be consumed by other teams and partners, with versioning, authentication, rate limiting and documentation treated as part of the product.
Legacy modernisation
Moving capability off an old system incrementally behind a stable interface, so the organisation is never dependent on a single cutover succeeding.
Product engineering
Building a product from first release to a scale where it needs multi-tenancy, usage metering and an operations model.
Arabic and bilingual systems
Right-to-left interfaces built rather than mirrored, Hijri and Gregorian date handling, and Arabic text, names and search that behave correctly at the data layer.
Local context
Why this is different in Makkah
Makkah's operating problem has no real parallel in commercial technology: extremely high density, a fixed physical envelope, a population that changes completely every few days, and a service window where failure is not recoverable after the fact. Systems here are judged on behaviour under load, not on features.
The commercial base around that is hospitality and pilgrim services — hotels, transport operators, catering, retail and the agencies that package and manage groups. Their systems have to coordinate with permit and scheduling arrangements outside their control, which makes integration and graceful failure far more important than a rich interface.
The seasonal shape also determines how work should be delivered. Nothing significant changes during the season. Delivery windows are the months between, and testing has to simulate a peak that cannot be reproduced in production.
What buyers in Makkah run into
- 01
The system must fail gracefully, because it will be tested at the limit
At peak, some component will saturate. The design question is what happens next: whether the platform sheds optional features and keeps the critical path running, or whether the whole service becomes unavailable. That behaviour has to be designed deliberately; it does not emerge by itself.
- 02
Delivery windows are narrow and fixed
Releases cannot land during the season, so the calendar is set by the season rather than by the project plan. That requires a delivery approach with real staging environments and rehearsed rollbacks, because there is no option to fix forward at the worst moment.
- 03
Coordination happens across organisations, not inside one
A pilgrim's journey crosses several independent operators. No single system owns it end to end, so useful technology here is about clean interfaces and reliable data exchange between parties rather than a comprehensive platform one organisation controls.
How an engagement runs
The stages, and what happens in each
Discover
Observe how the work is done today, with the people who do it, before writing a requirement.
Design
Architecture, data model, integration contracts and the security and compliance constraints, agreed before build.
Build
Delivered in increments a user can see and react to, not a single reveal at the end.
Test
Automated tests, real-data trials and load testing where volume matters, before users depend on it.
Launch
Phased rollout with a rehearsed rollback, and support present through the first operating cycle.
Hand over
Documentation, runbooks and paired working so your team can operate and change the system themselves.
Regulatory frame
What governs this work
References for buyers. Techbanq does not issue certifications, approvals or compliance determinations — those rest with the authority and its assessors.
The full frame in Saudi Arabia- NCA ECC
The Essential Cybersecurity Controls — the national minimum baseline for government entities and for private operators of critical national infrastructure. The 2024 revision expanded both scope and control depth.
- NCA CCC
Cloud Cybersecurity Controls — the requirements applied to cloud service providers and to the entities consuming their services.
- Aramco SACS-002 / CCC
Saudi Aramco's third-party cybersecurity standard. Vendors are classified into CCC or the on-site CCC+ tier, with audits carried out by firms Aramco authorises.
- PDPL
The Personal Data Protection Law, enforced by SDAIA. Sets lawful basis, transfer, retention and breach-notification duties for anyone processing personal data in the Kingdom.
- SAMA Cyber Security Framework
The mandatory framework for SAMA-regulated entities, organised across governance, risk, operations, third-party security, resilience and compliance.
Technologies
What we work with
Cost
What moves the price
We do not publish fixed prices, because any figure quoted before the scope is known is a guess. These are the variables that actually determine it.
Integration count
Each system the new one has to talk to adds design, testing and failure-handling work. Integrations are usually underestimated.
Requirement clarity
A well-understood process is cheaper to build for than one being defined during the project. Discovery is the cheaper place to resolve that.
Compliance and audit requirements
Systems that must produce audit evidence, enforce segregation of duties or meet a control framework carry additional design and testing effort.
Users and languages
More user roles means more permission logic and more testing. Bilingual Arabic and English interfaces add design, content and testing work.
Scale and availability
A system for fifty internal users and one for a national service are different engineering problems, even with identical features.
Common questions
What buyers usually ask
Should we build or buy?+
Buy if a packaged product covers the process reasonably well — it will cost less over the system's life even after configuration. Build when the process is genuinely specific to how you operate, when integration between what you already run is the real requirement, or when every product evaluated needs so much modification that you are effectively building anyway. We will tell you when we think buying is the better answer.
Who owns the source code?+
You do. Code is delivered into your repositories as it is written, not at the end. If the relationship ends, you keep a working system and the ability to hand it to someone else.
How do you handle scope changes?+
By pricing them and showing the timeline effect before they are accepted, rather than absorbing them quietly and missing a date. Some change is normal and healthy; what causes projects to fail is change that is agreed without anyone adjusting the plan.
Other services in Makkah
Related
Custom software development in other cities
Discuss custom software development in Makkah
Send us the scope as you understand it today, even if it is incomplete, and we will tell you what we need to know before giving an estimate.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
