# Sanitized Template — Route To A Paid Outcome

Use this skeleton when the original material describes a marketplace route, revenue path, or paid delivery loop that includes private platform tactics or branded infrastructure.

## Remove

- marketplace-specific tactics you do not want to disclose
- private account names, listing IDs, or customer names
- internal dashboards, payment account details, or credentials
- proprietary labels for stages, scoring, or routing

## Keep

- the buyer type
- the delivery route in generic form
- the payment and acceptance gates
- the evidence already available
- the exact point where the route becomes uncertain

## Copy-ready skeleton

```text
Objective:
Test whether a route to a paid outcome is real, payable, and repeatable.

Target buyer or user:
- [generic buyer type]

Planned route:
1. Discover or receive [task / lead / request].
2. Qualify whether the task fits [generic criteria].
3. Deliver [output type].
4. Reach [acceptance event].
5. Reach [payment event].

Current route status:
- discovery: [visible / unclear]
- qualification: [visible / unclear]
- delivery: [visible / unclear]
- acceptance: [visible / unclear]
- payment: [visible / unclear]

Approvals or gates:
- [platform review]
- [buyer acceptance]
- [payment release]
- [operator approval]

Evidence available:
- [live listing / buyer reply / paid transaction / delivery sample / none]

Known constraints:
- [budget]
- [time]
- [account or access requirements]

What is still unverified:
- [who accepts delivery]
- [how payment is released]
- [whether manual action is still required]
- [whether the route can repeat]
```

## Reminder

Do not claim that the route is live unless the payment and acceptance gates are actually evidenced.