“Generate your privacy policy/terms of service” is a proven SaaS micro-product — founders need one on day one, don't want to pay a lawyer for a first draft, and are happy to pay $10-30/month for something that looks professional. Here's how to build one on /legal's document generators.
The generators aren't templates — they're conditional assembly
/terms-generator takes structured input — company_name, website, email, service_type, country, and two booleans: has_subscription and has_user_content. Those two booleans aren't just inserted into the text — they control which entire clauses appear in the document. A SaaS with no subscription billing doesn't need a billing/refund clause; a platform with no user-generated content doesn't need a content-license clause. The generator assembles only the sections that actually apply.
const res = await fetch("https://aplicious.com/api/v1/legal/terms-generator", {
method: "POST",
headers: { "X-API-Key": "lapi_live_••••", "Content-Type": "application/json" },
body: JSON.stringify({
company_name: "Acme Inc.",
website: "acme.com",
email: "legal@acme.com",
service_type: "software as a service (SaaS)",
country: "United States",
has_subscription: true,
has_user_content: false,
}),
});The other generators in the namespace
/privacy-policy-generator, /cookie-policy-generator, /saas-agreement (vendor name, product name, governing law, support hours, data region), /nda-generator, /freelance-contract, /employment-contract, /dpa-generator, and /refund-policy-generator all follow the same pattern: structured input, conditionally-assembled real document text out, not a blank with placeholders.
What a generator-SaaS wrapper actually adds
The API gives you the document. The product you build on top of it is the part that makes someone pay: a clean intake form instead of raw JSON, a way to save and re-generate as the underlying business facts change, version history so a founder can see what changed between drafts, and probably a PDF export. That's a real, sellable wrapper — most of the legal-document-generator SaaS products in this space are exactly this shape, a UI layer on top of document assembly logic.
The disclaimer travels with the document
Every /legalresponse includes a disclaimer field stating the output is informational, not legal advice, and recommending a licensed local attorney review it. If you're building a paid product on this, keep that disclaimer visible in your UI — it's there because it's true, not as a formality.