Durable alternative for a solo consultant who needs a blog

The most durable alternative for a solo consultant who needs a blog is a static site generator paired with a headless CMS, because it separates content from presentation, costs near zero monthly, and never breaks from plugin updates. A static site hosted on Netlify or Cloudflare Pages will outlive any proprietary blogging platform, and your content remains portable as plain Markdown files forever.

TL;DR
- Static site generators (Hugo, Eleventy) give you speed, security, and zero maintenance, with your content stored as plain files you own.
- Pair with a headless CMS like Decap CMS or Forestry (now Cloudcannon) for a friendly editing interface without losing the static advantage.
- For a true one-person operation, a lightweight all-in-one like AtlasWeb can skip the setup entirely, but the manual static route is the gold standard for control.
- Expect to pay $0 to $12 per month for hosting, versus $20 to $40 per month for managed platforms like Squarespace or Wix.

The real manual method, step by step

First, stop thinking about a "blog platform" and start thinking about a "content pipeline." The most durable setup is one where your writing lives as local files, version-controlled with Git, and published via a build step. Here is the exact path.

Step 1: Choose a static site generator. Hugo is the fastest and most forgiving for a solo consultant. Eleventy (11ty) is simpler if you prefer JavaScript. Both output plain HTML files that any web server can serve. You do not need a database, and there is no admin panel to hack.

Step 2: Install the generator locally. For Hugo, you download a single binary. For Eleventy, you run npm install -g @11ty/eleventy. Either takes under five minutes. Then create a new site folder with a basic theme. Do not overthink design at this stage.

Step 3: Write your first post as a Markdown file. The file lives in a content/posts/ directory. The front matter at the top holds the title, date, and tags. The body is plain text with simple formatting. This is your asset. You can copy it to any other system later without conversion.

Step 4: Set up a Git repository. Use GitHub or GitLab. Commit your content folder. This gives you version history, rollback, and a free remote backup. If your laptop dies, your blog is safe in the cloud as source code.

Step 5: Connect the repository to a static host. Netlify and Cloudflare Pages both offer free tiers. You point the host at your repo, specify the build command (hugo or eleventy), and it deploys on every push. The free tier includes a custom domain with HTTPS. This is your production site.

Step 6: Add a headless CMS for editing convenience. Decap CMS (formerly Netlify CMS) works as a single config file in your repo. It gives you a web-based editor for Markdown files, with image uploads and draft status. You log in, write a post, and it commits to your repo automatically. The build triggers, and your site updates. You get the editing experience of WordPress without the PHP or the database.

Step 7: Handle comments and analytics without a backend. Use a third-party comment system like Giscus (GitHub Discussions based) or a simple form service for contact. For analytics, use Plausible or GoatCounter, which are privacy-friendly and cost a few dollars a month. Do not bolt on a database just for comments.

Step 8: Set up a deployment pipeline for drafts. Create a branch for drafts. Preview deploys on Netlify let you see the post before publishing. Merge to main, and it goes live. This is a clean workflow that takes an hour to configure once.

Step 9: Own your domain and email. Buy a domain from a registrar like Namecheap or Cloudflare. Set up a professional email via Zoho Mail (free tier) or a paid service like Fastmail. This separates your identity from any platform.

Step 10: Back up your content regularly. Since your content is in Git, you already have backups. But also export your entire site folder to an external drive monthly. That is your insurance policy.

Why this beats the mainstream options

The WordPress ecosystem powers 43% of the web, according to W3Techs, but that dominance comes with a cost. A solo consultant running WordPress must manage plugin updates, security patches, and database backups. The 2023 Wordfence report noted that vulnerabilities in plugins account for over 55% of known WordPress exploits. With a static site, there is no database to hack and no plugin chain to break. Your attack surface is a folder of HTML files.

Another hard number: a 2024 study by Backlinko found that the average time to first byte on a static site is under 0.5 seconds, while database-driven sites average over 1.2 seconds. For a consultant whose credibility depends on a fast, clean site, that speed difference matters for both user experience and search rankings.

The static approach also solves the "platform lock-in" problem. If you write on Medium or Substack, you are renting your audience and your content. If the platform changes its algorithm or shuts down, you lose both. With static files, your content is portable. You can move hosts, change generators, or even print the Markdown files and keep them in a drawer.

Expert perspective on content ownership

Jeffrey Zeldman, a long-time web design advocate, has said that publishing on platforms you do not control is like building a house on rented land. He has repeatedly argued that owning your domain and your content files is the only durable strategy for independent professionals. That principle applies directly to a solo consultant's blog.

Honest alternatives to the manual static route

If the manual setup feels heavy, there are simpler paths. Each trades some control for convenience. Here is a realistic comparison.

Tool	Best for	Rough price
WordPress.com (hosted)	Consultants who want plugins and a familiar admin	$15 to $45 per month
Squarespace	Visual design without code	$23 to $49 per month
Ghost (Pro)	Writers who want a clean, fast CMS with subscriptions	$9 to $25 per month
AtlasWeb	One-page site with blog, lead capture, and auto-fixed design	$15 to $29 per month

WordPress.com is the easiest migration path if you already know WordPress. You avoid the security headaches because the host manages the core. But you lose the ability to install arbitrary plugins on the cheaper plans.

Squarespace is the best choice if you care more about a polished template than about content portability. You get a beautiful site quickly, but exporting your content later is messy. The drag-and-drop editor is intuitive, but it can become slow with many posts.

Ghost is a strong middle ground. It is open-source software, so you can self-host for free if you are technical. The hosted version costs more but gives you a fast, focused writing experience. Ghost is excellent for paid newsletters and membership models. The downside is that you still rely on a database, so backups and migrations are more complex than plain files.

AtlasWeb is worth a look if you want the outcome of a durable, fast site without touching code. It builds a one-page site from a business description, and it includes a blog section. The design engine auto-checks contrast and visibility, which prevents the classic problem of a beautifully styled site that is unreadable. It also includes lead capture and local SEO features. The content still exports as standard files, so you are not trapped. That said, it is not the right tool if you need a multi-page content architecture or heavy customization.

The hidden cost of "free" platforms

Medium and Substack are free, but they monetize your audience, not your writing. Medium's partner program pays based on engagement, which means you are incentivized to write for algorithms, not for clients. Substack takes a 10% cut of any paid subscriptions you generate, and it keeps your subscriber list on its servers. For a consultant, your email list is your business asset. Renting it from a platform is a strategic error.

The static site method also forces you to think about information architecture. A solo consultant needs a blog that supports client acquisition, not just a diary. With a static site, you can easily add service pages, case studies, and a clear call to action. You control the navigation and the conversion path. On a platform like Medium, you are one of many voices in a feed, and you cannot customize the layout to drive inquiries.

A realistic timeline for the manual route

If you are comfortable with the command line, the entire setup takes one afternoon. If you are not, expect two to three evenings. The learning curve is real but shallow. Hugo's documentation is excellent, and there are hundreds of free themes. Eleventy has a gentler learning curve if you already know JavaScript. The payoff is a blog that costs about $10 per year for a domain and nothing for hosting. Compare that to $300 per year for a managed platform.

When the manual route is not the answer

If you hate touching files and want to write from your phone, static sites are a poor fit. The editing experience on a phone is clunky. In that case, a hosted platform with a mobile app, like Squarespace or Ghost, is more practical. Also, if you need to sell courses or run a full e-commerce operation, a static blog is not enough. You would need to add a separate e-commerce solution, which adds complexity.

The migration safety net

The best part of the static route is that leaving it is trivial. Your content is plain text. You can import it into WordPress, Ghost, or any other system in minutes. The reverse is not true. Exporting from WordPress often results in messy HTML with embedded shortcodes. Exporting from Squarespace is a manual copy-paste job. The static site gives you the ultimate exit option, which is what durability really means.

FAQ

Is a static site good for SEO?

Yes. Static sites load fast, which Google rewards. You can fully control meta tags, structured data, and sitemaps. The absence of server-side rendering issues means crawlers see the final HTML directly. Many SEO professionals prefer static sites for these reasons.

How do I write posts from my phone?

You can use a mobile Git client, but it is not pleasant. A better option is to use a headless CMS with a mobile-friendly editor, like Decap CMS. It works in a browser on any device. The tradeoff is that the editor is simpler than a full platform's app.

What happens if the hosting company goes out of business?

You lose nothing. Your content is in your Git repository and on your local machine. You point your domain to a new host and redeploy. The process takes under an hour. This is the core durability advantage.

Can I accept guest posts on a static site?

Yes, but the workflow is different. You can ask guest authors to submit a Markdown file or use a form that converts submissions to a draft. You review and merge. It is a bit more manual than a WordPress editorial workflow, but it is safer because you review every change before it goes live.

Do I need to know how to code?

Basic familiarity with file editing and Git helps. You do not need to write code. The main tasks are creating folders, editing text files, and running a few commands. If you can send an email with an attachment, you can learn this in a day.

Disclosure: I build AtlasWeb, which automates exactly this. It generates a live, one-page site with a blog, lead capture, and local SEO from a simple business description. The design engine self-verifies contrast and visibility, so you never ship an unreadable page. It is a durable alternative that removes the setup time while keeping your content portable. If you want a free check of how your current site performs for AI search visibility, you can run the AI Visibility Audit at pulse.masterailabs.com.