#NFF · How I cut my content week from 16 hours to 4

I sat down on a Sunday evening about six months ago and did the maths I’d been avoiding for a year.

16 hours a week on content. Sometimes 18. The carousels. The singles. The two newsletters. The captions. The repurposing. The thumbnails. The “let me just tweak that hook one more time” loop.

That’s two full working days a week. Eight working days a month. Ninety-six working days a year producing content for a business that wasn’t growing in proportion to the effort going in.

The worst part wasn’t the hours. The worst part was that I’d become bored of my own content. Five carousels a week, same shape, same hook structure, same Saturday morning panic about the Wednesday slot. Some weeks I couldn’t remember whether I’d actually posted Wednesday’s piece or just thought about posting it.

That’s phantom load at its purest. Effort going in. No outcome that matched it. The work was real, the cadence was real, the bank account didn’t move.

The fix wasn’t more discipline. The fix was admitting I’d been doing it the slow way for 18 months.

What changed in 90 days

Today my content week looks like this:

• Saturday 09:00-10:30 Dubai. Open Claude. Fire one Skill (Carousels & Singles Content Creator). Generate the week’s content — 5 carousels, 3 singles, hooks + captions + DM code-words built in. Score each piece against the 5-dimension rubric. Keep what scores 8+. Bin the rest.
• Saturday 10:30-11:30. Open Canva. Run the brand-template that the Skill points to. Drop the generated content in. Export to PNG.
• Sunday 17:00-18:00. Open Buffer. Schedule the week’s posts. Multi-channel: IG, Facebook, TikTok, LinkedIn, Threads, X. Per-platform caption swaps for X + Threads only (over the char limit on the base). LinkedIn First Comments tailored per carousel with the DM code-word.
• The rest of the week. Hands off. Posts ship on schedule. ManyChat handles the DM keyword triggers. The newsletter writes itself off the same source material. The Daily Brief fires every morning. I write this newsletter Friday morning Dubai and ship it.

Total weekly content time: ~3.5-4 hours. Down from 16. The output volume held. The output quality lifted because the Skill enforces an 8/10 self-score on every piece — which I never enforced on myself when I was running it manually.

The bit that really matters: I haven’t dropped a posting day in 6 months. The cadence holds because the friction is gone.

Why most creators stay stuck at 16 hours

The trap is the same for almost everyone I work with. Three patterns repeat:

Pattern 1 — you treat content as creation, not curation.

Most creators sit down at a blank document and try to invent something to say. That’s the slowest possible mode. Claude can draft any piece of content in 90 seconds if you’ve fed it the right context. Your time should go into the 30% that only you can do — the specific story, the in-the-trenches detail, the voice that makes it sound like you instead of a bot. Curating and codifying beats creating, every single time.

Pattern 2 — you don’t have a Skill, you have a habit.

Every time you sit down to write a carousel, you start from zero. You re-explain your business to ChatGPT. You re-paste your audience. You re-describe your tone. By the time the actual work starts, you’ve already burnt 20 minutes on context-establishment. A Skill bakes the context in once. You say a code word — “Carousels are a go” — and Claude already knows the audience, the offers, the voice, the pillars, the brand colours, the formats. You’re starting at minute 10, not minute 0.

Pattern 3 — you optimise the wrong block of the week.

Most creators try to spread content production across the week — a little Monday, a little Wednesday, a little Friday morning panic. That maximises the cognitive cost. Every context switch back into “creative mode” burns 15-20 minutes of warm-up. Batching the entire week into one 90-minute Saturday block kills the switching cost stone dead. You sit down once. You leave the laptop once. The week is done.

This is compound mode for content production. Build the Skill, batch the work, leave the rest of the week alone.

What’s actually in the Saturday block

This is the part most “content batching” articles skip — what the 90 minutes literally looks like:

• Minute 0-15: input dump. I paste this week’s signal into Claude. What I learned. What a client surfaced. What I shifted on. The 3 questions I got asked. The contrarian take that emerged from a real situation. That’s the source material the Skill mines.
• Minute 15-30: generation. I fire the Skill with the code word. Claude produces 5 carousel concepts + 3 single-post concepts, each scored against the 5-dimension rubric (Promise × Payoff, Teach AND Sell, Old/New positioning, named or numbered, voice match).
• Minute 30-60: curation + codifying. I keep the pieces scoring 8+. Bin the rest. For the keepers, I add the one specific detail only I know — the story, the in-the-trenches moment, the British operator phrasing that makes it sound like me, not Claude.
• Minute 60-90: visual handoff. The Skill outputs a clean spec — what goes on slide 1, slide 2, slide 3, slide 4, slide 5. I open the locked Canva brand template, drop the spec in, export.

That’s it. Saturday’s done. The week’s content is built.

The one rule that stops the system collapsing

Every batched-content system eventually drifts back into chaos. The rule that prevents it: never start the Saturday block without last week’s signal banked.

If I haven’t captured client conversations, decisions made, problems solved, observations from the week — the Skill has nothing to mine. The output gets generic. The Saturday block stretches to 3 hours because I’m trying to invent material instead of curating from real signal.

So I capture every week, even when the week feels boring. Three notes a day. Voice memos in the car. Two lines in Notion after a call. By Saturday morning there are 15-20 raw fragments to feed the Skill. The system holds because the input keeps showing up.

The Skill is the engine. The signal is the fuel. Run the engine on empty and you get noise.

The metrics that proved it’s working

Three months in, here’s what I track:

• Time per piece shipped. Was 90-120 min. Now 8-12 min (mostly the codifying pass on the AI draft).
• Posts shipped per week. Was 8-10 inconsistently. Now 10-12 every week without exception.
• Engagement-to-conversion rate. Was decent likes, low DM volume. Now lower like count, 2-3× the DM volume that opens with a code word.

The last one is the metric that matters. Followers are vanity. DMs with a code word are intent. The Skill’s CTAs route every piece toward a specific code-word reply that lands in a ManyChat sequence — and the qualified prospects book a call from there without me being in the conversation.

That’s build the backend applied to the content engine. The Skill produces. Buffer schedules. ManyChat qualifies. I show up at the qualified-call stage.

What this means for your week

If you’re running 16+ hours a week on content, you’re probably not lacking discipline. You’re lacking a Skill.

Three moves to install before next Saturday:

1. Pick one Skill to build first. Carousels are the highest-leverage starting point because they ship across 6 platforms with minor adaptation. Singles second. Newsletter last.
2. Build the context block once. Brand voice samples. Audience description. 5 banned phrases. 3 voice markers. Saved in a Claude Project so every Skill session starts informed.
3. Lock the Saturday block in your calendar. 90 minutes, same time every week, treated like a client meeting. If you can move it, you’ll move it. If it’s blocked, it holds.

You don’t need a bigger team. You don’t need a smarter AI. You need a Skill, a block, and the rule that keeps the input flowing.

Build the backend of your content engine. Then take Saturday afternoon back.

— Quinton

📬 No-Fluff Friday — one sharp move every Friday morning Dubai.

Read the archive: newsletter.founders.systems

Follow Quinton: LinkedIn · Instagram · X