Why does data model expertise carry the highest weight?

The data model determines how products, variants, attributes and relations are stored, and every workflow, integration and channel depends on it. Mistakes in the data model spread into every downstream system and are expensive to correct after go-live. A partner with strong data model skills prevents those mistakes during design, which is why PIMvendors weights it at 20 percent.

Can we change the weights in the scorecard?

Yes. The default weights suit a typical mid-sized implementation. Agree changes with the buying committee before any partner is scored, and record the reason. A project dominated by ERP integration may raise integration capability; a first PIM with poor source data may raise methodology. Changing weights after scoring undermines the result.

What are knock-out criteria?

Knock-out criteria are conditions a partner must meet before scoring starts. Examples are the availability of a named team for interview, certified consultants on the proposed team and acceptance of named key staff in the contract. A partner that fails a knock-out is excluded, whatever its score on the other criteria would have been.

Who should score the partners?

Each member of the evaluation team scores independently, using the anchors and the evidence collected: workshop output, team interviews, references and the written proposal. The team then meets to discuss differences of two points or more and agrees a final score per criterion. Independent first scores reduce the influence of the most senior voice in the room.

PIM Implementation Partner Scorecard

How does the partner scorecard work?

The scorecard compares implementation partners on seven weighted criteria, each scored from 1 to 5 against written anchors. Knock-out criteria come first, then independent scoring, then calibration. The weighted result then informs the buying committee's discussion and decision.

Use the scorecard after the design workshop and team interviews described in choosing a PIM implementation partner. By then you have the evidence each criterion needs: workshop output, interview notes, references and the written proposal. The implementation pillar explains where partner choice sits in the wider plan.

Five rules keep the scorecard honest:

Agree weights and anchors before any partner is scored.
Apply knock-out criteria before scoring.
Score independently, then calibrate as a team.
Record the evidence behind every score.
Score the proposed team on its own evidence.

The fifth rule matters most. A partner's best consultants may not be on your project. Every anchor below refers to the named team and to evidence from your own workshop where possible.

Knock-out criteria

Apply four knock-out criteria before scoring, and exclude any partner that fails one. These conditions protect the project from risks no weighted score can offset.

The proposed team is available for interview before contract.
At least one certified consultant on the current product version is on the named team.
The partner accepts named key staff and replacement approval in the contract.
The partner accepts your ownership of configuration, documentation and custom code.

If no partner passes all four, revisit the brief before relaxing the criteria. A brief that asks for an unrealistic team size or start date can push good partners out. The Red Flag Register lists further warning signs to record alongside the scorecard.

Record each knock-out check in writing, with the date and the person who confirmed it. A partner that passes on a verbal promise during the sales process should confirm the same point in the proposal. That written confirmation becomes the basis for the contract clause later.

Weighted criteria

Seven criteria cover the partner's skills, people, method and commercial terms. Default weights suit a typical mid-sized implementation.

Criterion	Weight (percent)	What to assess	Evidence
Data model expertise	20	Quality of the model proposed in the workshop; handling of variants, inheritance and classification	Workshop output, design samples
Platform certification depth	15	Certified consultants on the named team, on the current version	Certificates, vendor confirmation
Industry references	15	Comparable projects by industry, scope and complexity	Reference calls
Integration capability	15	ERP, DAM, commerce and syndication experience relevant to your landscape	Proposal, interviews, references
Team continuity	15	Named team, allocation, turnover and replacement policy	Interviews, contract terms
Methodology	10	Phases, sign-offs, migration rehearsals, knowledge transfer	Proposal, workshop
Commercial model	10	Pricing clarity, change request rules, incentives tied to outcomes	Proposal, draft contract
Total	100

Adjust the weights for your project before scoring:

Project profile	Suggested adjustment
Heavy ERP or commerce integration	Integration capability up 5, commercial model down 5
First PIM, poor source data	Methodology up 5, platform certification depth down 5
Regulated products, complex classification	Data model expertise up 5, industry references down 5

Scoring anchors

Score each criterion from 1 to 5 against the anchors below. Scores of 2 and 4 sit between the written anchors.

Criterion	1 (weak)	3 (adequate)	5 (strong)
Data model expertise	Workshop copies the source structure; no variant or inheritance logic	Sound model for the sample family with some open questions	Model handles variants, inheritance, classification and channel needs; trade-offs explained
Platform certification depth	No certified consultant on the named team	One certified consultant on the current version	Several certified consultants, including the lead, on the current version
Industry references	No comparable references	One comparable reference by industry or scope	Two or more references comparable in industry and scope, positive on data model and team
Integration capability	No experience with your ERP or channels	Experience with your ERP or main channel	Delivered integrations with your ERP, DAM and main channels, with patterns to show
Team continuity	Team unnamed or changes after workshop	Named team with partial allocation commitments	Named team with stated allocation, low turnover and contractual replacement terms
Methodology	Generic method, no migration rehearsals	Clear phases and sign-offs, one or two rehearsals	Phases with signed outputs, three or more rehearsals, structured knowledge transfer
Commercial model	Unclear pricing, open-ended change requests	Clear rates, change process described	Clear rates, change thresholds, incentives or holdbacks tied to acceptance

The anchors describe evidence a team can observe. Where the evidence is missing, score 1 and note what would change the score.

Calculating and reading the result

Multiply each score by its weight, add the results and divide by 100 to get a weighted score from 1 to 5. Read the result together with the scores per criterion.

Illustrative example, with fictional partners:

Criterion	Weight (percent)	Partner A score	Partner A weighted	Partner B score	Partner B weighted
Data model expertise	20	5	100	3	60
Platform certification depth	15	3	45	5	75
Industry references	15	4	60	4	60
Integration capability	15	3	45	4	60
Team continuity	15	4	60	3	45
Methodology	10	4	40	3	30
Commercial model	10	3	30	4	40
Weighted score (1 to 5)	100		3.80		3.70

In this example the totals are close, and the profiles differ. Partner A is stronger on data model and team; Partner B is stronger on certification and integration. The buying committee should decide which gap is easier to close, for example by adding a vendor architect to Partner A's team.

Feed the result into contract talks. Every score below 3 on a high-weight criterion becomes a contract condition, such as a named data model lead or an extra migration rehearsal. The timeline guide helps test the partner's plan against realistic ranges.

PIM implementation partner scorecard: weights and scoring anchors