How to Write Blog Posts When You're Not a Writer

Read this with AI

Read with ChatGPT Read with Claude Ask Gemini

Short answer: You don't need to write well to blog for your business. You need to answer the questions your customers already ask you, in plain words, the way you would explain it at the counter. Talk it out, keep it short, and fix it once. That is the whole job.

The block is almost never about writing. It is about a blank page and the fear that whatever you type will sound wrong. You already explain your trade twenty times a day. A customer asks why their kitchen lights flicker, and you answer in thirty seconds without once thinking about grammar. A blog post is that answer, typed once, so the next hundred people who ask can read it instead of calling.

You are not the first owner to freeze here. A small-business owner named Mark Hayward, writing on ProBlogger, called himself the dictionary "poster child" for a non-writer and said that until recently he "would never have published anything on the Internet because I have never considered myself a writer." He named the three complaints he hears most from owners: "I don't have the time," "I am not a writer (or I hate writing!)," and "I don't know what to write about." Then he made the point this whole article rests on: "you don't have to be a writer in order to be a small business blogger."

It is worth pushing through, because the payoff is real. HubSpot's blogging statistics report that companies with blogs produce about 67% more leads per month than companies without one, and that sites with an active blog have 434% more indexed pages, citing DemandMetric and BKA Content respectively. Every plain answer you post is another page Google can find, and another reason a stranger calls you first.

This is not a guide to launching a blog or to general writing mechanics. If you want those, start with what business blogging actually is and the general how-to on writing a post. This piece is about the one thing that stops most owners cold: the belief that you can't write. Here is how to work around it, step by step.

Start from a question a customer actually asked you

Do not open a blank document and try to think of a topic. Open your phone instead. Scroll your texts, your emails, your booking messages, and write down the last ten questions customers asked you. That list is your first ten blog posts.

An electrician gets asked "why do my lights flicker when the fridge kicks on?" every week. A florist gets asked "how long will these last if I keep them in the car for an hour?" almost daily. You already know both answers cold. The post writes itself the moment you stop inventing a topic and start with a real question.

The best part is that these are the exact phrases people type into Google. When you title a post with the customer's own question, you match the way they search. To find more of them, look at the People Also Ask questions Google shows for your trade, and mine the questions your customers and competitors keep answering. Your inbox is the first place to look, not the last.

Outline it before you write anything: title first, then bullets

The reason the page feels blank is that you are trying to write and think at the same time. Split the two. Write the title first, then list your main points as bullets, then and only then fill them in.

Keap's small-business blogging guide calls the outline "the oldest trick in the (writing) book" and says to start with your headline, then flesh out your main points before you write a single sentence. The same guide is honest that a good business blog is "tricky for writers and non-writers alike" and mostly "just takes practice," so do not wait to feel ready.

Say the electrician's title is "Why your lights flicker when the fridge turns on." The bullets might be: what flickering means, the common cause (a shared circuit and a big motor), when it is normal, when to call an electrician. Four bullets. Now each one is a two-sentence job, not a scary essay. If titles are where you stall, writing the headline first is its own small skill worth learning.

Talk it out loud instead of typing

This is the biggest unlock for non-writers, so try it before anything else. You are not bad at explaining. You are bad at typing while judging yourself. So do not type. Open the voice memo or dictation on your phone, pull up your outline, and just answer each bullet out loud like a customer is standing in front of you.

Mark Hayward's second option on ProBlogger is exactly this: for owners who refuse to write a word, he recommends using speech-recognition software to talk your posts out, and notes those posts still rank in Google. An electrician can dictate a whole post in the van between jobs. A florist can talk one out while trimming stems. The words come out in your voice because you never stopped to "write."

Then you clean it up. Spoken drafts have false starts and rambles. That is fine. You cut those in the tidy pass later. Getting the answer out of your head is the hard part, and talking is the fastest way to do it.

Write the way you would explain it at the counter

Once the words are down, resist the urge to make them sound fancy. The counter voice is the right voice. Short sentences. Plain words. No "utilize," no "in order to," no phrases you would never say to a real person.

There is a hard reason plain writing wins, not just a friendly one. A Snopes fact-check, rated true, reviewed U.S. Department of Education and APM Research Lab data from the PIAAC adult-skills assessment and found that about 130 million U.S. adults, roughly 54% of those aged 16 to 74, read below the equivalent of a sixth-grade level. Writing plainly is not dumbing down. It is the only way to reach most of the people searching for you. Keap makes the same point about tone: keep it conversational while still sounding like the person who knows the trade.

Read your draft and ask one question of every sentence: would I actually say this to a customer? If not, swap it for what you would say. The florist does not write "floral longevity is contingent upon hydration." She writes "cut flowers last longer if you top up the water every couple of days." Same fact, and the second one gets read.

Keep it short and stop when you have answered the question

You do not owe the internet a thousand words. You owe the reader an answer. The moment the question is answered, stop.

Jeff Goins, writing for people who blog but do not consider themselves writers, gives the same advice: keep it short and stop once you start rambling, get creative with formats like bulleted lists and quick step-by-step guides, and turn conversations into posts instead of forcing a big essay. One question, one post, one idea. If a second question shows up while you write, that is not a longer post. That is your next post.

A florist answering "how long will these last in a hot car?" needs maybe two hundred words: yes it shortens their life, here is roughly how much, here is what to do about it. Publishing that is worth more than a two-thousand-word flower-care manual you never finish. Short and done beats long and stuck every time.

Read it out loud before you publish

This is the non-writer's entire editing pass, and it works. Read the finished post out loud, start to end. Every place you stumble, run out of breath, or think "no one talks like that" is a place to fix. Your ear catches what your eye misses.

Hayward names this step too: read your post aloud before you publish. You do not need to know grammar rules to hear that a sentence is clunky. If it sounds wrong when you say it, it reads wrong. Change it, read it again, and when it sounds like you explaining something to a friend, you are done.

Let AI draft or tidy, then make it sound like you

AI is genuinely useful here, as long as you stay in charge of it. The honest workflow is this: dictate your answer to a real question, let a tool clean up the grammar and tighten the rambling, then read it back and change anything that does not sound like you. The tool does the tidying. You supply the answer and the voice.

In the work we do at Fonzy building content for owner-run businesses, the same pattern shows up again and again: the owner who dictates a rough answer between jobs writes something clearer than the owner who sits down and tries to "write properly." The talking version has their real voice in it. The writing version has stiff phrases they would never say to a customer. The fix is always the same, which is to start from how you talk and tidy from there, not to start from a blank page and try to sound like a writer.

Where AI goes wrong is when you skip your part. If you ask a tool to invent a post about flower care from nothing, you get a page that sounds like every other flower-care page, which is exactly what buyers scroll past. Feed it your real answer to a real question, and it can turn your rough spoken draft into a clean post that still sounds like you. That is the whole role AI should play. It is a tidier, not a ghostwriter.

Frequently asked questions

Do I need good grammar to write a business blog post?

No. You need to be clear, not correct. Read the post aloud, fix what sounds wrong to your own ear, and let a spellchecker or an AI tool catch the rest. Snopes, reviewing PIAAC adult-skills data, reported that most U.S. adults read below a sixth-grade level, so plain writing reaches more people than polished writing does.

What if I genuinely can't write a single word?

Then talk. Mark Hayward's advice on ProBlogger for people who refuse to write is to use speech-recognition software to dictate your posts out loud, and he notes those posts still rank. Open your outline, answer each point into your phone like a customer is in front of you, and clean up the transcript afterward.

How long should a business blog post be?

As long as it takes to answer the question, and no longer. Jeff Goins advises non-writers to keep posts short and stop once they start rambling. Two hundred clear words that answer one real question beat a long post you never finish, and they still earn an indexed page on your site.

What should my first blog post be about?

The question a customer asked you most recently. Scroll your texts and emails, pick the one you get asked most, and answer it. That single question is a topic, a title, and a post all at once, and it matches how people actually search.

You explain your trade every day without thinking twice. A blog post is just that explanation, typed once, so the next customer finds it before they even pick up the phone. Start from one real question, talk out the answer, and fix it once. That is the whole job, and you already know how to do the hard part. When you want the tidying handled for you, that is where a tool like Fonzy earns its place.

Sources

Roald

Founder Fonzy. Obsessed with scaling organic traffic. Writing about the intersection of SEO, AI, and product growth.