I Built an AI Agent That Makes Any Landing Page (Next.js App) Multilingual in 3 Minutes

The Problem Nobody Wants to Solve Going multilingual is one of the most commonly requested — and most commonly abandoned — features in software development. Companies know they need it. Users demand it. Global markets require it. Revenue depends on it. But the implementation consistently defeats engineering teams. Why? Because translation is only 10% of the work. The other 90% is orchestration: String externalization — wrapping every hardcoded string in t() functions across hundreds of files Configuration — setting up i18n libraries, locale directories, provider wrappers, config files Translation management — maintaining JSON locale files that drift out of sync with every feature Deployment — creating branches, opening PRs, setting up preview environments to verify the result Coordination — developers, translators, reviewers, and PMs rarely speaking the same language about the problem Retrofitting i18n into an existing codebase costs 3–10x more than building it in from the start. So te