# Design a two-week paid pilot for a new service offer

**trustWF workflow pack** · Solopreneurs

## Outcome
A pilot brief, participant criteria, delivery checklist, feedback questions, and decision rules for the next iteration.

## Who this is for
A solo consultant or service founder testing a defined offer with a small number of paying clients

## What to provide
Required: target customer, problem, service hypothesis, proposed scope, delivery capacity, price or pricing hypothesis, and learning question. Optional: draft terms, onboarding steps, and prior evidence. Do not include client personal data.

## Steps
1. State the riskiest service and customer assumptions and the evidence already available.
2. Define a narrow pilot scope, exclusions, duration, participant criteria, and delivery capacity.
3. Create a transparent invitation and feedback plan without promising unproven outcomes.
4. Set learning-based decision rules for iterate, pause, or expand; keep these distinct from revenue forecasts.

## Copy-ready instructions
STAGE 1 — 1. Define what the pilot tests
When to use: Use before recruiting participants.
Prompt: Help me design a small paid pilot for a new service. Target customer: [specific segment]. Problem to address: [description]. Proposed service and boundaries: [details]. Evidence so far: [customer conversations, sales, or none]. Riskiest assumptions: [list or ask me]. Delivery capacity over two weeks: [hours/slots]. Price or pricing hypothesis: [amount or undecided]. Identify the main learning question and separate facts, hypotheses, and unknowns. Do not promise outcomes.
Expected return: A pilot hypothesis sheet and a list of decisions that must be made before recruitment.
User check: Ensure the service can be delivered safely within the stated capacity and boundaries.

STAGE 2 — 2. Build the pilot plan
When to use: Use after choosing the learning question.
Prompt: Create a bounded two-week pilot plan. Include: eligible participant criteria; number of slots based on my capacity (do not invent a market-valid sample size); exact deliverables; what is excluded; timeline and participant responsibilities; fee/payment terms as supplied; support boundaries; data collected and consent; feedback points; and stop conditions. Mark terms needing legal or professional review.
Expected return: A pilot brief, delivery calendar, and participant checklist.
User check: Verify that price, scope, refund/cancellation terms, privacy, and service limitations are explicit and approved.

STAGE 3 — 3. Prepare invitation and learning review
When to use: Use after approving the pilot plan.
Prompt: Using the approved pilot details: [paste], draft a transparent invitation that says this is an early pilot, describes what is included and excluded, states the fee and timeline, and avoids unverified benefit claims. Then create a short feedback form and a review table linking each pilot observation to the assumption it informs. Define iterate/pause/expand criteria using thresholds I supply: [criteria or placeholders].
Expected return: An invitation draft, feedback questions, and post-pilot learning template.
User check: Do not recruit or charge participants until the user approves the offer terms; separate participant feedback from the founder’s interpretation.

## Review before using
Make pilot terms and limitations clear to participants. Do not overstate likely results, use customer data without permission, or treat a tiny pilot as proof of broad demand.

---
Use the result as a draft. Review it for accuracy, context and any required approvals.