Taking every surface Phases 2 and 3 put in place into other languages, built so Spanish is engineering and every language after it is only translation.
Only 7% of women receive hormone treatment today, and the share is lower still among women who do not read clinical English. Every questionnaire, consent form, and monthly report in Phases 2 and 3 assumes one language.
Kelly and Betty asked whether everything being built can work in other languages. It can, and the cost depends almost entirely on when you ask. Localization retrofitted onto a shipped screen is expensive. Localization designed into the layer underneath every screen is a one-time build.
So Phase 4 buys the machine once, and only the machine. Interface strings, clinical content, documents, and everything outbound, with Spanish shipping as the proof. Live cross-language notes, a second launch language, right-to-left layouts, and the AI translation layer all sit on the scope pages switched off. Turn each one on when a market is real.
Every optional feature is switched on. This is the top of the range.
Priced at the same contracted rates as Phases 2 and 3. Approving the task list locks this number, and it bills across four milestones: half of design before we start, half at design handoff, half of development at kickoff, half at launch.
Design and development, itemized on the scope pages. Project management, CTO oversight, design review, and QA break out separately so nothing is buried in a lump sum.
Every string in the patient app, the practitioner workspace, and the clinic console pulled into one translation layer, with dates, numbers, units, and pluralization handled by locale rather than by hand.
Questionnaires, symptom taxonomy, phenotype descriptions, consent forms, and the monthly report narrative translated by medical linguists and reviewed clinically, because a mistranslated consent form is a liability rather than a bug.
A Spanish-speaking patient writes symptom notes and an English-speaking practitioner reads the chart. Live translation in both directions sits on the scope page as an option, priced on its own.
The monthly report, consent documents, invoices, push notifications, email, and SMS all render in the locale the patient chose, not the locale the system defaulted to at signup.
A managed workflow rather than a spreadsheet: new copy routed to translators, reviewed, versioned, and shipped without a code release, with an AI-assisted first pass where the content is not clinical.
Spanish ships with this phase and proves the machine end to end. Every language after it is translation work and a configuration change, roughly a week each, rather than another project.
Eight weeks covers the base scope and Spanish. Each optional row on the scope pages adds to that, and each language after Spanish runs about a week of translation and review rather than a project.
Kelly and Betty asked whether everything being built can work in other languages. This is the answer, and the timing matters more than the price: the layer is cheapest to build before the clinic surfaces ship, not after. Six moves, 396 hours, eight weeks, with Spanish live at the end of it. Four more features sit on the scope pages switched off, waiting for a market to need them. Open any line for the detail, and tell us where this should sit.
Brian Hammond
VP of Sales, FYC Labs
bhammond@fyclabs.com
fyclabs.com