Centry Services
Kings Langley, Hertfordshire
Purpose Lead the move from Legacy Dynamics NAV to a single Microsoft Dynamics 365 Business Central platform for the Pickfords group, then stay on as the owner of the platform you built. In the first year you will architect the solution and deliver it hands-on: the group chart of accounts, the migration strategy, the build, the test cycles and the phased go-lives. Once the group is live, you run and develop what you built: release waves, an improvement roadmap agreed with the businesses, the operational scope, group reporting, and a small team to support it all. Context Pickfords is one of the oldest and best-known names in British moving, with roots in the seventeenth century. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts and dimension design, the financial ledgers across the entities and consolidated group reporting in Power BI, with the first go-live targeted within months of joining. Phase two brings the operational scope onto the platform: job costing and billing, per-job profitability across every business, the integrations to the operational systems that feed the ledgers and the remaining migrations off the Legacy estate. BC SaaS is the preferred target; validating the final tenant and environment architecture is part of mobilisation. The role runs in two chapters. The first, roughly a year, is delivery: leading the re-platforming from mobilisation through phased go-lives and hypercare, hands-on throughout. After that comes ownership. The platform, its roadmap and the team around it are yours, and the group's wider Microsoft estate (Azure data platform, Power BI, a CRM decision on the horizon) grows around them. Team and governance The role reports to the Group Head of Finance, IT & Administration, who runs the programme day to day; the sponsor is the group chief executive and progress runs through a fortnightly steering group. Around the role: group IT, which maintains the Legacy NAV estate and supports extraction and infrastructure; finance superusers in each business, who carry UAT, with business superusers joining for the operational phase; contract development capacity where the plan calls for it; and the incumbent support partner for the live BC environment. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off. This role owns the solution design and the technical delivery, and after go-live it owns the platform. Key responsibilities Leading the re-platforming Own the solution architecture: group chart of accounts, dimension design, company structure, intercompany and consolidation. Validate the target tenant and environment architecture during mobilisation, with BC SaaS as the preferred destination. Own the migration strategy for Pickfords and the other businesses on Legacy NAV, and deliver it end to end: extraction, transformation, opening balance loads and the reconciliations that prove them. Design the interim bridge from the Legacy NAV estate into BC for the period the two systems run alongside each other, with the retirement of NAV planned as a later piece of work. Build hands-on. Lead configuration, data loads, test cycles and cutover through each phased go-live, and write production AL where the plan needs it. Design the integration layer to the group's operational systems and set the development standards: AL extensions only, base application untouched, and environment, release and upgrade management aligned to BC release waves. Work with finance superusers in each business on process design at the platform boundary; agree what BC does and what stays in the systems feeding it. Run each cutover in person: training, floor-walking, first-weeks support and hypercare. Direct any contract development capacity on the programme, and coach the internal people who will support the platform with you. Owning the platform Own the run model: release wave management, environment and permissions management, upgrade testing, and the internal support model. Deliver the operational scope: job costing and billing on BC, per-job profitability across every business, and the integrations to the operational systems that feed the ledgers. Own the reporting architecture: the BC data model, the Azure data estate around it and consolidated group reporting in Power BI. Own the roadmap: a prioritised backlog agreed with Finance and the businesses, delivered in regular drops. Manage the Microsoft estate around BC: ISV partners, CSP licensing, and the partner relationships the group keeps for specialist work. Keep the platform current and controlled: extension compatibility across release waves, permissions and segregation of duties, audit trail, and the controls Finance relies on Essential experience Multiple full-cycle Business Central implementations delivered end to end, led from the finance side, including at least one greenfield chart of accounts and dimension design. A strong NAV and C/AL background combined with BC SaaS implementation experience; the Legacy estate is heavily customised NAV on-prem and the target is SaaS. Data migration ownership on at least one implementation, from Legacy extraction through reconciled opening balances. BC finance configuration in depth: posting groups and setups, dimensions, journals, approvals, permissions and the core sales, purchase and finance flows. Integration design: APIs and OData, and at least one delivered interface to a non-Microsoft operational system. Production AL: enough to set extension standards, review all code and write production AL yourself, with source control and controlled deployment through sandbox and production environments. Power BI against ERP data: able to define the BC data model and reporting architecture and build hands-on where needed. Experience of running a BC platform after go-live: release wave management, support, upgrades and continuous improvement. Able to explain technical and data issues clearly to finance users and senior stakeholders, in person and in writing. Why this role This is an end-user platform role with direct access to the day-to-day decision-maker and clear design authority. The mandate is approved and sponsored by the group's chief executive, and progress runs through a steering group. The design is mainly greenfield: a new group chart of accounts, a clean company structure and a phased rollout across the group's businesses, with the first go-live targeted within months of joining. The design decisions you make in the first year are yours to refine and build on: job costing and billing, per-job profitability across the group, the integration layer, group reporting, and the wider Microsoft estate growing around BC. There is scope to shape and lead a small in-house BC team as the platform matures. Pickfords has been moving Britain for centuries, and this is the moment it moves onto a modern cloud platform.
Purpose Lead the move from Legacy Dynamics NAV to a single Microsoft Dynamics 365 Business Central platform for the Pickfords group, then stay on as the owner of the platform you built. In the first year you will architect the solution and deliver it hands-on: the group chart of accounts, the migration strategy, the build, the test cycles and the phased go-lives. Once the group is live, you run and develop what you built: release waves, an improvement roadmap agreed with the businesses, the operational scope, group reporting, and a small team to support it all. Context Pickfords is one of the oldest and best-known names in British moving, with roots in the seventeenth century. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts and dimension design, the financial ledgers across the entities and consolidated group reporting in Power BI, with the first go-live targeted within months of joining. Phase two brings the operational scope onto the platform: job costing and billing, per-job profitability across every business, the integrations to the operational systems that feed the ledgers and the remaining migrations off the Legacy estate. BC SaaS is the preferred target; validating the final tenant and environment architecture is part of mobilisation. The role runs in two chapters. The first, roughly a year, is delivery: leading the re-platforming from mobilisation through phased go-lives and hypercare, hands-on throughout. After that comes ownership. The platform, its roadmap and the team around it are yours, and the group's wider Microsoft estate (Azure data platform, Power BI, a CRM decision on the horizon) grows around them. Team and governance The role reports to the Group Head of Finance, IT & Administration, who runs the programme day to day; the sponsor is the group chief executive and progress runs through a fortnightly steering group. Around the role: group IT, which maintains the Legacy NAV estate and supports extraction and infrastructure; finance superusers in each business, who carry UAT, with business superusers joining for the operational phase; contract development capacity where the plan calls for it; and the incumbent support partner for the live BC environment. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off. This role owns the solution design and the technical delivery, and after go-live it owns the platform. Key responsibilities Leading the re-platforming Own the solution architecture: group chart of accounts, dimension design, company structure, intercompany and consolidation. Validate the target tenant and environment architecture during mobilisation, with BC SaaS as the preferred destination. Own the migration strategy for Pickfords and the other businesses on Legacy NAV, and deliver it end to end: extraction, transformation, opening balance loads and the reconciliations that prove them. Design the interim bridge from the Legacy NAV estate into BC for the period the two systems run alongside each other, with the retirement of NAV planned as a later piece of work. Build hands-on. Lead configuration, data loads, test cycles and cutover through each phased go-live, and write production AL where the plan needs it. Design the integration layer to the group's operational systems and set the development standards: AL extensions only, base application untouched, and environment, release and upgrade management aligned to BC release waves. Work with finance superusers in each business on process design at the platform boundary; agree what BC does and what stays in the systems feeding it. Run each cutover in person: training, floor-walking, first-weeks support and hypercare. Direct any contract development capacity on the programme, and coach the internal people who will support the platform with you. Owning the platform Own the run model: release wave management, environment and permissions management, upgrade testing, and the internal support model. Deliver the operational scope: job costing and billing on BC, per-job profitability across every business, and the integrations to the operational systems that feed the ledgers. Own the reporting architecture: the BC data model, the Azure data estate around it and consolidated group reporting in Power BI. Own the roadmap: a prioritised backlog agreed with Finance and the businesses, delivered in regular drops. Manage the Microsoft estate around BC: ISV partners, CSP licensing, and the partner relationships the group keeps for specialist work. Keep the platform current and controlled: extension compatibility across release waves, permissions and segregation of duties, audit trail, and the controls Finance relies on Essential experience Multiple full-cycle Business Central implementations delivered end to end, led from the finance side, including at least one greenfield chart of accounts and dimension design. A strong NAV and C/AL background combined with BC SaaS implementation experience; the Legacy estate is heavily customised NAV on-prem and the target is SaaS. Data migration ownership on at least one implementation, from Legacy extraction through reconciled opening balances. BC finance configuration in depth: posting groups and setups, dimensions, journals, approvals, permissions and the core sales, purchase and finance flows. Integration design: APIs and OData, and at least one delivered interface to a non-Microsoft operational system. Production AL: enough to set extension standards, review all code and write production AL yourself, with source control and controlled deployment through sandbox and production environments. Power BI against ERP data: able to define the BC data model and reporting architecture and build hands-on where needed. Experience of running a BC platform after go-live: release wave management, support, upgrades and continuous improvement. Able to explain technical and data issues clearly to finance users and senior stakeholders, in person and in writing. Why this role This is an end-user platform role with direct access to the day-to-day decision-maker and clear design authority. The mandate is approved and sponsored by the group's chief executive, and progress runs through a steering group. The design is mainly greenfield: a new group chart of accounts, a clean company structure and a phased rollout across the group's businesses, with the first go-live targeted within months of joining. The design decisions you make in the first year are yours to refine and build on: job costing and billing, per-job profitability across the group, the integration layer, group reporting, and the wider Microsoft estate growing around BC. There is scope to shape and lead a small in-house BC team as the platform matures. Pickfords has been moving Britain for centuries, and this is the moment it moves onto a modern cloud platform.
Centry Services
Kings Langley, Hertfordshire
Location London & Kings Langley 3 days in office and 2 days hybrid; travel to group sites around cutovers Purpose Architect a single Microsoft Dynamics 365 Business Central platform for a multi-entity UK group and lead the technical side of the deployment through build, testing and into production. The work runs on two tracks: refine the live BC environment of the entity already on the platform, and design the new build for the businesses still on legacy Dynamics NAV, including the migration strategy that gets them there. Context Centry Services Group comprises four trading businesses in moving, relocation and related services, plus an overseas shared service centre running finance processing on the legacy estate. The largest business runs a heavily customised on-premises NAV 2009 R2 system across finance and operations; one entity's financials are already live on Business Central SaaS in its own tenant, with an Azure Data Factory and Power BI estate around it. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts, the financial ledgers across the entities and consolidated group reporting in Power BI, targeted at three months subject to validation during mobilisation and discovery. Phase two covers the operational scope (job costing and billing, the integrations to the operational systems that feed the ledgers, and the remaining migrations off the legacy estate) over a further three to six months depending on design and complexity. BC SaaS is the preferred target; validating the final tenant and environment architecture is part of mobilisation. Entity user counts and the integration inventory are being compiled and will be shared with shortlisted candidates. Team and governance The role reports to the Group Head of Finance, IT & Administration, who runs the programme day to day; the sponsor is the group chief executive and progress runs through a steering group. Around the role: a BC consultant-developer recruited in parallel; group IT, which maintains the legacy NAV estate and supports extraction and infrastructure; and finance superusers in each business, who carry UAT, with business superusers joining for phase two. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off; this role owns the solution design and the technical delivery within that frame. Key responsibilities Own the solution architecture: group chart of accounts, dimension design, company structure, intercompany and consolidation. Bring the live BC entity onto the group design through a controlled migration: a new company on the group chart of accounts, cut over at a period end and reconciled to Group Finance sign-off. Own the migration strategy for the businesses on legacy NAV and deliver it end to end: extraction, transformation, opening balance loads and reconciliations through to Group Finance sign-off. Build hands-on. Lead configuration, test cycles and cutover through each phased go-live alongside a mid-level consultant-developer, who carries the bulk of AL development; this role designs and then delivers, it does not hand drawings to others. Design the integration layer to the group's operational systems and set the development standards: AL extensions only, no base-code modification, and environment, release and upgrade management aligned to BC release waves. Work with finance superusers in each business on process design at the platform boundary; agree what BC does and what stays in the systems feeding it. Coach the consultant-developer and shape the team as it grows, including any third hire at the operational phase (phase two). Design the run model for handover: update cadence, permissions model, environment management and the internal support model, documented and transferred to the permanent support team before contract end. Essential experience Multiple full-cycle Business Central implementations delivered end to end, led from the finance side, including at least one greenfield chart of accounts and dimension design. A strong NAV and C/AL background combined with BC SaaS implementation experience; the legacy estate is heavily customised NAV on-prem and the target is SaaS. Data migration ownership on at least one implementation, from legacy extraction through reconciled opening balances. Multi-company configuration: intercompany, consolidation and group reporting structures. Integration design: APIs and OData, and at least one delivered interface to a non-Microsoft operational system. Working AL knowledge: enough to set extension standards, review all code and write production AL when needed. Power BI against ERP data: able to define the BC data model and reporting architecture and build hands-on where needed; consolidated group reporting lands in Power BI in phase one. Desirable Personally led an end-to-end NAV (or on-prem BC) to BC SaaS migration. Familiarity with the wider Microsoft data estate: Azure Data Factory and data lake patterns. Sector exposure to job-costed or project-based businesses (removals, logistics, construction, field services). Why this role This is an end-user platform role, not a partner consultancy seat, with direct access to the day-to-day decision-maker and clear design authority. The mandate is approved and sponsored by the group's chief executive. The design is mainly greenfield: a new group chart of accounts, a clean company structure, and a phased rollout across the group's trading businesses, with the first go-live targeted within months of joining.
Location London & Kings Langley 3 days in office and 2 days hybrid; travel to group sites around cutovers Purpose Architect a single Microsoft Dynamics 365 Business Central platform for a multi-entity UK group and lead the technical side of the deployment through build, testing and into production. The work runs on two tracks: refine the live BC environment of the entity already on the platform, and design the new build for the businesses still on legacy Dynamics NAV, including the migration strategy that gets them there. Context Centry Services Group comprises four trading businesses in moving, relocation and related services, plus an overseas shared service centre running finance processing on the legacy estate. The largest business runs a heavily customised on-premises NAV 2009 R2 system across finance and operations; one entity's financials are already live on Business Central SaaS in its own tenant, with an Azure Data Factory and Power BI estate around it. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts, the financial ledgers across the entities and consolidated group reporting in Power BI, targeted at three months subject to validation during mobilisation and discovery. Phase two covers the operational scope (job costing and billing, the integrations to the operational systems that feed the ledgers, and the remaining migrations off the legacy estate) over a further three to six months depending on design and complexity. BC SaaS is the preferred target; validating the final tenant and environment architecture is part of mobilisation. Entity user counts and the integration inventory are being compiled and will be shared with shortlisted candidates. Team and governance The role reports to the Group Head of Finance, IT & Administration, who runs the programme day to day; the sponsor is the group chief executive and progress runs through a steering group. Around the role: a BC consultant-developer recruited in parallel; group IT, which maintains the legacy NAV estate and supports extraction and infrastructure; and finance superusers in each business, who carry UAT, with business superusers joining for phase two. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off; this role owns the solution design and the technical delivery within that frame. Key responsibilities Own the solution architecture: group chart of accounts, dimension design, company structure, intercompany and consolidation. Bring the live BC entity onto the group design through a controlled migration: a new company on the group chart of accounts, cut over at a period end and reconciled to Group Finance sign-off. Own the migration strategy for the businesses on legacy NAV and deliver it end to end: extraction, transformation, opening balance loads and reconciliations through to Group Finance sign-off. Build hands-on. Lead configuration, test cycles and cutover through each phased go-live alongside a mid-level consultant-developer, who carries the bulk of AL development; this role designs and then delivers, it does not hand drawings to others. Design the integration layer to the group's operational systems and set the development standards: AL extensions only, no base-code modification, and environment, release and upgrade management aligned to BC release waves. Work with finance superusers in each business on process design at the platform boundary; agree what BC does and what stays in the systems feeding it. Coach the consultant-developer and shape the team as it grows, including any third hire at the operational phase (phase two). Design the run model for handover: update cadence, permissions model, environment management and the internal support model, documented and transferred to the permanent support team before contract end. Essential experience Multiple full-cycle Business Central implementations delivered end to end, led from the finance side, including at least one greenfield chart of accounts and dimension design. A strong NAV and C/AL background combined with BC SaaS implementation experience; the legacy estate is heavily customised NAV on-prem and the target is SaaS. Data migration ownership on at least one implementation, from legacy extraction through reconciled opening balances. Multi-company configuration: intercompany, consolidation and group reporting structures. Integration design: APIs and OData, and at least one delivered interface to a non-Microsoft operational system. Working AL knowledge: enough to set extension standards, review all code and write production AL when needed. Power BI against ERP data: able to define the BC data model and reporting architecture and build hands-on where needed; consolidated group reporting lands in Power BI in phase one. Desirable Personally led an end-to-end NAV (or on-prem BC) to BC SaaS migration. Familiarity with the wider Microsoft data estate: Azure Data Factory and data lake patterns. Sector exposure to job-costed or project-based businesses (removals, logistics, construction, field services). Why this role This is an end-user platform role, not a partner consultancy seat, with direct access to the day-to-day decision-maker and clear design authority. The mandate is approved and sponsored by the group's chief executive. The design is mainly greenfield: a new group chart of accounts, a clean company structure, and a phased rollout across the group's trading businesses, with the first go-live targeted within months of joining.
Centry Services
Kings Langley, Hertfordshire
Location London & Kings Langley 3 days in office and 2 days hybrid; travel to group sites around cutovers Purpose Build and configure Microsoft Dynamics 365 Business Central across a multi-entity UK group, working to an architecture set by a hands-on lead solution architect. Carry configuration, data loads, interfaces and testing through phased go-lives, provide hypercare at each cutover, and hand the platform to the permanent support team before contract end. Context Centry Services Group comprises four trading businesses in moving, relocation and related services, plus an overseas shared service centre running finance processing on the legacy estate. The largest business runs a heavily customised on-premises NAV 2009 R2 system across finance and operations; one entity's financials are already live on Business Central SaaS in its own tenant, with an Azure Data Factory and Power BI estate around it. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts, the financial ledgers across the entities and consolidated group reporting in Power BI, targeted at three months subject to validation during mobilisation and discovery. Phase two covers the operational scope (job costing and billing, the integrations to the operational systems that feed the ledgers, and the remaining migrations off the legacy estate) over a further three to six months depending on design and complexity. BC SaaS is the preferred target; the lead solution architect validates the final tenant and environment architecture during mobilisation. Entity user counts and the integration inventory are being compiled and will be shared with shortlisted candidates. Team and governance The role reports to the Group Head of Finance, IT & Administration and takes day-to-day direction from the lead solution architect, recruited in parallel. Around the role: group IT, which maintains the legacy NAV estate and supports extraction and infrastructure, and finance superusers in each business, who carry UAT, with business superusers joining for phase two. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off. Key responsibilities Configure BC companies from the group template: posting setups, number series, journals, approval workflows and user permissions. Run data loads: configuration packages, master data, opening balances, and the reconciliation work that proves them through to Group Finance sign-off. Carry the bulk of AL development to the standards set by the lead solution architect: interim interfaces to the legacy NAV estate, integrations to the operational systems, and extensions where standard BC falls short. Run test cycles to the lead solution architect's plan: prepare scripts, support superuser-led UAT in each business, fix defects and retest. Support cutovers in person: training, floor-walking and first-week support at each go-live. Provide hypercare after each go-live and build the handover: support documentation, interface runbooks and knowledge transfer to the permanent support team before contract end. Essential experience At least two years' hands-on Business Central delivery, with practical competence in both finance configuration and AL development; candidates may lean functional or technical but must work independently in both. BC finance configuration: posting groups and setups, dimensions, journals, approvals, permissions and the core sales, purchase and finance flows. Production AL delivery: VS Code, extensions and events, APIs, OData or web services, debugging, source control and controlled deployment through sandbox and production environments. At least one full implementation or major rollout from build through go-live. Hands-on data migration using configuration packages; RapidStart experience from NAV or earlier BC versions counts. Able to explain technical and data issues clearly to finance users, in person and in writing. Desirable A NAV and C/AL background, including experience transitioning legacy customisations to AL extensions. A delivered interface to a non-Microsoft operational system. Power BI report building against BC data. AP automation ISVs (Continia or similar). Jobs, projects or costing module experience. Why this role This is an end-user platform role, not a partner consultancy seat. The mandate is approved and sponsored by the group's chief executive, the architecture is set by a hands-on lead, and the work is build, load, test and cutover from week one. The rollout is phased across the group's trading businesses, with the first go-live targeted within months of joining.
Location London & Kings Langley 3 days in office and 2 days hybrid; travel to group sites around cutovers Purpose Build and configure Microsoft Dynamics 365 Business Central across a multi-entity UK group, working to an architecture set by a hands-on lead solution architect. Carry configuration, data loads, interfaces and testing through phased go-lives, provide hypercare at each cutover, and hand the platform to the permanent support team before contract end. Context Centry Services Group comprises four trading businesses in moving, relocation and related services, plus an overseas shared service centre running finance processing on the legacy estate. The largest business runs a heavily customised on-premises NAV 2009 R2 system across finance and operations; one entity's financials are already live on Business Central SaaS in its own tenant, with an Azure Data Factory and Power BI estate around it. The programme consolidates the group onto one BC platform in two phases. Phase one delivers the group chart of accounts, the financial ledgers across the entities and consolidated group reporting in Power BI, targeted at three months subject to validation during mobilisation and discovery. Phase two covers the operational scope (job costing and billing, the integrations to the operational systems that feed the ledgers, and the remaining migrations off the legacy estate) over a further three to six months depending on design and complexity. BC SaaS is the preferred target; the lead solution architect validates the final tenant and environment architecture during mobilisation. Entity user counts and the integration inventory are being compiled and will be shared with shortlisted candidates. Team and governance The role reports to the Group Head of Finance, IT & Administration and takes day-to-day direction from the lead solution architect, recruited in parallel. Around the role: group IT, which maintains the legacy NAV estate and supports extraction and infrastructure, and finance superusers in each business, who carry UAT, with business superusers joining for phase two. Data cleansing sits with the businesses. Group Finance owns accounting policy, data quality, UAT acceptance and financial sign-off. Key responsibilities Configure BC companies from the group template: posting setups, number series, journals, approval workflows and user permissions. Run data loads: configuration packages, master data, opening balances, and the reconciliation work that proves them through to Group Finance sign-off. Carry the bulk of AL development to the standards set by the lead solution architect: interim interfaces to the legacy NAV estate, integrations to the operational systems, and extensions where standard BC falls short. Run test cycles to the lead solution architect's plan: prepare scripts, support superuser-led UAT in each business, fix defects and retest. Support cutovers in person: training, floor-walking and first-week support at each go-live. Provide hypercare after each go-live and build the handover: support documentation, interface runbooks and knowledge transfer to the permanent support team before contract end. Essential experience At least two years' hands-on Business Central delivery, with practical competence in both finance configuration and AL development; candidates may lean functional or technical but must work independently in both. BC finance configuration: posting groups and setups, dimensions, journals, approvals, permissions and the core sales, purchase and finance flows. Production AL delivery: VS Code, extensions and events, APIs, OData or web services, debugging, source control and controlled deployment through sandbox and production environments. At least one full implementation or major rollout from build through go-live. Hands-on data migration using configuration packages; RapidStart experience from NAV or earlier BC versions counts. Able to explain technical and data issues clearly to finance users, in person and in writing. Desirable A NAV and C/AL background, including experience transitioning legacy customisations to AL extensions. A delivered interface to a non-Microsoft operational system. Power BI report building against BC data. AP automation ISVs (Continia or similar). Jobs, projects or costing module experience. Why this role This is an end-user platform role, not a partner consultancy seat. The mandate is approved and sponsored by the group's chief executive, the architecture is set by a hands-on lead, and the work is build, load, test and cutover from week one. The rollout is phased across the group's trading businesses, with the first go-live targeted within months of joining.