Clear information. Confident decisions.
Who you work with, what to agree before starting, and how to plan the life of your software. A practical basis for choosing MUJEER.
01 / Who you work with
People you can reach.
A business you can identify.
Based in Amman
Founded in 2017. 53 Al-Fadeleyah Street, 2nd Floor, Shmeisani, Amman 11194, Jordan.
Contact MUJEERMeet our published team
Your proposed delivery team, responsibilities and availability are confirmed for your scope. The published profiles introduce people at MUJEER; the project proposal identifies who will work on your engagement.
02 / Make an informed choice
Explore the work.
Discuss what matters to you.
Delivered scope and client perspectives
Our case studies describe published client assignments and the services involved. Product capabilities explain what a platform can support; they do not establish which features a specific client uses or a measured business result.
Testimonials share client feedback published by MUJEER. Use them alongside your own reference and technical checks when choosing a delivery partner.
Demonstrations and reference requests
Tell us which workflow, integration or delivery question you need to evaluate. We can discuss a relevant demonstration, a scoped pilot or a request for a comparable client reference.
Reference introductions depend on the client’s consent. Demonstration access and any project-specific technical information are agreed for the evaluation, with confidential data kept private.
Discuss your evaluation03 / Before work begins
A shared understanding.
Recorded in the agreement.
Use these points to shape your proposal and project discussion. The signed scope and applicable product or service agreement define the actual deliverables, rights, fees and commitments.
- Scope & acceptance
- List deliverables, supported workflows, exclusions, dependencies and the tests used to accept each milestone. Agree who can approve work and how changes affect cost and timing.
- People & capacity
- Confirm the project lead, engineering responsibilities, availability and escalation contact for your engagement. Identify any subcontractor or specialist role, its access and its responsibilities before work begins.
- Fees & third-party costs
- Record the quotation, currency, payment milestones, recurring fees and who pays for hosting, domains, app stores, licences, messaging, AI or payment providers. Provider approval and charges depend on the service.
- Source code & intellectual property
- Specify the ownership or licence for custom work, reusable components and third-party software. Agree repository access and the timing and conditions of source-code handover in the project agreement.
- Data, accounts & hosting
- Name the owner of business data, hosting, domains and provider accounts. Agree administrator access, data export, retention and deletion responsibilities, including any records that must be kept.
- Security & recovery
- Define access roles, data protection requirements, update responsibilities and incident contacts. Agree backup ownership, frequency, retention, restore testing and recovery targets for the actual deployment.
- Warranty & managed support
- Separate defect correction from new features. Record warranty scope, support hours, severity definitions, response targets, escalation, maintenance windows and recurring charges in the agreed service coverage.
- Handover & exit
- List the documentation, repositories, deployment instructions, configuration inventory, access transfer and data exports needed at handover. Agree any transition assistance, timing and costs, and revoke access that is no longer needed.
Keep the next step clear.
Talk through the work, the people and the operating responsibilities before making a commitment.
