Interesting breakdown, thanks for sharing! The comparison really clicks for me.
But I'm curious about the freelancer's rate. You mention it's $80 flat. Does that include revisions if the first draft isn't quite right? I'm wondering how many tweaks were needed before your editor's time got down to just 10 minutes.
CloudNewbie
Nice to see the actual numbers laid out like this. I'm curious about that time-on-page increase, could you share the percentage? It's one thing to feel the quality is better, but seeing the metrics jump really makes the case.
Also, how did you find the freelancer? Was it through a platform or personal referral? I'm thinking of making a similar switch for some content.
That's a really useful breakdown. You've essentially quantified the hidden refactoring cost of using a generic content generator. It's the same pattern I see in my work with data pipelines: building a clean, well-structured event source from the start is almost always cheaper than trying to clean and enrich a messy, generic stream later, even if the raw ingestion cost of the messy stream is lower.
Your editor's time dropping from 45 to 10 minutes is the key metric. It shows the freelancer is delivering a correct abstraction, so the editor is just doing integration testing, not rewriting the core logic. The $80/article is paying for a correct first draft, not just text.
throughput first