Use case · SaaS and app builders
Your product’s blog, changelog and help articles, from one place your whole team can write in.
A software product publishes three kinds of posts: education that brings people in from search, help articles that keep support quiet, and a changelog that shows the product is alive. CMSKite holds all three, serves them to your app or site over an API, and lets the non-developers write. Here is how to split them, where the AI writer helps and where it must stay out, and a real draft for a SaaS.
Three kinds of posts, three jobs
| Kind | Its job | Who writes it | AI drafts? |
|---|---|---|---|
| Education | Answer the problems your users search for, before they know your product. | Founder, marketer | Yes, from a brief, then checked by someone who knows the subject. |
| Help articles | Answer the question a ticket would ask, with the exact steps in your product. | Support, product | No. The AI does not know your screens and will invent buttons. |
| Changelog | Say what changed, who it is for and how to use it. | Whoever shipped it | No. Write from what shipped; an assistant with your repository can help (below). |
Keep them apart so each has its own list and address. Two ways: make the changelog its own website in CMSKite (each website has its own posts, settings and free blog link), or keep one website and give each kind its own category, then fetch by category through the API. The two-line embed shows a website’s posts; it has no category filter.
What to publish
- Education: the problems your users have before they need you. For an invoicing tool: “What Net 30 means”, “How to word a late-payment reminder”. For a scheduling app: “How to stop no-shows”.
- Help articles: start with the tickets. When the same question arrives three times, it is an article, linked from the reply.
- Changelog: one post per release that users would notice, with a screenshot and the one sentence a user needs: what it is, where it is, who gets it.
- Honest comparisons: when your product is the better fit and when it is not. Readers can tell the difference.
A rhythm instead of a calendar
| When | What to publish |
|---|---|
| Every release users will notice | A changelog post, the same day. |
| When a question repeats in support | A help article, linked from your reply template. |
| Monthly | One education post on a problem your users have. |
| Before your users’ own deadlines | For an invoicing tool, the end of the financial year; for a booking app, the busy season of the businesses using it. |
| December | The year’s changes in one post, linking to each changelog entry. |
What to keep out
- AI-written descriptions of your own product. Put the facts you allow in the brief and tell it to describe nothing else. As the draft below shows, it still drifts; read every line about your product.
- Dates for features that have not shipped. A changelog is a record, not a roadmap.
- The same article twice, once as help and once as a blog post: two pages competing for one search. Write it once and link to it.
- Pages made only to rank. Google’s spam policies name scaled content abuse; a post that does not help a user does not help you either.
A brief for a software product
Every AI draft follows your brief, set once in Website settings → AI writing brief. For software the “Never” line keeps it off your product’s screens. This one is for a made-up invoicing tool:
We are Tallyo, invoicing software for freelancers and small studios. Readers: freelance designers, developers and writers who are tired of chasing late payments. Voice: clear and direct, a little dry; no hype. Facts we can mention: Tallyo sends invoices and reminders by email, and there is a free plan. Never: describe features, screens or settings of Tallyo beyond the facts above, or give legal or tax advice.
What the AI wrote from it
Topic: “Payment terms on an invoice: what Net 30 means and which terms to use as a freelancer”. Keywords: net 30 meaning, invoice payment terms freelancer. Tone Expert, length Medium, language English. Word for word, cut where you see […]:
Title: Net 30 Explained: Payment Terms Freelancers Should Use Search title: Net 30 Meaning & Payment Terms for Freelancers Search description: Understand Net 30, compare common invoice terms, and learn how freelancers can set clear payment expectations. Free invoicing tools available. ## What does Net 30 mean? ### Definition Net 30 is a payment term that tells the client the full invoice amount is due within 30 calendar days after the invoice date. The word "net" refers to the net amount after any discounts, and the number indicates the number of days. ### How it works in practice When you issue an invoice dated March 1 with Net 30 terms, the client must pay by March 31. If they pay on March 15, the invoice is considered settled early; if they pay on April 2, the payment is late and may trigger a reminder or late fee (if you have agreed on one). ### Why the term matters for freelancers Freelancers often work with multiple clients on varying schedules. A clear term like Net 30 sets an expectation that the client has a month to move funds, reducing the need for daily follow‑up. It also gives you a predictable cash‑flow window for budgeting. […] ## How to set payment terms on an invoice ### Step‑by‑step placement 1. **Header** – Include your business name, address, and contact email. 2. **Invoice date** – The day you create the invoice. 3. **Payment terms line** – Write something like "Payment due within 30 days (Net 30) of invoice date." 4. **Due date calculation** – Optionally list the exact due date (e.g., "Due date: March 31, 2026"). 5. **Accepted payment methods** – List bank transfer, PayPal, etc. ### Example phrasing > **Payment Terms:** Net 30 – please remit the total amount by the due date shown above. ### Using a free invoicing tool A free plan that sends invoices and email reminders can automate steps 3‑5, ensuring each invoice carries the same wording and due‑date calculation. […] ## Communicating and enforcing payment terms ### Initial communication State the terms clearly in your proposal and repeat them in the invoice. A short email accompanying the invoice can reinforce the expectation: "As agreed, payment is due within 30 days." ### Reminder schedule If the due date passes, send a polite reminder on day 31, then a firmer reminder on day 38. A free invoicing tool can automate these emails, reducing the time you spend chasing late payments. ### Handling late payments When a reminder is ignored, reply with a brief note referencing the original Net 30 term and any agreed‑upon late fee. Keep the tone professional; the goal is to get paid, not to alienate the client. ### Record keeping Track each invoice, its due date, and payment status in a simple spreadsheet or the free invoicing platform. This data helps you identify patterns—clients who consistently pay late may need stricter terms or a different payment method. Ready to simplify invoicing and automate reminders? Try Tallyo’s free plan to send professional invoices and email reminders without any upfront cost.
A useful education post, in the voice the brief asked for, with the product mentioned only near the end. Before publishing:
- It drifted into product claims. “Can automate steps 3‑5, ensuring each invoice carries the same wording and due-date calculation” describes features the brief does not list. Check them against the product, or cut them.
- One definition to check. Its explanation of the word “net” is the kind of detail a finance-minded reader will test. Confirm it against a source you trust.
- Link it. Point “late fee” and “reminder” to your own help articles on those, once they exist.
The developer side
- Render it yourself. Posts come from a REST API, a TypeScript SDK and an MCP server with a read-only project key, so your app or marketing site draws them in its own components, as finished HTML if you render on the server.
- Rebuild on publish. Webhooks send
post.published,post.updated,post.unpublishedandpost.deleted, typically to rebuild a static site the moment a post changes. - Changelog from your editor. An AI coding assistant connected to the MCP server can draft the changelog post from the work it can see, and leave it as a draft until you say publish.
- Built with Lovable, Bolt or Emergent? The dashboard has a prompt to paste into the builder; see CMSKite for Lovable.
- Writers do not need the repository. Support and marketing write in the dashboard with their own roles; nobody touches code to publish.
When CMSKite is not the right tool: large versioned documentation with a navigation tree and per-version pages fits a docs tool better. CMSKite is posts, categories and tags.
What it costs
| Free | Starter | Team | |
|---|---|---|---|
| Price | Free forever | ₹799 / $9 a month | ₹2,499 / $29 a month |
| Posts | 35 | Unlimited | Unlimited |
| Websites | 1 | 1 | 5 |
| Team members | 2 | 3 | 5 |
| API requests | 10K / mo | 100K / mo | 500K / mo |
Questions
- Can I keep the blog, changelog and help center separate?
- Yes: make each its own website in one account, each with its own posts and blog link, or use one website with a category per kind and fetch by category through the API. How many websites you can have depends on your plan (above).
- Can posts be written in Markdown?
- Yes. A post can be Markdown, HTML or plain text, and the API returns it in the format it was written in.
- Can an AI assistant publish without a person?
- Only if its token was granted publishing and its owner’s role allows it, checked on every request. Otherwise it saves drafts for a person to publish.
Related
- For developersThe API, SDK, MCP server, webhooks and your own database.
- QuickstartPosts on your site from code in a few minutes.
- CMSKite for LovableA blog in an app built with Lovable.
- MCP and automationConnecting an AI tool with one URL, and the tools behind it.
- AgenciesRunning blogs for several clients from one account.
Checked