Starting a business blog takes about an hour of setup and one page of decisions. The setup is the easy part. The decisions are what keep the blog alive after the third post.
Most guides that rank for this question are written for people who want to blog for a living. They spend most of their length on niches, hosting plans and making money from ads. A company blog has a narrower job. Founders and small teams who ask about it on Reddit describe the same failure again and again: they publish two or three posts, nothing obvious happens, and the blog goes quiet.
I think the fix is deciding five things before the first draft: what the blog is for, who it is written for, who writes and who checks, where it lives, and which five questions the first posts answer. Then publish on a schedule you can keep for 90 days before you judge whether it works.
Decide the one job the blog does
A business blog can do several things, but in the first 90 days it should do one. Pick the one that matches the problem you have now:
- Get found by people who don't know you yet. Posts answer questions customers type into Google before they have heard of you: what something costs, how long it takes, which option to pick. For most small businesses this is the job to start with.
- Answer the questions your sales calls keep repeating. Posts become links you send after a call or paste into a quote. They work from the day you publish, because you deliver them yourself.
- Cut repeat support questions. Posts explain setup, troubleshooting and policies once, so the inbox can reply with a link.
- Show your work. Project stories and case studies for a business that sells on trust, such as a builder, a design studio or an agency.
Write the job down in one sentence. It decides the topics, and it tells you what to look at on day 90. "Get more traffic" is not a job. "Answer the five pricing questions prospects ask before they book a call" is one.
The one-page plan
Copy the Decision column into a document and write your own answer next to each row. The middle column is a worked example for a made-up three-person bookkeeping firm, so you can see how specific each answer needs to be.
| Decision | Example: a small bookkeeping firm | Why it matters |
|---|---|---|
| The blog's one job | Answer the questions owners ask before they hire a bookkeeper, so first calls start further along | Every topic is checked against this sentence |
| Who it's for | Owners of businesses with 1 to 10 staff, doing their own books, a few months before tax season | Sets the vocabulary. Write for the owner, not for other accountants |
| First five posts | What a monthly bookkeeping service costs; bookkeeper vs accountant; what to send a new bookkeeper; catching up on a year of missed books; cash vs accrual for a small shop | Five posts is enough to start, and enough to send to prospects |
| Who writes | The founder drafts. A colleague turns call notes into outlines | Name a person. "We'll all contribute" means nobody does |
| Who checks before it goes live | The senior bookkeeper reads for accuracy, within two working days | A wrong number in a public post costs more than a late post |
| Where it lives | blog.firmname.com, linked from the main site's menu | Changing the address later means redirecting every post |
| Schedule | One post every second Tuesday, two finished drafts in reserve | A steady schedule beats a burst followed by months of silence |
| Each post's next step | A link to the "book a call" page, plus one related post | A reader who arrives from search has never seen your homepage |
| Day-90 check | Which posts show impressions in Search Console, and which ones the team has sent to prospects | Decided now, so you are not tempted to judge the blog in week three |
Where the first five posts come from
Don't start with a keyword tool. Start with your inbox. For the last month of sales emails, quotes and support tickets, write down every question a customer asked, in their words. The list is usually longer than you expect. Then pick five that meet three tests:
- Someone asked it more than once. A repeat question is evidence that other people have it too, including people who haven't found you yet.
- You can answer it better than a generic article. You know your prices, your area, your process and the mistakes you see. A general guide can't say "most of our clients pay between X and Y, and here is what moves it."
- It ends somewhere useful for you. A post about what a service costs leads naturally to a quote. A post on a topic you don't sell anything around leads nowhere.
Two kinds of question tend to bring in customers, not just readers. One is the cost question ("how much does X cost"). The other is the comparison ("A vs B", "us or doing it yourself"). In one r/smallbusiness thread, a SaaS founder wrote that the only posts that ever brought in real customers were direct comparisons with competitors. In another, about why business blogs get no traffic, the first cause listed was topics that are too broad. "5 tips for a better business" competes with every big publisher and gives a reader no reason to pick you.
Who writes, and who checks
On a small team, the person who knows the answer is usually not the person with time to write. Two setups work:
- The founder writes, someone else reads. Works when the founder enjoys writing and the posts depend on their judgement. The reader checks facts and prices, not style.
- Someone else writes from a 20-minute interview. A colleague or freelancer asks the founder or the expert the customer's question, records the answer, and turns it into a draft the expert approves. This is usually faster than waiting for the expert to find a free afternoon.
Whichever you pick, give the reviewer a deadline. A draft that waits a week for approval breaks the schedule faster than anything else. The one rule that holds it together: the writer shouldn't be the only person who reads a post before it's public.
What it actually costs
"How much does it cost to start a business blog?" gets answers from a few dollars a month to hundreds of dollars in tools before the first post. For a company blog on a hosted platform, there are four costs:
| Cost | What to expect |
|---|---|
| Blogging platform | Can be $0 on a free hosted plan with a custom domain, or a small monthly fee if you need team reviews and editable themes |
| Domain | Usually $0 extra. Put the blog on a subdomain of the domain you already own, such as blog.yourcompany.com |
| Design | Can be $0 to start. Use a built-in theme, set your logo, colours and menu, and leave custom design until you have posts to judge it against |
| Time | The real cost. A few hours per post for writing, plus review and images |
For most small businesses that adds up to little or no money, and about a day a month of someone's time. If you can't find that day, choose a slower schedule rather than skipping the blog.
Setting it up (the short version)
Wherever you host it:
- Create the blog and pick a theme you can live with for now. You can change themes later without rewriting posts.
- Link the blog and the website both ways. Add a "Blog" link to your website's menu, and put your website's Home, Pricing and Contact links in the blog's header.
- Connect a subdomain under your existing domain. Your platform will show the DNS record to add where the domain is managed.
If your website runs on Squarespace, Wix, Shopify or a similar builder, the decision is whether to use the builder's own blog or a separate one. That choice is mostly about who will write and whether you want writers inside the site editor.
The first 90 days
At one post every two weeks, the first quarter adds up to six posts plus two in reserve.
Week 1. Fill in the plan, set up the blog, and write two posts before you announce anything. Publish the first one. Keep the second as a finished draft in reserve.
Weeks 2 to 12. Publish on the schedule you chose. For most founders writing alone, one post every two weeks is a pace they can hold. Write each new draft while the reserve covers the weeks when a launch or a busy client eats your time. Schedule finished posts ahead so they go out on time even when you're busy.
Use every post the week it goes live. Send it to the customer who asked the question. Add it to your email signature or your quote template. Share it once on the channel where your customers already are. Search traffic takes time to build. Links you send yourself work right away, and they tell you quickly whether a post actually answers the question.
What to look at on day 90
Don't judge a new business blog on traffic in its first month. Google has to find and index the posts first, and new pages on a new blog usually take weeks to show up for many searches. Day 90 is a reasonable first checkpoint. Look at two things.
Search Console impressions, by page. Add the blog to Google Search Console in week 1. On day 90, open the Performance report and filter by page. A post with impressions but few clicks is being shown for something. Look at the queries it appears for, and rewrite the title and opening so they answer those queries. A post with no impressions at all after two months usually targets a question nobody searches in those words, so rewrite it in the customer's phrasing.
Which posts your team actually sent people. Ask whoever handles sales and support which links they used. A post sent to ten prospects is doing its job even if search hasn't found it yet. A post nobody has sent is either answering the wrong question or hard to find.
Then make one of three decisions. Keep the schedule if posts are being used or starting to show impressions. Change the topics if posts are published but nobody sends them and nothing shows up in search. Slow the schedule if you missed slots, because a pace you can keep beats one you can't.
What the first quarter should give you is six or more real answers to real customer questions, on your own domain, which your team can link to.
I run JustBlogged, a blog platform, and this is the plan I wish every new business blog started with before the theme picker.
Top comments (0)