A SaaS founder with a few hours a week should write about the questions customers and prospects already ask, publish in a fixed weekly slot, share each piece where those buyers spend time, and judge the work by trial sign-ups and sales conversations instead of page views. Start with the questions closest to a purchase: price, comparisons, problems and who the product is a poor fit for. This post covers how to find those questions, a four-hour weekly routine, a distribution checklist and the few numbers worth watching.

Start with the questions people already ask

Your best topic list is already in your inbox and call notes. JDR Group's summary of the They Ask, You Answer method advises listing "the questions prospects ask before they buy, especially the awkward ones" and turning the important ones into clear pages. Marcus Sheridan's own write-up for IMPACT sorts buyer questions into five topics: cost and price, problems, versus and comparisons, reviews, and best-in-class lists.

For a SaaS product, those five translate into plain questions:

  • Price: what each plan includes, what costs extra and how billing works.
  • Problems: why a setup step fails, where the limits are and who the product does not suit.
  • Comparisons: how you differ from the spreadsheet, the incumbent or the other tool the buyer is weighing.
  • Experiences: how customers set it up, using real accounts and only with their permission.
  • Best for: "best tool for this job" lists that are honest about where your product fits and where it does not.

Collect the questions from sales calls, demo requests, support tickets, replies to onboarding emails and cancellation notes. Put each in a spreadsheet with a column for where it came from and a tally of how often it appears.

Score before you write

Give each question a score from 1 to 3 on three things: how often it comes up, how close the asker is to buying, and whether you can answer from your own experience. Write the highest totals first. Ahrefs' guide to SaaS content makes the same fit argument: its author says the team focuses "only on topics our product can solve" and advises ranking topics by business potential.

Write from what only you know

Google's guidance on helpful content asks whether a page shows first-hand expertise and depth of knowledge, and calls the reason a page exists "perhaps the most important question": it should be made primarily to help people, not to attract search visits. Founders hold material a generalist writer lacks, such as the support thread that exposed a confusing setting, the integration you rebuilt, or the pricing change you decided against and why. If you quote a number from your own product, check that it is real and current. If you do not have the number, describe what you saw.

The same page lists using extensive automation to produce content on many topics as a warning sign, and says Google has no preferred word count. Write until the question is answered, and start each piece from your own notes even if a tool helps tidy the draft.

A minimal publishing system

Choose a slot and a pace you can keep. Ahrefs' guide ends on the point that "the most difficult part is to do it consistently." A post every second week that you actually publish is a better plan than a weekly schedule you drop. Here is a four-hour week. The times are our suggestion, not a benchmark, so adjust them to your own speed.

  1. 20 minutes: pick the next question from the list and write its answer in two sentences. If you cannot, the topic is not ready.
  2. 90 minutes: draft in one sitting from your notes, with the answer in the first paragraph.
  3. 40 minutes: edit. Add one real screenshot or example, cut any claim you cannot support and add who the answer does not suit.
  4. 30 minutes: publish, then run the distribution checklist below.
  5. 60 minutes: reply to responses, send the post to the person who asked, and add new questions to the list.

Give every post the same shape so drafting gets faster:

  • An opening paragraph that answers the question in plain words.
  • One real example or screenshot.
  • Limits, and who the answer does not apply to.
  • One next step, such as a trial link or a related post.
  • The date you last checked it.

Distribution checklist

A published post that nobody sees has not done its job. Pick one or two channels from the list below instead of all of them. The post on customer acquisition channels for early-stage SaaS explains how to choose and test one.

  • Send it to the person who asked the question, with a short personal note.
  • Email it to your list or current customers if it answers something they ask. Email automation workflows for SaaS covers what to automate.
  • Share it on the social channel your buyers use, written for that channel. One video, four platforms shows how to adapt a single piece per platform.
  • Answer the question in a community where it is asked, only if the rules allow links, and say that you work on the product.
  • Tag each link with utm_source, utm_medium and utm_campaign. Google's analytics help says to use all three and notes that values are case sensitive, so write them in lowercase and keep it.

Measure what matters

Google Search Console's performance report defines clicks as the number of times a user clicked your site from Google Search results, impressions as how many times your site appeared in Search results, and click-through rate as clicks divided by impressions. You can group the data by query and by page. A page with impressions and few clicks probably needs a clearer title. A page with clicks and no sign-ups probably needs a clearer next step. Those two readings are our interpretation of the report, so test them against your own pages.

Once a month, look at these:

  • Trial sign-ups or demo requests that started on a post, using your UTM tags or the landing page in your analytics.
  • Sales conversations where the prospect mentions a post. Add a "how did you hear about us" field to your sign-up form to catch them.
  • Queries in Search Console that bring impressions to each page, to see which questions the page really answers.
  • Replies and forwards from real buyers.

Treat page views and follower counts as context. Search traffic takes time to build, so judge the first quarter by whether you shipped on schedule and by the conversations it started.

What to skip while time is short

  • Broad educational articles before you have answered your price, comparison and problem questions.
  • Publishing on every channel.
  • Articles on topics where you have no first-hand experience.
  • Chasing a word count.
  • Redesigning the system every month. Change it after a quarter of data.

Where to start this week

  1. Export the last 20 questions from sales calls and support into one spreadsheet.
  2. Score them and pick the top one.
  3. Block next week's 20-minute, 90-minute and 40-minute slots in your calendar now.
  4. Set up UTM tags and a Search Console property so the first post is measured from day one.

The SaaS Marketing Starter Package does not write articles. It begins with a kickoff call and a one-page content plan, then delivers five AI UGC videos, one motion graphics video, an automated email sequence of up to five emails and a 14-day posting schedule for the videos. If you want those pieces handled around your own writing, read the package page for exactly what is and is not included, or the Complete Marketing Automation overview.