Payment Terms Design for Consumer Deposits
DolceDrago 350 — a skill for the money taken before the work, from a consumer
Variant of Nº135 — Payment Terms Design
What it is
Redesigns the money taken up front when the customer is a private individual: what the deposit is for, what may be kept when a booking dies, when the terms must reach the customer, and where the money sits until the work is done. Replaces a percentage copied off a competitor with a ladder costed rung by rung, and assembles the evidence before a dispute rather than during one. For salons, studios, schools, installers, makers and anyone taking consumer money in advance.
What you receive
the deposit redesigned for a private customer — mobilisation costed, a cancellation ladder built on loss actually incurred, terms given before the money and evidenced, prepayments held apart, and the dispute file built in advance
Delivered as a single, complete .md skill file — open it, paste it into any capable chat model, and work. No installation, no account with anyone but us.
Supported models
- Claude (Opus/Sonnet)
- ChatGPT (GPT-4o/5)
- Gemini
- any capable chat model
People reach for it when
- “how much deposit can i keep if a customer cancels”
- “cancellation policy wording for a booking deposit”
- “customer cancelled two days before can i keep the deposit”
- “do i have to give my terms before they pay the deposit”
- “customer did a chargeback on a deposit what do i need”
Record
lineage: variant · parent 135
gates passed: demand-evidence · function-fit · beats-the-blank-page
status: IN THE COLLECTION
Sale-time bench runs and the fix-or-refund log attach to this record when the payment room opens.
In the collection. The sale room is being fitted; this work goes on sale when it opens.
Join the house — be written to when sales openBack to the collectionLicense
Free-shelf works ship under the DolceDrago House License — use the outputs freely, personal or commercial; the work file itself stays with the house.