TradeTongue — on-site interpreter for home-service technicians

1. One-liner

Lets a monolingual technician close a Spanish-speaking homeowner in real time, and leaves a signed bilingual record of what was agreed.

2. Trend signal — why now?

Two things collided in 2026. First, speech-to-speech translation crossed the usability line: production APIs now do two-way spoken translation with sub-one-second round-trip latency and the speaker’s own voice preserved (Palabra.ai advertises <1s and speaker voice auto-cloning; Soniox claims sub-200ms STT across 3,600 language pairs; ElevenLabs Dubbing v2 and OpenAI’s GPT-Realtime-Translate hit conversational latency). A year ago this was a robotic, three-second-lag toy you’d never hand to a paying customer. Now it’s fast enough to hold a kitchen-table sales conversation.

Second, the pain got loud and expensive. Home-service trades serve neighborhoods where a large share of homeowners prefer Spanish, and the industry openly says it’s leaking money: “When a Spanish-speaking customer calls and encounters a language barrier, research shows they’re likely to hang up and call someone else” and “the problem is often silent — no complaint form captures customers you never converted due to language barriers.” The workaround — hire bilingual staff — carries a real wage premium: bilingual service technicians average $35.81/hr vs monolingual peers, and job boards are full of “bilingual technician NOW HIRING” listings. The other workaround, a per-minute human interpreter line (LanguageLine at $3.95/min audio, no monthly minimum), is clumsy on a doorstep and leaves no usable record.

Provenance:

• Signal 1 (Demand): Home-service contractors lose jobs to language barriers — customers hang up and call someone else; the loss is silent and uncaptured — gosameday.com/post/spanish-speaking-ai-receptionists-a-must-have-for-home-service-contractors and ainora.lt/blog/multilingual-business-communication-statistics-2026 — 2026-07-22
• Signal 2 (Feasibility): Two-way speech-to-speech translation with <1s latency and preserved speaker voice is now a production API — palabra.ai and soniox.com and ElevenLabs Dubbing v2 / OpenAI GPT-Realtime-Translate (openai.com/index/advancing-voice-intelligence-with-new-models-in-the-api) — 2026-07-22
• Signal 3 (Economic): Bilingual service techs earn a wage premium (~$35.81/hr) and human phone interpreting runs $1.50–$3.95/min; medical/field interpreting market $7.8B (2025) → $16.2B (2034) — ziprecruiter.com/Jobs/Bilingual-Service-Technician and languageline.com/interpreting/self-service and dataintelo.com/report/medical-interpreter-services-market — 2026-07-22 Category: Tech-unlock

3. The opportunity

The phone-booking side of this problem is already crowded. “Spanish-speaking AI receptionist” is a live, contested category (Sameday, Dapta, and every bilingual answering service) — the Spanish-speaking customer who calls now gets answered. And the paperwork side is partly handled too: FieldPulse ships native Spanish in its mobile app at $59/mo, Housecall Pro and ServiceTitan render Spanish invoices and UI. So the office and the documents are covered.

What nobody owns is the 90 seconds that decide the job: the technician standing in the customer’s kitchen, needing to say “your compressor is failing because the capacitor blew — here are three options, this one’s $1,800” to a homeowner who only speaks Spanish. Right now that tech either (a) mangles it through Google Translate typed one sentence at a time with no trust and no record, (b) calls a $3.95/min interpreter line and hands a stranger their phone while the customer waits awkwardly, or (c) doesn’t get hired because the company had to send a bilingual tech and none was free. The Spanish app UI doesn’t help — a pre-translated invoice label doesn’t explain a diagnosis or handle the homeowner’s follow-up question.

The 10× play: purpose-build the spoken, two-way, on-site moment as flat-rate SaaS on the tech’s own phone — and, critically, drop out a signed bilingual summary of what was diagnosed, quoted, and approved. That last part is the wedge that turns a translation gimmick into something a contractor pays for every month: it kills the “I didn’t understand what I agreed to” dispute, which is the #1 source of home-service payment fights.

4. Target market

• Primary customer: Owner-operators and 3–30-truck HVAC, plumbing, and electrical shops in US metros with large Spanish-speaking populations (TX, CA, FL, AZ, NV, greater NYC/NJ) whose field techs are mostly monolingual English.
• Why they buy: In their words — they “lose the job” when they can’t send a bilingual tech, they eat chargebacks and CSLB-style complaints when a customer claims they never understood the estimate, and they’re paying a wage premium or a per-minute interpreter to paper over it. They already feel this every week in specific ZIP codes.
• Rough TAM reasoning: ~120,000 HVAC firms, ~130,000 plumbing firms, ~70,000 electrical firms in the US (Census/IBISWorld order of magnitude). Conservatively, 15–20% operate in heavily Spanish-preferring markets and would value this → 45,000–65,000 target shops. At a few hundred dollars/mo, a low-single-digit-percent penetration clears the $5M ARR ceiling.
• Why now for them: The tech to do it well only arrived this year, the labor market makes bilingual hires scarce and pricey, and their own field-service platforms have trained them to expect mobile tools — but none of those platforms do live spoken interpretation.

5. Product sketch (MVP)

• Push-to-talk two-way interpreter on the tech’s phone: tech speaks English, customer hears Spanish in a natural voice within ~1 second, and vice versa. Optional speakerphone “conference” mode so both hear both languages.
• Trades vocabulary tuning so “capacitor,” “condensate line,” “panel upgrade,” “P-trap” translate correctly instead of literally.
• Auto-generated bilingual job summary: at the end of the visit, a clean English + Spanish recap of the diagnosis, the options presented, the price quoted, and what the customer approved.
• On-device signature capture on that bilingual summary, timestamped and emailed/texted to the homeowner — the dispute-proof record.
• Quote read-back: tech types or dictates the line-item price; app reads it aloud in Spanish and confirms the customer heard the number.
• Works offline-degraded: if signal is weak in a basement or attic, falls back to slower turn-based translation rather than dying.
• Call-log for the office: every visit’s transcript + summary syncs to a simple web dashboard the owner can search when a dispute or callback comes in.

6. AI angle — what’s load-bearing

Remove the AI and there is no product — it’s just Google Translate plus a PDF. The load-bearing AI is (1) real-time speech-to-speech translation fast and natural enough that a nervous homeowner trusts a $1,800 quote delivered through it, (2) trades-domain terminology handling so the translation doesn’t embarrass the tech, and (3) LLM summarization that turns a messy spoken sales conversation into a clean, accurate, bilingual “here’s what we agreed” record. The summary-and-record layer is where the AI does work no human interpreter line even offers — LanguageLine hands you an interpreter, not a signed bilingual agreement.

7. Localization angle (if any)

This is a localization play, inverted: the product’s whole reason to exist is the US English↔Spanish gap inside the domestic home-services market. English↔Spanish is v1. Fast-follow expansions: English↔Vietnamese and English↔Mandarin (nail/beauty and restaurant-adjacent service trades), English↔Haitian Creole (Florida), and Portuguese for the Brazilian-heavy Northeast contractor pockets. The signed-bilingual-record format localizes cleanly to each. No India/LatAm angle here — the money and the pain are in US metros.

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

• Pricing: Flat SaaS, not per-minute (that’s the whole pitch against LanguageLine). ~$39/mo per active tech seat, or shop plans: $99/mo up to 3 techs, $249/mo up to 10, $499/mo up to 25. Usage is bundled — an owner budgets one predictable number instead of watching a per-minute meter.
• ACV: Blended ~$2,000–$3,000/yr per shop (most land on the 3–10 tech tiers).
• Rough math to $1M ARR: ~400 shops × ~$210/mo avg × 12 ≈ $1.0M.
• Rough math to $5M ARR: ~1,700–2,000 shops, or fewer shops at higher seat counts plus a per-visit “premium summary/e-sign” add-on. Well inside the 45K–65K target-shop TAM.
• Expansion path: seats grow as the shop grows; add languages as paid packs; add a “review-my-disputes” tier where the office dashboard becomes a lightweight dispute-defense record system; eventually an API/embed so field-service platforms license the interpreter layer.

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

• Ride the existing “Spanish for contractors” demand. People already buy Survival Spanish books and “Spanish for HVAC” courses — those buyers are a pre-qualified list. Sponsor/insert into those channels and the trade Spanish-vocabulary newsletters; the reader has literally self-identified as feeling this pain.
• Trade Facebook groups and forums. HVAC-Talk, r/HVAC, r/Plumbing, r/electricians, and the big regional contractor Facebook groups have recurring “how do you deal with Spanish-speaking customers” threads. Show up with a 60-second phone demo video (tech quotes a repair, customer signs a bilingual summary). These threads convert because the pain is acknowledged and unsolved.
• Local-market ground game. Pick one metro (Houston or Phoenix), pull the licensed-contractor list from the state board, and run a two-week outreach sprint: personalized demo texts to 500 shops in Spanish-heavy ZIPs, “try it on your next job, free for 30 days.” A per-visit ROI story (“one saved job pays for a year”) closes owner-operators fast.
• Ride-along referrals. Techs talk. Get 10 techs at one shop using it, they tell their buddies at other shops. Field trades are a tight word-of-mouth network.
• Supply-house counters. HVAC/plumbing supply distributors (where every tech shows up weekly) are a physical distribution surface — counter cards, rep partnerships.

10. Build complexity — justification

Medium. The hard parts — real-time speech-to-speech translation and voice synthesis — are now off-the-shelf APIs (Palabra/Soniox/ElevenLabs/OpenAI), so this is integration and UX, not model research. The real work is a rock-solid mobile app that handles bad connectivity in basements and attics, the trades-terminology tuning layer, and the bilingual-summary + e-signature record flow. A technical pair can ship a credible v1 in roughly 10–14 weeks; the terminology accuracy and offline-degraded behavior are what take the extra polish.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Non-certified everyday interpretation is unregulated; we explicitly stay out of legal/medical certified settings.
Ethical — no harm / dark patterns	✅	The bilingual signed record makes the customer more informed, not less.
Market exists (evidence above)	✅	Bilingual-tech wage premium + interpreter spend + hang-up losses are documented.
1–5 person team can build this	✅	Integration-heavy, off-the-shelf AI, standard mobile stack.
Launchable with <$50K / ₹40L	✅	Main cost is per-minute translation API usage, covered by subscription revenue at any real scale.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Real, recurring, money-losing — but felt acutely only in specific markets, and many shops have limped along with Google Translate. Not universal hair-on-fire.
Demand evidence	15	12/15	Strong indirect signals (wage premium, interpreter spend, hang-up losses, adjacent AI-receptionist category thriving). Weaker on direct “I’d pay for exactly this” verbatims.
Build feasibility	15	10/15	Core AI is off-the-shelf; the mobile reliability + offline behavior + terminology tuning is genuine 10–14 week work.
Distribution clarity	15	11/15	Named channels (trade forums, contractor lists, Spanish-for-trades buyers, supply houses) with plausible conversion, but no single guaranteed-cheap firehose.
Revenue mechanics	15	12/15	Flat pricing benchmarked against a per-minute incumbent and a wage premium; ACV and customer counts to $1M are modest and credible.
Time to first revenue	10	7/10	30-day free trial → paid; owner-operators decide fast, but a working mobile MVP must exist first. Revenue in ~6–8 weeks post-launch.
Defensibility	10	5/10	Translation APIs are commoditized. Moat is the trades-record workflow lock-in and accumulated terminology/dispute data — soft, copyable, but head-start-defensible.
Total	100	72/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (real-time mobile audio + API orchestration) · sales-heavy (owner-operator outreach and ground game close the first 100)

Key assumptions to validate (3–5)

1. Assumption: Homeowners will trust a $1,000+ quote delivered through machine interpretation enough to sign. How to test: Run 20 live ride-alongs with a rough prototype in one metro; measure close rate and homeowner comfort vs the tech’s usual method.
2. Assumption: Shop owners will pay flat SaaS rather than keep using free Google Translate. How to test: 40 owner interviews + a fake-door pricing page; look for >15% “start trial” intent at the $99–$249 tiers.
3. Assumption: Current translation-API latency and accuracy on trades vocabulary is good enough on a phone in a real basement, not a demo room. How to test: Field-test the top 3 APIs across 30 real service calls; measure mistranslation rate on domain terms and dropped-call behavior.
4. Assumption: The bilingual signed record actually reduces disputes/chargebacks (the retention hook). How to test: Track dispute rate on jobs closed with vs without the record across pilot shops over 60 days.

Risk flags

1. Platform dependency: Reliant on third-party speech-to-speech APIs whose pricing/availability could shift. Mitigate by staying API-agnostic across 2–3 providers.
2. Incumbent absorption: ServiceTitan/Housecall Pro/FieldPulse could bolt live interpretation onto their Spanish UI. This is the biggest threat — the defensibility is a head start plus the dispute-record workflow, not a technical moat.
3. Market timing / trust: Machine interpretation of a high-dollar sales conversation may feel too risky to some homeowners for another year; adoption could lag the tech.
4. Accuracy liability: A mistranslated quote that leads to a bad job could create a “the app lied to me” liability narrative. Mitigate with the signed bilingual written record as the source of truth over the spoken exchange.

14. Structured verdict

Score:                  72/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can ship reliable mobile audio, paired with someone willing to run a metro ground-game close
Time to revenue:        ~6–8 weeks after a working mobile MVP (30-day trial → paid)
Capital to launch:      $15–30K (mostly translation-API usage + one metro pilot)
Top 3 assumptions to validate first:
  1. Homeowners sign high-dollar quotes delivered via machine interpretation — 20 live ride-alongs, measure close rate
  2. Owners pay flat SaaS over free Google Translate — 40 interviews + fake-door pricing, >15% trial intent
  3. Trades-term translation accuracy holds up in real field conditions — field-test top 3 APIs on 30 real calls
Kill criteria:
  - Abandon if <30% of pilot ride-alongs close at or above the tech's normal close rate
  - Abandon if domain-term mistranslation rate exceeds ~5% on real service calls after tuning
  - Abandon if a major field-service platform ships an equivalent live-interpreter feature before your v1

15. Next step — 1-week validation sprint

• Day 1–2: Wire the top real-time speech-to-speech API (Palabra or Soniox) into a bare push-to-talk phone screen. No polish — just English↔Spanish that works.
• Day 3–4: Get it into the hands of 3 friendly HVAC/plumbing shops in one Spanish-heavy metro. Ride along on 8–12 real service calls. Watch whether techs use it and whether homeowners engage with it or freeze.
• Day 5: Decide go / no-go on one falsifiable metric: did ≥50% of the tech-run calls result in the homeowner comfortably completing the conversation and agreeing to next steps through the app — versus the tech giving up and switching back to gestures or a bilingual coworker? If yes, build the summary/record layer next. If no, the trust barrier is real and the idea waits.