A six-week workshop programme that prepares the organisation for a PIM implementation. We train the team, map the processes, and design the data model, the integrations and the workflow. At the end you receive a full set of documentation and an implementation quote based on an agreed scope.
Why a programme before the project
They fall over on the organisation: the data model is undefined, roles and responsibilities are unclear, and individual departments hold expectations that nobody put side by side before the start. What follows is a run of redesigns mid-project, and every one of them costs more than settling the same question in a workshop.
PIM Starter takes those risks off the table before the implementation itself begins. Over six weeks we walk the organisation through a structured programme: we train the team, map the processes, and design the data model and the integration architecture. Only on that basis is a quote written, and only then does it stand a chance of holding to the end of the project.
In short: a process project before the system project.
What the programme changes
Each of them is a standard source of delay in a PIM project. The programme resolves them in a workshop, where they cost nothing but time.
Skills
We train everyone who will work with the system: production, marketing, sales, e-commerce, IT and logistics. After the programme every department understands what a PIM system does, and can state its own requirements in language that can be costed.
System choice
We show Akeneo, Ergonode and Pimcore on working installations, not on sales decks. The recommendation follows from your catalogue, your number of markets and your team, not from vendor material.
Budget
We price the implementation only once the data model, the integration list and the workflow have been approved together. That is the difference between an estimate and a range guessed before any analysis.
Risk
A prepared team means fewer redesigns during delivery. It rules out the scenario where a department nobody invited at the start turns up near the end and wants everything done differently.
Programme
Each week has one goal and ends in a specific document. The schedule is indicative: the final dates are set once the contract is signed.
Week 1
We build a shared vocabulary. Akeneo, Ergonode and Pimcore are shown live, from every department’s point of view, and we collect what the whole organisation expects. You leave with expectations and challenges listed per department, an early system preference, plus the materials and a recording of the workshop.
Week 2
We map how product data moves today: from the source, meaning the ERP, spreadsheets and shared drives, through to publication in sales channels. Operational problems and bottlenecks get named. Output: an as-is process diagram, a prioritised list of problems and a RACI matrix of roles and responsibilities.
Week 3
We design the data model on your real products: templates, attributes, categories, variants and language versions. Output: the data model in a spreadsheet plus a sample product structure broken down into attribute groups.
Week 4
We design the system architecture with the PIM at its centre: flows from the ERP into the PIM and onward to sales channels, the role of middleware, the demands placed on each API. Output: an architecture diagram and a prioritised list of required integrations, each with its data flow described.
Week 5
We design the product workflow: statuses, transitions, permissions per department, validation rules and notifications. What we model is the process the company actually runs, not the one in the documentation. Output: a workflow diagram, a permissions matrix and a list of automated actions.
Week 6
We prioritise the implementation scope: must-have against nice-to-have. The quote is reviewed and approved, and the schedule agreed. Output: an agreed MVP scope, a schedule with milestones and a quote broken down by role and task.
The programme in numbers
From the first workshop to an approved quote
Online, one a week, with your own work in between
In the final pack, in formats you can keep working in
Remote, with no cap on participants on your side
Deliverables
Eight documents, each in a format you can keep working in. They stay with you whoever ends up running the implementation.
| Document | Format | Contents |
|---|---|---|
| PIM Starter report | The complete pre-implementation analysis: current state, target model and a system recommendation with the reasoning behind it. | |
| Data model | Spreadsheet | Attributes, templates and categories, ready to be extended during the implementation. |
| Process model | BPMN | Product data flow in its as-is and to-be variants, with each department’s role marked on it. |
| Workflow diagram | Diagram | Statuses, transitions, notifications and the permissions matrix per department. |
| Integration architecture | Diagram | The PIM at the centre: ERP, sales channels and marketplaces, with the data flow described per integration. |
| Implementation schedule | Gantt | A week-by-week plan with milestones and a split of responsibilities. |
| Implementation quote | Spreadsheet | A detailed estimate per role and task, and the basis of the implementation contract. |
| Training materials | PDF and recordings | Workshop decks, recordings and further reading for the whole team. |
The implementation quote is the most important item here. It comes last, because only once the data model, the integrations and the workflow have been designed is it clear what is being priced. That is the difference between an estimate and a range handed over before the analysis.
Format
The programme is fully remote and built so that people can take part alongside their day-to-day work.
Rhythm
One workshop a week, fully remote. Between workshops the team works internally on the tasks from the previous session, with a consultant on hand.
Participants
Invite everyone who will work with the PIM system: marketing, sales, IT, e-commerce, logistics and production. The programme is not billed per participant.
Documentation
After each session you receive training materials and working documents, and at the end the full implementation documentation. Nothing stays in our notes.
Fit
The programme is a first step for companies that know they need a PIM system but have not yet described their product process. Below we also say when it is not needed.
Next step
Tell us about the catalogue, the number of markets and the systems the PIM has to integrate with. We will say plainly whether the programme is needed, or whether you can go straight to implementation. The consultation is free and commits you to nothing.
Materials
PIM Academy is our video series on PIM implementations from the practical side. The three episodes below cover exactly the stage that PIM Starter organises.
PIM Academy · episode 6
What the analysis is in practice, what the final document contains, and five steps that will get you ready for the workshops.
Watch the episodePIM Academy · episode 4
Eight situations that cost the most during a project. The preparation programme exists so you can avoid them.
Watch the episodePIM Academy · episode 3
What beyond the licence really decides the budget, and why a range quoted before the analysis always drifts.
Watch the episodeFAQ
No. Choosing the system is one of the outcomes of the programme, not a condition of entry. In week one we show Akeneo, Ergonode and Pimcore on live installations, and we only make a recommendation once we know the data model, the integrations and the processes.
If you want a sense of the differences beforehand, start with the three systems side by side on our PIM hub.
Tell us how many products you have, how many markets you sell in and which systems the PIM has to integrate with. We will reply with what the programme would look like in your case and what should be in the implementation scope.
We will be in touch shortly and work out the next move together.
A reply within one business day
Needs analysis and a project estimate
Pre-implementation analysis and consulting
Our experts run the project, so you can focus on your business