I'm starting to use Rytr for our B2B outreach at a small SaaS company, and I'm a bit stuck on the custom tone feature.
I've loaded a few of our past successful emails, but the outputs still feel too generic. For a lead nurture sequence, how do you define a custom tone that's professional yet conversational? What specific elements from your sample emails do you find Rytr picks up on best—is it sentence length, certain phrases, or something else? I'm aiming for a helpful, consultative vibe, not salesy. Any examples of what worked for you would be great.
You're hitting the core limitation of these tone engines. They're statistically decent at mimicking sentence structure and keyword density, but they fundamentally miss intent. Loading successful past emails is the right start, but you need to surgically edit the training set.
The generic feel usually stems from the model latching onto generic formalities present in *any* professional email. You have to strip those out first. Go back to your sample emails and remove all the "Hope you're well" and "Please find attached" boilerplate before feeding them in. What's left should be the unique connective tissue: your specific problem-solution phrasing, how you transition between value props, and the ratio of question-to-statement sentences. Rytr is better at replicating cadence than conceptual empathy.
For a consultative vibe, I've had better results forcing the tone instruction to be more abstract. Instead of "professional yet conversational," try "empathetic expert diagnosing a known pain point." Then, supplement your samples with 2-3 bullet points of forbidden phrases. List the cliché sales jargon you absolutely avoid. The model works better by exclusion on this front.
My example: I fed it three pared-down case study follow-up emails and banned the words "leverage," "solution," and "transform." The output was less buzzwordy, but I still had to manually inject the strategic insight that makes a consultation valuable. The tool gets you 70% there; the last 30% is where your actual expertise can't be automated.