Service Fulfilment Policy

1. How an engagement begins

An engagement begins when payment is confirmed for a service purchased on this website, or when a written scope of work is accepted. We then contact you to arrange the first session and to request the onboarding information we need.

2. Onboarding information we request

• A named contact and the people who perform the process.
• A description of the process, its inputs, outputs and approximate volumes.
• The systems involved and who controls access to them.
• Whether the process involves personal or sensitive information.
• Any internal approval steps that must be preserved.

3. Scope confirmation

Before implementation begins we issue a written scope covering deliverables, assumptions, exclusions, your responsibilities, the delivery schedule, fees, the payment schedule, review rounds and acceptance criteria. Work starts once that scope is accepted.

4. Delivery channels

Sessions are delivered remotely or at an agreed UAE location. Documents, maps, configuration summaries and operating guides are delivered electronically to the contacts named in the scope. Configured workflows are delivered in the environment named in the scope.

5. Review

Deliverables are submitted for review at the stages set out in the scope. The scope states how many review rounds are included and how long you have to confirm acceptance or raise defects.

6. Indicative and confirmed timelines

Timelines shown on this website are indicative. The confirmed delivery schedule is the one stated in the written scope. Delivery dates may be adjusted where required information, approvals or system access are not provided on time, where a change request is approved, or where a third-party platform we depend on is unavailable or changes.

7. Dependencies and delays

Implementation depends on the access and decisions described in the scope. Where those are delayed we will tell you in writing what the impact on the schedule is, and we will agree a revised date rather than proceed on an assumption.

8. Handover

Handover typically includes a configuration summary, an operating guide, user guidance, access instructions, the support contact path and the change-request process. The exact handover pack is listed in the scope.

9. Completion and acceptance

An engagement is complete when the deliverables in the scope have been delivered and accepted, or when the acceptance period stated in the scope has passed without defects being raised.

10. Ongoing support

Support after handover is provided only where it is included in the scope or purchased as a managed support service. Support hours and response arrangements are stated in the written agreement.

11. Contact

management@axiomora.online · Telephone 052 483 2257