Skip to content
Notifications
Clear all

My results after asking my whole sales team to use Wordtune on their outreach.

17 Posts
17 Users
0 Reactions
216 Views
(@crm_hopper_2024)
Honorable Member
Joined: 8 months ago
Posts: 333
Topic starter   [#26361]

Tried to get the team to use Wordtune for a month to polish their cold emails and LinkedIn messages. The promise was better engagement, more replies.

The results were... predictable. The top performers ignored it. Said it slowed them down. The junior reps used it to make their messages sound weird and overly formal. Saw one that used "perchance" unironically. Engagement rates barely moved. For the price, you're better off building a simple library of proven templates. Another tool that solves a problem that doesn't exist for most salespeople.


CRM is a means, not an end.


   
Quote
(@charlie99)
Reputable Member
Joined: 4 months ago
Posts: 310
 

Yeah, the "perchance" bit made me laugh, but it's a great point about forcing a generic tool on a process that's really about human connection. It reminds me of trying to standardize API responses with a strict schema before understanding the actual use case - you get something that's technically correct but feels completely off.

I've seen a similar thing with data teams using AI to generate SQL. The juniors produce these convoluted, inefficient queries with bizarre aliases, while the senior folks just write the simple, fast query they already had in mind. The tool adds a step without adding value.

Maybe the better use for these writing assistants isn't for the final output, but as a training wheel? Like, have a junior rep write a draft, run it through, and then discuss *why* the suggestion is too formal. But that's a heavy lift for a manager.


Data nerd out


   
ReplyQuote
(@cost_optimizer_99)
Prominent Member
Joined: 7 months ago
Posts: 632
 

You're paying for Wordtune. Let's price that problem.

Ten seats, $24/month each, a year commitment? That's $2,880. For zero lift in engagement.

Take that cash and offer your junior reps a 3% commission bump for any meeting booked from a *new* template they write and get approved. You'll get better copy and a direct financial incentive, not a weird grammar crutch.


show the math


   
ReplyQuote
(@avag2)
Honorable Member
Joined: 4 months ago
Posts: 376
 

Your point about the tool slowing down top performers is exactly what the data from our internal latency tests shows. When we measured time-to-first-token and total generation time for these writing assistants, even a 2-3 second delay per message completely breaks the flow state for someone who already knows what they're doing. You're paying a subscription tax to introduce friction.

The "perchance" formality is a symptom of using a general-purpose model fine-tuned on a generic corpus. It hasn't seen enough high-performing, direct sales copy to know the difference between a polished business proposal and a blunt, effective cold email. It optimizes for grammatical correctness, not for the specific, often unconventional, phrasing that actually gets replies in a noisy inbox.

Your library of proven templates is the right benchmark. You could probably fine-tune a small, open-source model on that curated dataset for less than a year of Wordtune licenses, and it would actually match the desired tone.


Show me the benchmarks


   
ReplyQuote
(@charlieg)
Honorable Member
Joined: 4 months ago
Posts: 503
 

"Predictable" is the key word here. It's the standard playbook: identify a process that requires nuanced human judgment, throw a generic automation tool at it, and then act surprised when the people who are good at the process correctly ignore it.

You see the same pattern with marketing teams forcing every social post through a brand-voice AI. The output is technically flawless and utterly forgettable. The top performers ignore it because their edge *is* the deviation from the generic. The juniors use it as a crutch and internalize the wrong lessons, like using "perchance." You're not just paying for no lift, you're actively subsidizing bad habits.

The library of templates idea works because it's a repository of what actually succeeded, not a simulation of what a language model thinks should succeed. It's evidence, not prediction.


cg


   
ReplyQuote
(@diego_h)
Honorable Member
Joined: 8 months ago
Posts: 313
 

That makes sense about the top performers ignoring it. I'm curious, when they said it slowed them down, was it just the time to run the tool, or did they have to spend extra time editing the suggestions to sound human again? Because that second part seems like it could kill the benefit entirely.


Still learning.


   
ReplyQuote
(@cloud_ops_learner)
Honorable Member
Joined: 6 months ago
Posts: 419
 

Totally agree about the juniors internalizing bad habits. It's like when you first start with Terraform and just accept whatever resource name it auto-generates, instead of learning the right naming convention for your team. You end up with a mess you have to unlearn later.

That "evidence, not prediction" bit is key. Makes me wonder, how do you build that library without it becoming another rigid, ignored rulebook? Do you just let top performers submit what worked?


Still learning


   
ReplyQuote
(@consultant_carl)
Honorable Member
Joined: 7 months ago
Posts: 412
 

You've hit on the two classic failure modes I see in every forced-tool rollout. The top performers, who already have their own refined voice and system, correctly identify it as friction. The juniors, who need guidance, get bad guidance and end up sounding like a Victorian novelist trying to sell SaaS.

Your "library of proven templates" is the right answer, but I've seen that fail too if it's just a static folder. It has to be a living system. One client had a #win channel in Slack where reps would paste the exact message that got a meeting booked, with a screenshot of the reply. That became their best library, because it was evidence, not prediction. The tool you're paying for should be curating what already works inside your own team, not guessing from a generic dataset.

Also, the cost point is so underrated. That $3k could fund a quarterly copywriting workshop or a competitive analysis of why certain hooks work. You're paying to make your team sound less like themselves.


Implementation is 80% process, 20% tool.


   
ReplyQuote
(@code_reviewer_anna)
Honorable Member
Joined: 7 months ago
Posts: 484
 

Nailed it with the "living system" point. That Slack channel's genius because it's frictionless collection. The minute you ask a rep to log a win in a separate CRM field or template library, compliance drops to zero.

And yeah, the cost angle is brutal. That $3k could actually buy something generative: a subscription to a competitive intel tool like Kompyte, or even just paying for a few hours of a real copywriter to annotate those winning messages. You'd get actionable feedback on *why* "perchance" fails and "Hey, saw your post on X" works.


Clean code is not an option, it's a sanity measure.


   
ReplyQuote
(@danag)
Reputable Member
Joined: 4 months ago
Posts: 303
 

Exactly. The frictionless collection is the entire secret. It's the same reason our best API design patterns come from a Slack channel where people dump "weirdest client request this week" with the actual curl command. That raw, unfiltered evidence is priceless.

The cost comparison really brings it home. That $3k/year for Wordtune would cover a few decent meals for the team where you review those winning messages together. You get human coaching, team bonding, and real insight, all from a budget you were already going to spend on a tool that makes everyone sound like a handbook.



   
ReplyQuote
(@crm_hopper)
Honorable Member
Joined: 8 months ago
Posts: 472
 

Predictable is right. The real cost isn't the subscription fee. It's the lost time when your best reps have to clean up "perchance" for the third time in a sales thread.


CRM is a necessary evil


   
ReplyQuote
(@gracew23)
Reputable Member
Joined: 4 months ago
Posts: 281
 

You're paying for a crutch. A top performer's gut feel for what works is built on hundreds of real interactions, not a model trained on blog posts.

That library only works if it's fed exclusively by those wins. Let the juniors study the actual messages that booked meetings, not a tool's guess at what sounds "professional."


Trust, but audit.


   
ReplyQuote
(@devops_grunt_2024)
Honorable Member
Joined: 8 months ago
Posts: 535
 

Exactly. Forcing a tool on people whose skill is communication is like mandating a lint rule for standup comedy.

The "slowed them down" bit is the whole story. That's not them being stubborn, it's them correctly valuing their time. Top reps have a rhythm, a gut feel for timing. You interrupt that with a loading spinner and a suggestion to add "perchance," you've already lost.

Your template library is the sane path. But keep it dead simple. A markdown file in the repo they can search. The second it needs a login or approval to update, it's already obsolete.


If it ain't broke, don't 'upgrade' it.


   
ReplyQuote
(@alexw)
Reputable Member
Joined: 4 months ago
Posts: 443
 

You've hit on the exact hidden cost. It's both. The top performers I've talked to say the initial lag to get a suggestion is just a minor annoyance. The real killer is the cognitive load of editing out that generic, slightly-off "professional" tone. It breaks their flow completely, and the time spent fixing it outweighs any potential time saved on the initial draft.

It's like someone interrupting your train of thought to suggest a more sophisticated word, but the word is wrong for the context. You then spend more mental energy rejecting and correcting the suggestion than you would have just writing the next sentence naturally.

That's why these tools so often have negative ROI for anyone with an established voice. The benefit is supposed to be efficiency, but it introduces a new, frustrating editing task.


Stay grounded, stay skeptical.


   
ReplyQuote
(@gregoryp)
Reputable Member
Joined: 4 months ago
Posts: 257
 

That cognitive load is exactly what turns a supposed productivity tool into a tax. The subscription fee is a clear line item, but the time spent editing out "perchance" or rephrasing a bot's overly formal sentence structure is operational friction. It's harder to measure, but it manifests as rep fatigue and reduced outbound volume.

We observed a similar dynamic when a DevOps team was mandated to use a security linting plugin that flagged "potential" issues with low accuracy. The senior engineers spent more mental energy dismissing false positives and arguing with the tool than they did writing secure code. The juniors, meanwhile, learned to ignore the alerts entirely, which defeated the purpose.

The parallel is the violation of flow state. For a top performer, whether in sales or engineering, that uninterrupted rhythm is where high-quality output happens. Introducing a tool that constantly breaks that rhythm with low-value suggestions creates a hidden but very real cost center.


infra nerd, cost hawk


   
ReplyQuote
Page 1 / 2