<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Writizzy</title>
        <link>https://blog.writizzy.com</link>
        <description>Blog posts from Writizzy</description>
        <lastBuildDate>Mon, 15 Jun 2026 07:51:28 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>Writizzy</generator>
        <language>en</language>
        <image>
            <title>Writizzy</title>
            <url>https://writizzy.b-cdn.net/blogs/42d1f2b8-0289-464e-9d66-1b70ccdfd2d8/1775484493389-aq4ihur.png</url>
            <link>https://blog.writizzy.com</link>
        </image>
        <copyright>All rights reserved 2026, Writizzy</copyright>
        <item>
            <title><![CDATA[How to Build a Multilingual Blog ]]></title>
            <link>https://blog.writizzy.com/p/how-to-build-a-multilingual-blog</link>
            <guid>https://blog.writizzy.com/p/how-to-build-a-multilingual-blog</guid>
            <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Discover how to build a clean multilingual blog without destroying your SEO.]]></description>
            <content:encoded><![CDATA[<p>There are plenty of reasons to build a blog in multiple languages. Personally, I run two blogs: <a href="https://eventuallymaking.io">eventuallymaking.io</a> and <a href="https://eventuallycoding.com">eventuallycoding.com</a>.</p>
<p>I created the second one a long time ago. At this time, the vast majority of the web was in English and let’s be honest, for a long time, English was hard for a lot of people in France :) So I decided to write my blog in French for… french reader.</p>
<p>But over time, I realized I was missing out. Some of my articles could clearly bring value to an English-speaking audience too. After all, I don&#39;t just write about pure tech; I talk about building companies, my experience as a CTO, and leadership.</p>
<p>However, going multilingual is far from simple. You can&#39;t just stack articles one after another using structures like <strong>myblog.com/article1-fr</strong> and <strong>myblog.com/article1-en</strong>. Between duplicate content issues, reader confusion, and SEO penalties, that approach is a recipe for disaster.</p>
<p>In this post, I’ll walk you through the best methods to create a multilingual blog that keeps both your readers and search engines happy.</p>
<h2>URL Structures: The Blueprint</h2>
<p>The very first decision you need to make is how you want to present and organize your content. Generally speaking, you have two main options:</p>
<ul>
<li>Subdirectories: myblog.com/en/ and myblog.com/fr/</li>
<li>Subdomains: en.myblog.com and fr.myblog.com</li>
</ul>
<p>The first method (subdirectories) is what you’ll see most often with WordPress setups using plugins like WPML, Polylang, or Weglot. Personally, I’m not a big fan. I find it creates a bit of confusion for the reader since all content lives under the exact same roof. It also complicates the backend: all your posts are mixed together, making it hard to see at a glance which ones have been translated and which haven&#39;t.</p>
<p>That being said, this method has one huge SEO advantage: the site is treated as a single, massive block. If your French article gets a high-quality backlink from a major media outlet, that &quot;SEO authority&quot; (PageRank) instantly benefits your English articles too.</p>
<p>The second method (subdomains) has other benefits. It’s much cleaner for the reader and offers better peace of mind when you’re writing. However, search engines view each subdomain as an independent site. </p>
<p>In the end, it’s all about trade-offs.</p>
<p>Whichever structure you choose, you must pay close attention to geographic and linguistic targeting. You need to tell search engines exactly who the content is for, and if an alternative version exists in another language.</p>
<p>This is done using <a href="https://en.wikipedia.org/wiki/Hreflang">hreflang</a> tags. They allow you to specify for any given page:</p>
<ul>
<li>&quot;This page is meant for a French-speaking audience.&quot;</li>
<li>&quot;An alternative version of this exact page exists here for English speakers.&quot;</li>
</ul>
<p>Crucially, this prevents search engines from flagging your translated posts as duplicate content. Because even when translated, Google (and others) are smart enough to know it&#39;s the same core content. <strong>You absolutely need to feed them the right data</strong>.</p>
<h2>The Translation Workflow: From Python to AI</h2>
<p>The second challenge is the translation process itself. For years, I translated my first articles entirely by hand. It was incredibly time-consuming, and as a non-native speaker, my English wasn&#39;t always sharp enough to accurately capture local idioms.</p>
<p>Later on, I switched to DeepL. It was faster, but DeepL used to struggle with the broader context of a technical or philosophical article.</p>
<p>More recently, I’ve been using AI. The game-changing advantage of LLMs is their contextual understanding. They can take a specific French idiom and translate it into its actual English equivalent. For instance, if I want to say a tool is decent but &quot;doesn&#39;t break three legs of a duck&quot; (a literal French idiom), the AI knows to translate it as &quot;it’s nothing to write home about.&quot; It saves an incredible amount of time.</p>
<p>Still, human proofreading remains mandatory. You always need to replace localized reference links, tweak the tone, and double-check that no mistranslations slipped through.</p>
<p>For a long time, my workflow relied on custom Python scripts. I would write in Google Docs, download the content via a script, and shoot it to the DeepL API. It worked, but managing the whole pipeline was a massive chore.</p>
<p>And that is exactly why I couldn’t wait to solve all these pain points with Writizzy.</p>
<h2>The Writizzy Solution</h2>
<p>When building <a href="https://writizzy.com">Writizzy</a>, my ultimate goal was to streamline the writing workflow as much as humanly possible. And today, the multilingual feature has officially arrived.</p>
<p>I made design choices that prioritize clarity and user experience. From now on, you can leverage our multi-blog feature to run an English blog and a French blog side-by-side (and as many other languages as you want).</p>
<p>Each blog is mapped to its own language, naturally adopting the clean subdomain structure: e.g., hugo.writizzy.com and eventuallymaking.writizzy.com.</p>
<p>Inside the dashboard, I added a translation status indicator to the post list. You can see at a glance if an article is missing a translation, making your content todo-list crystal clear.</p>
<p><img src="https://writizzy.b-cdn.net/blogs/42d1f2b8-0289-464e-9d66-1b70ccdfd2d8/1780927522283-2nnz54f.png" alt="list of posts with a translation status" /></p>
<p>When working on a post, Writizzy allows you to either link it to an existing article or automatically translate the entire draft into another language. The time saved is just massive.</p>
<p><img src="https://writizzy.b-cdn.net/blogs/42d1f2b8-0289-464e-9d66-1b70ccdfd2d8/1780927572253-yvvs12a.png" alt="automatic translation for a post" /></p>
<p>And of course, Writizzy handles all the heavy lifting for hreflang tags under the hood, ensuring your SEO remains flawless and protected against duplicate content penalties.</p>
<p>Long story short: you can now seamlessly run a beautiful, SEO-friendly multilingual blog on Writizzy. 😉</p>
]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manage all your blogs in one place: multi-blog support is here]]></title>
            <link>https://blog.writizzy.com/p/manage-all-your-blogs-in-one-place-multi-blog-support-is-here</link>
            <guid>https://blog.writizzy.com/p/manage-all-your-blogs-in-one-place-multi-blog-support-is-here</guid>
            <pubDate>Thu, 26 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[If you are like me, you may have multiple blogs.]]></description>
            <content:encoded><![CDATA[<p>If you are like me, you may have multiple blogs.</p>
<p>Until now, juggling multiple blogging projects could be a logistical headache. Today, we are stripping away that friction. We are excited to announce the launch of <strong>Multi-Blog support</strong> on Writizzy.</p>
<h2>Why Multi-Blog?</h2>
<p>I know that forcing everything into a single blog often leads to a messy experience for readers. People who follow you for coding tips might not be interested in your favorite cooking recipes.</p>
<p>Multi-blogging allows to keep your content organized and relevant:</p>
<p>With this update, you can now:</p>
<ul>
<li><strong>Switch in one click</strong>: Jump from one dashboard to another without the constant dance of logging in and out.</li>
<li><strong>Centralize your management</strong>: A single interface to pilot all your different publications.</li>
<li><strong>Keep contexts separate</strong>: Each blog retains its own settings, unique domain, and specific audience.</li>
</ul>
<h2>Leading by Example</h2>
<p>To give you an idea of how much this changes the workflow, I’ve been using this feature daily to manage my own three distinct blogs:</p>
<ol>
<li><strong><a href="http://eventuallymaking.io">eventuallymaking.io</a></strong>: My thoughts on product , tech and engineering leadership (in English).</li>
<li><strong><a href="http://eventuallycoding.com">eventuallycoding.com</a></strong>: the same, but in French.</li>
<li><strong><a href="http://blog.writizzy.com">blog.writizzy.com</a></strong>: This very blog, where we share the behind-the-scenes and updates of our SaaS platform.</li>
</ol>
<p>Three domains, two languages, different targets, but one seamless writing experience.</p>
<h2>How to Get Started</h2>
<p>It couldn’t be simpler. In your dashboard, you will now find a blog selector. You can add a new blog to your account in seconds and start publishing immediately. Whether you are a solo creator or part of a team, the transition is invisible.</p>
<p><strong>So, what will your next blog be?</strong></p>
<p>Log in to your Writizzy dashboard and try the switch today!</p>
]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monetize your blog without commissions]]></title>
            <link>https://blog.writizzy.com/p/monetize-your-blog-without-commissions</link>
            <guid>https://blog.writizzy.com/p/monetize-your-blog-without-commissions</guid>
            <pubDate>Wed, 18 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Turn your passion into revenue. Writizzy now supports paid subscriptions with premium content. The best part? We take 0% commission on your earnings.]]></description>
            <content:encoded><![CDATA[<p>Since we started Writizzy, our mission has been clear: providing a sovereign space for those who actually write. But &quot;sovereignty&quot; isn&#39;t just about owning your data, it’s also about <strong>owning your revenue.</strong></p>
<p>Today, we’re excited to announce a feature many of you have been waiting for: <strong>Paid Subscriptions.</strong> This is a major step for Writizzy. We are now a serious alternative to Substack but without commission. </p>
<h2>Premium Content, Simple Setup</h2>
<p>We wanted to make monetization as frictionless as the writing experience itself. You can now offer your readers the option to support your work directly through a monthly subscription.</p>
<p><strong>How it works:</strong> On every post you write, you now have a simple toggle: <strong>Free</strong> or <strong>Premium</strong>.</p>
<ul>
<li><strong>Free posts</strong> keep building your reach and attracting new readers.</li>
<li><strong>Premium posts</strong> are reserved for your most loyal supporters, allowing you to share deeper insights, exclusive stories, or specialized knowledge.</li>
</ul>
<p>Your subscribers get a seamless experience, receiving both your public and private updates directly in their inbox or on your blog.</p>
<h2>The Writizzy Difference: 0% Commission</h2>
<p>This is where we stand apart from the &quot;big&quot; platforms.</p>
<p>Most platforms take a cut of your revenue—usually between 5% and 10%. When you’re just starting out, it feels like a small price to pay. But as you grow, that &quot;tax&quot; on your hard work becomes a massive burden. To be honest, we’ve always found this model <strong>unfair</strong>.</p>
<p><strong>At Writizzy, we take 0% commission on your subscriptions.</strong></p>
<p>Here is our logic: our effort as a platform isn&#39;t proportional to your earnings. Whether you charge $5 or$50 to your readers, our job remains the same.</p>
<p>We don&#39;t see why we should tax your success.</p>
<p>If your audience grows, your infrastructure needs might increase (like email volume), and that’s reflected in our transparent subscription tiers. But your actual revenue? That’s the result of <strong>your</strong> work and <strong>your</strong> relationship with your readers. </p>
<p><em>(Note: The only fees you’ll pay are the standard Stripe processing fees—we haven’t found a way to bypass those... )</em></p>
<h2>Why Monetize Now?</h2>
<p>Beyond the revenue, it’s about the relationship between you and your audience.</p>
<p><strong>1. Authenticity has a price</strong> In a world of &quot;free&quot; platforms, we’ve learned that when the product is free, <em>you</em> (and your readers) are the product. Your data is tracked, sold, and used to feed algorithms. By offering a paid tier, you’re making a different promise. It guarantees your editorial independence because you only answer to the people who value your work.</p>
<p><strong>2. A healthy constraint</strong> We don&#39;t steal your data. We don&#39;t sell ads. This is a commitment, but it’s also a constraint: to keep building this independent space, we (and you) need to make a living from it. Paid subscriptions are the cleanest, most honest way to fund a sustainable project without compromising on ethics.</p>
<p><strong>3. Quality over Noise</strong> When you’re paid directly by your readers, you don&#39;t need to chase clicks or create &quot;noise&quot; to survive. You can focus on what matters. It’s a shift from quantity to quality.</p>
<h2>How to get started</h2>
<p>The feature is already live in your dashboard. Just head to your <strong>Settings</strong>, connect your Stripe account, and set your pricing. You can be up and running in less than 5 minutes.</p>
<p>We can’t wait to see what kind of premium communities you’re going to build.</p>
<p><strong>Hugo &amp; Thomas</strong></p>
]]></content:encoded>
            <category>product update</category>
        </item>
        <item>
            <title><![CDATA[Protect Your Content: How to Block (or Allow) AI Bots on Your Blog]]></title>
            <link>https://blog.writizzy.com/p/protect-your-content-how-to-block-or-allow-ai-bots-on-your-blog</link>
            <guid>https://blog.writizzy.com/p/protect-your-content-how-to-block-or-allow-ai-bots-on-your-blog</guid>
            <pubDate>Fri, 23 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Your content, your choice. Discover Writizzy’s new feature to block AI crawlers like GPTBot from training on your writing with a simple toggle.]]></description>
            <content:encoded><![CDATA[<p>One of the biggest debates in the creative world right now is how AI models use our work. Should an AI be allowed to &quot;train&quot; on your personal stories, your research, or your unique insights without your explicit consent?</p>
<p>At Writizzy, we believe the answer should be in your hands. That’s why we’ve introduced a new feature: <strong>the AI Crawler Toggle.</strong></p>
<p><img src="https://writizzy.b-cdn.net/blogs/42d1f2b8-0289-464e-9d66-1b70ccdfd2d8/1775652683801-mc9o7ri.png" alt="option available within your settings to block AI bots or not" /></p>
<h2>How it works (and what it does)</h2>
<p>In your settings, you’ll now find a simple checkbox: <strong>&quot;Allow AI bots to crawl your content.&quot;</strong></p>
<ul>
<li><strong>Disabled by default:</strong> Because we respect your privacy, this is turned off from the start. Your content is not an open buffet for AI training unless you say so.</li>
<li><strong>The robots.txt directive:</strong> When disabled, we automatically update your <code>robots.txt</code> file to tell crawlers like <em>GPTBot</em> (OpenAI) or <em>Claude-Web</em> (Anthropic) to stay away.</li>
</ul>
<h2>A quick reality check</h2>
<p>It’s important to be transparent: the <code>robots.txt</code> file is <strong>indicative</strong>. It’s like a &quot;No Trespassing&quot; sign on a fence.</p>
<ul>
<li><strong>The &quot;Good Citizens&quot;:</strong> Major AI companies (Google, OpenAI, Anthropic) generally respect these directives. If you tell them to stop, they usually do.</li>
<li><strong>The &quot;Outlaws&quot;:</strong> Some smaller or less ethical bots might ignore the sign and crawl anyway. There is no magic &quot;delete&quot; button for the internet, but using this toggle is currently the most effective standard way to protect your work.</li>
</ul>
<h2>Should you allow it?</h2>
<p>Why would someone <em>want</em> to be crawled by AI? There are a few reasons:</p>
<ul>
<li><strong>Visibility:</strong> Some AI-powered search engines (like Perplexity or Google Search Generative Experience) might use your content to answer queries and provide links back to your blog.</li>
<li><strong>Reference:</strong> If your goal is to be cited as an expert by AI assistants, they need to be able to read you.</li>
</ul>
<h2>Our Philosophy: Consent First</h2>
<p>Whether you want to be cited by AI bots or keep your writing strictly for human eyes, it’s your call. Writizzy is just here to provide the &quot;No Trespassing&quot; sign if you need it.</p>
<p>You can find this new option in your <strong>Dashboard &gt; Settings &gt; SEO &amp; Indexing</strong>.</p>
<p><strong>Hugo &amp; Thomas</strong></p>
]]></content:encoded>
            <category>product update</category>
        </item>
        <item>
            <title><![CDATA[Making Blogging Fair: Why Writizzy Implements Purchasing Power Parity (PPP)]]></title>
            <link>https://blog.writizzy.com/p/making-blogging-fair-why-writizzy-implements-purchasing-power-parity-ppp</link>
            <guid>https://blog.writizzy.com/p/making-blogging-fair-why-writizzy-implements-purchasing-power-parity-ppp</guid>
            <pubDate>Wed, 05 Nov 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Why Writizzy uses Purchasing Power Parity (PPP) to offer fair global pricing.]]></description>
            <content:encoded><![CDATA[<p>At Writizzy, we’re building a global platform. But &quot;global&quot; shouldn&#39;t just mean &quot;available everywhere&quot;, it should mean <strong>accessible to everyone.</strong></p>
<p>Until now, we’ve mostly worked on products centered in Western Europe. But recently, we received a message that made us stop and think:</p>
<blockquote>
<p><em>&quot;Hi there, your product is awesome... However, can you implement a purchasing power parity policy? Your current pricing is too high for me in Indonesia.&quot;</em></p>
</blockquote>
<p>This is a real issue for any independent creator. If you’re in Vietnam, Brazil, or Poland, a <strong>$10/month</strong> subscription doesn&#39;t represent the same part of your budget as it does for someone in the US or France.</p>
<h2>The Big Mac, the Median Salary, and Fairness</h2>
<p>You’ve probably heard of the <strong>Big Mac Index</strong>. It’s the simplest way to understand Purchasing Power Parity (PPP).</p>
<p>To put it into perspective:</p>
<ul>
<li>In the <strong>US</strong>, the median salary is around <strong>$3,800/month</strong>. A $10 subscription is <strong>0.3%</strong> of that budget.</li>
<li>In <strong>Vietnam</strong>, the median salary is around <strong>$350/month</strong>. That same $10 represents <strong>3%</strong> of their budget.</li>
</ul>
<p><strong>Is it fair? No.</strong> If we want to be the home for authentic writing worldwide, we can’t ignore the economic reality of our writers.</p>
<h2>Why most SaaS avoid PPP (and why we don&#39;t)</h2>
<p>Most companies avoid PPP for two reasons: <strong>Production costs</strong> and <strong>VPN &quot;tourists.&quot;</strong></p>
<ol>
<li><strong>Production Costs:</strong> Our servers cost the same in Euros regardless of where our users are. But as a lean, bootstrapped team, we focus on <strong>marginal costs</strong>. As long as a user covers the cost they generate (hosting, emails, support), they help the platform grow. Having 5,000 users in Southeast Asia at a fair local price is better for the ecosystem than having zero because we were too rigid.</li>
<li><strong>The VPN Problem:</strong> Sure, some people might try to use a VPN to pay less. We could spend thousands of dollars on complex verification systems, but we’d rather spend that time building features you actually want.</li>
</ol>
<p><strong>Our stance? We will trust people.</strong> We believe the vast majority of our community values what we’re building and won&#39;t spend their energy trying to &quot;cheat&quot; the system for a few dollars.</p>
<h2>How it works on Writizzy</h2>
<p>We want to keep things simple and human. Instead of an automated, cold algorithm, we’re doing this <strong>on-request.</strong> If our standard pricing is a barrier for you due to your country’s purchasing power, here is the process:</p>
<ul>
<li><strong>Check our documentation:</strong> our <a href="https://writizzy.com/docs/welcome/ppp">PPP Docs</a>.</li>
<li><strong>Send us an email:</strong> Reach out at <strong><a href="https://blog.writizzy.commailto:contact@writizzy.com">contact@writizzy.com</a></strong> mentioning your country.</li>
<li><strong>Verification:</strong> No passports, no invasive data (we don’t want to store such sensitive information !). Just a link to your public LinkedIn or professional profile is enough.</li>
<li><strong>Get your code:</strong> We’ll send you a personal coupon code to adjust your subscription.</li>
</ul>
<h2>Building a better web, one country at a time</h2>
<p>Blogging is the ultimate space for personal expression. We don&#39;t want your geography to dictate whether or not you can own your corner of the internet.</p>
<p><strong>Hugo &amp; Thomas</strong></p>
]]></content:encoded>
            <category>product update</category>
        </item>
        <item>
            <title><![CDATA[Why we are building Writizzy]]></title>
            <link>https://blog.writizzy.com/p/welcome-to-your-new-blog</link>
            <guid>https://blog.writizzy.com/p/welcome-to-your-new-blog</guid>
            <pubDate>Sat, 01 Nov 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Discover the story behind Writizzy. Built by Hugo Lassiège (Malt) and Thomas Sanlis (Uneed), we’re creating a European, independent alternative for authentic writing.]]></description>
            <content:encoded><![CDATA[<p><strong>Why we are building Writizzy (and why now)</strong></p>
<p>Launching a blogging platform in 2026 might seem like a counter-intuitive bet. Between social media fragmenting our attention and the explosion of AI-generated noise saturating the web, why add one more destination?</p>
<p>The answer is simple: <strong>we want to make writing meaningful again.</strong></p>
<h2><strong>The end of authenticity?</strong></h2>
<p>We see it every day: the web is drowning in &quot;AI slop.&quot; It’s becoming impossible to tell if what you’re reading was actually thought out by a human or spat out by a prompt in three seconds.</p>
<p>At Writizzy, we are convinced of one thing: <strong>trust and authenticity still matters.</strong> This trust isn’t built with three-line &quot;hooks&quot; on X or LinkedIn. It’s built with long-form, thoughtful content where you take the time to share a vision. This is exactly why we wrote <a href="https://writizzy.com/docs/welcome/manifesto">our Manifesto</a>: to define what we stand for.</p>
<h2><strong>Two paths, one shared frustration</strong></h2>
<p>Writizzy was born from the meeting of two &quot;indie makers&quot; who believe in &quot;eating their own dog food&quot;:</p>
<ul>
<li><strong>Hugo Lassiège:</strong> I’ve been blogging since 2001 (the good old days of <em><a href="http://free.fr">free.fr</a></em>). After co-founding <strong>Malt</strong>, I felt the need to get back to tools that aren&#39;t bloated corporate machines. I created <em>Bloggrify</em> and <em>Hakanai</em> to reclaim that freedom.</li>
<li><strong>Thomas Sanlis:</strong> As a designer and the founder of <strong>Uneed</strong>, I’m obsessed with simplicity. I wanted a tool that is a joy to use every day, without the friction.</li>
</ul>
<p>We looked at the market and nothing quite fit: <strong>Beehiiv</strong> is expensive, <strong>Medium</strong> locks you in, and <strong>Substack</strong> is pushing more and more towards a &#39;closed garden&#39; model, prioritizing their own ecosystem over your independence. Most importantly, almost no serious alternative is <strong>European</strong>. Not out of nationalism, but because we believe it’s healthy to have options outside of the US giants when you entrust a platform with your content.</p>
<h2><strong>Powerful, but never bloated</strong></h2>
<p>To be clear: we aren&#39;t building a &quot;minimalist&quot; tool that lacks power. Writizzy will be a complete platform. We will offer everything a modern author needs: newsletters, analytics, audience management...</p>
<p><strong>The difference? Clarity.</strong> At least, that’s what we hope for, and we’ll do everything we can to make it happen.</p>
<h3><strong>Our three core pillars:</strong></h3>
<ul>
<li><strong>No Lock-in:</strong> Your content is yours. Reversibility is a first-class citizen: you can import and export your entire blog in a click.</li>
<li><strong>Zero Commission:</strong> We charge a flat subscription fee. If your audience explodes, our take doesn&#39;t. Your success belongs to you.</li>
<li><strong>No AI Factories:</strong> You won&#39;t find a &quot;Write this article for me&quot; button. If you don&#39;t take the time to write it, your readers shouldn&#39;t have to take the time to read it.</li>
</ul>
<h2><strong>A Bootstrapped journey</strong></h2>
<p>Writizzy is just the two of us. No investors, no insane growth pressure that eventually degrades the product. We want to build a sustainable platform, funded solely by its users.</p>
<p>If enough people find value in what we’re building, we’ll keep refining the tool until it’s perfect.</p>
<p><strong>We’re building Writizzy for ourselves. We hope it’ll be for you, too.</strong></p>
<p><strong>Hugo &amp; Thomas</strong></p>
]]></content:encoded>
        </item>
    </channel>
</rss>