Localized Translation
Translate with meaning intact: idioms adapted, formality calibrated to the locale, tricky sentences back-translated so you can verify.
Translate the text below into [TARGET LANGUAGE + LOCALE, locale matters: "Spanish (Mexico)" and "Spanish (Spain)" differ, as do "Portuguese (Brazil)" vs "(Portugal)"].
Source text:
"""
[PASTE TEXT]
"""
Audience: [WHO READS THIS IN THE TARGET LANGUAGE, e.g. "customers of our app", "business partners", "social media followers"]
Purpose: [WHAT IT MUST ACCOMPLISH, e.g. "get them to complete signup", "explain a policy change without alarm"]
Formality: [FORMAL / STANDARD-PROFESSIONAL / CASUAL, or "match the source"; if the language has T-V address forms (tú/usted, du/Sie), say which to use or let me know what you chose and why]
Do not translate: [BRAND NAMES, PRODUCT TERMS, TECHNICAL TERMS TO KEEP IN ENGLISH, or "none"]
Deliver:
1. **The translation**: natural target-language writing that serves the purpose, not word-for-word transfer. Adapt idioms, metaphors, and examples to ones that land with this audience; keep all formatting, placeholders ({name}, %s), links, and markup exactly intact.
2. **Translator's notes**: only where you made a real choice: idioms you adapted (source → what you used → why), the formality/address decision, terms with multiple valid translations and why you picked yours, and anything untranslatable (wordplay, cultural references) with what you did instead.
3. **Back-translation check**: for the 2-4 sentences where meaning was most at risk (idioms, legal-ish phrasing, humor), give a literal English back-translation of your version so I can verify nothing drifted.
4. **Flags**: anything in the source that may not work in the target culture even correctly translated (humor that doesn't cross, references the audience won't know, tone that reads differently), each with a suggested adaptation.
Rules: meaning and intent outrank literal fidelity, but never add claims or soften commitments. If the source promises something, the translation promises exactly the same thing. If a sentence is ambiguous in the source, say so and translate the most likely reading rather than silently picking one.How to use
The back-translation section is your verification tool when you don't speak the target language. Read it against your source and anything that drifted will show. For customer-facing or legal text, have a native speaker review the flagged sentences specifically; the notes and flags tell them exactly where to look, which makes a 10-minute review as good as a full re-translation.
More business prompts
Build me a monthly budget and a debt payoff plan from these numbers. Take-home income per month: [AMOUNT, and note if it varies] Fixed costs: [RENT/MORTGAGE, UTILITIES, INSURANCE, SUBSCRIPTIONS, TRANSPORT, CHILDCARE, with amounts] Variable spending, last 3 months if known: [GROCERIES, DINING, SHOPPING, ETC.] Debts: [FOR EACH: name, balan
Budget and Debt Payoff Plan
Turn your real income, bills, and debts into a monthly budget and a payoff schedule with the math shown and the tradeoffs named.
Build a 13-week cash flow forecast. Cash on hand today: [AMOUNT, and which accounts] Any restricted or committed cash: [AMOUNT AND WHAT IT IS FOR] Expected inflows: - Receivables outstanding: [CUSTOMER, AMOUNT, INVOICE DATE, TERMS, and how reliably each pays] - Recurring revenue: [AMOUNT, BILLING DATE, CHURN ASSUMPTION] - New sales expe
13-Week Cash Flow Forecast
Build the rolling weekly cash forecast operators actually run on: opening balance, timed inflows and outflows, and the week you run short.
Help me set pricing for [PRODUCT/SERVICE]. What it does and who buys it: [PRODUCT + BUYER] The alternative if they do not buy: [COMPETITOR, IN-HOUSE, SPREADSHEET, DOING NOTHING] What that alternative costs them: [MONEY, TIME, RISK. Estimate if needed and say so.] Value we create, quantified if possible: [TIME SAVED, REVENUE GAINED, COST
Pricing Strategy
Work out what to charge and how to package it: value basis, tier structure, the metric you meter on, and how to test before committing.