A paid pilot should make the bigger decision easier.

A buyer asks for proof before making a larger commitment. The seller offers a pilot. Both parties agree, but they may be imagining different things.

One expects a small version of the complete service. The other expects a tightly scoped test. Without an explicit decision to work towards, a pilot can become an extended negotiation with deliverables attached.

What Stravito’s early pilot involved

On SaaS Club, Stravito co-founder Thor Olof Philogène describes an early paid proof of concept that ran for five months with check-ins every two weeks. The company had to demonstrate progress against what it had proposed, and could have been removed from the process. He says Stravito ultimately won the contract.

This is a founder’s account of an enterprise software sale. No contract value or comparable agency conversion rate is disclosed. It does not establish that a five-month pilot is the right format for a marketing engagement.

The useful structure is the connection between the work, regular evidence reviews and a decision about the larger relationship.

Choose one question the pilot can answer

For a proposed agency pilot, begin by writing the uncertainty in plain language. Can the team produce creative the business is willing to run? Can a particular service page attract suitable enquiries? Can the sales team use a follow-up resource in real conversations?

These are different questions and require different evidence. A short creative pilot may establish production quality and working cadence. It may be too small or too brief to establish durable acquisition economics.

Choose a question that matters to the buying decision and can reasonably be examined within the available scope. Avoid a broad objective such as “prove marketing works”.

Define the responsibilities on both sides

A pilot brief should explain what the delivery team will produce and what the client needs to provide. Access, timely approvals, product information and sales feedback can determine whether the work produces anything useful.

Assign a named role to each responsibility. The relationship can be team-led while still making ownership clear. “The client will approve assets” is less useful than identifying the person who can approve them and the agreed review window.

Also define what is outside the pilot. A test of one service, audience or location should not quietly expand into a complete website rebuild. Any change in scope should lead to an explicit discussion of the decision, time and cost involved.

Agree the evidence before the result arrives

Write down what will be reviewed at the end. Some evidence concerns delivery: were the agreed assets completed and usable? Some concerns the market: did suitable people respond? Some concerns the relationship: could the two teams make decisions and act on feedback?

Set expectations for each without pretending they are interchangeable. A successful delivery test is not automatically proof of profitable scale. A weak market result can still reveal a useful constraint if the test was run competently and recorded honestly.

Keep the baseline and the important assumptions in the brief. This makes the final discussion less vulnerable to moving expectations.

Use reviews to make decisions during the work

Regular check-ins should examine a small set of questions: what was completed, what happened, what was learned and what changes next?

For a hypothetical six-week project, the review cadence could follow its actual milestones: initial brief, first deliverable, live test and final assessment. The right interval depends on how quickly meaningful evidence can arrive.

Bring examples and working records. A meeting dominated by an attractive slide deck can conceal practical issues such as delayed approvals or missing enquiry feedback. Resolve those issues while there is still time for the pilot to be useful.

Give the ending a real choice

Before launch, agree what happens when the pilot ends. The options might include continuing the work, changing the scope, running one further bounded test or stopping.

The final review should recommend one of those choices and explain the evidence. If the result is inconclusive, name the remaining uncertainty and the cost of resolving it. Avoid converting a lack of evidence into an automatic retainer.

A paid pilot works best when both sides understand what they are buying: a defined piece of work and a better basis for the next decision. Our Interest-to-Intent approach can help frame that work around acquisition and qualification, with responsibilities and review points established from the start.