EN/ES
All work
Case study
MD Kitchen & Baths
Boutique kitchen + bathBoutique cabinet shopLive — current

MD Kitchen & Baths —
bilingual by default.

MD is the second shop on the AI-agent stack. The buyer profile skews bilingual and the inbound mix is roughly even between English and Spanish, so the agent handles both without escalation. The deployment mirrors KCD's architecture — different module count, different finish library, same delivery model.

ODOO 19 — IN PRODUCTIONAI AGENT — EN + ES INBOUNDSOW DRAFTED PER LEADHOSTED ON HETZNER
The engagement

How the stack lands at MD.

MD ran with KCD's blueprint and a finish library of its own. Same six stops — what was there before, what we shipped, how the months ran, what changed on the floor, the owner's read, and what's queued next.

Before the stack

EN + ES inbound bouncing between two operators, mid-conversation.

MD's buyer profile is roughly even between English-first and Spanish-first. Without a bilingual agent, inbound was handed off mid-thread when a Spanish reply came back to an English first-touch — or vice versa. The owner ended up shadow-reading both inboxes to make sure nothing was dropped at the language handoff.

  • Roughly even EN + ES inbound mix
  • Two operators rotating language coverage
  • Mid-thread handoffs caused lost context and slow replies
  • Owner shadow-read both inboxes to catch dropped threads
What we shipped

Same architecture as KCD. Bilingual agent, MD's finish library.

The deployment is the same shape as KCD with a different finish catalogue and different module count. The AI agent qualifies inbound in both languages without escalating, and writes a draft scope-of-work into the owner's inbox per qualified lead. The owner signs from email — there's no portal to log into.

  • Odoo 19 — Estimating, BOM, install scheduling
  • Next.js site with bilingual lead capture
  • AI agent qualifies in EN + ES, drafts SOW
  • Managed Hetzner hosting with daily Postgres backups
How the months ran

KCD's blueprint, ported to MD's catalogue. Shorter build slice.

The second deployment ran faster because the architecture was settled. Discovery confirmed MD's catalogue and the bilingual edge cases. Build proceeded in two-week reviewable slices, biased toward the finish library since the modules were KCD-parity. Handoff was a one-week shadow on the live floor.

  • Week 0 — Paid discovery, scoped MD's catalogue + bilingual cases
  • Weeks 1–6 — Build slices reviewed every two weeks
  • Week 7 — AI agent trained on MD's quote language
  • Week 8 — One-week shadow on the live floor, then handoff
What changed

One agent on both languages. SOW drafts in the owner's inbox per lead.

Bilingual inbound is qualified by one agent, not two operators on rotation. The mid-thread handoff is gone. The owner sees a draft SOW for each qualified lead and signs from email — no portal round-trip.

  • EN + ES inbound qualified by one agent, no escalation
  • Draft SOW lands in the owner's inbox per qualified lead
  • Owner signs from email; no portal round-trip
  • Operator rotation freed up for shop-floor work
Owner's read

Owner quote — currently being recorded.

Real attributed testimony from MD's owner is in scheduling and will live here once recorded. We don't run synthetic quotes on this site. If you want to talk to MD directly about running a bilingual agent, ask on the call and we'll set up a fifteen-minute reference chat.

What is queued

Phase two — finish-library expansion and a referral program in the agent.

Two add-ons are on deck. An expansion of the finish library with the agent re-trained against the new SKUs; and a light referral program woven into the agent's confirmation flow — so a qualified lead can name a referrer and the owner sees that attribution on the SOW.

  • Finish-library expansion + agent re-training pass
  • Referral attribution in the agent's confirmation flow
  • Optional — install-photo capture pushed back into Odoo job records

A bilingual shop floor,
deserves a bilingual agent.

If your inbound mix runs EN + ES and your operators are paging between languages mid-conversation, MD's stack is the reference. Twenty minutes on a call is the fastest way to know if it ports.

Loading sequence…

Let's get your whole shop in one place.

Chat on WhatsAppBook a free consultation

[b.] LEGAL

© 2026 Metrica Development LLC
Florida, USA · All rights reserved.

[c.] NEWSLETTER

Tips on running your shop, straight to your inbox. No spam — just useful stuff.