DRAFT — Replace placeholder text and metrics with verified detail before publishing
Case Study · 2025

La Profe Vero — bilingual tutoring with warmth, not corporate sterility.

A Colombian Spanish tutor serving a global student audience needed a site that captured the warmth of her in-person teaching style — and a booking flow that let students go from "interested" to "scheduled" in under 90 seconds.

TypeBilingual Marketing + Booking
StackNext.js · next-intl · Stripe
LocalesEN · ES
StatusLive
The problem

Online language tutoring sites are warm in person and cold on the web.

Vero's existing students raved about her teaching style — patient, warm, fluent across Colombian and neutral Latin-American Spanish. Her existing online presence didn't reflect any of that. It was a templated booking page on a third-party platform, the kind of generic interface that could have been any tutor anywhere. Prospective students who landed there had no sense of who Vero was as a teacher before they handed over a credit card.

The other constraint: her audience is bilingual by definition. The site had to feel native in both English and Spanish, which meant a translation strategy that went beyond word-for-word and respected the way each audience actually reads the web.

The approach

Personality first, booking flow second.

The home page leads with Vero — her photo, her teaching philosophy, a one-paragraph story about why she teaches. Pricing tiers come after the story, not before. The bet was that students who'd already developed a sense of who they were about to book with would convert at higher rates than students arriving at a price chart cold. Early testing confirmed it: time-on-page tripled compared to the third-party platform, and direct-to-booking conversion improved meaningfully.

The bilingual implementation uses next-intl with locale-prefixed URLs (/en/, /es/), per-locale meta tags, and language-switcher logic that preserves the user's current page across language changes. Both versions of every page were copy-edited by a native speaker of the target language — not auto-translated.

Fig. 01 — La Profe Vero in production
The stack

Built for two languages, one deploy.

The stack was chosen to make the second locale a configuration choice, not a separate deployment.

Next.js 14
next-intl
Tailwind
Stripe Checkout
Calendly
Resend
Vercel
GA4
The outcome

A site that sounds like the teacher behind it.

The result is a small site that punches well above its weight. The bilingual implementation handles SEO correctly across both locales, the booking flow connects directly to Stripe and Calendly without a third-party intermediary, and Vero owns every line of the experience — including the email confirmations students receive after booking.

  • Locale-prefixed URLs with proper hreflang for SEO
  • Native-speaker translated copy in both languages
  • Stripe Checkout for international card support
  • Calendly embed for live availability
  • All email branded under La Profe Vero — no third-party signatures
[Replace with quote from Vero on the difference between her old platform-hosted setup and the custom site.]— Verónica, La Profe Vero

Visit the live site →

Have a build like this?

Let's talk.

If you're scoping a project in this category, start the conversation here.

Start a Project