<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Louis Carter</title>
    <description>The latest articles on DEV Community by Louis Carter (@louiscarter196).</description>
    <link>https://dev.to/louiscarter196</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4196928%2Fad3cd563-8e23-4d34-af51-af6ffe0eaff5.png</url>
      <title>DEV Community: Louis Carter</title>
      <link>https://dev.to/louiscarter196</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/louiscarter196"/>
    <language>en</language>
    <item>
      <title>I Run a One-Person Content Business — Here's the Publishing System That Keeps It Sane</title>
      <dc:creator>Louis Carter</dc:creator>
      <pubDate>Tue, 20 Oct 2026 21:32:02 +0000</pubDate>
      <link>https://dev.to/louiscarter196/i-run-a-one-person-content-business-heres-the-publishing-system-that-keeps-it-sane-22g6</link>
      <guid>https://dev.to/louiscarter196/i-run-a-one-person-content-business-heres-the-publishing-system-that-keeps-it-sane-22g6</guid>
      <description>&lt;p&gt;I don't have a team. It's me, a laptop, and a publishing schedule that would collapse inside a week if it lived in my head.&lt;/p&gt;

&lt;p&gt;I run a small niche content site solo — research, writing, editing, publishing, promotion, all of it. After a few years of doing this the loud way (bursts of motivation, then silence), I rebuilt the whole operation around one idea: &lt;strong&gt;the system should be boring, so the work doesn't have to be.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Here's what actually stuck.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. One calendar, not five apps
&lt;/h2&gt;

&lt;p&gt;Everything I publish — articles, updates, guest posts, social posts — goes on a single calendar. Not a project board, not a notes app, a calendar with dates on it.&lt;/p&gt;

&lt;p&gt;The rule that made it work: &lt;strong&gt;drafting and publishing are separate events, on separate days.&lt;/strong&gt; I write things when I have the energy, then schedule them to go out spaced like a person actually lives — one or two a day, never a burst of nine. A queue of finished work sitting between me and the publish button is the whole trick. Motivation fills the queue; the calendar empties it.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Two queues, brutally labelled
&lt;/h2&gt;

&lt;p&gt;Every piece of content is in exactly one of two states:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ready&lt;/strong&gt; — finished, checked, could go live today.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In draft&lt;/strong&gt; — everything else, no matter how "almost done" it feels.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;"Almost done" is where solo operations go to die. If it's not ready, it doesn't get a date. This one distinction killed the Sunday-night scramble completely.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Batch by type of energy, not by topic
&lt;/h2&gt;

&lt;p&gt;Research days, writing days, editing days. Switching between them is where my hours used to leak. A research session produces raw material for four or five pieces, not one. A writing session is only allowed to open drafts, never a blank page and a search engine at the same time.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. One spreadsheet for what happened
&lt;/h2&gt;

&lt;p&gt;I track every piece I publish in one plain spreadsheet: where it went, when, and what it links to. Once a week, ten minutes, I update it and look at what's actually moving. Not daily — daily metrics-watching is just anxiety with charts.&lt;/p&gt;

&lt;p&gt;The spreadsheet has saved me more than once. Duplicate content, forgotten follow-ups, a pitch I sent twice to the same editor (once — never again).&lt;/p&gt;

&lt;h2&gt;
  
  
  5. A weekly review that takes 20 minutes
&lt;/h2&gt;

&lt;p&gt;Same time every week:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What's in the ready queue? (Less than a week of runway = writing becomes the priority.)&lt;/li&gt;
&lt;li&gt;What's waiting on someone else? (One polite follow-up, then I move on.)&lt;/li&gt;
&lt;li&gt;What did last week's numbers quietly tell me?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That's it. No quarterly planning theatre. The review is small enough that I never skip it, which matters more than it being thorough.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell another solo operator
&lt;/h2&gt;

&lt;p&gt;Your system doesn't need to be impressive. It needs to survive your worst week, not showcase your best one. Mine is a calendar, two queues, and a spreadsheet — and it has carried the whole business for years now.&lt;/p&gt;

&lt;p&gt;If you run something solo, I'd genuinely like to hear what your version looks like. Especially if it's weirder than mine.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>writing</category>
      <category>career</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
