Building your team's blog just got easier with Writizzy

I have written a lot of blog posts for myself.

Then I started a company, and inside that company I built the engineering team. I wanted us to adopt those same writing habits, because writing pays off in many ways.

First, it is a great way to formalise things, and to explain them simply. As Boileau put it, "Whatever we conceive well we express clearly". Writing a good post forces you to dig into a subject and clarify your own thinking about it.

Then it is excellent documentation "for the record". Code lives alongside documentation that describes it at a given point in time. Blog posts let you trace back where the decisions came from, and why. Why we went with feature flags, with a monorepo, why we picked MongoDB (and why we later decided to drop it). A post is history, not just a technical tutorial.

Finally, it is a showcase for your brand. A blog reflects the culture of the team writing it. Plenty of candidates came to us through our posts, won over by the culture that showed through them, and they started the conversation right there.

It is also an asset for your company's SEO. I have been talking about teams here, mostly engineering ones, but really anyone in your company can use this, along with everything else Writizzy brings: detailed analytics, newsletters tuned for deliverability, SEO audits and more.

So of course, for Writizzy, I wanted team writing to feel first class:

A proper editorial setup

Writizzy comes with several roles, contributor, author and editor, and you can change them at any time. They define who can write, who can review and who can publish. Nice bonus: there is no limit on how many people can join a team.

An optional review cycle

By default, everyone publishes their own posts, just like before. But if you would rather have a second pair of eyes on a post, the author sends it to review in one click. It lands in the "In review" tab, the reviewer gets an email, opens the post, leaves notes, and either publishes it or sends it back to the author.

Discussion threads, built in

No more back and forth in Google Docs. Write and approve your posts in the same place, and leave review notes right inside the post to talk things through with your reviewers.

Version history and conflict handling

You will never lose anything. Nothing is more frustrating than several people editing the same document and one of them silently overwriting the other. Writizzy now detects those conflicts, and keeps a version history so you can roll back easily.

Your own custom domain

You should be building your own brand, not lending your reputation to someone else. It is better for your SEO, and it also makes it easy to move elsewhere later if you ever want to.

What about you?

Want to give it a go? Create an account on Writizzy to try the basics, then pick the "Teams" plan to invite the rest of your team.

And if you already write somewhere else, Medium, Substack, Ghost, WordPress or Beehiiv, your posts come over in a single import, images included.

One last thing: send us your feedback. The product moves forward every day thanks to what its users tell us.