Check-in, September 3, 2026
Key changes since June 4
- The certificate flow was completely overhauled with guided steps, delegated upload, save-and-resume links, chat support, reminders, and clearer error recovery.
- A web tool was launched that prepares the files needed to request an SAT digital seal certificate, without installing SAT’s Certifica Java app.
- A route planner was launched with toll and fuel-cost calculations.
- Work began on a browser extension that helps users semi-automate Carta Porte entry in existing web tools. Chrome and Edge marketplace requirements mean the first release needs to be more complete than initially planned.
- Nightly synchronization with official SAT sources keeps compliance catalogs current and feeds an automated content-generation pipeline.
Next steps to discuss
Go-to-market shift: selling AI driven components into mid-size carriers
What we learned
Both ends of the market are structurally hard to sell, for opposite reasons.
- Mid/large carriers: full TMS replacement is a rip-and-replace decision. Switching costs (data, process, retraining) make the sale long and low-probability regardless of product quality.
- Small carriers: the product works and converts, but the motion behaves like B2C, low ACV, high volume, one-by-one acquisition. Hard to scale efficiently without significant marketing spend.
The insight
High switching costs are an opportunity to attach.
- If the system of record is immovable, it makes more sense to sell something that makes it more valuable than something that replaces it.
- We don't need to build for this, building the TMS already produced components that work standalone.
- The components may be more sellable than the complete package. Buying one is a decision, not a migration.
- The AI wave opens the door. Mid-size companies are actively looking for where AI fits their processes; our components all integrate AI.
- Mexican fiscal-compliance intelligence gives us a MOAT. A global TMS vendor won't build this, and a generic AI vendor can't.
What we've built, and what we believe
| Component | Our hypothesis |
|---|---|
| Automated data ingestion | Offsets a cost already paid in salary; no new budget line needed |
| Portal-fill extension (SAT/Facturama/Siigo) | Removes the last manual step without requiring system access |
| Automated Carta Porte | SMB traction could transfer upmarket |
| WhatsApp agent | Real channel fit; ops teams already live in WhatsApp |
| Agent tooling / Claude Code | Carriers might want to build on our primitives |
| Route planner | Outside our moat; incumbents adequate |
| CSD generator | A feature, no recurrence |
SAT compliance correctness is part of whatever we sell, it’s not a separate component.
How we test
- 1–2 paid design partners, mid to large-size trucking companies, interested in AI, have pains with their current TMS.
- Paid, not free, there should be willingness to pay/invest.