Publizo: AI publishing SaaS I designed and built

Publizo is an AI publishing system that researches, writes and fact-checks SEO articles, then publishes them to WordPress on a schedule. I designed and built it end to end: research, product design, the editorial system and the brand. It's a multi-tenant SaaS with live billing, and it publishes every day to three sites I run.

Most AI writers produce volume, not articles you'd publish under your own name. If the first article looks publishable, people stay. If it looks generic, they leave within a minute. So the free plan delivers a finished article on the first try, and a quality gate holds weaker drafts back instead of pushing them live.

Generate, Sites, History and Settings. Free and paid plans share the same shell, so nobody relearns the product when they upgrade. I tested grouping articles into projects and dropped it: it added clicks without adding meaning, because a site already carries that context.

The hardest design problem wasn't the dashboard. It was whether the article that lands on someone's site reads like a person wrote it. Most of that work was prompt design, evaluation and house style rules:

Banned punctuation and phrasing handled at the model layer

Leads that take a side in the first 80 words

Structure decided per topic, not per template

A draft that scores below the threshold retries with a stricter prompt, and after a second miss it lands as a draft instead of going live

Sign-up is one screen with Google or email, and no tour. New users see a finished sample article before they connect a site, and the path to a first published article fits on a single screen.

A free plan with five articles a month, monthly plans for solo writers and for operators with several sites, and a lifetime Founding Member plan capped at 20 seats. Paid tiers list what they include, never what cheaper tiers lack. Choosing a paid plan carries through sign-up straight to checkout.

Try it at publizo.io with five free articles a month. The full case study, including the QA, security and reliability problems I found and fixed, is on danielpetrevski.com.