Transept

For product marketers & localization managers

Localize the launch kit, all of it

Email, landing page, FAQ, release notes, social posts — the assets that make a launch. Run them through Transept as one bundle with a shared product glossary and a shared brand styleguide. What ships is consistent across every surface and every language.

Start translating→

Free to begin · No card required

In context✦

Product launches in multiple markets used to require a localization team, a project manager, and a six-week runway. The assets — announcement email, landing page, FAQ, release notes, social copy, sales-enablement deck — go into 8–12 languages, with consistent product terminology across all of them, and ship simultaneously on launch day. This workflow is built for that exact problem: bundle the assets, apply the launch glossary, run Publish-Ready Mode across the whole batch, run reviewer passes per language via client review links, and ship every asset to its destination platform. The 12-language launch that took six weeks now takes a working day.

A launch in twelve languages, on launch day

The standard launch kit workflow — refined from GTM § 9 with localization managers running launches across 8–12 languages on a release cadence.

  1. Bundle the assets

    Email template, landing page HTML, FAQ in Markdown, release notes, social copy. Upload them as a batch — or import the relevant Notion / Drive folder.

  2. Apply the product launch glossary

    The feature name, the version number, the tagline, the pricing labels. Pinned across every asset so the announcement reads as one campaign in every language.

  3. Apply the brand styleguide

    Tone, voice, sentence length, idiom handling. The marketing style that ran the source campaign carries into every target language.

  4. Batch translate at Publish-Ready

    Publish-Ready Mode for marketing copy. Translation + proofread + polish + QA, every asset, every language, one queue.

  5. Reviewer pass on the language-pair leads

    Share the document with each language’s reviewer via a client review link. They comment; you resolve; ship.

  6. Export to where each asset ships

    Email HTML to your ESP. Landing-page HTML to your CMS. FAQ Markdown to Notion or your docs site. Release notes to wherever they live.

Transept batch queue with launch kit assets — email, landing page, FAQ, release notes

Why launch kits work as one bundle

Consistency across assets

The feature name in the email matches the feature name on the landing page matches the feature name in the FAQ. Shared glossary, by construction.

One review pass per language

The localization reviewer sees every asset for their market in one workspace, not in five emails across three tools.

Ready-to-ship at Publish-Ready

Premium models, full review workflow, the works. Spend the credits to save the launch-day fire drill.

Footnotes✦

Questions, answered without the fluff

  • Announcement email; localized landing page (or a section of it); FAQ; release notes; in-product changelog; social posts. Some teams also include sales-enablement decks and press kits.
  • Many teams use a TMS for product-string localization (UI strings, mobile app bundles) and Transept for the document-heavy assets (emails, FAQs, release notes, marketing copy). The two coexist; share the glossary between them.
  • Yes — save the launch glossary and styleguide; reuse them next release. Most teams update the glossary with the new feature names each release and rerun the same workflow.
  • A 6-asset launch kit averaging 800 words per asset, into 8 languages at Publish-Ready: ~190K credits. Comfortably inside Pro plan’s monthly allowance.
  • Announcement email, localized landing page (or a section of it), FAQ, in-product changelog, release notes, social posts (LinkedIn / X / Instagram), and often a sales-enablement deck and press kit. Some teams add a help-center article. The bundle averages 6–10 assets, totaling 5–8K source words.
  • TMS handles the product UI strings — the feature name, button labels, in-app changelog text. Transept handles the document-heavy launch content — emails, landing pages, FAQs, press kits. Share the glossary between the two so the feature names stay consistent across surfaces.
  • Yes — save the launch glossary and styleguide; reuse them next release with just the new feature names added. Most teams update the glossary once per release and rerun the same workflow. Time investment after the first launch is roughly half of the first time.
  • Client review links — generate one per language for your regional reviewer. They open in any browser, leave comments per sentence, you resolve in the editor. No accounts needed for the reviewers. Most launches run a 24–48 hour review window before publishing.
  • A 6-asset kit averaging 800 words per asset, into 12 languages at Publish-Ready Mode: about 290K credits. Comfortably inside Pro plan (500K). For teams running monthly launches, Pro plus top-up packs is the typical setup.
Related✦

Keep reading around this workflow

❧

Ship the next launch on every market simultaneously

Start translating→

Free to begin · No card required