AI writing tools come in two classes. Writing assistants such as ChatGPT, Jasper, Neuroflash or Copy.ai help you formulate individual texts that you start, check and publish yourself. Blog systems run the blog as a whole: topics from search data, a fixed rhythm, publication in the CMS, approval. Comparing tools within one class only makes sense once you know which class you need.
Anyone searching for "AI writing tool comparison" finds lists of ten tools with stars and prices. These lists skip the first question: what job should the tool actually do? There are two classes of AI tools for text, and they solve different jobs. Comparing within the wrong class leads to the wrong purchase, no matter how many stars it has.
The two tool classes
Writing assistants are tools where you enter a task and get a text back. ChatGPT is the best-known example; Jasper, Neuroflash and Copy.ai are other examples of this class, with templates for blog posts, ad copy or social media. What they have in common: they become active when you use them, and they stop when you stop. Topic, timing, checking, publishing and linking all stay with you.
Blog systems are tools that run the blog as an ongoing process. They derive topics from search queries, write at a fixed pace, put posts into the website via a connection and submit them for approval. What they have in common: they keep running even when you do nothing, and they're limited to one job, the blog.
| Feature | Writing assistant | Blog system |
|---|---|---|
| Who chooses the topic | You | System, from search data, with your correction |
| Who triggers the post | You, every time | The rhythm |
| Who publishes | You, in the CMS | System, via the connection |
| Who links internally | You | System |
| Range of use | All types of text | Blog, possibly shared on social media |
| Pricing logic | Per user, often by word volume | Per post or per month |
| Typical user | Someone who writes themselves and wants to save time | Someone who wants to hand off the blog but keep approval |
A detailed comparison with the best-known assistant is at Using ChatGPT yourself or a blog system.
Which class you need
The decision comes down to a single question: is there someone in the business who wants to and can run the blog? Running it means: choosing a topic every week, generating a draft, checking it, adding images, publishing it, linking it. If yes, an assistant is the cheaper class. If that person is missing, or drops out in busy weeks, the blog system is the class that fills the gap.
Three examples:
- A trust office with an employee who already writes circulars and enjoys writing: assistant.
- A joinery where the owner has no appetite for a second screen in the evening after writing quotes: blog system.
- An online shop with a marketing person who handles newsletters, social media and product texts: assistant for everything except the blog, blog system for the guide section, because otherwise it never gets done.
Checklist for choosing
Whichever class you choose, these eight criteria decide in everyday use, not the length of the feature list.
- Swiss Standard German. Does the tool write without coaching, using ss, Swiss terms and the chosen form of address? With an assistant, that's down to the prompt; with a system, it should be a setting.
- Topic source. Where do the topics come from? Your own head, templates, or search data for your region?
- Factual accuracy. How does the tool handle figures, regulations and names? Does it make things up, flag uncertainty, or leave them out?
- Cliché density. How much editing does the text need before it stops sounding like a machine? The Spotting AI clichés page gives you a checklist.
- Approval. Is there a step between draft and publication that a human checks?
- Connection. Does the post go straight into the CMS, or do you copy it across?
- Data storage. Where are your inputs and texts kept, and who's allowed to use them, and for what?
- Exit. What stays behind when you cancel: the texts, the topic list, the settings?
Questions to ask a writing assistant
- Can I save a company profile with region, services, form of address and writing style, so I don't have to repeat it in every briefing?
- How long can a post be before the tool shortens or cuts it off?
- Is there a mode that only revises rather than rewriting from scratch, for my own drafts?
- How many posts a month does the word allowance in the plan realistically cover?
- What happens to my texts: are they used for training, and can I switch that off?
Questions to ask a blog system
- Where exactly do the topics come from, and can I see and remove them before they're written?
- What happens if I don't approve a post: does it stay pending, does it get overwritten, does it get published anyway?
- What connection is available for my CMS, and what access does the system need for it?
- What do three real, published customer posts look like, with a link?
- What stays on my website after cancellation, and what's the minimum contract term?
A blog system like BlogPilot should have a concrete answer to each of these questions; the terms are on the pricing page. The detailed version of this question list, with twelve questions and an evaluation grid, is at Choosing blog software.
The most common wrong decision
It goes like this: subscribe to an assistant hoping the blog will then run by itself. It won't. The assistant speeds up writing by a factor of three to five, but writing was never the bottleneck. The bottleneck is the Tuesday when the post is due and nobody has time. If you don't have that bottleneck, you don't need a system. If you do, no assistant, however good, will solve it.
The reverse wrong decision also exists: a blog system for a business that actually needs product copy, newsletters and LinkedIn posts. That's too narrow a use for this class of tool. In that case, the assistant is the right tool, and the blog can perhaps come later.
Frequently asked questions
Isn't a blog system just a writing assistant with automation?
The text part is similar, the rest isn't. A blog system decides on topics based on search data, keeps to a publishing schedule, puts posts into the CMS via a connection, and organises approval. An assistant does none of this on its own; it waits for your input.
Which class makes sense for an SME with five employees?
It depends on whether someone in the business actually wants to run the blog. If so, an assistant is enough and saves money. If nobody has the time to find topics, keep to deadlines and publish posts, the blog system is the class that fills that gap.
Can I use both classes side by side?
Yes, and that's common. The blog system delivers the weekly guide post, while the assistant helps with newsletters, quotes, social media texts or revising a post before approval. Both tools then have clearly separate jobs.
What should I watch out for with Swiss Standard German?
Without instructions, assistants usually write in standard German spelling, with ß and German terms. You need to specify the style in every briefing or in a saved instruction. With a blog system, Swiss Standard German should be a setting that's set once and applies to all posts.