Client Onboarding

Horizon manages projects based on the PRINCE2 method

Client requirements are gathered into a predefined Business Requirement Document (BRD) shared with the Product Team and the client’s Management Team. The BRD includes a detailed description of functional and technical customer requirements, a description of the customer's business workflows and a diagram illustrating the target platform.
Following customer approval of the BRD, the Client Service Management (CSM) team determines the total required effort, with subsets of tasks and related effort.
Project Definition – Based on the set of defined products, the Project Manager (PM) creates a Project Definition (PDEF) with relevant information, including project objectives, scope, the team involved, and hardware requirements. The PDEF also facilitates task planning (in Monday.com) to produce a Project GANTT and related tools.

Pre-sales handover – Once the project is contracted, pre-sales organizes an internal Kick-Off Meeting with all stakeholders to provide required details.
Project requirements – a Project Manager (CSM) prepares a Kick-Off Meeting (KOM) document summarizing project aim, business case, roles and responsibilities, high-level timeline and scope, and project governance.

Technical implementation – The CSM breaks down the technical build into work packages and allocates them to the Implementation Team to start the build. As the build progresses, the Implementation Team updates the PM and raises any issues. Work packages are tracked using JIRA Tickets.
Continuous project reporting – The CSM submits periodic progress updates to the Project Board, using a set of predefined reports.
Go Live phase – During this final step, the PM organizes a production-readiness meeting with the client to ensure that the product requirements and the project plan have been fulfilled.

Segments