Writing Every Article Yourself: A Practical Guide

You can write every article on your site yourself, and for some businesses it is the right call. It stays sustainable only if you treat each article as a repeatable process rather than a burst of inspiration. You need a fixed set of facts you write from, a short sequence of stages every piece passes through, and a clear rule for which articles deserve your personal time.

This guide gives you that process. The cited sources are general guides to the writing process, written for students and scholarly writers rather than for blogs. The stages they describe are applied here to blog articles, along with a few editorial checks that matter when the goal is customers from search. The workflow in the later sections is the author's recommendation, not an industry standard, so adjust it to your own pace.

Decide whether writing everything yourself fits your goal

Writing your own articles has real advantages. You know the product, the customers and the objections better than anyone you could brief. Your voice is consistent, and nothing gets published that you have not personally read.

The cost is time and continuity. A founder's writing slot is easily the first thing to disappear in a busy month, and a blog that goes quiet stops building anything. So before committing, answer three questions honestly:

Can you protect writing time every week, not just when things are calm? If the answer is no, a smaller, steadier plan beats an ambitious one.
Is your expertise the product of the article? Opinionated pieces, customer stories and "how we do it" explanations are hard to hand off. Generic definitions are easier.
Are you willing to edit your own work critically? Writers who skip revision publish drafts, and drafts read like drafts.

If you answered yes to most of them, the rest of this guide is for you. If not, skip ahead to the section on splitting the work.

Treat each article as four stages, not one task

MIT's writing center describes the writing process as having at least four distinct steps: prewriting, drafting, revising and editing. It is also recursive, meaning that while revising you may need to go back to prewriting to develop or expand your ideas [1]. Purdue's writing lab describes a similar sequence: writers usually start by choosing a topic and brainstorming, may outline, compose a rough draft, and then may revise by adding or removing sentences [2].

Applied to a blog, "writing an article" is really four jobs with different mindsets: inventing ideas, producing sentences, judging them and fixing commas. If writing feels exhausting, check whether you are trying to do all four in the same sitting. Giving each job its own stage is the author's suggested remedy.

Prewriting: decide what the article must do

Before you draft a sentence, write down:

The reader. Who is searching for this, and what situation are they in? Purdue's revising guide, written for papers, asks you to identify your readers and your purpose, meaning what the piece is trying to do [4]. The same question works for a blog post.
The main point. One or two sentences you could say out loud. The same guide suggests summarizing your main point and the evidence supporting it, then imagining the piece belongs to someone else and asking whether you know what it is going to be about [4].
The facts you will rely on. Pricing, features, process steps, service areas, guarantees, and any claim about your product. Pull these from one place you maintain, so you are not recalling them from memory.
The search question. The plain-language question a customer would type. Your title and first paragraph should answer it.

A page of notes is enough. If you cannot state the main point, the article is not ready to be drafted, and drafting will only hide that.

Drafting: get the whole thing down without judging it

Draft quickly and in order. Do not polish while drafting. Lead with the answer to the search question, then add the explanation, the steps or examples, and the caveats. Leave a visible marker, such as "CHECK:", beside any number, date or claim you are unsure about, and keep going. Stopping to look things up breaks the flow, and you can resolve every marker in revision.

Revising: fix the big things first

Revision and editing are different jobs. Purdue's guide compares revision to the big changes in a renovation, such as tearing out the kitchen or removing a wall, while editing generally comes as the very last step before submitting, possibly in more than one pass [3].

For a blog article, these revision questions are the author's suggestions:

Does the opening answer the question the reader came with?
Is every section earning its place, or is some of it background you enjoyed writing?
Is anything missing that a skeptical customer would ask next?
Does each claim have a source or a fact you can point to?

The same Purdue guidance advises adding needed information, eliminating irrelevant information and clarifying sections or sentences [4]. It also recommends putting your writing aside at least twice: once early when reorganizing, and once later when polishing, and it notes that forgetting about a draft for a day or two lets you return with a fresh outlook [4]. Author's suggestion: if you publish weekly, stagger your articles so one is resting while you work on another.

Editing: the last pass

Only after the structure holds should you edit sentences: tighten wording, fix grammar, check names, links and formatting. Editing generally comes last [3], and the author's reasoning is that editing early risks wasting effort on paragraphs you may later delete.

A recommended weekly rhythm for a solo writer

Treat the following as the author's suggested structure, to adapt to your own schedule. Its logic is to give each stage its own slot so you never face a blank page and a blank calendar at the same time.

Hypothetical example: a founder aiming for one article a week might use four short sessions on different days.

Session	Stage	What you produce
Early in the week	Prewriting	A one-page brief for the next article: reader, main point, facts, search question
Next	Drafting	A complete rough draft with "CHECK:" markers left in
Later	Revising	A restructured draft with every marker resolved
End of week	Editing and publishing	A clean final article, published and checked on the live page

Author's suggestion: write the brief for next week's article while this week's article rests, so the pause overlaps with other work instead of stalling your calendar.

If you plan more than one article a week, check whether these sessions still fit your calendar. If they do not, that is the signal to rethink scope, covered below.

Build a facts sheet so you are not writing from memory

One risk in founder-written content is not bad prose. It is small factual drift: a feature described as it worked last year, a price that has changed, a claim that was true for one customer type. Over a library of articles, these contradictions accumulate.

Keep a single facts sheet and write from it:

What you sell and who it is for
Current pricing and plan details, or the statement that you do not publish pricing
What your product or service does and does not do
Your process, from first contact to delivery
Claims you are willing to make and the evidence behind each one
Claims you will not make

When something changes, update the sheet first and then fix any article that mentions it. Before publishing, scan the draft and confirm every product statement exists on the sheet. Anything that does not should either be added to the sheet deliberately or cut.

For statements about the outside world, such as how search works or what an industry typically does, link to a source you have actually read, or leave the claim out. Avoid inventing statistics because they sound plausible. A confident number you cannot trace is a liability.

A pre-publish checklist

Run this after editing, before you hit publish:

Answer check. Read only the title and first paragraph. Does that alone answer the search question?
Claim check. Highlight every number, date, price and product statement. Can you point to the facts sheet or a source for each?
Reader check. Purdue suggests imagining the paper belongs to someone else and asking whether it has a clear thesis [4]. Do that with your draft.
Scope check. Delete any section that does not serve the main point, even if it is good.
Link and format check. Confirm links work, headings are descriptive, and the page renders properly.
Live check. After publishing, open the real page in a browser and confirm the right version is showing.

None of these steps is difficult. Their value is that they happen every time, including in the weeks when you are tired.

Protect the habit: where solo writing can break

A few patterns can derail self-written blogs. Plan for them in advance.

Perfectionism in drafting. If you edit as you draft, each article may take longer and you may start avoiding the work. Keep drafts rough on purpose.

Topic scarcity. If you run out of ideas, check your prewriting. Keep a running list of real customer questions from emails, sales calls and support tickets, and draw topics from it.

Over-ambition. If you miss sessions repeatedly, lower the target instead of lowering quality.

No revision gap. Publishing the same day you finish drafting leaves no room to set the draft aside. Purdue's guidance says that forgetting about a draft for a day or two lets you return with a fresh outlook [4].

Neglecting published pages. Writing new articles is only part of the job. Pages already live need occasional review against your facts sheet, especially after pricing or feature changes.

Which articles to write yourself and which to hand off

You do not have to choose between writing everything and writing nothing. This is the author's recommendation for sorting your list:

Article type	Suggested approach
Opinion pieces, customer stories, founder perspective	Write yourself; your voice is the value
Detailed explanations of how your product or process works	Write yourself, or draft from your facts sheet and review closely
Common customer questions with straightforward answers	Good candidates for assisted drafting, with a fact review before publishing
Pages that need regular refreshing	Review on a schedule; hand off or automate only if you can verify the result

Whichever way you go, the principle holds: nothing goes live that you have not either written or confirmed against your own facts.

Where Pentra fits, if you decide to hand part of it off

If the answer to the first question in this guide was "no, I cannot protect the time," Pentra is one way to take routine articles off your plate while keeping the facts under your control. Pentra is autopilot SEO software. It reads your website and drafts a business profile that you confirm, researches keywords people search for, and writes articles from those confirmed facts. A separate fact check reviews each article before it goes out. Pentra then publishes to WordPress or a GitHub-based site on the schedule you choose and checks that the page is live. It also improves published pages that sit close to page one and reports results from your Google Search Console data.

You can choose Autopilot or Review first: pick a pace from 1 to 21 articles a week, or approve every article yourself. The free plan includes 3 articles a month and requires no credit card, so you can compare the output with your own standards before deciding how much to delegate.

A reasonable test: keep writing the opinion and story pieces yourself, hand a few straightforward customer-question topics to the free plan in Review first mode, and compare the drafts with what you would have written. If you find yourself rewriting them heavily, your facts sheet probably needs more detail or those topics should stay with you.

Try Pentra

A Practical Guide to Writing Every Article Yourself