1) Required deliverables
Buyers should receive everything needed to deploy without guessing.
- •Workflow + logic (n8n/Make/Zapier/etc.) or deployable instructions
- •System prompt(s) with guardrails and escalation rules
- •Setup instructions with prerequisites + configuration checklist
- •Requirements list (accounts, tools, webhooks, etc.)
- •Use cases + what’s out of scope
2) Safety + trust
- •Safe defaults (no risky actions without buyer confirmation)
- •Escalation path for uncertain/high-risk scenarios
- •No hidden data collection/exfiltration
- •BYOK-friendly (sellers never need buyer API keys)
3) Testability
Buyers should be able to validate success quickly.
- •Happy-path test steps
- •Failure-mode behavior (timeouts, missing fields, API failures)
- •Expected outputs + acceptance criteria
4) Support expectations
Support is ticketed and time-boxed to protect both sides.
- •Sellers respond to tickets within a reasonable timeframe
- •Refund eligibility is defined by the Refund Policy (technical failure / misrepresentation)
- •AOS can escalate and adjudicate if needed