ClaroSite — bilingual job-site interpreter for home-service contractors

1. One-liner

Turns the on-site estimate conversation between an English-speaking tech and a Spanish-speaking homeowner into a translated, signed record — spoken live, no human interpreter.

2. Trend signal — why now?

Three things moved in the last 90 days, and they point at the same place.

The feasibility unlock is fresh and specific. In May 2026 OpenAI shipped GPT-Realtime-Translate — live speech-to-speech translation across 70 input languages into 13 output languages, priced at $0.034/min — alongside GPT-Realtime-Whisper streaming transcription at $0.017/min. Real-time, low-latency, two-way voice translation just dropped below a nickel a minute. Eighteen months ago this was a $900 hybrid-interpreter session; today it’s an API call.

The demand is a demographic fact, not a hunch. ~25.6M US residents speak English “less than very well,” and Spanish-only LEP alone is ~16M (AMS Resources, language-access statistics 2026). In California, ~44% of households speak a non-English language at home. Meanwhile the on-demand interpreter incumbents (LanguageLine) charge $3.95/min audio, $4.95/min video (ConsumerAffairs / LanguageLine) — a price no plumber pays for a driveway estimate, so today they just muddle through with Google Translate or lose the job.

The money is moving. The US field-service-management software market is $3.1B in 2026 and SMB adoption is a named growth driver (IBISWorld, FSM software 2026). Yet the two category leaders — ServiceTitan and Housecall Pro — ship no real-time translation feature as of mid-2026. The wallet is already open for job-site software; nobody has put translation in it.

Provenance:

• Signal 1 (Demand): 25.6M US LEP residents, 16M Spanish LEP; interpreter incumbents charge $3.95–4.95/min — a price SMB trades won’t pay per estimate — accessmultilingual.com / languageline.com — 2026-07-25
• Signal 2 (Feasibility): GPT-Realtime-Translate (70→13 langs, $0.034/min) + Realtime-Whisper ($0.017/min) shipped May 2026 — openai.com — 2026-07-25
• Signal 3 (Economic): US FSM software market $3.1B in 2026, SMB-led growth; ServiceTitan/Housecall Pro ship no translation feature — ibisworld.com — 2026-07-25 Category: Tech-unlock

3. The opportunity

The gap isn’t “translate a conversation” — Google Translate does that for free, badly, and everyone knows it. The gap is the estimate-and-approval moment: a tech stands in a kitchen, quotes $2,400 to replace a water heater, the homeowner nods without fully understanding the scope or the exclusions, signs, and then — three days later — disputes the bill, refuses the change order, or chargebacks the card because “that’s not what I agreed to.” Language-barrier jobs have higher callback and dispute rates precisely because nobody has a shared record of what was actually agreed.

Two incumbents leave this on the table:

• Interpreter lines (LanguageLine et al.) are priced for hospitals, not driveways — $4–5/min, dial-a-human, no artifact. A tech is not calling an interpreter to explain a capacitor.
• FSM platforms (ServiceTitan, Housecall Pro) own the estimate/invoice/e-signature workflow but have zero language layer. The tech types the estimate in English; the homeowner signs an English form they can’t read.

ClaroSite sits exactly on that seam: it translates the spoken estimate walkthrough live, and — this is the load-bearing part — it produces a bilingual, timestamped, e-signed record of what was scoped and approved, in both languages, that the contractor keeps. It’s not a translate button. It’s a dispute-proof, understood-and-agreed artifact that happens to be bilingual.

4. Target market

• Primary customer: Owner-operators and small crews (1–15 techs) in the residential trades — HVAC, plumbing, electrical, pest, appliance repair, restoration — operating in high-LEP metros (SoCal, Texas triangle, Florida, Chicago, NY/NJ). Revenue $300K–$5M/yr. These are Housecall Pro / Jobber customers, not enterprise ServiceTitan shops.
• Why they buy (their pain): “Half my calls in this zip code are Spanish-only. I lose the job to the bilingual outfit down the street, or I win it and eat a callback because grandma didn’t understand the tech, or I get a chargeback I can’t fight because the signed form’s in English.” Language-barrier jobs cost them on three fronts: lost bookings, rework, and undefendable disputes.
• Rough TAM reasoning: There are ~200K+ residential trade businesses in the US in the 1–15 tech band. Conservatively, 30–40% operate in metros where Spanish-speaking homeowners are a routine part of the book — call it 60–80K businesses with real, recurring pain. At $79/mo that’s a ~$60–75M SAM before expanding to construction/property-mgmt/adjacent LEP languages.
• Why now for them: The LEP homeowner share keeps climbing, bilingual staff are expensive and get poached, and their competitors are starting to advertise “hablamos español.” The under-$0.05/min translation cost means, for the first time, a solo operator can offer it without hiring a bilingual CSR.

5. Product sketch (MVP)

• One-tap “Interpreter” mode in a phone/tablet app: tech and homeowner speak naturally, ClaroSite translates two-way out loud in near-real-time (English↔Spanish at launch).
• Trade-tuned glossary so “condenser coil,” “P-trap,” “GFCI,” “panel upgrade” translate correctly — not the generic-translate mush contractors already distrust.
• Live estimate capture: as the tech quotes line items, ClaroSite structures them into a bilingual estimate on screen the homeowner can actually read in Spanish.
• Bilingual e-signature: homeowner signs an approval that shows the scope, price, and exclusions in their language and English side-by-side — one signed artifact, two languages.
• Recorded, timestamped session (with consent capture) stored as the proof-of-agreement record, retrievable if a dispute or chargeback hits later.
• Post-visit summary auto-sent to the homeowner via SMS/WhatsApp in Spanish: what was done, what’s next, what it cost.
• Works offline-degraded: if signal is weak in a crawlspace, it queues audio and reconciles the transcript/translation when back online.

6. AI angle — what’s load-bearing

Remove the AI and there is no product — you’d be back to a $5/min human on speakerphone or a monolingual paper form. Three AI jobs are doing real work:

1. Real-time speech translation (Realtime-Translate) is the core interaction — without sub-second, natural two-way voice, a tech won’t use it in a live conversation.
2. Trade-domain accuracy layer: raw translation mangles technical terms; a glossary + light correction model on top is what makes contractors trust it over the free tools they already rejected. This is the wedge that separates ClaroSite from “just use Google Translate.”
3. Conversation → structured bilingual estimate: extracting line items, prices, and exclusions from a spoken walkthrough and rendering them as a signable bilingual document is pure LLM structuring work. That artifact is the defensible output.

7. Localization angle (if any)

The whole product is a localization play, inverted — it localizes the US contractor’s workflow to their non-English customers. English↔Spanish is the launch beachhead (16M Spanish LEP). Expansion languages are demand-ranked: Chinese, Vietnamese, Tagalog, Haitian Creole, Arabic — all covered by the 70-language input support, so adding a language is a glossary + go-to-market task, not a rebuild. WhatsApp/SMS for the post-visit summary matches how these homeowners actually communicate. This is a US-first play; the same shape ports to any high-immigration service economy (Gulf states, Western Europe) later.

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

• Pricing: $79/mo per business for solo/small (unlimited interpreter sessions, fair-use cap), $149/mo for crews up to 8 techs, usage overage above the cap. Translation COGS is ~$0.05/min — a 15-min estimate costs ~$0.75 to serve, so gross margins are healthy even at $79.
• ACV: ~$1,100/yr blended.
• Rough math to $1M ARR: ~900 businesses × ~$92/mo avg × 12 = ~$1M. Realistic inside 18 months in Spanish-heavy metros.
• Rough math to $5M ARR: ~4,500 businesses, OR ~2,500 businesses + a per-signed-estimate transaction fee + 2–3 expansion languages lifting ACV toward ~$1,800. Requires becoming the default “hablamos español” layer for the Housecall Pro/Jobber long tail.
• Expansion path: more techs (seat expansion), more languages (per-language add-on), per-artifact fee on high-value signed estimates, and — the real prize — a Housecall Pro / Jobber marketplace integration that makes ClaroSite the embedded translation layer inside the FSM workflow.

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

• Scrape the “hablamos español” gap. Pull HVAC/plumbing/electrical businesses in 15 high-LEP zip clusters (LA, Houston, Miami, Phoenix, Chicago) from Google Maps/Yelp. Segment into (a) those already advertising Spanish service and (b) those not. Cold-email/SMS both with a 40-second demo video of a translated estimate walkthrough. Pitch (a) on dispute-proof records, (b) on “stop losing Spanish-speaking jobs.” Target 3–5% reply.
• Ride the FSM communities. Housecall Pro and Jobber have large, active Facebook groups and subreddits (r/HVAC, r/Plumbing, r/smallbusiness) where “how do you handle Spanish customers?” is a recurring thread. Show up with a genuinely useful answer and a free trial link, not a pitch.
• Bilingual-tech referral loop. The bilingual techs who currently are the workaround are the best evangelists — they hate being pulled off jobs to translate for the crew. Give them a referral kickback.
• Trade-show + supply-house flyering. Local HVAC/plumbing supply houses in Spanish-heavy metros are where owner-operators physically show up weekly. A counter flyer + QR demo converts better than any ad.
• Regional trade associations (state HVAC/plumbing contractor associations) for a lightweight partner/discount deal — instant credibility with the exact ICP.

10. Build complexity — justification

Medium. The hard parts are off-the-shelf: real-time translation and streaming transcription are now single API calls with published latency/pricing. The custom work is the trade glossary + correction layer, the conversation-to-bilingual-estimate structuring, the mobile app with degraded-connectivity handling (crawlspaces and mechanical rooms have bad signal), and consent/recording capture done cleanly. A technical founder plus one mobile/full-stack builder ships a credible v1 in ~10–14 weeks. Not a weekend project (audio UX and offline resilience take real care), but nowhere near research-grade.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Consumer-facing translation + record-keeping. Must handle two-party recording consent per state (get consent in-app) and avoid claiming certified/legal-interpreter status. No licensure needed.
Ethical — no harm / dark patterns	✅	Improves comprehension for LEP homeowners — net positive. Guardrail: never position as a substitute for a certified interpreter in medical/legal contexts.
Market exists (evidence above)	✅	16M Spanish LEP, $3.1B FSM market, interpreter lines already monetizing the pain at $4–5/min.
1–5 person team can build this	✅	2 builders, ~10–14 weeks to v1.
Launchable with <$50K / ₹40L	✅	Off-the-shelf APIs, no hardware, no data acquisition.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Real, recurring pain (lost jobs, callbacks, disputes) but felt per-job, not hair-on-fire daily. Bilingual competitors and workarounds exist, so switching isn’t automatic.
Demand evidence	15	12/15	Hard demographic + incumbent-pricing signals; interpreter lines prove willingness to pay for the underlying need. Docked for thin direct evidence that trades specifically will pay for a translation SaaS (adjacent, not proven).
Build feasibility	15	11/15	Core is API-level, but real-time audio UX + offline resilience + estimate structuring is genuine engineering. ~10–14 weeks, not 4.
Distribution clarity	15	11/15	Named channels (scraped lists, FSM communities, supply houses) with plausible conversion. Cold outreach to owner-operators is workable but not a 2-week slam-dunk.
Revenue mechanics	15	12/15	Clean pricing benchmarked below interpreter cost, fat margins (COGS ~$0.05/min), clear customer count to $1M. ACV modest.
Time to first revenue	10	7/10	Trial-to-paid inside 4–8 weeks once v1 ships; SMB self-serve, no long sales cycle.
Defensibility	10	5/10	The translation is a commodity API; moat is the trade glossary, the signed-artifact workflow lock-in, and (later) FSM integration. An FSM incumbent could add this — that’s the real risk.
Total	100	73/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (real-time audio + mobile + offline), sales-heavy (owner-operator cold outreach and supply-house/association legwork is the growth engine, not organic).

Key assumptions to validate (3–5)

1. Assumption: Owner-operators will pay ~$79/mo for translation when a bilingual competitor is their current alternative. How to test: 30 cold demos to HVAC/plumbing owners in LA/Houston; measure how many pre-commit or start a paid trial.
2. Assumption: The trade-tuned glossary makes translation trustworthy enough that techs use it live instead of abandoning it like Google Translate. How to test: Ride along on 10 real estimate visits; measure tech confidence and how often they fall back to gestures/English.
3. Assumption: The bilingual signed record actually reduces disputes/chargebacks (the ROI story). How to test: Pilot with 15 businesses for 60 days; compare dispute/callback rate on translated vs. non-translated jobs.
4. Assumption: ServiceTitan/Housecall Pro won’t ship a native translation layer before you reach escape velocity. How to test: Monitor their release notes and roadmap chatter; move fast on the workflow/artifact lock-in they can’t trivially copy.

Risk flags

1. Platform dependency: Core translation is a single-vendor API (OpenAI Realtime). Pricing or availability shifts hit COGS directly. Mitigate by keeping the app model-agnostic (Azure/Google realtime as fallbacks).
2. Incumbent-eats-feature: The FSM giants own the estimate/e-sign workflow; if one bolts on translation, the standalone thesis weakens. The defense is depth (trade glossary, artifact, multi-language) and speed — and ideally becoming their embedded layer via partnership.
3. Commodity translation: The raw capability is cheap and copyable. If ClaroSite is just a translate button, first cheap clone wins. The whole bet rides on the signed-artifact workflow being the product, not the translation.
4. Liability positioning: Must never drift into medical/legal interpretation where certification and error liability are real. Stay in the home-services scope-and-estimate lane.

14. Structured verdict

Score:                  73/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder (real-time audio/mobile) + a scrappy SMB-sales co-founder; trade domain advisor a strong plus
Time to revenue:        8–12 weeks (v1 ~10–14 weeks, paid trials shortly after)
Capital to launch:      ₹4–8 lakh ($5–10K) — API credits + app dev tooling, no hardware
Top 3 assumptions to validate first:
  1. Owners pay ~$79/mo vs. their bilingual-competitor alternative — 30 cold demos, measure paid-trial starts
  2. Trade glossary is trustworthy enough for live use — 10 ride-alongs, measure fallback rate
  3. Bilingual signed record measurably cuts disputes — 15-business 60-day pilot, compare dispute rates
Kill criteria:
  - Abandon if <10% of 50 cold-outreach owner-operators start a paid trial
  - Abandon if techs abandon live translation mid-visit >30% of the time in ride-alongs (trust failure)
  - Abandon if ServiceTitan or Housecall Pro ships an equivalent native translation+bilingual-signature layer before your v1 has 100 paying accounts

15. Next step — 1-week validation sprint

• Day 1–2: Scrape 300 HVAC/plumbing/electrical businesses across 5 high-LEP zip clusters. Build a 40-second screen-recorded demo of a translated estimate walkthrough → bilingual signed approval (mock the UI, real translation API in the loop).
• Day 3–4: Cold email + SMS the list. Book 15+ discovery calls / ride-along requests. On each call, run the three price/trust probes: would they pay $79/mo, do they trust it enough to use live, do disputes actually cost them.
• Day 5: Decide on a falsifiable bar — go only if ≥8 of 15 owners say they’d start a paid trial AND ≥5 confirm they currently lose jobs or eat callbacks specifically over the Spanish barrier. Below that, the pain is real but not paid-for — shelve or re-cut toward property management / construction crews.