Week 3 · Day 12 · Wednesday 16 September

Content that earns attention

Sivaguru Ayyadurai · Founder, LotsTech14 min readTask: 60 minSubmit your work

You have a page and you have a standard. Now: how does anyone arrive at that page in the first place? Content is the slowest channel on the map and the only one that keeps working after you stop paying attention to it. It is also the one I personally got most expensively wrong.

1. Content is one of the few assets that keeps working after you stop.

A post disappears in a day. An email is read once. An ad stops the moment the card stops.

An article that answers a question people keep asking can bring the right person to you for years, and it costs nothing further after it is written. That is what "compounds" means, and it is the entire argument for a channel that is otherwise slow and thankless.

It is not the only one — documentation, templates, a free tool, an email sequence and a good reputation all keep working too. But content is the one you control entirely and can start today.

The trade is honest: months before it does anything. On a new site, expect nothing for a quarter. Anyone promising faster is selling something.

Which is also why content is where the most money gets wasted. A slow channel with no early feedback is the easiest place to do a year of confident, useless work.

2. The rule the best publishers hold, and it is checkable.

You have heard me say content has to contain something a competitor could not have written. That is true and it is too vague to act on. Here is the operational version, and it comes from people measuring this at scale in 2026:

Every article must contain at least one fact, example or perspective that is not available on any top-10 competing page.

That is a test you can actually run. Open the ten pages currently ranking for your question. If everything in your draft already exists across those ten, you have no answer to the only question that matters: why would anyone read yours instead of one of those?

It does not have to be globally new. A comparison nobody has made, a process you actually ran, a number from your own data — all of these count, even on a familiar topic. The bar is absent from the pages you checked, not unprecedented.

Where that one thing comes from. It is not style, and it is not a better introduction. A piece qualifies if it contains at least one of:

  • Original product experience — what happened when you actually did it
  • Real customer language, quoted
  • A specific example with names and numbers
  • A useful comparison nobody has made
  • A clear process someone could follow
  • A mistake and what it taught
  • Evidence from your own research
  • A demonstration rather than a description

Look at that list and notice something: every item requires you to have done something. None of them can be produced by better prompting, which is exactly why Day 7 came before today.

3. Volume without a standard is not slower progress. It is damage.

I ran lots.blog on full automation. AI wrote the articles, they published themselves, I never reread them. Over a hundred posts. Zero rankings. I audited the lot, found it was slop end to end, and deleted the entire blog.

I told you that on Day 4. Here is the part I could not tell you then, because I did not have the numbers.

What I can and cannot tell you here. There are industry analyses circulating that put precise numbers on this — penalty rates for high-volume AI publishing, an optimal articles-per-month band. I have not traced any of them to a primary source I would defend, so I am not going to quote them at you as fact.

What I can tell you is first-hand and it cost me a blog.

The pattern every serious publisher reports is the same shape: volume without a documented standard produces risk, not growth. Not because AI wrote it — because nobody read it.

My failure was not using AI. It was volume with no standard in front of it. Same tools, same models, different outcome entirely:

Raw AI output, publishedAI draft, edited with real input
ResultDoes not rank. Accumulates risk.Ranks, and the evidence is now substantial.
What's missingExperience, proprietary perspective, a reviewer—

That is the whole thesis of this program: AI drafts plus human judgement works. AI drafts alone does not.

4. Topics come from real questions, not keyword lists.

The standard approach is to pull a keyword list, sort by volume, and write against the top rows. It produces articles that are technically about something people search for, and that nobody needed.

The better starting point is the one you already have. On Day 7 you collected verbatim quotes of people describing this problem in their own words. Each of those is a topic, and it arrives with the language, the context and the frustration attached.

Keyword data still matters — it tells you how many people share the question and what words they use for it. That is Thursday's lesson. It is a check on the topic, not the source of it.

The order is: real question first, demand check second. Reversed, you get volume without relevance.

5. A content strategy is not a topic dump.

A list of twenty article ideas is not a strategy. A strategy has shape, and pieces that hold each other up.

TypeHow manyJob
Cornerstone3–5The definitive piece on a territory you intend to own. Long-lived, updated, linked to by everything else.
Supporting8–12Answer one specific question each, and link back to a cornerstone.
Series2–3A repeatable format that gives people a reason to come back.

The linking is not decoration. A supporting post that answers a narrow question and points to the cornerstone tells both readers and search engines that the cornerstone is the serious piece on that subject.

Underneath this sit your pillars — three to five territories you intend to be known for. Pillars are a private strategic decision. Categories on the site are public navigation. They are related and they are not the same thing, and confusing them produces a blog with thirty tags and no argument.

6. Never draft a serious post without a brief.

This is the single most useful habit in the lesson, and it is the one most people skip because writing feels like progress and briefing does not.

A brief is the decisions made before the words. It takes fifteen minutes and it prevents the most common outcome in content: a competent article that was never aimed at anyone.

What belongs in one:

  • Target reader, and their current state — what they already believe when they arrive
  • The primary goal — rank, convert, engage, distribute, educate, or build trust. One of those.
  • The real question behind it, in their words
  • Search intent, when search is the route in
  • Reader outcome — what they can do afterwards that they could not before
  • The central argument — one sentence
  • The thing no competing page has — section 2, named explicitly
  • Evidence and examples to include, with sources
  • Claims needing verification
  • Internal links — what this points to, what points here
  • Outline and one CTA
  • What it will deliberately not cover

That last field does more work than it looks. Without it every article drifts into being a complete guide to the whole subject, which is how you end up with three thousand words that rank for nothing.

7. Structure that survives skimming.

Nobody reads an article the way you wrote it. They scan, decide, and then read the part that matters to them.

The promise lands in the first three sentences. Not the third paragraph. A reader who does not know what they are getting has already left.

Headings carry the argument. Someone reading only the headings should get the point. If yours are "Introduction", "Benefits", "Conclusion", the article has no argument.

Discrete blocks answer discrete questions. Tables, lists, a real FAQ. This is now doubly worth doing — it is how humans skim, and it is how an AI assistant lifts an answer and cites you. More on that tomorrow.

One call to action. Same rule as the page.

A specific, human title. Then the swap test: put a competitor's name in it. If it still reads true, it is too generic.

8. LotsBlog — and where the standard sits.

LotsBlog is the agent that owns the blog: strategy, keywords, ideas, briefs, drafts, publishing and scheduling.

Two things about how it is built are worth more than the feature list.

It refuses to draft without a brief. Its instructions say so plainly — do not draft a serious post without a brief — and the brief lives in a database as durable strategy rather than in a chat that scrolls away. So the decisions survive, and the next article starts from them rather than from nothing.

Its onboarding does not ask what you want to blog about. It asks what you are trying to achieve — visibility for a product, an audience, client work, documenting expertise. Purpose first, then reader, then voice, then territories, then cadence. That is Day 7 and Day 8 built into the tool.

And the boundary that matters: LotsBlog creates posts as drafts by default. It publishes only when explicitly told to. Nothing reaches the public because an agent decided it was finished.

The standard still sits in front of it, and it is yours. The agent will happily produce a competent article with nothing in it that a competitor could not have written. Only you can supply the thing from section 2 — and only Editor and your checklist decide whether it ships.

9. What this lesson did not cover, and how to go deeper.

Covered: why content compounds, the top-10 test, volume versus standard, topics from real questions, strategy shape, the brief, structure, and where the agent fits.

Not covered:

  • The actual writing craft — sentence rhythm, transitions, how to open. A lifetime's subject; you improve by writing and being edited.
  • Updating old posts — often higher return than writing new ones, and almost nobody does it.
  • Content formats beyond articles — templates, tools, calculators, original research reports. Frequently outperform posts.
  • Editorial calendars at team scale — commissioning, deadlines, freelancers.
  • Distribution — publishing is not distribution. That is the next three lessons.
  • Content pruning — deleting weak pages to strengthen the rest. I did the extreme version of this.

Where to go. Take one article you genuinely found useful in the last month and work out what its one unavailable thing was. That habit — reading as a maker rather than a reader — teaches faster than any guide.

Today’s task — one article brief for LotsSocial (60 min)

Objective: a brief good enough that someone else could write the article from it.
Evidence: your Day 7 quotes, your Day 8 positioning, your Day 10 page.
Deliverable: one brief with outline. Not a draft.
Review: Editor, plus your own Day 11 checklist.
Signal: what would tell you this article reached the right reader, not just readers.

Do the required deliverable first. Anything beyond it is optional — a finished minimum beats an unfinished maximum.

Reference: the real LotsSocial notes are at /lotssocial — look things up rather than reading it through. Note 8 is the one to read once, before you write anything: it lists what we may not claim.

LotsBlog is at lotsagent.com/agents/lots-blog. Editor, when you need it, is at lotsagent.com/agents/editor.

1. Start from a real question (10 min)

Go back to the verbatim quotes you collected on Day 7. Pick one where someone describes a problem LotsSocial genuinely addresses.

Write the question in their words, not yours. That sentence is the seed of everything below.

2. Run the top-10 test before you plan anything (15 min)

Search that question. Open the pages that come back — skip the ads. For each: note the date, and the one angle it takes.

Do not assume a top-ranking page is good. Several will be thin. That is often where the gap is.

Then answer the question that decides whether this article should exist: what will mine contain that is not on any of those pages?

If you cannot answer it, do not fix the article — pick a different question. Choosing again is the correct move and it is the point of doing this step first.

3. Write the brief (25 min)

All twelve fields from section 6. Short answers, but every field filled.

Two that people fudge: one primary goal, not four. And what it will deliberately not cover — be specific, because this is what keeps the piece from becoming a guide to everything.

4. Outline, title, swap test (10 min)

Headings that carry the argument — someone reading only those should get the point. Then a specific, human title, and put a competitor's name in it. Still true? Rewrite it.

Then run it through the gate

Editor, and your own checklist from yesterday. Submit the brief plus Editor's verdict.

Then post one line

In #daily-log: the one thing your article will contain that is not on any of the top ten pages.

One sentence. If it took you two attempts and a different question to find one, say that — it is the most useful thing you could report.

Tomorrow — Day 13: Search. You have something worth finding. Tomorrow is how anyone finds it — being found, being the answer, and being cited when someone asks an assistant instead of a search box.