Build Operate Transfer for CPG: IT Delivery Center Guide
CPG companies have two large, permanent IT demands that pull in different directions. On the commercial side, Salesforce estates covering Sales Cloud, Marketing Cloud, and increasingly Data Cloud and Agentforce require constant configuration, development, and integration work. On the operational side, SAP S/4HANA — covering demand planning, trade management, logistics, and finance — generates continuous enhancement and support requirements. Both demand specialist engineers. Neither is a project that ends.
The Build Operate Transfer (BOT) model builds a delivery center that covers both. A single BOT center serving a CPG company can staff a Salesforce center of excellence alongside an SAP functional team, with a data engineering cohort connecting the two platforms. The provider manages the operational overhead — HR, payroll, office, compliance. The client directs the work and, at Transfer, owns the team outright.
Below: how BOT delivery centers work for CPG IT, covering commercial operations, SAP, data engineering, and the CPG commercial context.
Why CPG IT Is a Strong BOT Match
CPG companies fit the BOT model for three structural reasons.
Commercial operations is a permanent IT function, not a project. A Salesforce Sales Cloud implementation at a CPG company generating €2B in revenue serves thousands of field sales reps, trade marketing managers, and key account teams across multiple markets. The platform needs constant configuration: new promotion types, pricing rules, reporting changes, integration updates with SAP and trade promotion systems. This work does not stop. A rotating contractor pool that turns over every 12–18 months cannot accumulate the Salesforce data model knowledge or the commercial process understanding required to do this work well.
The talent cost gap is significant. A senior Salesforce architect with CPG domain experience — trade promotion, revenue growth management, D2C — earns €90,000–€130,000 in Germany, the Netherlands, or the UK. In Romania, the equivalent profile earns €55,000–€80,000. For a center of 8–12 Salesforce and SAP engineers, the annual saving at Transfer is €300,000–€500,000 compared to Western European direct employment.
CPG companies expanding into direct-to-consumer channels — online stores, subscription platforms, loyalty programs — are running 3–5 year transformation agendas. A BOT center accumulates the knowledge of the D2C platform, the Salesforce integration, and the data architecture through the full program and transfers it to the client as an owned asset.
Systems Covered in a CPG BOT Center
| System category | Technologies | CPG use case |
|---|---|---|
| Commercial CRM | Salesforce Sales Cloud, Service Cloud, CPQ | Field sales, key account management, trade terms, order management |
| Marketing automation | Salesforce Marketing Cloud, Data Cloud, Agentforce | Consumer campaigns, loyalty programs, personalisation |
| Trade management | SAP Trade Management (TPM), Vistex, Blacksmith | Trade promotion planning, settlement, ROI analysis |
| ERP | SAP S/4HANA (SD, MM, PP, TM, FI/CO) | Order-to-cash, procurement, demand planning, logistics, finance |
| Demand planning | SAP IBP, SAP APO | Statistical forecasting, collaborative planning, S&OP |
| Data & Analytics | Databricks, Snowflake, Power BI, dbt | Revenue growth management, promotion analytics, retailer scorecards |
| D2C / e-commerce | Salesforce Commerce Cloud, Shopify Plus, custom APIs | Direct consumer channels, subscription, loyalty |
| Data integration | MuleSoft, Azure Integration Services, Boomi | SAP/Salesforce integration, retailer EDI, 3PL connectivity |
Salesforce Center of Excellence for CPG
Salesforce is the primary commercial operations platform for most large CPG companies. The Salesforce estate in a CPG business typically spans:
- Sales Cloud: field force management, opportunity tracking, account planning, route-to-market
- CPQ (Configure, Price, Quote): trade pricing, promotional pricing rules, contract management
- Service Cloud: consumer affairs, trade customer service, returns management
- Marketing Cloud: consumer-facing campaigns, loyalty programs, email and SMS automation
- Data Cloud: consumer data platform, first-party data unification, segment activation
- MuleSoft: integration platform connecting Salesforce to SAP, retailer EDI, and digital commerce
Roles in a CPG Salesforce CoE
- Salesforce Architect: platform design, integration architecture, release governance
- Apex Developer: custom server-side logic, integration services, Salesforce APIs
- LWC Developer: custom Lightning Web Components for field sales and trade marketing UIs
- Marketing Cloud Specialist: Journey Builder, Email Studio, Audience Builder, AMPscript
- Data Cloud Engineer: data stream configuration, identity resolution, segment building
- CPQ Specialist: pricing rules, quote templates, contract lifecycle
- Salesforce Administrator: configuration, user management, reports, standard customisation
A CPG Salesforce CoE of 8–10 people can cover all of these roles with appropriate seniority distribution. The minimum viable team for ongoing Salesforce development and administration without single points of failure is 6 people.
SAP for CPG: Demand, Trade, and Logistics
CPG companies typically run SAP SD, MM, and FI/CO as their transactional backbone, with SAP IBP (Integrated Business Planning) for demand planning and S&OP. SAP Trade Management or third-party TPM systems handle trade promotion, which in CPG can represent 15–25% of gross revenue.
Key SAP roles in CPG BOT centers
- SAP SD Consultant: order management, pricing, billing, rebate processing, returns
- SAP MM Consultant: procurement, materials management, consignment, vendor management
- SAP IBP Consultant: statistical forecasting, demand planning, S&OP, supply planning
- SAP Trade Management Consultant: promotion planning, funds management, settlement
- ABAP Developer: custom reports, enhancements, interfaces to Salesforce and TPM systems
- SAP BW/BI Developer: financial and commercial reporting, promotion analytics
SAP-Salesforce integration
The integration between SAP and Salesforce is a permanent operational requirement in CPG: orders from Salesforce must flow to SAP for fulfilment; pricing from SAP must flow to Salesforce CPQ; promotion accruals from SAP must be visible to trade marketing in Salesforce. This integration layer — typically implemented in MuleSoft, Azure Integration Services, or custom middleware — requires engineers who understand both platforms. BOT centers staffed with SAP and Salesforce expertise in the same location handle this integration more effectively than two separate outsourced teams working through ticket systems.
Data & Analytics for CPG
CPG analytics has shifted toward revenue growth management (RGM) — understanding which promotions, pack sizes, prices, and channels generate profitable volume. This requires a data infrastructure that integrates SAP sell-out data, retailer EPOS data, Nielsen/Kantar market data, and Salesforce promotion data into a single analytical layer.
A CPG data engineering BOT cohort:
| Layer | Technologies | CPG use case |
|---|---|---|
| Ingestion | Fivetran, Airbyte, custom SAP extractors, retailer SFTP | SAP data, retailer EPOS, panel data, promotion plans |
| Processing | Databricks, dbt, Snowflake | Promotion ROI, baseline/incremental split, market share |
| Consumption | Power BI, Looker, Tableau | RGM dashboards, retailer scorecards, promotion reporting |
| Governance | Collibra, Great Expectations | Product master data, hierarchy management, data quality |
A 4–6 person data engineering cohort within a larger CPG BOT center covers ingestion, transformation, and BI development. A standalone data BOT center of 8–10 people covers the full stack including data governance and self-service analytics enablement.
Cost Benchmarks
Indicative monthly per-head BOT rates for a CPG IT delivery center in Romania:
| Role | Romania gross salary (€/month) | BOT per-head rate (est.) |
|---|---|---|
| Salesforce Architect | €5,000–€8,000 | €6,500–€10,400 |
| Apex / LWC Developer (senior) | €4,000–€6,500 | €5,200–€8,500 |
| Marketing Cloud Specialist | €3,800–€6,000 | €5,000–€7,800 |
| SAP SD/MM Consultant (senior) | €4,000–€6,000 | €5,200–€7,800 |
| SAP IBP Consultant (senior) | €4,500–€7,000 | €5,800–€9,100 |
| ABAP Developer (senior) | €4,000–€6,500 | €5,200–€8,500 |
| Data Engineer (Databricks/Snowflake) | €4,500–€7,000 | €5,800–€9,100 |
| Power BI Developer | €3,500–€5,500 | €4,600–€7,200 |
Build Phase for CPG IT Centers
Salesforce releases three major updates per year. A Salesforce CoE requires engineers who hold current certifications and maintain them. The BOT employment framework should specify certification maintenance as an employer obligation, including funding for Salesforce Trailhead and exam costs.
Salesforce and SAP engineers who do not understand CPG commercial processes — trade terms, promotional mechanics, route-to-market structures — require significant ramp-up. The Build phase should include structured business context sessions covering how trade promotions work, how the sales force is structured, what the pricing architecture looks like, and how SAP and Salesforce interact. Engineers with prior CPG sector exposure should be prioritised in the sourcing brief.
CPG data — retailer performance data, promotional data, consumer data — is commercially sensitive. Data governance and handling policies must be agreed before the first engineer starts, not retrofitted once the team is operational.
Revenue Growth Management and D2C
Revenue Growth Management
RGM is the discipline of using pricing, promotion, pack architecture, and channel mix to maximise profitable revenue. The IT requirements for RGM programs are significant: integrating retailer EPOS data (often arriving as Excel files or EDI), building promotion baseline models, running pack-price elasticity analysis, and creating reporting that trade marketing and commercial finance teams can use without data science support.
BOT centers covering RGM analytics are built around data engineers who can operationalise these models in Databricks or Snowflake, and analytics engineers who can surface them in Power BI or Looker in forms that non-technical commercial users can work with.
D2C and E-commerce
CPG D2C programs — direct-to-consumer e-commerce, subscription, loyalty — require Salesforce Commerce Cloud development, Salesforce Marketing Cloud for lifecycle marketing, and data engineering for consumer data unification. The BOT model is well-suited to D2C because the program is multi-year (3–5 years to reach operating scale) and requires permanent embedded engineering, not a project team that exits at go-live.
Frequently Asked Questions
Can a BOT center serve both the Salesforce and SAP functions for a CPG company?
Yes, and this is the most common structure for CPG BOT centers. A center of 15–20 people splits across a Salesforce CoE (6–8 people), an SAP functional team (5–7 people), and a data engineering cohort (3–5 people). The co-location of these teams — engineers who cover SAP SD and engineers who build Salesforce integrations sitting in the same office — improves integration quality. Issues at the SAP-Salesforce boundary are resolved faster when the engineers can talk directly rather than through a ticket system across different outsourcing contracts.
How does Salesforce certification maintenance work in a BOT center?
The BOT employment framework should specify: certification maintenance as a condition of employment for designated roles, employer funding for Trailhead credits and certification exams (approximately €200–€400 per exam), and a minimum certification coverage requirement (e.g., every Salesforce developer holds at minimum Platform Developer I). Three Salesforce releases per year require active tracking of deprecated features and mandatory updates — a center without a structured certification and release management process will accumulate technical debt on the platform.
What is the right split between Salesforce architects, developers, and administrators in a CPG CoE?
For a CPG Salesforce CoE of 8 people, a typical structure is: 1 architect, 3 Apex/LWC developers, 1 Marketing Cloud specialist, 1 Data Cloud/integration engineer, 1 CPQ specialist, 1 administrator. The architect carries the release governance and integration design function. As the center grows to 12–15 people, a second architect or a dedicated delivery lead is added. The ratio of developers to administrators shifts toward more developers as the platform matures and standard configuration work decreases.
How are retailer EPOS data and panel data handled in a CPG analytics center?
Retailer EPOS data — weekly sell-out from major grocery retailers — arrives in multiple formats: EDI, SFTP flat files, retailer portal downloads, direct API (increasingly common with large retailers). The data engineering team builds ingestion pipelines for each retailer's format. Panel data from Nielsen or Kantar arrives in proprietary formats (dunnhumby, IRI) that require format-specific parsers. A data engineer with CPG analytics experience has dealt with these formats before — this is a CPG domain skill, not a general data engineering skill. Sourcing engineers with CPG analytics background in the recruitment brief significantly reduces ramp-up time.
How long does a CPG BOT center take to reach full productivity?
A Salesforce developer with no prior CPG domain exposure requires 2–3 months to reach full productivity on a CPG estate. An engineer with prior CPG Salesforce experience reaches productivity in 4–6 weeks. For SAP SD or IBP, the domain ramp-up is similar: 2–3 months for a general SAP consultant, 4–6 weeks for someone with CPG or FMCG sector background. The Build phase knowledge transfer program — covering commercial process, system architecture, and data model — compresses ramp-up. Teams that skip structured onboarding spend the first quarter of the Operate phase correcting misunderstandings rather than delivering.