How to brief a marketing automation platform review before you shortlist

What to take away

A review starts with a written buyer brief, not a feature list.
A test scenario turns a demo into evidence about lead scoring and campaign automation.
The output should feed lead nurturing workflow design and CRM sync decisions.
Compliance questions belong in the brief from the first page.
A table of evidence beats a star rating.

Begin with a buyer brief, not a demo request

A marketing automation platform review is only useful if you know what you are reviewing against. Write one page before you contact vendors. Cover your team size, campaign volume, data sources, budget range and the decisions the platform must support.

For background, marketing automation covers email, scoring and campaign workflows.

Your brief should name the workflows you need. A lead capture form, a welcome sequence, a score threshold and a sales alert are four common items. If your brief lists them, every vendor answers the same questions.

Data protection belongs on page one. The guide to the UK GDPR explains lawful bases, consent and individual rights. You need a named lawful basis for every contact you import.

Add a line about who signs off the shortlist. Include finance if the platform cost runs beyond one year. Include sales if CRM records are shared.

Write the test scenario before you shortlist

A test scenario is a script you run against every platform. Build it from a campaign you already know well. Use real data, not a demo dataset.

Write the test scenario

Choose one real campaign from the last quarter.
Map its data flowform, CRM record, score, email sequence, sales alert.
Set a pass or fail test for each step.
Record every manual workaround the vendor uses.
Ask for the same test in your sandbox with your sample data.

This scenario becomes the script for every vendor demonstration. It stops the review ending as a feature scorecard. A scorecard tells you what a platform can do, not what it does with your data.

Include a failure case. Ask what happens when a contact unsubscribes mid sequence. Ask where the record goes if the CRM sync drops.

Build a checklist for consent and data quality

Lawful basis recorded for each contact source.
Suppression rules for unsubscribes and complaints.
Lead scoring rules documented and reversible.
CRM field mapping agreed before import.
Retention period set for inactive records.

The ICO direct marketing guidance covers consent and soft opt in rules for email. Use it to test vendor answers on consent, not just their security page.

Ask vendors to show how they handle a complaint or a deletion request. A platform that cannot show the audit trail fails the brief.

Compare platforms against the scenario

Review area	Evidence to demand	Why it matters
Lead scoring	Show a score change from a real form fill	Your brief sets the buying signals
Campaign automation	Run a three step sequence with delays	Tests timing and suppression logic
CRM sync	Demonstrate a two way field update	Prevents duplicate records
Reporting	Export a campaign ROI report to CSV	Supports board reporting

Ask vendors to run the scenario in their own environment, then in yours. A platform that passes both is shortlisted. One that only passes a scripted demo is not.

Price the shortlist against the same brief. Ask for a three year total cost, including onboarding, contacts and support. Do not compare a starter tier with an enterprise quote.

Example: a brief that changed a shortlist

A six person B2B team wanted lead nurturing across a 90 day buying cycle. The brief required a score change after two website visits and a CRM task for sales. Two platforms failed the CRM task test. The team chose the third and connected it to B2B lead nurturing automation UK.

The review also flagged duplicate records. The team then read CRM integration marketing automation UK to plan the sync.

Turn the review into a decision record

End the review with a one page decision record. List the brief, the test results, the compliance notes and the CRM sync findings. Attach it to the shortlist. This record feeds workflow design and integration planning.

The record should name the owner of each integration. It should list the fields that must match between the platform and the CRM. It should note the renewal date and the exit process.

Common questions

How long should the buyer brief be?

One page is enough. Focus on campaign volume, data sources, compliance and the decisions the platform must support.

Who should write the test scenario?

The person who runs campaigns day to day. They know the real steps, delays and exceptions.

What if a vendor refuses a live test?

Treat that as a failed test. A platform review needs evidence, not promises.

How do we score CRM sync?

Score it on record matching, field mapping and error handling. Ask for a two way update in your sandbox.