Terms & Conditions Writer

The clauses that actually protect a business are the ones specific to how it makes money, delivers value, and could go wrong. A SaaS product needs uptime, subscription, and data terms. An e-commerce store needs shipping, returns, and product liability terms. A marketplace needs user-generated content, dispute, and commission terms. A free tool needs limitation of liability and no-warranty terms. Same generic template across all of them protects none of them.

The skill starts by classifying the business model — SaaS, e-commerce, marketplace, service provider, content/media, freemium — and identifying the risk areas specific to it. What could go wrong for the user? What could a user do that harms the business? What third-party dependencies exist? What refund and cancellation scenarios are likely? Is there user-generated content? Does the product use AI, and if so, are there accuracy disclaimers, no-reliance clauses, and disclosure that AI is being used? Each risk area shapes which clauses get tightened.

The structure runs fourteen sections (agreement to terms, description of service, accounts, payment and billing, refund and cancellation, acceptable use, IP, user content, disclaimers and liability cap, indemnification, termination, dispute resolution, changes to terms, general). Sections that don't apply get dropped — a free tool doesn't need a refund policy section. Sections that need tailoring get tailored: SaaS uptime promises are stated explicitly or disclaimed explicitly (never accidentally promised at 100%), auto-renewal disclosure follows the strictest applicable jurisdiction (California, New York, and Illinois have specific requirements), and price-change notice periods are spelled out rather than reserved as a vague "we may change prices."

Jurisdiction handling is layered. EU/UK consumer protection overrides unfair terms regardless of what the contract says, so the skill avoids clauses that wouldn't survive judicial review (broad liability disclaimers against consumers, unilateral right to change material terms without notice, removal of statutory rights). US arbitration and class-action waivers are included where enforceable and structured properly. Australian Consumer Law gets the specific guarantees language where ACL applies. Liability caps are kept proportionate to contract value — a £9/month SaaS capping liability at £1M is not credible and gets thrown out.

The output includes the Business Risk Profile, the full T&C document with [BRACKETED] customisation fields, Customisation Notes explaining what you need to fill in, and Red Flags for issues that need additional legal attention beyond what T&Cs can solve (regulated industries, payment processing, age verification, AI training on user data).

This produces a drafted document, not legal advice. T&Cs are legally enforceable contracts, and the difference between an unfair-terms challenge and an enforceable agreement is often a single word — particularly around liability caps, indemnification scope, dispute resolution mechanics, and consumer-rights carve-outs. Have a qualified commercial lawyer review the draft before publishing, especially if you operate in regulated sectors, process sensitive data, or serve consumers in the UK or EU. The skill is a starting point for professional review, not a substitute for one.