Design a paid pilot with a clear finish and learning goal

Identify the uncertainty a pilot can resolve

Choose a practical question: can you deliver the scope within the estimated hours, can the customer supply the needed inputs, or does the handoff format answer their decision? A pilot cannot cheaply prove every part of a business model.

Give the customer a complete outcome that matters regardless of continuation. If the only value is a promise that later work might succeed, reconsider the scope before charging for it.

Set a small delivery boundary

Specify the work units, time window, revisions and included communication. Describe what remains outside the pilot and how separate requests will be estimated. Keep the boundary understandable enough to fit in a short offer summary.

Use a finish condition you can control, such as delivering an approved audit and discussion. Avoid calling an uncertain downstream result the finish condition when customer actions or outside systems influence it.

Price from the actual work

Estimate preparation, delivery, coordination and review time before naming a pilot fee. If you choose an introductory price, explain the offer honestly and check whether you can absorb the difference. Record the ordinary delivery estimate separately from the learning cost.

Do not create a permanently discounted version of an unbounded service. A lower fee is easier to sustain when the pilot contains fewer defined tasks and a shorter commitment.

Agree on inputs and evidence

List the customer information and access needed, with a practical deadline and an owner. Define what evidence you will gather during the pilot, such as completed tasks, delivery hours and unresolved questions. Request only the information needed for those purposes.

Explain how feedback will be used. Permission to provide a service does not automatically mean permission to publish the customer's identity, photographs or an identifiable case study.

Hold a specific finish review

At the end, compare the promised deliverables with what was completed. Discuss actual delivery hours, input delays and whether the customer can use the outcome. Decide whether to continue, revise the scope or stop with a completed handoff.

Keep any longer engagement a separate decision with its own terms and scope. Avoid presenting continuation as automatic merely because the pilot finished or the customer gave positive feedback.

Improve the next pilot deliberately

Record which assumption changed and what you will do differently. If coordination took longer than expected, revise the input checklist or the price basis. If the outcome was unclear, improve the deliverable rather than simply extending the duration.

A successful pilot provides evidence about that situation. It does not establish typical customer results or justify public performance claims that the observed work cannot support.

Illustrative service-page planning pilot

A hypothetical provider offers a two-week pilot covering one service-page outline, one draft and one review call. The customer supplies approved service details and photographs. The pilot fee is illustrative, and publication or search traffic is outside its completion condition.

The provider estimates six hours and records eight, including two hours waiting for and reconciling conflicting service details. At the finish review, the customer receives the approved draft. The next pilot adds a single approval owner and revises the workload estimate; no ranking or revenue improvement is claimed.

Questions about this task