SourceReady — file-prep studio for translation freelancers & agencies

1. One-liner

Turns a scanned or non-editable source document into a clean, layout-matched, translation-ready file in minutes instead of an hour of DTP.

2. Trend signal — why now?

The translation industry has a boring, expensive, universally-hated chore: prepping a source file so it can actually be translated. When a client sends a clean .docx, everyone’s happy — the CAT tool counts words, the translator works, done. When the client sends a scanned PDF, a photo of a document, a flattened export, or a locked InDesign PDF — which is constantly — someone has to rebuild that file into editable, layout-faithful text before any translation can start. That’s Desktop Publishing (DTP), and the industry openly charges $25–$90 per page for it, or bakes a 20–30% surcharge into the quote for non-editable source.

What changed in the last 12 months: vision models good enough to read a messy scan, reconstruct its tables and columns, and re-emit an editable, layout-preserving file got cheap and reliable. The DTP task — the exact task agencies pay humans $25–90/page for — is now largely automatable end-to-end. It wasn’t 18 months ago; OCR gave you a text blob, not a usable layout.

Provenance:

• Signal 1 (Demand): Agencies openly monetize the pain — DTP charged at “$25–$75 per page” / “$30–90 per page,” and non-editable PDFs trigger a “20% to 30% surcharge for Desktop Publishing and manual text extraction.” — https://translators-usa.com/how-much-does-document-translation-cost-2026-pricing-guide/ & https://www.bluente.com/blog/translation-pricing-models-explained — 2026-07-21
• Signal 2 (Feasibility): “DTP surcharges apply for non-editable formats such as scanned PDFs, InDesign, or AutoCAD files” — the whole “multilingual DTP” service line exists precisely because rebuilding these files is manual today; vision+layout models now collapse it. — https://www.betranslated.com/translation-services/multilingual-dtp/ — 2026-07-21
• Signal 3 (Economic): Scoping/quoting a job “means getting a precise read on the project’s scope, from word counts… to how much cultural tweaking is needed” and CAT-tool file prep is a paid, staffed step (“Localization engineers/DTP specialists prepare files, handle complex formats… fix layout”). Money and headcount already sit on this task. — https://doctorelearning.com/blog/translation-project-management/ — 2026-07-21 Category: Workflow automation

3. The opportunity

The gap is the pre-translation prep step, and it’s wedged between two worlds that both do it badly:

• Freelancers do it by hand — retyping a scan into Word, rebuilding a table, guessing a word count — or they turn the job away because prepping a messy 30-page PDF eats their evening for no billable gain. Either way they lose money.
• Small agencies either eat DTP as an internal cost (a staffed “localization engineer” step) or outsource it to per-page DTP shops at $25–90/page. That surcharge is a margin leak and a customer-friction point — clients argue about why the quote jumped.

The incumbents are the wrong shape. CAT tools (Trados, memoQ, Phrase) assume you already have a clean, editable file — they analyze and count, they don’t rebuild a scan. DTP service shops are humans billing per page. Generic OCR gives you a text dump with the layout destroyed, which is worse than useless when the deliverable must match the original’s tables, forms, and columns.

Nobody sells the boring middle: drop in the ugliest file the client sent, get back a clean, editable, layout-faithful source ready for your CAT tool — plus an accurate word count and a quote line you can defend. That’s a 2-minute job that costs an hour today.

4. Target market

• Primary customer: (a) Full-time freelance translators (there are 640K+ globally per industry associations; the working professional subset who handle document work numbers in the low hundreds of thousands) and (b) small translation agencies / LSPs with 2–15 staff who don’t have a dedicated DTP team.
• Why they buy (their words): “The client sent me a scanned PDF and I spent an hour retyping it before I could even start.” / “We add a DTP surcharge but half the time the client walks, so we eat it.” / “I turned down a good job because the file was a mess and prepping it wasn’t worth it.”
• Rough TAM reasoning: ~300K working document translators + tens of thousands of small LSPs. If even 40K pay $19–49/mo, that’s a $9M–$24M ARR ceiling before agency seats. Comfortably a sub-$5M target, not a unicorn — exactly the wallet band this repo hunts.
• Why now for them: Speed and price pressure from MT/AI is squeezing their margins; the non-billable prep hour is the least defensible cost they have. Removing it is pure recovered profit.

5. Product sketch (MVP)

• Drop in any source file — scanned PDF, photo, flattened PDF, locked export — and get back a clean, editable, layout-preserving file (docx/idml-style) ready to load into any CAT tool.
• Accurate word/character count on the reconstructed content, including text trapped in tables, forms, and image captions that a naive count misses.
• A defensible quote line: “38 pages, 9,240 words, non-editable source → recommended prep + rate.” A number the translator can send the client without arguing.
• Table/column fidelity — the thing generic OCR destroys and DTP humans get paid to preserve.
• Reflow-back: paste the translated text and get it re-poured into the original layout, so the deliverable matches the source.
• Batch mode for a multi-file project; a shareable, itemized scope summary for the client.
• Pay-as-you-go page credits for overflow above the monthly plan.

6. AI angle — what’s load-bearing

Remove the AI and there is no product — you’re back to a human retyping a scan. The load-bearing work is: vision-model reading of a degraded/scanned document → structural reconstruction (columns, tables, forms, reading order) → re-emission as an editable, layout-faithful file. That’s the entire DTP task the industry pays $25–90/page for, done by the model. The word-count and quote outputs are downstream of getting the reconstruction right. This is not “OCR with a chatbot bolted on” — plain OCR is exactly the inadequate incumbent, because it drops layout.

7. Localization angle (if any)

N/A as a geographic wedge — this is a global play by nature; translators everywhere hit the same messy-file wall. The one nuance worth exploiting: script and non-Latin layout fidelity (Arabic RTL, CJK vertical/column text, Devanagari). Generic tools mangle these; getting them right is a credibility moat with the exact professionals who’ll evangelize the tool. So the “localization” is in supported scripts, not supported countries.

8. Business model — path to $1M–$5M ARR

• Pricing: Freelancer $19/mo (≈150 pages), Pro $49/mo (≈500 pages), Agency $149/mo (multi-seat + batch). Overflow page credits on top.
• ACV: ~$350 blended (mix of $19 solos and $49–149 agencies).
• Rough math to $1M ARR: ~2,900 paying accounts at $29 blended monthly (500 × $19 + 2,400 × ~$31) ≈ $1M. Very reachable given the population size.
• Rough math to $5M ARR: ~12–14K accounts, or fewer if agency ACV rises via seats + per-page overage. Requires the agency tier to carry weight, which it should once reflow-back is solid.
• Expansion path: solo → agency seats → per-page overage on big projects → an API tier so mid-size LSPs pipe prep into their existing workflow. The API tier is where ACV can 5–10×.

9. Go-to-market wedge — first 100 customers

• The ProZ / Translators Café forums and the r/TranslationStudies + r/translator subreddits are where these people vent about exactly this pain daily. Post a genuinely useful “drop your ugliest file, get it back clean” free-tier link. This is a warm, self-identifying audience.
• Cold outreach to small LSPs: scrape the “multilingual DTP” service pages of small agencies (they advertise the pain), send a 60-second Loom turning one of their sample scans into a clean file. Expect 3–5% reply among firms already paying humans for this.
• Translator YouTube / newsletter creators (there’s a healthy niche of “freelance translator business” content creators) — the “stop losing an hour per messy file” hook is native to their audience; affiliate them.
• Free single-file tier as the acquisition engine: the “before/after” of a rebuilt scan is instantly obvious and screenshot-shareable, which drives organic word-of-mouth in a small, chatty profession.

10. Build complexity — justification

Medium. The vision-model prep pipeline (read → reconstruct layout → emit editable file) is off-the-shelf-model plus real engineering discipline on the reconstruction/reflow — tables and RTL scripts are where it gets gnarly, and reflow-back is the hardest bit. A technical founder with translation-domain input can ship a credible v1 (single-file prep + count + quote) in ~10–14 weeks; reflow-back follows. No custom model training required at v1; no regulatory gate.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Processing documents the user already holds. Handle client-confidential files with clear retention/deletion terms.
Ethical — no harm / dark patterns	✅	Recovers translator margin; no dark pattern.
Market exists (evidence above)	✅	DTP is a monetized, staffed line item industry-wide.
1–5 person team can build this	✅	Solo/pair to v1 in ~3 months.
Launchable with <$50K / ₹40L	✅	Model inference + web app; well under budget.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Real, recurring, monetized pain ($25–90/page). Not hair-on-fire daily for every freelancer, but constant for those who take document work.
Demand evidence	15	11/15	Strong: an entire paid service line (“multilingual DTP”) exists to do this by hand. Docked because direct verbatim complaints were paraphrased from industry sources, not pulled as raw quotes.
Build feasibility	15	11/15	v1 is off-the-shelf models + solid engineering. Table/RTL fidelity and reflow-back are the hard 20%.
Distribution clarity	15	12/15	Self-identifying audience in named forums/subreddits; agencies advertise the exact pain on their own sites. Screenshot-shareable before/after.
Revenue mechanics	15	11/15	Pricing benchmarks against a real $25–90/page cost, so ROI is obvious. Docked on solo-tier churn risk and low ACV until agency/API tiers land.
Time to first revenue	10	8/10	Free-tier → paid conversion can happen within weeks of a working single-file demo.
Defensibility	10	6/10	Soft moat: reconstruction quality on hard scripts + workflow lock-in + a growing library of layout patterns. Copyable, but quality-on-the-hard-cases is a real head start.
Total	100	74/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required — needs someone who can wrangle vision-model reconstruction AND understands what “translation-ready” actually means to a working translator (CAT-tool import cleanliness, segment integrity, layout fidelity).

Key assumptions to validate (3–5)

1. Assumption: Freelancers/agencies will trust an AI-rebuilt file enough to load it into their CAT tool without re-checking every line. How to test: Give 20 working translators 5 messy real-world files each; measure how much manual correction the output still needs and whether they’d pay to skip the prep.
2. Assumption: Reconstruction quality on hard cases (tables, RTL, CJK, poor scans) is good enough to be worth paying for, not “80% and then I fix it anyway.” How to test: Benchmark output against a human DTP shop on 30 hard files; a translator rates each usable / not-usable.
3. Assumption: The quote-line output changes buying behavior (freelancers win or price jobs they’d have declined). How to test: Track whether beta users report taking on messy jobs they’d previously have turned away.
4. Assumption: Solo-tier churn is survivable — people keep needing it monthly, not once. How to test: Cohort usage over 3 months; look for repeat file-prep, not one-and-done.

Risk flags

1. Platform dependency: Reliant on third-party vision-model APIs for the core task; pricing/quality shifts hit unit economics directly. Mitigate by keeping the pipeline model-swappable.
2. Quality cliff: “Almost right” is worthless here — a translator who has to re-verify every table gains nothing. The product lives or dies on the hard-case accuracy, not the easy demo.
3. Commoditization: If a CAT-tool incumbent (Trados/memoQ/Phrase) or a document-AI player ships “import any scan cleanly” as a feature, the standalone wedge narrows. Speed to the agency/API tier and hard-script quality is the defense.

14. Structured verdict

Score:                  74/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder (vision/document AI) with a translation-industry advisor
Time to revenue:        6–10 weeks after a working single-file prep demo
Capital to launch:      ₹4–8 lakh ($5–9K) — mostly inference + web app
Top 3 assumptions to validate first:
  1. Rebuilt files are trusted into CAT tools with minimal re-check — 20-translator, 5-file trial
  2. Hard-case reconstruction (tables/RTL/CJK/bad scans) beats or matches a human DTP shop — 30-file benchmark
  3. The output changes behavior (jobs won/priced that would've been declined) — beta cohort self-report
Kill criteria:
  - Abandon if <60% of beta translators rate the rebuilt hard-case files "usable without significant rework"
  - Abandon if free→paid conversion stays below 3% after 500 free-tier files processed
  - Abandon if a CAT-tool incumbent ships equivalent "clean-import-any-scan" before v1 ships

15. Next step — 1-week validation sprint

• Day 1–2: Collect 40 genuinely messy real source files (scanned PDFs, photos, locked exports, RTL/CJK samples) from 8–10 working translators — the ones they’d normally dread. Run them through a prototype pipeline (off-the-shelf vision model + reconstruction).
• Day 3–4: Put the rebuilt files in front of those translators. Ask one falsifiable question per file: “Would you load this into your CAT tool and start, or would you rebuild it yourself?” Record usable / not-usable and how much correction remained.
• Day 5: Decide. Go if ≥60% of hard-case files are rated “usable without significant rework” AND ≥5 of the translators say they’d pay $19–49/mo to skip the prep. Below that, the quality cliff kills it — no-go.

The result is falsifiable: it’s a usable/not-usable count on real hard files from real translators, not a vibe.