SaaS founders debate: build your own blog or use a CMS/service?
A question was raised about how solo SaaS founders should set up a blog for SEO and . The options listed include building a blog directly into the app, using WordPress, using a such as Contentful, Sanity, or Strapi (a content system that separates content storage from the page design, delivering content via an API), or using a hosted content service that also exposes an API.
Beyond that, the question asks whether a product already exists that goes further: connecting to your SaaS product to understand its features, docs, , and , then using AI to suggest or generate blog posts based on that context, and handling publishing, SEO, images, and metadata while exposing through an API for your own frontend. The core question is whether such an integrated product already exists, or whether everyone is currently just combining WordPress or a with separate AI tools.
Key points
- Candidate approaches for a SaaS blog: building it into the app, WordPress, (Contentful, Sanity, Strapi), or a hosted content API service
- Asks whether a product exists that understands the SaaS product's features, docs, , and audience to auto-suggest or generate blog posts
- Interest in a service that also handles publishing, SEO, images, and metadata, delivered via an API for a custom frontend
- Current common practice appears to be combining WordPress or a with separate AI tools rather than one integrated solution