中文导读
Prepay Chargeback Defense SOP for Solo SaaS 是一套面向一人公司的通用 playbook，帮助你用更少的人力完成更稳的增长、交付与决策。
概览
Canonical sourcing log: /Users/xiaoyinqu/onepersoncompany-deploy/automation/reports/daily-skill-sourcing-log-2026-04-03.md
概览
If you run a solo SaaS, annual prepay looks like a win until one payment gets disputed. A single disputed invoice can lock funds, create support overhead, and force reactive policy decisions under pressure.
This skill gives you a practical SOP to reduce dispute probability before payment, and to respond with strong evidence if a dispute still happens. The focus is not legal theory. The focus is cashflow protection for one-person operators.
For one-person companies, this is a survivability workflow. When revenue concentration is high, payment reliability matters as much as top-line growth.
适用场景
- You sell annual or multi-month prepay plans
- You process larger invoices where one dispute materially affects runway
- You want clearer refund boundaries and acceptance proof
- You have no standardized dispute evidence packet
这个技能能做什么
- defines prepay-safe billing terms and acceptance checkpoints
- standardizes proof collection before fulfillment
- creates a reusable dispute evidence packet
- sets response timing and communication rules
- introduces a prepay risk gate for high-risk buyers
如何使用
- Define prepay-safe terms before payment.
Include refund window, delivery milestones, service start point, and cancellation boundaries in plain language.
- Capture explicit acceptance proof.
Store timestamped proof for terms acceptance, invoice scope, buyer identity, and delivery start trigger.
- Standardize fulfillment logging.
Track delivery artifacts (account provisioning, milestone completion, support actions) in one timeline.
- Build the dispute evidence packet in advance.
Create a single folder that always includes:
- invoice and payment record
- accepted terms snapshot
- scope and deliverable agreement
- fulfillment timeline and support logs
- customer communication extracts
- Add a prepay risk gate.
Score new buyers before accepting annual prepay. Route high-risk accounts to monthly plans first.
- Define a response SLA and owner checklist.
Set a same-day first response target and a fixed submission checklist so you never start from scratch.
- Audit monthly.
Review disputes, refunds, and near-misses. Update policy language where ambiguity repeats.
Output / Result
- reduced exposure to avoidable prepay disputes
- faster, cleaner dispute responses
- clearer billing boundaries for customers
- more predictable cashflow for a solo operator
Common Mistakes to Avoid
- vague annual-plan refund language
- no explicit acceptance proof before fulfillment
- collecting evidence only after a dispute begins
- accepting annual prepay for every new buyer without risk screening
- treating payment risk as a support issue instead of an operating system
SKILL.md 原文件
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# prepay-chargeback-defense-sop
Prepay Chargeback Defense SOP for Solo SaaS
Canonical sourcing log: `/Users/xiaoyinqu/onepersoncompany-deploy/automation/reports/daily-skill-sourcing-log-2026-04-03.md`
Overview
If you run a solo SaaS, annual prepay looks like a win until one payment gets disputed. A single disputed invoice can lock funds, create support overhead, and force reactive policy decisions under pressure.
This skill gives you a practical SOP to reduce dispute probability before payment, and to respond with strong evidence if a dispute still happens. The focus is not legal theory. The focus is cashflow protection for one-person operators.
For one-person companies, this is a survivability workflow. When revenue concentration is high, payment reliability matters as much as top-line growth.
When to Use This Skill
- You sell annual or multi-month prepay plans
- You process larger invoices where one dispute materially affects runway
- You want clearer refund boundaries and acceptance proof
- You have no standardized dispute evidence packet
What This Skill Does
- defines prepay-safe billing terms and acceptance checkpoints
- standardizes proof collection before fulfillment
- creates a reusable dispute evidence packet
- sets response timing and communication rules
- introduces a prepay risk gate for high-risk buyers
How to Use
1. Define prepay-safe terms before payment.
Include refund window, delivery milestones, service start point, and cancellation boundaries in plain language.
2. Capture explicit acceptance proof.
Store timestamped proof for terms acceptance, invoice scope, buyer identity, and delivery start trigger.
3. Standardize fulfillment logging.
Track delivery artifacts (account provisioning, milestone completion, support actions) in one timeline.
4. Build the dispute evidence packet in advance.
Create a single folder that always includes:
- invoice and payment record
- accepted terms snapshot
- scope and deliverable agreement
- fulfillment timeline and support logs
- customer communication extracts
5. Add a prepay risk gate.
Score new buyers before accepting annual prepay. Route high-risk accounts to monthly plans first.
6. Define a response SLA and owner checklist.
Set a same-day first response target and a fixed submission checklist so you never start from scratch.
7. Audit monthly.
Review disputes, refunds, and near-misses. Update policy language where ambiguity repeats.
Output / Result
- reduced exposure to avoidable prepay disputes
- faster, cleaner dispute responses
- clearer billing boundaries for customers
- more predictable cashflow for a solo operator
Common Mistakes to Avoid
- vague annual-plan refund language
- no explicit acceptance proof before fulfillment
- collecting evidence only after a dispute begins
- accepting annual prepay for every new buyer without risk screening
- treating payment risk as a support issue instead of an operating system
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# prepay-chargeback-defense-sop
Prepay Chargeback Defense SOP for Solo SaaS
Canonical sourcing log: `/Users/xiaoyinqu/onepersoncompany-deploy/automation/reports/daily-skill-sourcing-log-2026-04-03.md`
Overview
If you run a solo SaaS, annual prepay looks like a win until one payment gets disputed. A single disputed invoice can lock funds, create support overhead, and force reactive policy decisions under pressure.
This skill gives you a practical SOP to reduce dispute probability before payment, and to respond with strong evidence if a dispute still happens. The focus is not legal theory. The focus is cashflow protection for one-person operators.
For one-person companies, this is a survivability workflow. When revenue concentration is high, payment reliability matters as much as top-line growth.
When to Use This Skill
- You sell annual or multi-month prepay plans
- You process larger invoices where one dispute materially affects runway
- You want clearer refund boundaries and acceptance proof
- You have no standardized dispute evidence packet
What This Skill Does
- defines prepay-safe billing terms and acceptance checkpoints
- standardizes proof collection before fulfillment
- creates a reusable dispute evidence packet
- sets response timing and communication rules
- introduces a prepay risk gate for high-risk buyers
How to Use
1. Define prepay-safe terms before payment.
Include refund window, delivery milestones, service start point, and cancellation boundaries in plain language.
2. Capture explicit acceptance proof.
Store timestamped proof for terms acceptance, invoice scope, buyer identity, and delivery start trigger.
3. Standardize fulfillment logging.
Track delivery artifacts (account provisioning, milestone completion, support actions) in one timeline.
4. Build the dispute evidence packet in advance.
Create a single folder that always includes:
- invoice and payment record
- accepted terms snapshot
- scope and deliverable agreement
- fulfillment timeline and support logs
- customer communication extracts
5. Add a prepay risk gate.
Score new buyers before accepting annual prepay. Route high-risk accounts to monthly plans first.
6. Define a response SLA and owner checklist.
Set a same-day first response target and a fixed submission checklist so you never start from scratch.
7. Audit monthly.
Review disputes, refunds, and near-misses. Update policy language where ambiguity repeats.
Output / Result
- reduced exposure to avoidable prepay disputes
- faster, cleaner dispute responses
- clearer billing boundaries for customers
- more predictable cashflow for a solo operator
Common Mistakes to Avoid
- vague annual-plan refund language
- no explicit acceptance proof before fulfillment
- collecting evidence only after a dispute begins
- accepting annual prepay for every new buyer without risk screening
- treating payment risk as a support issue instead of an operating system
评论与讨论
添加评论