A Strategic Flow newsletter audit — before & after
A product update newsletter with five genuine innovations — buried under flat descriptions, absent social proof, and CTAs that point readers to demos instead of outcomes. Here's what should have been said, and why.
01 · Original Newsletter
From brand-adaptive translations to intelligent automation and seamless integrations, this edition is packed with updates that help your teams go global confidently, without ever sacrificing quality or oversight.
AI translations
Custom AI profiles: Beyond one-size-fits-all translations
We're happy to announce that Custom AI Profiles is out of beta this month! One-size-fits-all never fitted anyone, that's why our AI is powered by Retrieval-Augmented Generation (RAG) to dynamically retrieve your most relevant past examples…
Why teams love it: Up to 95% ready-to-publish translations · AI that adapts to your Translation Memory · Brand-consistent output · Faster localization, fewer manual edits
Integrations
New integrations and file formats to plug Lokalise directly into your workflow
We've expanded our integrations to fit seamlessly into your existing stack. Since our last edition in Autumn, we launched native support for Apple's XCStrings format, a new Customer.io integration…
Beta
MCP Server: Talk to your translations
Imagine if managing your localization workflow was as simple as having a conversation. No more context-switching between tools, no more hunting through API documentation…
AI agents
The AI buddy inside Lokalise
Our new AI agent helps you create, configure, and manage localization projects for you. Just ask and it'll execute actions behind the scenes…
Invitation-only beta
Autopilot: Localization built for marketing and content teams
Autopilot automates localization for long-form marketing and content workflows, helping teams move faster with less manual coordination and more control…
All our product updates are published on the Lokalog on a regular basis. Want to be the first to know about them? Get updates every two weeks in your inbox.
02 · Subject Line
A filing label. "Shipped by Lokalise" is a format announcement — it tells the reader what kind of email this is, not why they should open it. "Winter 2026" is a date stamp, not a reason to act. There is no pain identified, no outcome promised, no curiosity gap created. This subject line competes with every other product update email in the inbox at a zero-differentiation disadvantage.
Personalisation to team role ("your localization team") + specificity (five) + change-signal ("what changed") = a subject line that creates a curiosity gap. The reader knows something happened that applies to them, they know a number, and they don't yet know what it is. All three are conversion signals. The original has none of these.
03 · Structural Audit
04 · Rewritten Newsletter
Strategic Flow · Rewrite · Winter 2026
This winter, Lokalise shipped five capabilities that change how localization actually works inside your stack. Not incremental improvements — architectural shifts. Custom AI Profiles hit general availability. The MCP Server removes API friction entirely. The AI Agent handles admin so your team doesn't have to. Here's what each one means for your workflow, in plain language.
What shipped — and what it means for your team:
All five capabilities are live in your Lokalise account today or available for immediate beta access. No setup required for GA features — open your project to see Custom AI Profiles active.
05 · Method
"Shipped by Lokalise – Winter 2026" is how you label a folder. "Your localization team just got five new capabilities. Here's what changed." identifies a role ("your localization team"), delivers a specific number (five), and creates a gap (what changed?). A subject line answers one question: why should I open this right now? The original answers: this is a scheduled product update. Those are not the same answer.
"AI you can trust. Orchestrated localization that never sacrifices quality." is a values statement — it belongs on an About page, not the hero of a product update newsletter. The rewrite opens with the change: "Five things your localization team couldn't do last quarter — now they can." A product newsletter hero should answer: what is materially different today? The original answers: here is what we stand for. Those are not the same question.
"Up to 95% ready-to-publish translations" is the single most specific, measurable, reader-relevant claim in the entire newsletter. It appears as the second item in a four-item bullet list. In the rewrite, it's a stat card at full width — the first number the reader sees. Numbers are scanned, not read. The number that most changes a localization manager's calculus should be the first number they encounter, not the fourth line of a sub-list.
"Dynamically retrieve your most relevant past examples and use them to guide each translation" describes architecture. "Up to 95% of translations arrive ready to publish without a human edit" describes what the reader no longer has to do. The MCP Server "enables natural language commands" in the original. The rewrite says: "No API documentation. No custom scripts. No context-switching." Every technical claim should be followed immediately by its operational consequence: what does my team no longer have to spend time on?
"Imagine if managing your localization workflow was as simple as having a conversation" signals that the product is aspirational, not actual. For a beta that already exists, this framing costs trust. The rewrite begins with the consequence: "Trigger any Lokalise action with a natural language command. No API documentation. No custom scripts." The MCP Server exists — the newsletter should speak as if it exists. Imagination prompts work in advertising; they signal fiction in product copy.
"We used to spend two days per release reconciling our Translation Memory with AI output. With Custom AI Profiles, that review round is nearly gone." That quote does what 400 words of feature description cannot: it answers the question the reader is actually asking — does this work in practice, for someone with a workflow like mine? The original newsletter displays 3,000+ customer logos in a scrolling ticker and uses none of them for proof. Third-party, role-specific, before/after social proof is the highest-trust asset in any B2B product email.
"Learn more in our next live webinar" requires the reader to attend a meeting at a future time before they can act on what they just read. "Open my Lokalise project →" is a decision the reader makes about their own work, immediately. For GA features already active in the product, the CTA should always be the shortest path to the feature — not a detour through a calendar invite. Ownership CTAs ("my project") outperform command CTAs ("try this") because they activate agency rather than compliance. The arrow matters too: it signals continuation, not departure.
Name the change before you name the product. Put the best number where it can be scanned. Translate every feature into what the reader stops doing. Use one real quote to do what five feature sections cannot. And make the CTA the shortest path to the thing — not the longest route around it.
strategicflow.carrd.co →