Bilingual Vertical SaaS for Mexico: What I Learned Building 8 Products in 30 Days

Over the last 30 days the council kept landing on the same insight: most US-built SaaS doesn't fit Mexican SMBs. Not because Spanish is missing — most of them have Spanish — but because the assumptions baked into the product are wrong. Customers don't read email. Invoicing isn't a feature, it's a regulator-mandated workflow. And the channel where business actually happens is WhatsApp.

So I built eight vertical products with that worldview baked in: AgroFlow (Michoacán supply chain), FloraFlow (Estado de México floriculture), FisioFlow + TerapiaFlow (PT clinics in Morelia), EntrenadorIA (personal trainers in Morelia), WaFlow (WhatsApp AI for service SMBs), MoreliaBox (subscription boxes from Morelia), and ArtisanFlow (Oaxaca artisan marketplace).

Here's what changed in how I build SaaS once the constraint became "must work for an SMB in Morelia, not San Francisco."

1. WhatsApp Is the Front Door, Not a Notification Channel

Three of the eight products (WaFlow, EntrenadorIA, parts of FisioFlow) start in WhatsApp and only escalate to a web dashboard for admin tasks. This isn't a UX preference — it's a market reality. WhatsApp Business penetration in Mexican SMBs is north of 80%. Email is for invoices and government notices.

What this changes architecturally:

• State lives in conversations, not in the database first. The conversation log is the canonical source of truth for what happened with a customer. The DB is a derived view of that log.
• Latency budgets get tight. A WhatsApp reply that takes >5s feels broken. This pushed me to Claude Haiku for the conversational layer with Sonnet only on heavy reasoning paths.
• Templates matter more than free-form generation. WhatsApp Business message templates need pre-approval. The product has to be designed around a fixed template library, with AI filling in the slots.

2. CFDI 4.0 Is Not a Bolt-On

Mexican SAT invoicing (CFDI 4.0) is the most under-appreciated complexity in selling SaaS to Mexican SMBs. Every transaction that touches money has to produce a compliant XML invoice. Every customer has an RFC (tax ID). Every product has a SAT-classified code.

TerapiaFlow generates CFDI 4.0 invoices natively for PT sessions, with insurance carrier (IMSS, GNP, AXA, MetLife) routing built in. This took roughly the same time as building the SOAP-note engine — and it's the feature that makes clinics actually buy.

If you're building for Mexico and CFDI is "we'll add that later," you're building a demo, not a product.

3. Compliance Is the Wedge, Not the Tax

FisioFlow and TerapiaFlow both ship NOM-004-SSA3 compliance as a first-class feature. This is the Mexican Official Standard for clinical records, and clinics get audited against it. Most existing PT software in Mexico either ignores NOM-004 or treats it as a checkbox. Generating SOAP notes that actually pass is the wedge that gets a clinic to switch off Excel.

Same pattern for ComplianceBot (federal/state/local for Spanish-speaking US SMBs) and ComplianceAPI Hub (NOM, CFDI, IMSS, COFEPRIS). When the regulator is the buyer's biggest fear, "we make compliance easy" is not a marketing line — it's the product.

4. Bilingual Means Per-User, Not Per-Site

"Bilingual" in most Mexican SaaS means a language toggle in the navbar. That's not enough. In FisioFlow, language is a per-patient attribute: Mrs. González gets her exercise instructions in Spanish, her son who reviews them gets them in English. In EntrenadorIA, the trainer might run their dashboard in English but their WhatsApp conversations with clients in Spanish.

This changes the data model. Every user-facing string that gets generated by AI needs a language tag attached to its target user. Every prompt needs a language slot. Generated content (workout plans, SOAP notes, marketing emails) gets generated in the recipient's language, not the operator's.

5. Local Ingredients, Local Insurance, Local Routes

Generic AI suggestions break the moment they hit local context. EntrenadorIA's nutrition plans use Mexican ingredients (avena, tortillas de nopal, pollo desmenuzado) instead of recipes that assume your supermarket has quinoa and Greek yogurt. TerapiaFlow's insurance routing knows the difference between IMSS reimbursement workflows and private-insurance pre-authorizations. AgroFlow's route optimization knows the actual market days in Pátzcuaro and Uruapan.

None of this is hard — it's just specific. And the council's Customer agent kept surfacing it because Reddit threads and r/Mexico complaints kept naming it.

6. Pricing in Pesos Beats Pricing in Dollars

$29/month sounds cheap to a US founder. ~$520 MXN/month sounds expensive to a Morelia clinic. Pricing in pesos with peso-anchored tiers (e.g., $499 / $999 / $1,999) outperforms dollar-anchored pricing every time.

It also forces honest unit economics. If your product can't sustain a Mexican price point with Mexican usage patterns, you don't have a Mexican product — you have a US product with a Spanish translation.

The Stack That Made This Tractable

All eight products share roughly the same skeleton:

• Backend: Python + FastAPI + PostgreSQL (Neon for production)
• CLI: Typer + Pydantic + Rich (for ops + scripting)
• Frontend (when needed): React + TypeScript + Tailwind
• AI: Claude Haiku for conversational paths, Sonnet for reasoning, Opus for long-form analysis
• Messaging: WhatsApp Business Cloud API webhook handlers
• Invoicing: CFDI 4.0 XML generation with shared complianceapi library
• Compliance: NOM lookup and audit-trail generators shared across products

The shared layers (compliance, invoicing, WhatsApp, bilingual content generation) are the leverage. Building each new vertical isn't writing eight stacks; it's parameterizing one stack against a new domain.

What I'd Build Next

The obvious next move is a unified Morelia Health OS that combines EntrenadorIA, FisioFlow, and TerapiaFlow into one offering for clinics — single login, shared patient records, unified billing. The council has been pushing this for two sessions running. I'm probably about a week away from starting.

If you're thinking about building for Mexican SMBs and want to compare notes, drop me an email at mauricio.gomez.77@gmail.com.