Our new group ERP goes live on 1 January 2027 and becomes the backbone for finance and order-to-cash across all of our companies. It sits in a wider landscape that includes our CRM, a number of operational systems and the reporting layer built on top of them. Once the implementation programme completes, that landscape needs a permanent owner inside Entirely rather than knowledge held largely by our partners and a project organization that stands down.
This role provides that ownership: the systems, the integrations between them, the data that flows through them and the reporting built on top, run reliably and with steadily less manual effort for the people who depend on them.
There is a second reason for the role. Entirely runs several front-end and back-office systems that were each designed for their own company, and decisions about integration, master data and reporting tend to be taken system by system. As the group continues to bring its companies closer together, we need someone holding the target application and data architecture, so that each decision moves us towards a coherent landscape rather than adding another connection to maintain.
Putting the two together in one role is deliberate. The architecture is only useful if the person who sets it also has to live with it, and the systems work is only sustainable if it is heading somewhere.
How we work
Entirely is a lean group. Teams are small, there is no large central function to delegate into, and we roll our sleeves up when a situation calls for it. This is a design and ownership role rather than a configuration role, but you will stay close to the detail: reviewing the work, going into the systems yourself when something needs to be understood properly, and staying near enough to delivery to know whether the design is holding up. Our intention is to own and run our own systems, and to build the internal capability to do that well, with partners supporting where they add specialist skills or capacity. We are looking for someone who moves comfortably between architecture and the practical detail.
The first months
The first months run alongside go-live, so the first priority is a safe cut-over and a stable start to live operation, working closely with Finance and the programme team. Alongside that, the role builds a clear baseline of the landscape: which systems and integrations we run, what each costs in licenses, implementation and support, where the knowledge of how it all works currently sits, and what the target architecture needs to change. From that baseline you agree the sequencing with the COO and the CFO, and you shape the team on evidence rather than assumption.
Responsibilities
What you will own- The target architecture: the application and data architecture for the group's finance and commercial systems, covering integration patterns, master data, reporting and the technical standards new systems are held to. The architecture is developed with the relevant business owners and used to guide technology investment decisions. This is the application and data layer. Infrastructure, cloud platform and identity sit with the Director, Group IT and Cloud Transformation.
- The landscape as one thing: the ERP, the CRM, the operational systems around them and the reporting layer built on top. One technical architecture, with clear accountability for resolving integration and data issues when systems do not agree.
- Order-to-cash systems integrity: the technical transaction path from sales through to the ledger, designed so that it reconciles. This includes idempotent handling, tracked asynchronous states, sensible retry behavior where interfaces fail, and reducing reliance on offline tracking.
- Cut-over and go-live readiness: the configuration baseline, environment strategy across test and production, technical traceability, and validation tooling for opening balances and historical data, so that the numbers are complete, traceable and reconcilable from day one.
- The platform after go-live: release and change control, environment management, configuration integrity, and a support model that does not rely on individual recall of decisions taken during the implementation.
- Master data and data governance: the data models, integration standards and governance mechanisms needed to maintain agreed definitions of customer, contract, product and project across the landscape, implemented consistently in every system that carries them.
- The reporting and data foundation: the data models, pipelines, integrations and reporting platforms behind management reporting, multi-currency consolidation, intercompany processes and tax reporting, producing the numbers consistently, traceably and with less manual assembly.
- The post go-live roadmap: the capability we have deliberately deferred until after go-live, prioritized and delivered on evidence from live operation.
- Vendor and support partnership: acting as our senior technical authority with the ERP vendor and our implementation partners through go-live and beyond, and bringing the knowledge of how our systems work inside the group so that external support becomes a choice rather than a necessity.
- Total cost and knowledge concentration: accountable for the total cost of the business systems landscape, covering licenses, implementation, integration and support, and for where the knowledge of it sits. A clear view of who is paid for what and where the concentration risk lies, established early and kept current.
- Integration playbook for acquired companies: a repeatable approach for bringing a newly acquired company's finance and commercial systems and data into the group landscape, with a realistic timeline and cost that can inform the transaction and the integration plan that follows it.
- Close and reporting enablement: reduce manual systems and data work around month end and ad-hoc reporting by improving integration, automation, data quality and self-service.
- The team: bringing the ERP and CRM capability together under one owner, so that integration is designed as a whole rather than coordinated across separate roles.
- Controls in the systems: system roles, segregation of duties, approval workflows, audit trails and the technical evidence behind them, implemented so that they can be shown to an auditor.
Requirements
How we expect you to work with AIA significant amount of effort across Finance and the business today goes into manual data gathering, reconciliation and analysis. AI can take much of that out, but only where the underlying data, permissions and system controls are dependable, which is why the architecture and the systems belong in the same role. We are looking for agent-assisted reconciliation and exception handling, including ingestion and classification of unstructured financial documents, natural-language access to governed finance and commercial data, documentation and test cases drafted with AI and kept current, and automated regression coverage around each release. AWS is the group's cloud platform, so the AI services there are the natural place to build.
What we are looking for
- Ownership of a major ERP and the business systems landscape around it, through at least one full implementation or migration and then into live operation. The second part matters as much as the first.
- Integration and data architecture depth across a finance and commercial landscape: middleware and API orchestration, event-driven patterns, idempotent transaction design, asynchronous state handling, and the data model underneath all of it.
- Migration and cut-over experience with financial data, including validation frameworks, opening balances and historical ledger integrity.
- NetSuite experience is an advantage. If your depth was built on another platform such as Oracle Fusion, SAP or Dynamics, tell us how you have come up to speed on a new one before and what you did to become technically credible on it quickly.
- Salesforce or comparable CRM integration experience. CPQ and contract data exposure is useful.
- Master data and data architecture across multiple legal entities and currencies, including the technical structures needed to support consolidation, intercompany processes and tax reporting.
- Enough finance fluency to translate requirements into systems, data and integration design across order-to-cash, revenue recognition, FX, intercompany and month-end close. You do not need to be an accountant, but you should be credible to one.
- Evidence of applying AI to real financial or platform work, whether in exception handling, document processing, code, tests or data access for business users.
- Experience as the senior technical authority in a vendor engagement, holding scope, quality and commercials, while building the internal capability to need the vendor less.
- You have contributed the systems and data view to acquisitions, whether in due diligence, integration estimates or the post-deal integration itself.
- A habit of raising risk early and in writing, with a recommendation attached. We have a fixed go-live date, and early visibility helps everyone.
- You stay close to the technical detail and are happy to get into the work when a situation calls for it.
- Working English. German or French is useful across our entities.
Why Entirely
- Shape outcomes, not just outputs — contribute meaningfully to company-level growth goals.
- Work at the frontier of AI-native marketing — build systems that don’t exist anywhere yet.
- Lead across a portfolio of six established products with real customers and real ARR.
- Collaborate across an ecosystem of 400+ professionals, partners, and clients globally.
- Backed by DuMont — a stable, long-term owner with a century of innovation heritage.
- Be the proof point: demonstrate to the world what agentic marketing looks like when it’s done right.