Lingo · Investor Book
Who is speaking?
An investor book about the one question no translator asks — and the company we are building on the answer.
First edition · 2026 · Tashkent
Contents
- 01A sentence that never got sentForeword
- 02Three problems, one rootThe problem
- 03What the incumbents actually askThe gap
- 04Not a plan — it already worksThe product today
- 05The layer above the modelHow it works
- 06Small numbers, honestly readTraction
- 07Why this is hard to copyDefensibility
- 08Translation is the foundation, not the productThe loop
- 09The problem is not nationalMarket
- 10Translation brings them in, learning keeps themBusiness model
- 11What could go wrongRisks
- 12Who is building this, and what we needTeam and the ask
Prepared for investors. All product screens in this book are live screens, not mockups.
Traction figures are as of August 2026 and are stated without rounding up.
Contact: Samar Saidov · lingo-translator.uz
01 — Foreword
A sentence that never got sent
Every day millions of people write a message in a foreign language, read it back, and delete it.
The founder of this company once spent eleven minutes writing four sentences to a foreign client. The grammar was correct — a machine had produced it. But it did not sound like him. It sounded like a form. He rewrote it three times, then wrote something shorter and safer instead, and lost the tone he actually needed.
That is the moment Lingo is built around. Not the moment a translation is wrong, but the moment a translation is correct and still unusable. Machine translation solved meaning years ago. What it never solved is the part a human hears first: who is speaking, to whom, and in what register.
Translation is a solved problem. Sounding like yourself in another language is not.
This book is written for one kind of reader: an investor who wants to know whether this is a thin wrapper around a model, or a company with a compounding asset. We answer that directly in chapter 07, and we do not hide the parts that are still small — chapter 06 states our traction plainly, including the number that is not yet impressive.
- What we are
- A translator that asks about speaker, listener and tone before it translates
- What we already run
- Web platform, Telegram mini app, 26+ languages, 12 registers
- What we are building
- A personal language-learning layer fed by real translation behaviour
- What we are raising
- Pre-seed / seed, to build the learning layer and the keyboard
02 — The problem
Three problems, one root
Translators are grammatically correct and humanly wrong.
A translation carries more than meaning. It carries a relationship. When you write to your manager, your closest friend and someone you love, you are the same person using three different languages — and every existing translator collapses all three into one flat output.
01 · Tone is not a setting, it is the message
Google Translate returns one string. DeepL adds a formal/informal switch, which is two options for a problem that has at least a dozen. Nobody addresses their boss the way they address a childhood friend, and a translation that gets the register wrong is not a small stylistic miss — it is read as rudeness, coldness, or naivety.
Hicasual
Wassupstreet
Good daybusiness
Hey youromantic
02 · Gender is grammar, not preference
In Arabic, kataba is “you wrote” to a man and katabti to a woman. In Russian, a woman says я сказала and a man says я сказал. Uzbek does not mark this at all. So when the source language is genderless and the target language demands gender, the machine has to choose — and it chooses masculine, silently, every time.
For roughly half of all users, that means a translator that has been misgendering them for a decade. It is not a rare edge case; in the six languages below it happens in ordinary, everyday sentences.
| Language | Where gender is forced | Current behaviour |
|---|---|---|
| Arabic | Verbs, adjectives, second person | Defaults masculine |
| Russian | Past tense, adjectives | Defaults masculine |
| Hebrew | Verbs, second person | Defaults masculine |
| Hindi | Verbs, adjectives | Defaults masculine |
| Spanish | Adjectives, participles | Defaults masculine |
| French | Adjectives, participles | Defaults masculine |
03 · Ten years of study, still no fluency
Courses teach exam language. People finish ten years of English and still cannot follow a film, read chat abbreviations, or write a message that sounds like an adult. The gap is not vocabulary — it is register, idiom and living speech, which is exactly the part no textbook can keep up with.
03 — The gap
What the incumbents actually ask
Not one of them asks who is speaking.
It is worth being precise about the competitive picture, because “Google already does this” is the first objection any investor raises. Google, DeepL and general chat assistants all translate well. The difference is in the inputs they accept before translating.
| Speaker gender | Register | Culture profile | Learning loop | |
|---|---|---|---|---|
| Google Translate | no | no | no | no |
| DeepL | no | formal / informal | no | no |
| ChatGPT (prompted) | if you ask | if you ask | generic | no |
| Duolingo | — | — | — | yes, but abstract |
| Lingo | yes | 12 registers | 26 languages | yes, from your own text |
The chat-assistant row deserves an honest note. A skilled user can prompt a general model into a good register. But that requires knowing what to ask for, in a language you do not speak well, every single time. Lingo turns that expertise into two taps — and stores the result, which is the part a prompt cannot do.
A universal product is optimised for the average user. There is no average speaker.
One concrete comparison
- Source (Uzbek)
- men charchadim
- Google → Spanish
- estoy cansado — masculine, always
- Lingo, female speaker
- estoy cansada — correct, without the user knowing the rule
- Lingo, business register
- me encuentro agotado tras la jornada
04 — The product today
Not a plan — it already works
Everything in this chapter is live, in production, built without outside investment.
Lingo asks three questions before it translates, and those three questions are the entire product thesis: who is speaking, who is listening, and in what tone. Everything else — files, poetry, glossary, history — is that same engine applied to a different surface.




- Who is speaking?
- gender · age · individual or company
- Speaking to whom?
- manager · client · friend · teacher · someone you love
- In what tone?
- 12 registers · formality level · length
Modules already shipped
- 01Web platform at lingo-translator.uz — full register control
- 02Telegram mini app and bot — where our users already are
- 0326+ languages, 12 registers, adjustable formality and length
- 04Document translation with formality preserved across the whole file
- 05Literary and poetry translation — rhyme and metre preserved, three variants offered
- 06Glossary for personal and company terms, voice input, full translation archive
05 — How it works
The layer above the model
The model is a commodity. The layer that feeds it is not.
Lingo is not a single prompt. It is a pipeline in which the model is one replaceable step, deliberately placed at the end. Everything valuable happens before and after it.
- 01Context capture — speaker gender and age, relationship to the listener, chosen register, target language, prior corrections by this user
- 02Cultural profile lookup — a hand-written politeness and idiom profile per language pair: how directness, honorifics, diminutives and refusals behave
- 03Register construction — the profile plus the context become a constrained instruction, not a free-form prompt
- 04Model routing — short everyday text goes to a fast, cheap model; literary, legal and long-form goes to a strong one; repeated requests are cached
- 05Post-check — gender agreement, honorific consistency and glossary terms are verified against the target language rules before output
- 06Feedback capture — which of the offered variants the user picked, and what they edited by hand
Step six is the company. The other five are engineering.
Step six produces something no competitor can scrape: a record of which register a real person chose in a real situation, and what they corrected afterwards. Public text on the internet shows what people published. Our data shows what they hesitated over — the exact material a learning product needs.

06 — Traction
Small numbers, honestly read
120 users is not a big number, and we will not dress it up as one.
120
registered users
~1 200
monthly visits
~100%
monthly return rate
$0
advertising spend
These figures are from August 2026, achieved with no marketing budget, no launch campaign and no press. Every user arrived by word of mouth, mostly through Telegram. What matters in that set is not the size — it is the shape.
What the numbers do say
- —Return rate is close to 100% per month on a zero budget, which is the cleanest available signal that the product is needed rather than tried
- —Roughly ten visits per user per month means people come back with real work, not curiosity
- —The most used features are register selection and file translation — the two places where generic tools fail hardest
What the numbers do not say
- —There is no daily habit yet. Translation is need-driven: you translate when something needs translating
- —We have no paid conversion data, because Pro has not launched
- —The base is small enough that a single Telegram channel could distort it, so we do not extrapolate from it
07 — Defensibility
Why this is hard to copy
Our moat is not the model. It is data, focus and speed of language.
01 · “Isn’t this a wrapper on ChatGPT?”
Today we use ready models, as nearly every AI product does. A wrapper, however, is a product where removing the model leaves nothing. Remove the model from Lingo and three assets remain: cultural profiles for 26 languages, the context-to-register logic, and the behavioural record of which register real users chose and edited. The first two took work. The third cannot be bought at any price, because it only comes from usage.
02 · “What if Google adds this?”
Google could. It will not, because it builds a universal product, and a universal product is tuned for the average user across every language. Writing a deep politeness and idiom profile for Uzbek, Kazakh or Turkmen will never reach the top of that roadmap — the market is too small to justify the attention. A focused product wins its audience precisely where a universal one cannot afford to look.
03 · The living-language layer
Slang decays fast; 2019 slang is comedy in 2026. A textbook is reissued every three to four years and is outdated the day it ships. Our layer can update weekly. That is not a temporary advantage but a structural one: a publisher's production cycle will always be slower than language change, and that will never reverse.
04 · Two products in one place
For competitors, translating and teaching are separate businesses: Google translates, Duolingo teaches, and neither ever sees the other's data. We hold both sides, so usage itself produces the teaching material.
Anyone can rent the same model. Nobody can rent our users' hesitation.
- Copyable in a week
- The interface, the register list, the language count
- Copyable in a year
- The cultural profiles, if someone hires the linguists
- Not copyable
- Years of real register choices and hand corrections by our users
08 — The loop
Translation is the foundation, not the product
Every translation reveals one thing: what this person could not say themselves.
The strategic move in this company is not a better translator. It is what a translator knows. Each request is a confession of a specific gap — a thought this person could not express, a phrase they struggle with, a register they are unsure of. Nobody else holds that signal at the moment of need.
- 01A person translates something they could not write themselves
- 02The system records the gap: the thought, the phrase, the uncertain register
- 03The system teaches exactly that, in the words that person actually needed
- 04They translate less and write more themselves — and stay, because progress is visible
Duolingo teaches abstractions: apple, horse, the boy eats bread. We teach the sentence someone failed to send yesterday. It is the same pedagogy applied to material that already carries emotional weight, which is why we expect retention to behave like a habit product rather than a utility.
The four layers
- Layer 1 — live today
- Translation with register, gender and culture control
- Layer 2 — 4 to 8 months
- Personal language learning built from your own translation history
- Layer 3 — 6 to 12 months
- Mobile keyboard and browser extension: Lingo inside every app
- Layer 4 — 18 months+
- Voice: real-time conversation with register preserved
09 — Market
The problem is not national
We start where we cannot be beaten, then expand along the same complaint.
Our entry market is deliberately narrow. Uzbek, Kazakh and Turkmen are languages where no global player will ever invest in cultural depth — which makes them the cheapest place on earth to build an unbeatable product. The expansion path then follows a complaint that turns out to be universal.
- Today · Uzbekistan
- ~31M internet users, ~6–9M realistic target audience
- Year 1 · Central Asia + diaspora
- ~40M people plus 2–3M labour migrants; willingness to pay is highest in the diaspora, where documents, work and healthcare make translation a daily necessity
- Year 2 · Turkic world
- Turkey, Azerbaijan, Tatar and Uyghur speakers — 90M+
- Year 3 · Global
- The complaint repeats in Japan, Korea and Brazil: “ten years of study, still can’t follow a film”
$60B+
language learning, annual
~$10B
translation services
6–9M
reachable users today
130M+
Turkic-speaking expansion
We do not claim the whole language-learning market as addressable. The honest framing is narrower: the paying segment we can reach in the first two years is diaspora and business users in Central Asia, and that segment alone supports a substantial company before any global step.
Start where you are strongest. Expand along the same complaint.
10 — Business model
Translation brings them in, learning keeps them
Nobody subscribes to something they use four times a month.
| Tier | Contents | Role |
|---|---|---|
| Free | Limited daily translations, core registers | Habit and trust |
| Pro | Unlimited translation, 12 registers, files, poetry, image and video translation, history, personal glossary, learning module | Primary revenue |
| B2B | Dubbing and subtitling studios, team accounts, licences for schools and universities | High ability to pay, short sales cycle |
The pricing logic follows directly from chapter 06. Translation alone is a need-driven utility: people arrive when something needs translating, which makes a subscription hard to justify. Learning is a daily need. The learning layer is therefore not a cost centre — it is the basis of the subscription.
Cost control
- —Short prompts route to a fast, cheap model; literary and long-form route to a strong one
- —Repeated and near-identical requests are served from cache
- —Cultural profiles reduce token overhead, because the instruction is compiled rather than re-explained
- —Result: unit cost per active user stays largely independent of user growth
11 — Risks
What could go wrong
Four risks we are asked about, answered without spin.
- Model vendors raise prices
- Routing and caching already isolate us; profiles and post-check are vendor-neutral, so a cheaper model can be swapped in without product change
- A global player adds register control
- They would ship it universally, not deeply. Our defence is per-language cultural depth and the behavioural dataset, neither of which arrives with a feature launch
- Users do not pay for learning
- This is the real risk, and it is why the next milestone is a measured Pro conversion rate rather than more users. B2B licensing is the hedge: schools and studios pay per seat regardless of consumer habit
- Small home market
- Uzbekistan funds the product; the diaspora and the Turkic world fund the company. Expansion needs no new thesis, only new profiles
The risk we take seriously is habit, not competition.
12 — Team and the ask
Who is building this, and what we need
A team that shipped 26 languages with no funding, asking for the layer that compounds.
- Samar Saidov — Founder & CEO
- Entrepreneur and startup builder. Lived the problem before building the product
- To'rabek Yo'ldoshev — CTO
- Software engineer. Owns the pipeline, routing and post-check layer
- Majitov Zuxriddin — Backend
- Infrastructure, data storage, Telegram and platform surfaces
Use of funds
- 40% — Learning module
- Turning translation history into personal lessons; the layer that creates daily use
- 30% — Keyboard and extension
- Mobile keyboard and browser extension, so Lingo works inside every app
- 20% — Quality and living language
- Linguists for cultural profiles, weekly slang and idiom updates, evaluation harness
- 10% — Infrastructure and AI cost
- Serving, caching and model spend during growth
Twelve months from now
- 0110 000 active users, grown mostly through the keyboard and Telegram
- 02Pro launched, with a measured conversion rate and a real price point
- 03First B2B customers: a dubbing studio and an educational institution
- 04Unit economics measured, not modelled
Keep translating, and one day the translator stops being necessary.
That last line is the ambition, and it is also the business model. A product that shortens its own necessity earns a habit on the way there — and habits, not translations, are what compound.