DEV Community: Dani Voss

Productivity Hacks That Tripled My Content Output in 4 Months (Without Burning Out)

Dani Voss — Tue, 21 Jul 2026 13:17:53 +0000

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.

AI Productivity Tools for B2B Content Teams in 2026: What I Use on Every Client Account

Dani Voss — Thu, 16 Jul 2026 14:34:37 +0000

9am in Medellín. Coffee went cold ten minutes ago. A client in Austin dropped a 400-word brief in Slack that needs to come back as a 1,500-word pillar page before noon eastern, three hours from now with the time difference.

I submitted at 11:40am their time.

Their response: "this is the best one yet."

The stack works. Not because I'm some content productivity wizard, but because I spent the better part of two years failing at this with worse tools and finally figured out what combination holds up. If you're running B2B content for multiple clients right now, especially SaaS, the ai productivity tools question in 2026 isn't "should I use them." It's which ones survive your quarterly cut and which ones you're paying $29/month for out of guilt.

Here's what I use, on every account, without exception.

The ai productivity tools I run on every account

The core of it is a humanization and detection loop. AI drafts for B2B SaaS are usually technically fine. Product information accurate, structure logical. They just read like nobody wrote them. Flat. Corporate in a way the client's actual marketing team doesn't sound. So the first thing I do after generating a draft is run it through a humanizer, then scan it with a detector before anything goes out.

For humanization I run a primary pass, and for pieces over 2,000 words there's usually a block or two that still doesn't land, so I'll spot-check those sections through a second tool. For detection I cross-check with two tools, not one. Different detectors flag different things, and if a client is running their own QA, one clean score isn't enough.

A grammar checker runs in the background on everything. Browser extension, passive. It catches the stuff that survives both AI generation and humanization: punctuation inconsistencies, phrasing that makes an editor stop. Table stakes.

For first drafts I use an LLM but I'm not naming one. The landscape shifts fast enough that any specific recommendation is stale in a few months. What I'll say: the draft is the lowest-value step in this workflow. The humanization loop and the detection check are where quality gets made. If you're spending 20 minutes on a prompt before you've even seen a draft, that's a skill issue. Get the draft and move.

I've gone deeper on the specific tools and why I landed on them on my Substack if you want the full breakdown.

AI tools for content strategists: what shifted in 2026

The tools haven't changed that dramatically. Clients have.

Two years ago I could run a single humanization pass and submit with confidence across most of my accounts. Now several of my clients have told me, at onboarding and sometimes mid-contract, that their editorial teams run submissions through two or three detection tools as standard QA. That's the market catching up, not clients being difficult.

The content strategists still treating humanization as an optional last step are going to hit a wall.

My workflow change was in the order. I don't draft, then polish, then humanize. I draft, rough humanization pass, edit for client voice, final detection scan. The sequence matters because editing a humanized draft produces better output than humanizing an edited one. Something in the final tightening pass reintroduces detectable patterns. Do the voice editing after the humanizer, not before.

I also cut two tools from my stack this year. They were introducing awkward phrasing on technical content, product marketing copy and SaaS explainers, because they're trained on general web text and don't know what to do with industry jargon. The output reads like a thesaurus made editorial decisions. That's not an editing problem. It's a tool problem.

The full breakdown of how I built this into my process is on my Substack.

B2B content workflow: how the stack runs in practice

Take a 1,500-word pillar page for a SaaS account, a standard deliverable for most of my clients.

Brief comes in. I read it once for technical requirements and any existing company language I need to mirror. Draft in an LLM with a prompt that locks in tone, audience, content goal. Working draft in 10-15 minutes.

Then humanization. I run the draft, read the result for anything that sounds off or misses the client voice, and do my voice edit at that point. Every account has different verbal patterns, formality levels, vocabulary preferences. Getting that right is what clients are paying for and it can't be automated. That pass takes 20-30 minutes and it's the most valuable work I do in the whole sequence.

Pre-submission: primary detector, cross-check with a second tool. Clean means it goes out. Something flags, I isolate the section, spot-check, fix, re-scan.

60-90 minutes end to end. That's the B2B content workflow.

Productivity tools updates worth paying attention to

Not everything I changed this year was about the humanization pipeline.

My brief template in Notion got rebuilt. Added a "voice sample" field, 100-200 words of each client's ideal content voice, and I paste it into every LLM prompt before drafting. That single change cut my revision round trips more than anything else I adjusted this year. Longer onboarding call to collect the sample. Far fewer back-and-forths after submission. Worth it.

I also started asking at onboarding which detection tools clients are running. Not suspicious. Standard. "What does your editorial QA process look like?" Knowing someone uses Originality.ai vs. GPTZero vs. something internal tells me which detector to weight most in my pre-submission checks. Do with this what you will, but my first-submission approval rate is noticeably cleaner since I started asking.

The ai productivity tools that moved my output forward most this year weren't new. Same stack, more intentional use.

Anyway. This is the first thing I'm posting on Dev.to. I write more regularly on my Substack if any of this is useful.

Productivity tips for remote content strategists: what works beyond time zones

Dani Voss — Mon, 13 Jul 2026 14:03:01 +0000

Since 2022, I've run content strategy for B2B SaaS clients while nomadic, spanning four continents. At some point I came to realize that most productivity recommendations are written for people who have a fixed address, a regular schedule, and at least one client in a time zone that aligns with their waking hours.

You may fit none of those descriptions if you're reading this.

I won't suggest you adopt deep work routines or Pomodoro timers. These productivity tips were developed from workflows that held up across visa runs, 11-hour client time zone gaps, and coworking spaces ranging from "really good" to "there was a rooster outside the window in Chiang Mai." If a workflow didn't survive when I moved to a new city, it's not listed here.

Nomadic workflows for remote content strategists

Every remote work productivity article I've read frames this as a focus problem. You can't maintain focus. You need better systems to protect your time. Get a good chair. Take breaks every 52 minutes.

That's not the problem.

The real issue for nomadic content strategists is that your availability setup was designed for a fixed location, and it fails the moment you cross a time zone. My Berlin client needs draft copy by 9am their time. My Sydney client reviews copy while she's online, which falls at my 11pm. My EST client schedules syncs at 8am her time, which lands somewhere between midnight and 2am depending on where I am. You can have perfect focus discipline and still lose your day to the coordination overhead of managing those three time zones simultaneously.

What fixed this was making async-first a contract term instead of a soft preference. Clients sign onboarding docs that specify response windows. Same-day turnaround is a paid line item. Since I hardened these as policies rather than guidelines, the daily communication chaos dropped by roughly 40%. I don't track that number formally, but the felt difference is significant enough to report.

On tooling: once I switched to per-deliverable billing, the calculation around AI writing tools flipped entirely. If a tool triples my output in a session, calling it infrastructure doesn't feel like a stretch. I went into the full workflow in I Tripled My Output in Four Months. Short version: generate fast, humanize properly, and do a read-through before anything goes to a client. The humanization step is non-negotiable if any of your clients run detection on submissions, and more of them do than will tell you upfront.

Digital nomad productivity: what the real challenge is

A quick distinction first, because digital nomad productivity content almost always conflates two separate problems. Logistics (visas, banking, SIM cards, accommodation) and actual work output. Fixing one doesn't automatically fix the other, but most advice treats them as one thing.

The logistics side is its own problem. The work output side comes down to which parts of your workflow depend on a stable location and which don't. Most content strategists discover this the hard way after the first or second move.

Building a location-independent content strategy workflow

Most content strategists who struggle with nomadic work are running a 9-to-5 structure in a different time zone. Same setup, just shifted. It doesn't hold up because that structure was built around real-time conversations and a stable physical context, both of which disappear the moment you start moving between cities every eight weeks.

My content strategy workflow is location-independent by design, which took about six months of breaking and rebuilding to get right.

Intake and planning are always done async. New briefs go into a shared doc. I leave clarifying questions as comments and give clients 48 hours to respond before I start. Unless there's a genuine strategic decision that requires back-and-forth, there's no kickoff call. Cutting unnecessary synchronous touchpoints frees up hours every week that used to just disappear into scheduling overhead.

Production runs on sprint cycles instead of weekly slots. Committing to one piece every Tuesday ties my schedule to whatever Tuesday looks like in whatever city I'm in, which is a fragile dependency. Four pieces delivered at the end of a two-week sprint gives clients consistent output without that fragility. It's also just easier to batch similar work than to produce it in small increments.

Humanization is built into production, not added afterward. I run an AI humanizer between first draft and final review on every piece, regardless of whether the first draft shows any obvious tells. The full stack is in My Nomad Content Stack: Every Tool I Actually Pay For.

Brand voice docs come first for every new client. No exceptions, no shortcuts. One hour upfront saves something like ten hours in revision cycles per contract, and it means subcontractors can produce consistent output without needing me involved at every step.

Tips for maintaining async client communication across time zones

Async communication is where most nomadic content strategists start losing clients. Not because the tools aren't capable, but because nobody updated expectations before the location changed. A client who got same-day Slack replies when you were local will read radio silence at 10pm their time as a problem, even when you're fully on top of the work.

The fix is an onboarding doc sent to every new client before work starts. It covers response windows by channel, how rush requests are priced, the revision process, and what you need from them to stay on schedule. I haven't had an availability complaint since making this standard. I know because I stopped sending it when I moved to Lisbon two years ago, and complaints resurfaced within three weeks.

Communication batching goes hand in hand with this. Responding to messages at set times rather than as they arrive, using status updates to give context. Clients who were initially skeptical now prefer it because the replies are properly thought through rather than reactive one-liners fired off mid-draft. Quality goes up when you're not in constant interrupt mode.

What I got wrong about productivity before going nomad

My assumption going in was that staying focused without external structure would be the hard part. No office, no colleagues nearby, no one checking whether I was at my desk.

That turned out to be irrelevant.

The real productivity drain is the chronic overhead of navigating administrative tasks in new countries: SIM cards, bank transfers, visa paperwork, finding reliable internet, figuring out which pharmacy is open. When you're handling all of that in the same week you're trying to hit 10,000 words of client deliverables, creative output degrades in a way that doesn't recover by morning. Permanent residents made those decisions once and they stay made. Nomads make them on repeat.

Reducing decisions in the workflow is what helps, more than any focus technique I've tried. Standardized tools, built templates, documented processes: each one removes something that used to require a choice. Over a week that adds up to meaningful bandwidth available for work that matters.

The productivity tips worth building around for nomadic content work aren't about improving focus. They're about system design: creating a workflow that runs consistently regardless of location, client time zone, or how much administrative overhead this particular city requires. Build it, move, watch what breaks, fix it, move again.

That's most of the job.