AI consultants who say where AI helps and where a person does

AI consulting services for multilingual search and content

Where machine output helps across languages, and where a person keeps the trust a page was built to earn.

We sort your multilingual content into what AI can handle and what needs a native reader, so you save time where it is safe and keep trust where it is decided.

English
I needed some help with my website, and thank God I found Mike and his team! They identified what was missing and started working on it from day one. Their improvements showed results and still do!… That's why I continue to work with them. If you feel lost with your website, SEO and marketing in general, contact them, they'll make your life easier. Thanks guys!
Alicia B., on GoogleOne month ago

What you get from our AI consulting services

An assessment of where AI fits in your multilingual workflow. We look at each step, from keyword research to the published page, and tell you which ones machine output can take on and which stay with a person who reads the language.

Machine translation set up with a reader. We set up neural machine translation with terminology-aware post-editing, so the first draft of a multilingual page arrives faster and a native editor makes it right.

A review of your multilingual support assistant. We assess whether it can answer on its own, or needs a human fallback past the routine questions, against the actual cost of a wrong answer.

Sentiment analysis across your markets, surfacing patterns in how your brand is discussed that a manual review would take weeks to find.

Measurement, so you see in figures whether each piece of the setup paid for itself.

Where AI gains you the most, with a person on the judgement calls

Speed on the early work. AI-assisted research gets through the first keyword and competitor work across languages far faster than doing it by hand, and we put it to work there.

Accuracy where it counts. We keep three judgement calls with someone who knows the market: commercial copy that converts in languages outside a model's native-sounding range, choosing which of two culturally different approaches will land better with a specific audience, and catching the subtle, confident error that reads as fluent and is factually off.

A reader on every output. Someone who reads the target language reviews the output of every AI system in the stack, so the fluent, professional-looking sentence that is quietly wrong gets caught before a customer sees it.

Open what you need

What we set up and review for you

The four pieces of work an AI consulting engagement usually covers, each checked by a reader of the language.

Machine translation with a reader on the output

We choose and tune an engine for your subject matter to take the first pass, then put a native editor on the material that carries risk and a lighter pass on the rest, so everything you publish has had a reader.

Multilingual support assistant review

We review the assistant that answers your customers on the site, built on your own material so it answers about your products specifically. We check that it handles the repetitive questions in each market with one team behind it, and hands over cleanly when a question goes beyond it.

We give every language the assistant answers in a reader who checks its answers, so an invented answer is caught early.

Sentiment analysis across markets

We run sentiment and theme analysis across reviews, support tickets and social mentions per language, which is where the gap between what a market says and what you assume it wants tends to show up first.

We split the report by language, so a complaint pattern that appears in one language alone, usually a sign of a localization defect, stands out.

Measuring whether it worked

We measure accuracy on a sample somebody checks, turnaround time, cost per published page, and whether the people using the output would choose to keep it. Market-level numbers sit alongside those, so each language shows its own result on the dashboard.

From the brief to the reporting

What happens after your first message

  1. A free 20-minute stack walkthroughWe walk through your current tools and multilingual workflow with you and point out where AI could save time, before you commit to anything.
  2. A written scopeAfter the call we send a written scope naming the workflows we will work on, the deliverables and how we will measure each one.
  3. An assessment of where AI fitsWe map your multilingual workflow step by step and report where machine output can take the first pass and where a native reader keeps it right.
  4. Setup with a reader on every languageWe set up the machine translation, support assistant review or sentiment analysis agreed in the scope, with a reader of each target language checking the output.
  5. Measuring whether it workedWe measure accuracy on a checked sample, turnaround, cost per published page and results per market, and give you a written report on what to keep.
Mike Bastin, founder, in Valencia

Who does the work

Mike Bastin and his team, working from Valencia in your buyers’ languages

Mike has worked in multilingual search for over two decades and founded BeTranslated, the translation agency he has run for twenty years, whose ten country sites each compete in their own market. He works natively in French, fluently in English, Spanish and Dutch, and well enough in German, Italian and Portuguese to run SEO projects in them.

We run our own sites the way we run yours. See how we built ValenciaMove, our removals site in five languages.

Mike leads the team on every engagement, so you deal with him from the first call to the monthly report.

The next step

Find out what AI consulting could be worth in your markets

Thirty minutes on which markets matter, what already ranks, and what has been tried before. A written scope naming pages and deliverables follows. Engagements continue one month at a time.

The whole scope

What else we take on for you

Where AI helps across languages, and where a human keeps the quality, is a question best answered on your own content. We look at what you already publish, what of it is machine-made, and what that is doing to the pages that have to be trusted.

The answer is usually a mix: some of it is worth automating, and some of it is the reason a reader believed you in the first place.