Product Block 13 · Sellable today

Bilingual Conversion Layer

Make an English-only site convert Miami buyers in English and Spanish.

Deploy: 1 day $1,500 setup $250/mo
Live demo Try the demo → https://bilingual.cafecito-ai.com/

Best fit: English-only Miami service businesses with Spanish-speaking buyers: contractors, medspas, law, healthcare, real estate, restaurants, and home services.

⚡ Self-bootstrap · paste into Claude Code or Codex

Bilingual Conversion Layer — build it without writing code

Drop the prompt below into Claude Code or Codex. The agent picks an English-only Miami business, builds a bilingual overlay (intake / FAQ / CTA / handoff email) on a sub-route mirroring their primary page, generates a screenshot pair (their English-only page vs the bilingual version), and produces a same-day cold pitch.

You provide

You provide: (1) the prospect site URL (must be English-only with Spanish-speaking customer base), (2) decision-maker email, (3) which of their pages to mirror first (homepage / services / contact).

You get back

You get: a hosted bilingual overlay at /bilingual-demo/<slug> mirroring their selected page with EN/ES toggle, intake form in detected language, handoff email in caller's language, and a side-by-side screenshot pitch.

Runtime & cost

Roughly 60 minutes wall-clock. ~$1 in Claude tokens.

📋 Copy the entire block below into Claude Code (`/plan`) or Codex
You are building a Bilingual Conversion Layer (Block 13 in the Cafecito AI new-hire playbook). Full reference at https://cafecito-ai.com/new-hire/blocks/13-bilingual-conversion-layer. Read it. Use plan mode. Stop at every [GATE].

INPUTS YOU NEED FROM THE HUMAN (ask before doing anything else):
1. Prospect site URL (English-only, Spanish-speaking customer base — confirm by checking neighborhood or services)
2. Decision-maker email
3. Which page to mirror first: homepage / services / contact (start with the highest-traffic conversion page)

ENVIRONMENT (verify):
- Working dir: /home/eratner/cafecito-ai
- Cloudflare account: f7a9b24f679e1d3952921ee5e72e677e

SECRETS TO CONFIRM:
- ANTHROPIC_API_KEY (Claude — translation + tone matching)
- RESEND_API_KEY (handoff emails)

THE PLAN:

STEP 1 — RESEARCH + TRANSLATE (15 min)
- Fetch prospect's selected page. Extract: hero copy, services, CTA buttons, contact info, brand color, logo URL.
- Use Claude to translate to Spanish — match formality (Usted vs Tú based on business tone), preserve any English brand terms.
- For services list: not just translation but cultural adaptation (e.g. "appointment" → "cita" not "nombramiento").
[GATE 1 — show side-by-side EN/ES copy, ask "translation reads natively?"]

STEP 2 — SCAFFOLD WORKER (10 min)
- Create /home/eratner/cafecito-ai/bilingual-<prospect-slug>/.
- Build a single-page mirror of the prospect's page with EN/ES toggle in top-right (default to browser-language detection, persist in localStorage).
- Embed an intake form: 3 fields (name, contact, "what do you need" textarea), submits to /api/intake.
- API handler: detects submission language, generates handoff email to prospect in customer's language (with English summary for staff).
[GATE 2 — show local preview in both EN and ES modes, ask "ready to deploy as demo?"]

STEP 3 — DEPLOY DEMO (5 min)
- Deploy as a route on the cafecito-ai worker: /bilingual-demo/<prospect-slug>.
- Test the language toggle. Test the intake form in both modes. Verify handoff email lands in YOUR inbox (testing only).
[GATE 3 — print URL + 2 screenshots (EN view, ES view), ask "ready for the screenshot pitch?"]

STEP 4 — SCREENSHOT PAIR (5 min, human action)
- Tell human: "Take a screenshot of THEIR current English-only page. Then take a screenshot of YOUR bilingual demo in Spanish mode. Combine side-by-side."

STEP 5 — DRAFT THE COLD PITCH (5 min)
- Email subject: "Half your customers in [neighborhood] speak Spanish. Your site only speaks English."
- Email body: 4 sentences, lead with the demographic stat, attach the side-by-side screenshot, link the live demo, name $1.5k setup / $250/mo, one yes/no close ("want me to set the toggle on your real homepage by Friday?").
[GATE 4 — show the draft, ask the human to send manually]

STEP 6 — SHIP THE SUMMARY
- Single-line: "[BUSINESS] bilingual demo at [URL] · pitch sent."
- Append to /home/eratner/cafecito-ai/bilingual-shipped.md.

DONE.

GUARDRAILS: NEVER auto-deploy to their real domain without signed pilot — only the demo subdomain. Translation must pass a native-Spanish-speaker eye check before going to the prospect. Cost ceiling: $2.
01Stack
  • Cloudflare Workers
  • Hono.js
  • HTML rewrite/proxy optional
  • Claude API
  • OpenAI API
  • D1 optional
  • Resend optional
03Day-1 plan

A real prospect. A real demo. A real outbound message — all before 5pm.

  1. 09:00-09:30 Find an English-only Miami site.

    Prioritize businesses with clear Spanish-speaking market exposure but no Spanish CTA, page, or intake.

  2. 09:30-10:30 Generate bilingual page and inquiry flow.

    Use the existing site as source. Produce Spanish hero, services, FAQ, and contact form copy without inventing credentials.

  3. 10:30-12:30 Build the demo route.

    Host a bilingual landing page on Cloudflare with language toggle and fake lead capture.

  4. 12:30-14:00 Build staff summary.

    When a Spanish lead submits, show English staff summary plus suggested Spanish reply.

  5. 14:00-17:00 Call with conversion wedge.

    Ask how often Spanish inquiries happen, whether staff can respond, and what lost bilingual leads are worth.

04Best practices & gotchas
  • Do not machine-translate blindly.

    Why: Literal translations sound cheap and can create trust issues.

  • Translate the conversion path first.

    Why: Hero, CTA, form, FAQ, and followup matter more than translating every blog page.

  • Give English staff a summary.

    Why: A Spanish lead is only useful if the team knows what to do next.

  • Respect regulated language.

    Why: Medical, legal, and financial claims need careful wording.

05Prompts (copy-paste)

Drop these into Claude Code. Replace the [BRACKETED] fields with the prospect's details.

Prompt 1 Bilingual page rewrite

Creates Spanish conversion copy grounded in the existing site.

Rewrite this business homepage into a Spanish conversion page.

Inputs:
- business type
- city
- existing homepage copy
- services

Output:
- Spanish hero
- three service cards
- FAQ
- contact form labels
- confirmation message
- English staff summary template

Rules:
- Keep claims conservative.
- Do not invent guarantees, credentials, prices, or availability.
- Use natural Miami Spanish, not literal translation.
Prompt 2 Bilingual layer scaffold

Builds a Cloudflare-hosted bilingual demo.

Build a Cloudflare Workers + Hono bilingual conversion demo.

Routes:
- GET / shows EN/ES toggle and Spanish landing page
- POST /lead stores fake lead in D1
- GET /admin shows English summary and suggested Spanish reply

Use Claude API or OpenAI API for language-aware summary.
Use fake leads only.
Deploy and print the demo URL.
06Selling script

Discovery question (ask this first)

"When a Spanish-speaking customer lands on your site or calls in, what happens today?"

The frame

This is not a full website rebuild. It is a conversion layer for buyers who already want the service but do not see a comfortable path to ask for it.

The demo play

Show their homepage concept in Spanish, submit a fake Spanish inquiry, then show the English staff summary and Spanish reply draft.

Objections

  • "We have someone who speaks Spanish."

    "Good. This helps that person by capturing the lead clearly and giving the rest of the team context."

  • "Google Translate is enough."

    "Google Translate translates words. This translates the buying path: CTA, form, trust language, followup, and staff handoff."

  • "We do not want a full rebuild."

    "That is why this starts as one route or one embedded flow, not a rebuild."

The close

"Let me launch one Spanish conversion page and lead flow this week for $1,500. If it produces qualified Spanish leads, we keep it live for $250/month and expand from there."

07Pricing notes

Anchor on one incremental lead. Keep the first scope to one page, one form, one followup path. Expansion can include full site, ads pages, SMS, and voice.