Terms of Service

Who this is for

Founders approaching launch who need terms that fit what they're actually offering.

What you'll actually decide

What the service is and isn't, what users may and may not do with it, how accounts end, and where your liability stops.

What first-time founders get wrong here

Pasting a SaaS template over a product that isn't that kind of SaaS — terms describing a subscription when you sell one-time, or a US-only jurisdiction clause on a product with mostly European customers.

The first 10 questions

This is where the conversation starts. Each answer shapes what gets asked next.

1. 01What is the product, and what does it do for users?
2. 02Is this B2C, B2B, or both? The nature of the relationship changes what the terms need to cover.
3. 03Is the product paid, free, or freemium?
4. 04What stage are you at — pre-launch, beta, or live with paying users?
5. 05What would constitute misuse of your product — things users could do that would harm you, other users, or third parties?
6. 06What are you explicitly not responsible for — what liability do you need to limit?
7. 07If it's paid, what are the payment terms — billing cycle, refund policy, what happens on non-payment?
8. 08Can users create content or upload data? If so, who owns it — and what license do you need to operate the service?
9. 09What happens when a user violates the terms — warning, suspension, termination? Is it reversible?
10. 10What is the legal name of your company and the jurisdiction whose law governs the agreement?

+ 7 more questions across discovery, validation, and the creative brief — each one adapting to what you've already said.

Related legal project types

• Incorporate Now — and As What?Decide whether it's time to incorporate, and what to form — LLC, C-corp, or your home-country equivalent — based on what you're actually doing, not startup folklore.
• Founder AgreementWork through equity, vesting, IP ownership, roles, and what happens if someone leaves — before those conversations become awkward or costly.
• Privacy PolicyThink through what data you collect, how you use it, and who you share it with — and produce a privacy policy tailored to your product, not a generic paste job.