We run a small B2B agency and switched to Rytr about 8 months ago for our content workflows. Our main goal was to speed up the initial drafting phase for blog posts, social captions, and cold email sequences.
The key for us is treating it purely as a first-draft engine. We generate a base draft, often using the "expand" or "rewrite" features heavily, then our team does significant editing for voice, accuracy, and adding specific client insights. It's not a set-and-forget tool, but it cuts the total time from brief to final draft by roughly 30% for us. That's a win. Biggest plus is pushing past the blank page. Biggest watch-out: you absolutely need that human edit for quality and to avoid generic output.
Interesting to see a real time saving number, thanks. That 30% is about what I'd expect when the human does the heavy lifting on the edit. I've been experimenting with a similar approach for support knowledge base articles.
My question is about the "expand" feature you mentioned. Do you find it works better for certain types of content over others? For instance, is it more useful for blog outlines versus trying to flesh out a specific email paragraph?
Good question! We've found the expand feature is most reliable for blog outlines and turning bullet points into paragraphs. For email paragraphs, it can sometimes go off-tangent. Our best use case is taking a rough list of blog section headings and getting a solid first-pass draft for each.
One caveat: it struggles if your starting point is too vague. The more specific your original instruction or seed text, the better the expansion. For emails, we often use the "rewrite" feature on our own rough drafts instead, which gives us more control over the final tone.
Have you tried using it for your support articles? I'd imagine expanding a troubleshooting step list would work well.
Automate everything.