DEV Community

Pizza Cat
Pizza Cat

Posted on

I Was Spending 10 Hours a Week Copy-Pasting Content. Here's What I Learned Building the Fix.

#vue #cloudflare #indiehacker #buildinpublic

I Was Spending 10 Hours a Week Copy-Pasting Content. Here's What I Learned Building the Fix.

Thursday night, 11:47 PM.

I had just finished writing a tutorial about Vue 3 + Cloudflare Workers. Good content. Solid code examples. The kind of thing that should get me eyes.

Then I spent the next 52 minutes doing this:

  1. Copy the article to Dev.to — need to add frontmatter, fix the code block formatting, rewrite the intro to be shorter
  2. Copy a thread version to Twitter — 280 char limit, break into 7 tweets, make each one a hook
  3. Copy to LinkedIn — professional tone, line breaks every 2-3 sentences, no code blocks
  4. Copy to Reddit — conversational, shorter, don't sound like a salesman
  5. Copy to Indie Hackers — narrative style, add the "I'm a solo dev" angle

Same content. Five different formats. Zero value added.

I did the math: over the last 3 months, that's 130 hours. Hours I could have spent building product, talking to users, or — you know — sleeping.

And the worst part? I wasn't even doing it well. The LinkedIn version looked like a Dev.to article. The Reddit post got removed by AutoMod for "promotion." The Twitter thread had a typo in tweet #3 that I didn't catch until 2 days later.

This is the part nobody tells you about being a solo creator:

Writing the content is 30% of the work. Distributing it is the other 70%.

And most of us pretend that 70% doesn't exist. We post to one platform, maybe two, and tell ourselves "the algorithm is broken" when nobody reads it.

But here's the thing I realized: the problem isn't that we're lazy. The problem is that the tools don't exist.

There's no "write once, publish everywhere" for indie developers. Not really. The enterprise tools are $500/month and designed for marketing teams. The free tools are half-baked and don't understand code.

So I decided to build it.

What I Built

MultiPost — write once, AI repurposes for every platform.

You write a blog post, a tutorial, or even just a thought. MultiPost generates platform-optimized versions — Twitter thread, LinkedIn post, Dev.to article, Reddit post, Indie Hackers story — in the time it takes you to make coffee.

The AI doesn't just reformat. It understands that:

  • Twitter needs a hook every 280 characters and a thread structure
  • LinkedIn needs professional tone, paragraph spacing, storytelling
  • Dev.to needs proper frontmatter, code blocks, a technical audience voice
  • Reddit needs to sound like a human, not a marketer
  • Indie Hackers needs narrative, numbers, the "solo founder" angle

One article. Five versions. Three minutes.

Here's What I Learned Building Day 1

1. Start with distribution, not product

I built the landing page before the actual tool.

A lot of developers will hate this advice. "Ship first!" "MVP!" "Move fast!"

But here's the truth: I built a 6-component landing page with an email signup form in ~2 hours. If nobody signs up, I just saved myself weeks of building something nobody wants.

The rule I set: 100 email signups or I pivot.

No marketing team. No ads. Just a landing page and organic content.

2. The pricing tells the story

Free → $19/month → $49/month.

$19 is "I'm a serious creator." $49 is "I'm making money from content."

I didn't invent these numbers. I looked at what Indie Hackers and creators actually pay for tools like this. Content Snare? $29/month. Senja? $39/month. Castmagic? $49/month.

The solo creator market has a very clear price ceiling: $49/month. Above that, you're selling to agencies, not individuals.

3. AI changes the build equation

This landing page + API endpoint took ~2 hours. With AI assistance.

Two years ago, that would have been a full day — writing CSS, debugging the form, setting up the database, configuring the deployment.

The AI didn't write everything. But it wrote enough that I could focus on the decisions that actually matter:

  • What problem am I solving?
  • Who is this for?
  • Is the messaging clear?

Code is cheap in 2026. Clarity is expensive.

The Tech Stack (Brief Version) 

Frontend: Nuxt 3 + TailwindCSS → Cloudflare Pages
Backend: Nuxt Server API → Cloudflare Workers  
Database: Supabase
AI: Claude API (coming when I build the engine)
Payments: Stripe (eventually)
Enter fullscreen mode Exit fullscreen mode

Why Nuxt 3? Because I can write frontend and API routes in the same project, and deploy both to Cloudflare Pages with a single build command.

What's Next

I'm building this entirely in public.

If this resonates:

  1. Drop your email at the landing page — early access gets 50% lifetime
  2. Follow me on Twitter/X — I post daily build updates
  3. Reply with your workflow — what platform gives you the best ROI? What's the most painful part of distribution?

I ship the AI engine next week.

P.S. The irony of repurposing this article across 5 platforms using a tool that doesn't exist yet is not lost on me. I'll let you know how long the manual version takes.

Top comments (0)