RutaLista — roadside-rejection screen for Mexico’s hombre-camión carriers

1. One-liner

Pre-flights every Carta Porte against SAT’s live registries and catches the capture errors that get a truck fined or detained on the highway.

2. Trend signal — why now?

Mexico’s Complemento Carta Porte 3.1 (mandatory since 17 July 2024) is now enforced at the roadside, and the 2026 tax reform handed the SAT expedited powers to verify CFDI authenticity, suspend digital certificates, and publish false-invoicing findings. The document is no longer paperwork you file — it’s a thing the Guardia Nacional checks on the highway, and a single bad field detains the truck.

The error taxonomy is now public and brutal:

• Wrong/extra space in the operator or owner RFC invalidates the whole CFDI 4.0 (SAT error CP195: RFC not found in the registered, non-cancelled list).
• Plates that don’t match SAT’s registry, or a vehicle config that doesn’t correspond to the declared plates, fail automatic validation.
• Generic merchandise descriptions (“productos varios”) are rejected; the merchandise SAT-code must match the 2,346-item dangerous-goods catalog where applicable.
• Mistyped postal codes on origin/destination render the document invalid on verification.

Industry sources put it plainly: “errores de captura manual representan el 80% de las multas” — manual-entry errors account for 80% of the fines. Fines run $760 to $14,710 MXN for the transportista who can’t present a valid complement, and $19,700 to $112,650 MXN per document for issuing one outside requirements (CFF arts. 83–84). Detentions last hours to days.

The generation market is crowded — Facturama, SenHub, Facture, CONTPAQi, IDNUBE all fill the complement. None of them tells a one-truck operator “this one will get you stopped — fix these three fields before you roll.” That’s the gap.

Provenance:

• Signal 1 (demand): Carta Porte error taxonomy — manual capture errors = 80% of fines; fines $760–$112,650 MXN; National Guard detains cargo — https://www.dufrei.com/blog/noticias-2/carta-porte-errores-que-frenan-a-la-carga-en-2026-197 — 2026-06-15
• Signal 2 (feasibility): SAT publishes the validation registries and error codes (CP195 = RFC not in registry; auto plate/vehicle validation) that a pre-flight engine can check against — https://www.edifact.com.mx/blog/error-carta-porte-cfdi-causas-soluciones-y-como-evitar-rechazos-del-sat/ — 2026-06-15
• Signal 3 (economic): Active funded CFDI/Carta Porte software market (Facturama, SenHub, CONTPAQi, IDNUBE) + 2026 tax reform expanding SAT enforcement powers and certificate suspension — https://senhub.mx/blog/carta-porte-31-guia-completa — 2026-06-15 Category: Regulatory arbitrage

3. The opportunity

The incumbents solve issuance, not survival. Facturama and friends let you produce a stamped Carta Porte; they assume the data you typed is correct. For a fleet with an accounting department, that’s fine — someone proofreads. For the hombre-camión (literally “man-truck,” the one-operator carrier) who keys the complement on his phone at 5 a.m. before a federal run, there’s no proofreader. He finds out the RFC had a trailing space when a Guardia Nacional officer pulls him over and the QR fails validation.

RutaLista sits before issuance (or wraps it) and runs every field against the same checks the SAT runs: is this RFC in the active, non-cancelled list? Do these plates exist and match this vehicle config? Is this postal code real? Is the merchandise clave specific enough, and does it trip the dangerous-goods catalog? Is the operator’s CURP well-formed? It returns a red/yellow/green verdict in seconds — and tells him exactly which field to fix. It’s a pre-flight checklist for a $112,650-peso mistake.

10× better than the incumbents on the one axis that matters to this buyer: don’t let me get stopped. Generators compete on features and PAC integrations; nobody competes on “we catch the error before the cop does.”

4. Target market

• Primary customer: Mexican owner-operators and micro-fleets — the hombre-camión and 1–10 unit fleteros who haul on federal highways and bill per freight. RFC as a persona física con actividad empresarial or a small persona moral with no dedicated fiscal staff.
• Why they buy: In their words — “un espacio de más en el RFC invalida todo,” “la placa no coincide y te detienen,” “no tengo contador de planta, yo lleno la carta porte.” A single fine equals weeks of margin; a detained load can blow a delivery window and lose the client.
• Rough TAM reasoning: Mexico has hundreds of thousands of registered autotransporte de carga units; the long tail of 1–10 unit carriers is the bulk by operator count and the segment with zero back-office. Even a few hundred thousand addressable operators at a ~₱200–400 MXN/mo price is a multi-million-dollar ARR ceiling well inside the sub-$5M target.
• Why now for them: 3.1 enforcement + 2026 reform turned a filing chore into a roadside liability. The pain moved from “the SAT might fine me later” to “I get stopped today.”

5. Product sketch (MVP)

• Paste or photo-import a draft Carta Porte (XML, a generator’s preview, or a phone photo of the data) and get a red/yellow/green pre-flight verdict in seconds.
• RFC check against SAT’s active/non-cancelled list — catches CP195 before issuance.
• Plate + vehicle-config check — flags plates that don’t exist or don’t match the declared configuración vehicular.
• Merchandise-clave check — flags generic descriptions, suggests a specific SAT clave, and warns when the goods hit the dangerous-materials catalog (extra fields required).
• Postal-code + route sanity check on origin/destination.
• CURP/operator-figure validation for the transport figures block.
• Plain-Spanish fix list: “Field X will fail because Y — change it to Z,” not a raw error code.
• WhatsApp-first delivery: send the draft to a number, get the verdict back in the chat the driver already lives in.

6. AI angle — what’s load-bearing

Two jobs. (1) Extraction: turn a phone photo or a messy generator export into structured fields — vision + OCR doing real work where the operator has no clean XML. (2) Judgment on the fuzzy fields: the deterministic checks (RFC-in-registry, plate-exists, postal-code-valid) are rules and lookups — and they should be, for trust. But the merchandise-description-to-clave mapping is genuinely AI-shaped: “lámina de acero galvanizado cal. 20” → the right SAT clave de producto, with a dangerous-goods flag if relevant. That classification across thousands of claves, from free-text a driver actually types, is where a model beats a dropdown. Remove the AI and you’re back to a human hunting a 50,000-line catalog — which is exactly the manual step that produces 80% of the fines. The AI is the difference between “fill this dropdown yourself” and “describe it, I’ll classify it.”

7. Localization angle

This is the localization — it cannot be a global product. It’s bound to the SAT’s CFDI 4.0 + Complemento Carta Porte 3.1 schema, Mexican RFC/CURP formats, the SCT plate registry, and Mexican postal codes, priced in pesos for a peso-thin wallet, delivered over WhatsApp (the default business channel in Mexico), in Spanish. A ₱299 MXN/mo tier works where a $49 USD/mo tool would be laughed off the lot. The regulatory specificity that makes it un-global is the same thing that makes it defensible against a US generalist.

8. Business model — path to $1M–$5M ARR

• Pricing: ₱249–₱399 MXN/mo (~$13–22 USD) per operator for unlimited pre-flights; a ₱699/mo micro-fleet tier (up to 10 units, shared) for the 2–10 truck carriers. Optional pay-per-check (₱20–30/check) for the truly occasional hauler as a top-of-funnel.
• ACV: ₱3,600 MXN ($200 USD) for the solo tier; ₱8,400 ($460) for the fleet tier.
• Rough math to $1M ARR: ~$1M ÷ $200 ACV ≈ 5,000 paying solo operators — a small slice of a six-figure operator base. Or ~2,500 solo + 900 fleet accounts.
• Rough math to $5M ARR: ~20,000–25,000 paying operators, or a mix tilted toward fleet tiers, plus a per-document fee skim when RutaLista wraps issuance itself. Requires becoming the default “check before you roll” habit, not just a tool.
• Expansion path: start as a pre-flight checker → add issuance (capture the PAC margin) → add a fine-defense packet when a stop happens anyway → fuel/insurance partner referrals to the captive operator base.

9. Go-to-market wedge — first 100 customers

• Transportista Facebook & WhatsApp groups. Mexican hombre-camión operators cluster in large FB groups (“Fleteros México,” “Hombre Camión,” route-specific groups). Post the error taxonomy as a free “10 errores que te detienen” checklist; offer a free pre-flight on their next load. These groups are where the complaints already live.
• Free single-check bot. Stand up a WhatsApp number that pre-flights one Carta Porte free. Seed it in the groups above; every red verdict is a conversion event (“we just saved you a ₱14,710 stop — ₱299/mo for unlimited”).
• PAC/generator co-marketing or affiliate. The smaller generators (not the CONTPAQi tier) lack a validation story; partner to bundle RutaLista as the “no-rejection guarantee” layer, or run an affiliate where they earn per converted user.
• Asesores fiscales for micro-carriers. The contadores who serve fleteros are a thin reseller channel — one contador covers dozens of one-truck clients.

10. Build complexity — justification

Low. The deterministic checks are rules + lookups against published SAT/SCT data (RFC status, plate registry, postal codes, the clave catalogs) plus schema validation against the 3.1 XSD. The only non-trivial pieces are (a) keeping the catalogs current as SAT updates them and (b) the merchandise-description classifier — both off-the-shelf-tractable. WhatsApp Business API + a vision model for photo intake + a rules engine. A focused pair ships a credible v1 in 8–12 weeks; the moat is in the catalog freshness, not the code.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Compliance-assist tool; checks public-rule conformance, doesn’t replace the PAC stamp.
Ethical — no harm / dark patterns	✅	Helps the smallest operators avoid disproportionate fines. Net-protective.
Market exists (evidence above)	✅	Mandatory regime, public fine schedule, documented 80%-from-manual-error stat, crowded adjacent market.
1–5 person team can build this	✅	Rules + lookups + one classifier + WhatsApp. 8–12 weeks.
Launchable with <$50K / ₩40L	✅	API + inference + WhatsApp costs; no capex.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Hair-on-fire at the roadside — a stop costs a load and a five-figure-peso fine. Slightly under top band because the operator can also just buy from a generator and hope.
Demand evidence	15	12/15	Hard public fine schedule, mandatory regime, “80% of fines from manual error,” documented error codes, crowded adjacent market. Missing: direct verbatim “I’d pay for a checker” quotes (forums show the pain, not the willingness-to-pay yet).
Build feasibility	15	12/15	Mostly rules + lookups + one classifier. The catalog-freshness treadmill is the only ongoing drag.
Distribution clarity	15	11/15	Named FB/WhatsApp groups + free-check bot is concrete; conversion from free-check to paid is the open question.
Revenue mechanics	15	11/15	Peso pricing fits the wallet and the math to $1M is a believable operator count; churn risk if they only haul occasionally.
Time to first revenue	10	8/10	WhatsApp free-check → paid can convert in days once the groups bite; no enterprise cycle.
Defensibility	10	3/10	Catalog freshness + WhatsApp habit + brand in the niche is real but thin; a funded generator could bolt on validation. Speed and being the “checker” brand is the only moat.
Total	100	73/100

13. Qualitative modifiers

Founder-fit tags

domain-expertise-required · technical-heavy — you must actually understand CFDI 4.0 / Carta Porte 3.1 rules and SAT validation behavior, and keep up with catalog changes. A Mexico-based founder (or a fiscal advisor co-founder) is a near-requirement.

Key assumptions to validate (3–5)

1. Assumption: Hombre-camión operators will pay ₱249–399 MXN/mo to avoid fines they only sometimes incur. How to test: run the free-check bot in 3 FB groups, then gate it; measure free→paid conversion on the first 200 users.
2. Assumption: A pre-flight can reach the same verdict the SAT/Guardia reaches at the roadside (no false “green” that still gets stopped). How to test: validate 100 real Cartas Porte against actual issuance/stop outcomes; target zero false-greens before charging.
3. Assumption: SAT’s validation registries (RFC status, plate, claves) are accessible/maintainable at acceptable cost and latency. How to test: build the lookup pipeline against current SAT sources; confirm refresh cadence and cost per check.
4. Assumption: Generators won’t trivially absorb this. How to test: talk to 2–3 smaller PACs about co-marketing vs. build — if they all say “we’ll just add it,” reconsider.

Risk flags

1. Platform dependency (SAT): the whole product is downstream of SAT schema and registry availability. A format change or a closed registry breaks checks overnight. Mitigate with fast catalog-update ops.
2. Incumbent absorption: a funded generator (CONTPAQi-tier) bolting “validation” onto issuance is the obvious counter. Win on the checker brand + the smallest-operator wedge they ignore.
3. Willingness-to-pay for prevention: people under-buy insurance against rare-but-severe events. The free-check funnel must make the avoided fine feel imminent, not theoretical.

14. Structured verdict

Score:                  73/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Mexico-based technical founder with a fiscal/Carta-Porte domain advisor
Time to revenue:        6–10 weeks (free WhatsApp check → paid)
Capital to launch:      ₱80K–₱200K MXN ($4–11K USD)
Top 3 assumptions to validate first:
  1. Free→paid conversion among hombre-camión operators — gate the bot after 200 free checks
  2. Zero false-greens vs. real roadside/issuance outcomes — validate 100 real documents
  3. SAT registry lookups are maintainable at cost — build the pipeline before the UI
Kill criteria:
  - Abandon if free→paid conversion <3% after 500 free checks across 3 groups
  - Abandon if you cannot eliminate false-greens (a "green" that still gets stopped destroys trust and the product)
  - Abandon if a major generator ships an equivalent pre-validation layer before your v1 and bundles it free

15. Next step — 1-week validation sprint

• Day 1–2: Build the dumbest possible pre-flight — RFC-format + plate-format + postal-code + merchandise-clave specificity checks over WhatsApp. No live SAT lookups yet, just the rules that catch the obvious 80%.
• Day 3–4: Drop the free “10 errores que te detienen” checklist + free-check bot into 3 large fletero FB/WhatsApp groups. Count how many drafts get sent in and how many come back red.
• Day 5: Decide go/no-go on a falsifiable bar: ≥75 real drafts pre-flighted, ≥40% returning at least one red flag, and ≥10 operators replying “yes, I’d pay ₱299/mo for this.” If the drafts don’t come in or nothing flags red, the pain is smaller than the fine schedule suggests — no-go.