Supplier identity
Legal name, commercial registration, headquarters and accountable contact channels.
A reference for decision-makers and technical teams
Evaluate the proposal and scope before committing to technology
A practical reference bringing together company identity and the scope, security, integration and handover questions institutional buyers need for a fair comparison.
Verifiable information
Business Field for Communications and Information Technology
Legal identity and official contact channels are kept in one place to support initial supplier qualification.
- Commercial registration
- 7004290479
- Headquarters
- Riyadh, Saudi Arabia
- Call us
- +966 11 2033 999
- info@majal.sa
Six areas every proposal should answer
Six areas every proposal should answer
Procurement, IT and security teams can use these areas before comparison or approval.
Scope and assumptions
Functions, quantities, exclusions, dependencies and responsibilities.
Licensing and cost
Pricing unit, limits, renewal and separately priced items.
Security and data
Deployment, data categories, roles, retention, logging and backup.
Integration and acceptance
Interfaces, test environment, failure cases and acceptance criteria.
Handover and continuity
Training, documentation, support, export and contract exit.
What we publish clearly
What we publish clearly
Identity, product status, delivery methods, pricing factors, privacy and security reporting.
From procurement question to comparable proposal
- Share requirementsFunctions, volumes, data, integrations, security and target timing.
- Expose the gapsAssumptions, constraints and dependencies affecting cost and delivery.
- Document the answersScope, responsibilities, acceptance, handover and support.
- Compare on one basisThe decision rests on explicit elements, not an isolated headline price.
Clear boundaries before contract
Does this page mean every product holds one universal security certification?
No. Controls, documents and deployment are defined for the product, scope and entity.
Can requirements be reviewed before requesting a price?
Yes. Sharing security, integration and acceptance requirements early improves proposal comparability.
Do all products use the same deployment model?
No. The choice depends on the product, infrastructure, data, requirements and feasibility.
What happens when no suitable interface exists?
We document the constraint and assess a governed file exchange or an intermediate layer instead of making an unverified promise.
A clear first step
Discuss evaluation requirements
A practical reference bringing together company identity and the scope, security, integration and handover questions institutional buyers need for a fair comparison.