I spent an entire day in a shared co-working space in Medellín sitting behind a computer with 8 tabs open. I had a partially completed brief on B2B SaaS onboarding workflows. And I had the feeling I was hitting a plateau. Not burnout. Not yet. But I was generating nearly the same amount of work I'd produced nine months prior, billing the same, putting in the same hours. Same clients, same deadlines, same output ceiling.
Not a math problem. System issue.
About four months later I was producing triple the content per week. Not because I worked harder. Not because I found a magical app. Because I built a system that reduced friction instead of requiring more coffee. These are the productivity hacks that helped create this shift, and why much of the online information about "productivity hacks" works counter to that purpose.
Short version: batch by format, not by client. Separate creation from editing. Use AI for first drafts and a humanizer for the post-generation layer. Review your system weekly. That's it.
Most Productivity Hacks Are Just Disguised Busyness
Hot take: much of the productive hacks content creators spend a great deal of time sharing online is simply creative ways to look busy without increasing output. Ninety-minute morning routines to organize your day. Seventeen linked databases in Notion. Time-blocking templates.
I lost a lot of time building optimized versions of inefficient workflows. The goal is not to develop an organized flow of work. The goal is output per hour. Once I shifted my focus towards that singular metric, everything became much easier.
What Slow Productivity Really Means for Freelancers
Slow productivity isn't a polite word for lazy. It refers to developing frameworks for working at a pace that allows you to sustain yourself month over month, year over year, versus burning off your top-level thinking during a single quarter.
Cal Newport's definition applies to academics and individuals focused on deep thinking, but the idea translates. Produce fewer things in parallel, at higher quality. For a freelancer billing per deliverable, that sounds counterintuitive. The focus isn't on decreasing your rate of output. It's on removing chaos around each task so you can perform more efficiently on each one individually.
In practice: instead of switching contexts between five different client types in a single day, I started grouping similar content formats together and batching those formats separately from clients. Blog posts on Tuesdays and Wednesdays. LinkedIn content on Thursday mornings. Strategy documents on Mondays only.
Anyway. Each piece didn't require my brain to reload into a new context every 40 minutes. I moved faster on each individual piece because I was already in the right mode.
Something I'd add: slow productivity works even better when there's no additional friction added via tools in your stack. Running every AI draft through an AI humanizer before I start editing is part of this logic. I'm not introducing a new step. I'm replacing a slower manual step with a faster alternative that produces better output.
I wrote more about how this transition played out in the piece where I broke down tripling my output.
My Content Output Strategy: Three Non-Negotiable Rules
My content output strategy to scale my work wasn't complex. Three rules, followed without exceptions.
Rule 1: No blank-page drafting.
All pieces begin with either a template I've created or a brief I've written myself. Writing from scratch is the least efficient thing you can do as a writer. Creating from structure eliminates the need to think of both the frame and the answers at the same time.
Rule 2: Separate creation from editing.
When writing, I don't edit. I write a complete first draft, close the document, and come back to it. This is a well-documented productivity hack and I don't care that it sounds obvious. Many writers read their own sentences aloud as they write and rewrite them on the spot. That habit doubles production time.
Rule 3: Use AI for first drafts, then humanize before delivery.
This is the rule that caused the largest jump in efficiency. I use AI-generated drafts for common content types, then run them through an AI humanizer before any editing.
The humanizer removes the generic AI tone before I start reading critically. That means I'm editing for substance instead of rewriting sentences that look like they came from a template. That step alone saves me 30 to 45 minutes per piece on anything over 800 words.
Building a Freelance Productivity System That Scales
A scalable freelance productivity system doesn't become slower as volume increases.
Many systems fail because they're based on the premise that you'll continue to serve the same clients, work the same content types, receive the same revision cycles going forward. As soon as any of those variables change, the system fails and you're improvising again.
My system runs on three levels.
Level 1: Client infrastructure.
Each client has its own folder hierarchy, a style guide I've written myself, and a standard brief format. When new projects come in, I open my brief template first and populate it before touching any writing tool.
Level 2: Delivery infrastructure.
Each piece follows the exact same four-step process: draft, humanization pass, edit for substance, final read. I don't consider this flexible. For every draft, mine or AI-generated, I don't skip the humanization pass because it identifies awkward phrasing I'm too close to catch myself.
Level 3: Review cadence.
On Sundays, I review last week's output and flag any piece that required more time than expected. In about two months, three repeated bottlenecks were identified through this routine. Eliminating those three things accounted for nearly all of my current time savings.
Do with this what you will: a system you review is a system that improves. A system you set and forget is just a habit with extra steps.
The output-based billing model created the pressure to build this properly. I broke down how that shift changed my relationship to efficiency in this post on output-based billing.
The AI Layer Most Content Creators Are Using Wrong
Most content creators use AI for two purposes: to generate an initial draft they then rewrite from scratch, or to fill in parts they're too exhausted to write. Both are fine. Neither represents where the greatest productivity gains exist.
The greatest potential lies in the post-generation layer. How you treat your draft after you have it matters far more than what you originally generated.
Genuinely, the biggest quality jump in my workflow came from treating humanization as a completely separate, non-negotiable step rather than something I'd get to if I had time. The editing phase goes faster, the output reads more like me, and clients don't flag anything.
Top comments (0)