I've been testing Wordtune for the last month, primarily to clean up internal documentation and user-facing emails from our international teams. The core question: can it handle the lexical and grammatical nuances between British and American English, or does it just default to a generic "English" that butchers regional specifics?
Here's the blunt summary: Wordtune is heavily biased toward American English. It consistently misidentifies correct British English as errors and suggests American alternatives. This isn't just about "colour" vs. "color"; it's about sentence structure, preposition use, and formality.
**Key Findings:**
* **Spelling & Vocabulary:** As expected, it flags standard British spellings (centre, organise, travelled) and suggests American ones. More problematic is vocabulary. It suggested changing "I'll put that in my diary" to "I'll put that in my calendar," which changes the connotation.
* **Grammar & Prepositions:** This is where it fails. For "The team are happy," (correct UK collective noun agreement) it insisted on "The team is happy." It also frequently messed with prepositions common in UK English.
* **Tone Adjustments:** The "Casual" and "Formal" rewrites seem trained on American corpora. A British English formal sentence rewritten to be "more formal" often resulted in an awkward, American-business-jargon-filled output.
**Test Example:**
I ran the same poorly written British English source through both regional settings.
```text
Source (Deliberately poor UK): The project got finalised at the weekend. The staff have been brilliant managing the enquiries.
Wordtune (UK setting): The project was finalised at the weekend. The staff were brilliant at managing the enquiries.
Wordtune (US setting): The project was finalized over the weekend. The staff have been brilliant at managing the inquiries.
```
Notice the UK setting kept "finalised" and "weekend" structure, but the US setting changed spelling, preposition ("over the weekend"), and even flipped "staff were" back to "staff have been." The US version is more polished, but it's not British English.
**Verdict:** If your team operates primarily in American English, it's a decent tool. For British English, it's an aggressive American editor, not a nuanced assistant. You'll spend more time rejecting its suggestions than accepting them. For a data pipeline analogy, it's like a job that forces a `CAST(uk_text AS american_english)` without a `WHERE` clause—you lose fidelity. Not production-ready for UK contexts.
garbage in, garbage out
I lead a small project team (around 15 people) in a UK-based SaaS company, and we evaluated Wordtune last quarter for the same purpose - polishing client communications and internal docs.
**Audience Fit:** It's squarely aimed at US-centric users or companies. If your team is mostly UK/EU, it fights you on fundamentals. For us, it added a frustrating correction step.
**Real Pricing:** The Teams plan ran us about $12/user/month billed annually. That's not cheap for a tool that adds friction to our core task.
**Where It Breaks:** Exactly as you said. Beyond spelling, it mis-handles collective nouns and prepositions. We saw it flag "at the weekend" and "in hospital" (without 'the') as incorrect, suggesting US phrasings every time.
**Where It Wins:** Its rephrasing for clarity on simple, direct sentences is fast and helpful. For internal Slack messages where regional nuance doesn't matter, the "Shorten" feature got used.
Given your focus on British English accuracy, I'd skip Wordtune and look at a human-led service if budget allows, or just use a good style guide. If your teams are mixed, which specific document type (client emails vs. internal wikis) is the higher priority? That would help narrow a better alternative.
You hit on something really key with the vocabulary suggestions, like the diary/calendar swap. That's not just a regional tweak, it changes the meaning of the sentence! Our team in Dublin found it kept trying to "Americanize" idioms in a way that stripped the local flavour and sometimes even introduced ambiguity.
It feels like the tool is optimising for a single, standardised version of English, which just isn't how many international teams work. The extra step of having to *reject* its "corrections" adds real friction.
Have you found any workarounds, or are you just living with the constant corrections?
You're absolutely right about the preposition and collective noun issues, that's where the friction becomes really tangible. I've seen it trip up on things like "I'll email you **on** the weekend" versus "**at** the weekend," treating the latter as wrong every time.
This bias creates a bigger problem than just extra clicks for international teams: it can erode confidence in non-US writers. If a tool constantly underlines your perfectly correct grammar, you start second-guessing yourself, which defeats the purpose of a writing assistant.
Have you looked into whether any of their competitors, like Grammarly with its regional English settings, handle this any better? Or is this just an inherent limitation of most of these AI-powered writing tools right now?
api first