{"path":"/transparency","url":"https://mujeer.com/transparency","title":"MUJEER Transparency | People, Project Ownership \u0026 Delivery","description":"Know who you work with at MUJEER: company identity, published team profiles, project evidence, scope, fees, source-code ownership, support and handover.","language":"en","lastModified":"2026-11-12","markdownUrl":"https://mujeer.com/read?path=%2Ftransparency","content":"#  Clear information. Confident decisions.\nWho you work with, what to agree before starting, and how to plan the life of your software. A practical basis for choosing MUJEER.\n01 / Who you work with\n##  People you can reach. A business you can identify.\n###  Business name\nMUJEER FOR SOFTWARE\n[Website \u0026 app terms](/terms)\n###  Based in Amman\nFounded in 2017. 53 Al-Fadeleyah Street, 2nd Floor, Shmeisani, Amman 11194, Jordan.\n[Contact MUJEER](/contact)\n###  Business enquiries\ninfo@mujeer.com · +962 6 222 0747\n[Email our team](mailto:info@mujeer.com)\n###  Meet our published team\n[Mujeer S. CEO](/team#mujeer-s)\n[Noor S. HR Manager](/team#noor-s)\n[Yasmeen A. Manager Assistant](/team#yasmeen-a)\n[Duaa M. Full-Stack Developer](/team#duaa-m)\nYour 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.\n02 / Make an informed choice\n##  Explore the work. Discuss what matters to you.\n###  Delivered scope and client perspectives\nOur 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.\nTestimonials share client feedback published by MUJEER. Use them alongside your own reference and technical checks when choosing a delivery partner.\n[Read case studies](/case-studies) [Client testimonials](/testimonials)\n###  Demonstrations and reference requests\nTell 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.\nReference 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.\n[Discuss your evaluation](/contact?topic=Other)\n03 / Before work begins\n##  A shared understanding. Recorded in the agreement.\nUse 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.\nScope \u0026 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.\nPeople \u0026 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.\nFees \u0026 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.\nSource code \u0026 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.\nData, accounts \u0026 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.\nSecurity \u0026 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.\nWarranty \u0026 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.\nHandover \u0026 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.\n##  Keep the next step clear.\nTalk through the work, the people and the operating responsibilities before making a commitment.\n[Discuss your project](/contact) [Delivery \u0026 support](/support)\n[Security \u0026 reporting](/security) [Terms \u0026 Conditions](/terms) [Privacy Policy](/privacy) [Cancellation Policy](/cancellation) [Refund Policy](/refund)"}