Everything the clinic needs to be
findable, readable, and bookable
in the patient's language.
DentalPolyglot is the software layer between a Romanian, Hungarian, or Italian clinic and the German, British, Norwegian patients who want their work done there. One paste of an existing clinic URL, eight locales, a patient pipeline from inquiry to boarding pass, and the email cron that gets it done.
Paste a clinic URL.
Have a draft site while the coffee brews.
Claude Opus reads the clinic's existing site, lifts the treatments, team, certifications, and brand colors, then reorders the sections for a conversion funnel a German patient actually reads. The clinic owner edits, nothing else.
Three deep-dives into the public-facing layer.
Each is a deep-dive page with the workflow, the limits, and the receipts. The short version is below.
Source content in the clinic's native language. Mirrored into the patient languages you enable, from a standard library of eight, glossary-locked for clinical terms.
Per-tenant sitemap, hreflang alternates across every enabled locale, JSON-LD Dentist schema. The plumbing a German Google needs to index a Romanian clinic.
Speed, WCAG 2.2 AA accessibility, and multilingual SEO, built to one standard on every page in every language.
Type German. Watch eight languages mirror it.
Glossary-locked, tone-fingerprinted.
The translation pipeline that ships on every clinic page. Same glossary, same tone, same reviewer queue, no matter which tier. Type something on the right and watch the mirror.
- Glossary-aware: Heil- und Kostenplan never becomes "healing plan".
- Tone-locked to warm, professional, calm.
- Reviewer queue: every line passes a native reviewer.
· Start: you review in your dashboard
· Expand: full review pass · Concierge: native translator
The part a website builder
cannot ship for you.
A website brings the inquiry. Everything after that, from the clinic's PDF treatment plan to the patient stepping onto a plane, is what DentalPolyglot does and what Wix, Squarespace, and a translator do not. Six stations, one queue, one inbox.
Clinic uploads their native-language PDF or pastes text. Claude parses findings, treatments, totals, recommended stay.
Token-gated page, no account. Accept / Request changes / Decline. Accept fires the next email automatically.
Calendar picker that respects the recommended stay length, blackouts, closed weekdays, capacity-full days.
Two-month view, three layers: blackout, proposed, confirmed. Side panel for pending windows with Accept and Counter-propose.
T-7 and T-1 to the patient, T-3 and T-1 to the clinic, T+1 follow-up. Each with an .ics that calendar apps deduplicate.
Outbound from the clinic, with typeahead over patients and leads, {first_name} substitution, branded shell, auto-saved draft.
Andrei drops a 4-page PDF treatment plan into the dashboard, written in Romanian. Claude parses it: 6 findings, 4 treatments, total 8,400€, stay 6 nights. He renames the patient (Stefan Müller), confirms the stay length, clicks send. Stefan receives a German PDF, branded with the clinic's logo and not ours, and a respond link.
Stefan clicks Accept on his phone in Munich. The schedule page opens, he picks three week windows. Andrei sees them in his calendar side panel, confirms one. Both sides get an .ics with a stable UID. The T-7 reminder mails itself on the morning of week 5.
One dashboard. Eight destinations.
Nothing where you'd never look.
Three operator-only surfaces, each tenant-scoped, password-protected, and built so the clinic's receptionist can use it on the day they are hired.
Every contact form submission lands here with reply tracking. No spreadsheet, no Outlook rule.
Inquiry trends by category, plan-to-acceptance funnel, reply-time median, and outbound volume. Real data from your clinic's own dashboard, nothing sent to third-party trackers.
Overview, leads, plans, calendar, composer, settings, sent log. Filter by kind and status.
Four screens from the dashboard a clinic actually opens.
Not mockups. The real surface.
What a clinic sees the morning after their first lead arrives. Shot from the seeded demo clinic on the live build.
What the platform does not do, on purpose.
The product decisions a clinic's IT counsel would otherwise ask about, made for them, in the EU.
Patient data never crosses the Atlantic.
Vercel Web Analytics and Speed Insights, both cookie-free.
No Google Fonts CDN; nothing leaks to a third party on first paint.
Email and password day-to-day. Magic link for first-time setup and password reset. Argon2id, HIBP-checked at set time.
DPA on request. Article 9 handling for health data.
Flat subscription. We are not a marketplace.
Most clinics
choose Expand.
Full matrix at /pricing. The short version is below.
Paste your URL.
See the draft.
Bucharest, Romania · CET · Mon–Fri