SelloSeguro — sello-freeze sentinel for Mexican micro-businesses

1. One-liner

Watches your SAT filings so a frozen digital seal never stops your invoicing — and drafts your defense if it does.

2. Trend signal — why now?

The SAT (Mexico’s tax authority) turned CSD restriction from a rare penalty into a routine, automated pressure tool in 2026. The Certificate of Digital Seal (CSD) is the cryptographic key you need to stamp a CFDI — no CSD, no invoice, no sale, no incoming payment. When the SAT restricts it under Art. 17-H Bis, your business stops that hour.

What changed in the last 12 months:

• CFF 2026 = “fiscalización inteligente.” The SAT now auto-cross-matches the totals on your issued/received CFDIs against your monthly ISR/IVA and annual declarations. Any discrepancy between declared income and CFDI totals is an explicit cause for restriction, flagged by machine (xData), not by a human auditor who might give you slack. (mysuitemex, iacontable)
• The annual-return trap fired in 2026. Legal entities that missed the 31 March 2026 annual return got their CSD restricted and their invoicing paralyzed — a scheduled, predictable freeze that thousands walked into. (El Contribuyente)
• Volume is real. The SAT’s head of collection told the IMCP (15 June 2026) that ~7,300 taxpayers had their seals restricted in 2026 over irregular-invoicing schemes — and that’s only the enforcement-heavy bucket, not the far larger set frozen for ordinary filing slips. (search-sourced, IMCP conference report)
• The clock shrank. New accelerated procedures give some taxpayers only 5 business days to present evidence before the freeze hardens. Regular restriction cases get 40 business days via form 296/CFF, but the aclaración must carry pruebas idóneas — most micro-businesses don’t know what those are. (El Contribuyente, Praxium)

The pattern: a preventable, machine-detectable event with catastrophic operational cost, and the victim finds out only when the invoice won’t stamp.

Provenance:

• Signal 1 (demand): CSD restriction paralyzes invoicing and cash flow; “each day without invoicing means delayed payments and impatient customers” — https://www.contpaqi.com/publicaciones/contabilidad/cancelacion-certificado-sello-digital-frena-ventas-y-pagos — 2026-07-08
• Signal 2 (feasibility): SAT web service (Regla 2.7.2.4 RMF) allows programmatic mass CFDI + metadata download, authenticated with the taxpayer’s e.firma (.cer/.key) — https://www.satfacil.com.mx/blog/sat-descarga-masiva-cfdi-2026 — 2026-07-08
• Signal 3 (economic): active paid market for SAT reconciliation (“Blindaje Fiscal”, CONTPAQi Analiza, gigstack, ezaudita) proves money moves here — https://blog.gigstack.pro/post/conciliacion-sat-como-funciona-guia-practica-2026 — 2026-07-08 Category: Regulatory arbitrage

3. The opportunity

Two failures sit on top of each other.

Prevention is sold to the wrong buyer. Every existing reconciliation tool — CONTPAQi Analiza, Intelisis “Blindaje Fiscal 360°”, gigstack, ezaudita — is bolted to an ERP and built for the contador. It assumes you already run their accounting suite and pay a monthly accountant who reads the reports. The 1–3-person taxpayer who invoices through a standalone PAC (Facturama, gigstack free tier) and files through a part-time contador has zero continuous CSD-risk monitoring. Nobody watches the specific gap that trips the freeze.

Defense is sold at panic prices, after the fact. When the seal freezes, the owner discovers it live, googles frantically (“no puedo facturar, me bloquearon el sello”), and calls a fiscal lawyer or despacho who charges a scared client a premium to draft a form-296/CFF aclaración that is 80% boilerplate plus their own CFDI-vs-declaration evidence.

SelloSeguro takes the owner’s side on both. It watches the four or five machine-detectable triggers continuously and warns before the SAT acts, then — if a freeze lands anyway — auto-assembles the 296/CFF defense packet from data it already holds, turning a ₹-panic legal errand into a one-click filing.

4. Target market

• Primary customer: RESICO personas físicas (freelancers, professionals), RESICO PyMEs, and micro-S.A.s / S.A.S.s in Mexico with MXN 300K–3.5M annual revenue, 0–5 employees, who invoice through a standalone PAC and use a part-time or shared contador — not a full ERP.
• Why they buy: In their words — “no puedo facturar, se me cayeron las ventas.” A CSD freeze means they literally cannot bill the client sitting in front of them; payments stop, cash flow stops, and they don’t know why or for how long. They will pay to never feel that again, and pay more to get out of it fast.
• Rough TAM reasoning: Mexico has well over 5M formal taxpayers issuing CFDIs; RESICO alone covers millions of personas físicas plus PyMEs. Even the narrow “standalone-PAC, no-ERP, revenue-exposed-enough-to-be-audited” slice is comfortably in the hundreds of thousands. A tool that captures a few thousand at a low monthly price clears the $1M line.
• Why now for them: 2026 is the first year the SAT’s cross-matching runs automatically and at scale, and the first year a missed annual return reliably triggers a freeze. The risk went from “unlikely and negotiable” to “algorithmic and this-month.”

5. Product sketch (MVP)

• Connect once: owner uploads e.firma (.cer/.key + password) or their contador does it; SelloSeguro pulls all issued and received CFDIs from the SAT web service on a schedule.
• Freeze-risk score: a live dashboard scoring the handful of known 17-H Bis triggers — CFDI-vs-declaration income gap, missing/overdue provisional declarations, missing annual return, unresolved payment complements (PPD without REP), and supplier appearing on the 69-B blacklist.
• Early warnings in plain Spanish: “Your declared October income is MXN 84,000 below your stamped CFDIs — this is the #1 seal-freeze cause. Fix before your next provisional declaration.” Not accountant jargon — the number, the cause, the deadline.
• Buzón tributario watch: monitors the SAT tax mailbox so the owner learns of a restriction notice the moment it lands, not when an invoice fails.
• One-click 296/CFF defense packet: if a restriction hits, auto-drafts the aclaración with the taxpayer’s own reconciled CFDI evidence attached as pruebas idóneas, formatted to the ficha 296/CFF requirement, ready to file (or hand to their lawyer half-done).
• Missing-complement chaser: flags PPD invoices lacking a REP and drafts the payment-receipt CFDIs owed.
• Contador share view: read-only link so the part-time accountant sees the same risk board without a login seat.

6. AI angle — what’s load-bearing

Two places AI does real work, not decoration:

1. Discrepancy explanation and triage. Raw CFDI-vs-declaration diffs are noise; the value is telling a non-accountant which gaps will actually freeze the seal, why, and what single action closes them, in the owner’s language. An LLM turns a reconciliation delta into a ranked, plain-Spanish action list with the correct fiscal deadline — the thing a contador charges hourly to explain.
2. Defense-packet drafting. Generating a compliant 296/CFF aclaración means composing legal-fiscal argument text bound to the taxpayer’s specific numbers and the specific cited irregularity. That’s structured generation over the customer’s own data — remove the AI and you’re back to a lawyer typing.

Remove the AI and you have a raw CSV diff tool nobody in this segment can read. The AI is what makes it usable by the owner instead of only the accountant.

7. Localization angle

This is the localization play — it can only exist inside Mexican fiscal rails.

• Language: Spanish-first, and specifically owner-Spanish, not contador-Spanish.
• Payment rails / pricing: MXN pricing on SPEI/OXXO/card; a ₹499-equivalent tier that global compliance SaaS never bothers to build for this wallet.
• Regulatory quirk = the entire moat: 17-H Bis, ficha 296/CFF, CFDI 4.0, e.firma auth, RESICO rules, 69-B blacklist. Nothing about this transfers to another country — which is exactly why global players won’t build it and why a focused local team can own it.
• Distribution: Mexican fiscal-Twitter/X, contador Facebook groups, and WhatsApp — where this audience already asks “¿por qué no puedo facturar?“

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

• Pricing: MXN 249/mo (≈ $13) solo/persona física tier; MXN 599/mo (≈ $32) PyME tier with multi-RFC and contador share; one-time MXN 2,500 (≈ $135) “emergency” packet for a business already frozen who just needs the 296/CFF filing now (a lead magnet that converts to subscription).
• ACV: ~$220/yr blended across tiers.
• Rough math to $1M ARR: ~4,600 paying accounts at $220 ACV. Against a base of hundreds of thousands of exposed RESICO/PyME taxpayers, that’s a low-single-digit-percent penetration.
• Rough math to $5M ARR: ~23,000 accounts, or the same base plus a per-RFC reseller deal with mid-size despachos who put their whole client book on it (contador-as-channel, 20–200 RFCs each).
• Expansion path: add RFCs, then add adjacent freeze-adjacent workflows (annual-return reminder-and-file, provisional-declaration prep, 69-B supplier screening) that raise ACV without leaving the “keep your seal alive” promise.

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

• Panic-keyword capture. Buy/rank the exact terms people type at the moment of freeze: “no puedo facturar,” “me restringieron el sello,” “SAT bloqueó mi CSD.” Land them on a free instant risk-check + the one-time emergency packet. This is a channel where intent is maximal and the incumbent is a $frantic lawyer call.
• Contador micro-influencers. Mexico has a large fiscal-creator scene on TikTok/YouTube/X (“contador que explica”). Give 10–15 of them the tool free and an affiliate cut; their audience is the frozen-seal-terrified segment. One good video on “cómo evitar que el SAT te bloquee” converts.
• Despacho reseller pilots. Cold-approach 30 small/mid despachos that manage 20–200 RFCs on standalone PACs; pitch it as liability insurance for their client book (“we’ll warn you before your client’s seal freezes on your watch”). Each closed despacho is 20+ seats.
• 69-B / annual-return event marketing. Every March (annual-return deadline) and every provisional-declaration cycle is a predictable freeze wave — run timed campaigns just ahead of each.

If March’s annual-return freeze wave doesn’t convert a cold panic-keyword funnel, the idea’s core bet is wrong — and that’s testable in one filing season.

10. Build complexity — justification

Medium. The SAT web service for mass CFDI + metadata download is documented and already consumed by many tools, and CFDI 4.0 XML is a known schema — so ingestion and reconciliation are off-the-shelf-ish. The custom work is (a) reliable e.firma-authenticated syncing and buzón monitoring, (b) the trigger-scoring logic encoding 17-H Bis causes correctly, and (c) the 296/CFF packet generation, which needs a fiscal advisor to get right. A technical founder plus a part-time fiscal domain expert ships v1 in ~3–4 months.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Reads the taxpayer’s own SAT data with their credentials; assists a legitimate defense procedure.
Ethical — no harm / dark patterns	✅	Helps compliant businesses stay compliant; does not help evade tax.
Market exists (evidence above)	✅	Active paid reconciliation market + documented freeze pain + 7,300 restricted taxpayers.
1–5 person team can build this	✅	Technical founder + fiscal advisor; off-the-shelf CFDI ingestion.
Launchable with <$50K / ₹40L	✅	SaaS build, no capex; advisor fees + infra only.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Frozen seal = zero invoicing = zero revenue that day. Hair-on-fire, felt as an emergency, willingness-to-pay peaks at the freeze moment.
Demand evidence	15	11/15	Documented pain, 7,300 restricted, live panic-search terms, paid reconciliation category — but no clean public count of the broader “filing-slip freeze” population; demand for prevention (vs. panic cure) is inferred.
Build feasibility	15	10/15	CFDI ingestion is solved; e.firma sync, buzón watch, and correct 17-H Bis trigger logic + 296/CFF drafting are the real work. 3–4 months.
Distribution clarity	15	11/15	Panic-keyword + contador-creator + despacho-reseller are concrete and intent-rich; conversion math on the subscription (vs. one-time cure) is the open question.
Revenue mechanics	15	11/15	Clear MXN pricing benchmarked to accountant-fee pain; ACV modest; $1M needs only low-single-digit % of the exposed base.
Time to first revenue	7	7/10	The one-time emergency packet can sell in week one to already-frozen owners; subscription retention takes a season to prove.
Defensibility	4	4/10	Regulatory-knowledge moat is real but copyable; incumbents own the ERP relationship and could add an owner tier. Speed + owner-brand + contador channel are the only durable edges.
Total	100	71/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required

Key assumptions to validate (3–5)

1. Assumption: The freeze-exposed micro-taxpayer will pay a subscription for prevention, not just a one-time fee once already burned. How to test: run the panic-keyword funnel; measure what % of one-time emergency-packet buyers convert to a monthly plan within 30 days. If <20%, the business is a one-shot cure, not SaaS.
2. Assumption: e.firma-authenticated SAT sync + buzón monitoring is reliable enough to promise “we’ll warn you first.” How to test: build the ingestion against 20 real RFCs (via friendly contadores) and measure sync success and notice-detection latency for a month.
3. Assumption: Small despachos will resell it as client-book insurance rather than see it as a threat to their advisory fees. How to test: pitch 15 despachos; count how many sign a paid pilot vs. object that it cannibalizes their aclaración billing.
4. Assumption: The 17-H Bis trigger logic can be encoded accurately enough that warnings aren’t false-alarm noise. How to test: back-test the scoring against a set of RFCs that were actually restricted and check whether SelloSeguro would have flagged them in advance.

Risk flags

1. Platform dependency: Total reliance on the SAT web service and e.firma auth. If the SAT changes the API, throttles it, or tightens credential handling rules, ingestion breaks. Mitigate with PAC-side data as a fallback source.
2. Incumbent counter-move: CONTPAQi/gigstack could ship an owner-facing “seal health” tab and undercut on bundling. The window is the head start before they notice this segment.
3. Trust / security: Holding customers’ e.firma private keys is holding the keys to their entire tax identity. A breach is existential; security posture and possibly a “you hold the key, we hold the cert” split-custody design are non-negotiable and add build cost.
4. Regulatory whiplash: The Suprema Corte already struck down one “most-hated” SAT rule as unconstitutional; the 17-H Bis regime could be softened or reshaped, changing the urgency the product sells against.

14. Structured verdict

Score:                  71/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder + part-time Mexican fiscal advisor (contador/fiscal lawyer)
Time to revenue:        4–8 weeks (one-time emergency packets); a full season to prove subscription retention
Capital to launch:      $8–15K (₹7–12L) — infra + advisor fees + security review
Top 3 assumptions to validate first:
  1. One-time-buyer → subscription conversion ≥20% (run the panic-keyword funnel)
  2. e.firma sync + buzón watch reliable enough to promise "warned first" (20-RFC pilot for a month)
  3. Despachos resell rather than resist (15 paid-pilot pitches)
Kill criteria:
  - Abandon if <20% of emergency-packet buyers convert to a monthly plan within 30 days after 3 months of funnel
  - Abandon if e.firma-authenticated sync can't hit >95% reliability or the SAT restricts programmatic access
  - Abandon if a major incumbent (CONTPAQi/gigstack) ships an equivalent owner-facing seal-health product before your v1

15. Next step — 1-week validation sprint

• Day 1–2: Stand up a landing page + the free “instant seal-risk check” and the paid one-time 296/CFF emergency packet. Wire the panic keywords (“no puedo facturar,” “me restringieron el sello”).
• Day 3–4: Recruit 2–3 contadores to run 10 real RFCs through a manual back-office version of the reconciliation, and pitch 5 despachos on a reseller pilot to gauge resist-vs-embrace.
• Day 5: Decide go / no-go on a falsifiable bar: at least 3 paid emergency packets sold from cold panic traffic and at least 1 despacho verbally committed to a paid pilot. Miss both and the demand is softer than the pain suggests — revisit.

The result is falsifiable: real pesos from strangers in panic, or none.