Regional Language Strategy

Strategic Positioning

Regional-language support is a strategic placeholder and platform capability area. AblePro should be language-aware from v1, but language-specific workflows, content, models, and datasets should be developed progressively based on demand, impact, business value, clinician/therapist readiness, partner needs, and quality data availability.

Roadmap

Phase	Language Scope	Positioning
v1 / Initial validation	Kannada	First regional-language validation candidate
v1.x / Expansion candidates	Hindi, Tamil	Prioritized based on market demand, impact, and business value
v2+ / Demand-led expansion	Telugu, Malayalam, Marathi, Bengali, others	Added based on geography, partners, usage, clinician readiness, and data availability
Future IP path	Language-specific models/datasets	Developed only when sufficient reviewed, consent-aligned, quality-controlled data exists

ADB Language Metadata

ADB should capture:

• primary language;
• home language;
• session language;
• observation language;
• parent input language;
• therapist/doctor note language;
• content language;
• report language;
• translation required flag;
• translation/review status;
• language code;
• script;
• dialect or regional variant.

Guardrails

• Regional-language support is not only translation.
• It is part of the speech, communication, content, parent-engagement, and future dataset/IP strategy.
• Do not claim full automatic language-specific diagnosis.
• Do not claim mature AI support for every language from day one.
• Build language-specific models only after reviewed, consent-aligned, quality-controlled data exists.