How to Build a Campaign Launch Pilot Without Creating a Transformation Project 

A small pilot can grow surprisingly quickly. One landing page becomes several locations. A form of connection becomes a CRM redesign. A launch test becomes a discussion about the entire website. 

A campaign launch pilot needs boundaries that are understandable before work begins. Otherwise, the business cannot tell whether it is evaluating a product or financing a new implementation programme. 

Write the business question first 

Use one sentence: can this recurring campaign journey be launched and changed with less time or effort, at acceptable quality, for a worthwhile total cost? 

Then name the actual journey. Identify the property, template, content records, variants, action, and receiving team. Keep the language specific enough that a new participant can understand what is being tested. 

Avoid making the goal ‘prove the platform’. That is too broad to produce a clear answer and too easy to reinterpret after the work is complete. 

Put exclusions beside inclusions 

State what is not part of the pilot: a complete website redesign, replacement of core systems, every location, new custom functionality or ownership of the full customer lifecycle. 

An exclusion is not a weakness. It prevents an unrelated requirement from changing the meaning of the test. If a missing capability is essential to the chosen journey, resolve it before promising the pilot rather than hiding it in an exclusion. 

Also state who provides approved content and design. A template demonstration does not automatically include bespoke creative production. 

Give the baseline a usable shape 

Record the current route, request-to-live and approved-brief-to-live, active effort, specialist help, external spending, rework and quality. Use comparable tasks where records exist; otherwise gather as a prospective example. 

Choose a small set of primary measures. Keep the rest as guardrails or explanatory context. Trying to prove every possible benefit can make the measurement less clear. 

For conversion, specify whether the available data can support a meaningful comparison. Do not assume the duration of a marketing technology pilot is also a sufficient outcome-test window. 

Define the repeat before the setup 

Write the second task in the charter. Which facts, structures, and checks should be reused? Which parts are expected to change? Who should be able to perform the task? 

Measure help and correction work as well as completion time. A repeat task completed only through extensive supplier intervention may reveal a training, usability or service-model issue. 

The aim is not to make the second task artificially easy. It is to test a realistic example of the work the buyer expects to repeat. 

Assign decisions, not just a coordinator 

Name the business sponsor, daily user, content approver, technical validator, delivery owner, and economic approver as needed. One coordinator does not mean one person can make every decision. 

Keep the responsibility list short and practical. The content team provides the message and content requirements. The platform team confirms the configured route. The receiving team confirms whether the enquiry is usable. 

This prevents the pilot from succeeding in a demonstration while failing in the actual business process. 

Agree the review options in advance 

The final review should compare the same measures and disclose changed scope, missing evidence, and unexpected effort. Options include continue, rescope, extend for a specific evidence need or stop. 

Include the full incremental cost and the cost of the current alternative. Faster work is valuable only in relation to what it takes to deliver and maintain it. 

A focused digital experience platform implementation should finish with a decision the buyer can defend. One property, one journey, and one repeat task provide enough structure to start, without turning the first test into a promise to transform everything.