What changed
FACT: FinCEN (with OCC, FDIC, Board, NCUA) published a proposed rule (2026-06-22) mandating a Customer Identification Program for Permitted Payment Stablecoin Issuers, plus companion AML/CFT and sanctions rules (2026-04-10, 2026-06-24) and OCC/NCUA issuance frameworks (2026-03-02, 2026-05-18). The GENIUS Act is enacted; the rulebooks are being written now.
Why now
FACT: The CIP rule is at proposed stage and near-certain to finalize; an OCC PRA information-collection notice (2026-06-12) shows reporting forms are already being drafted. Issuers seeking permitted status must have CIP/KYC, recordkeeping and reserve-attestation artifacts ready to apply — INFERENCE: a 12–24 month readiness window opens before rules bite (2026–2027 phase-in).
Converging signals
A statutory mandate (GENIUS Act) + proposed CIP/AML/reserve rules + a defined but forming class of permitted issuers (non-bank fintechs, credit-union CUSOs, national banks) converge on one point: every issuer must produce bank-grade compliance artifacts they mostly do not have today.
Customer pain
HYPOTHESIS (not evidenced in input): emerging issuers lack bank-grade CIP/AML infrastructure and must interpret dense proposed rules, map requirements to systems, and produce audit-ready documentation to win permitted status. No complaint or hiring evidence was provided — this pain is inferred from the mandate, not observed.
Who pays
FACT (from FORCED BUYER evidence): non-bank stablecoin issuers, credit-union subsidiaries, and fintechs seeking OCC/NCUA issuer status. INFERENCE: also the law/consulting firms and fractional-CCOs who prep these applications and would white-label a mapped artifact kit.
Solved today
Established KYC/AML vendors (Alloy, Persona, Jumio, Socure) and crypto-analytics/compliance incumbents (Chainalysis, Elliptic, TRM) plus Big-4/boutique regulatory consultants billing hourly. Issuers stitch these together manually against evolving rule text.
Why current solutions are bad
Those vendors sell identity-verification plumbing, not a GENIUS-Act-specific requirements map or the application-artifact package; consultants are expensive and slow. There is a genuine gap for a rule-line-mapped readiness/documentation layer — but it is narrow and the underlying KYC function is already saturated.
Proposed product
A GENIUS-Act CIP/reserve-attestation readiness kit: a living requirements matrix mapped line-by-line to the proposed rules, templated identity-collection/recordkeeping schedules, reserve-report export templates matching the OCC PRA forms, gap-assessment checklists, and audit-artifact generation. Positioned as a documentation/readiness data product, NOT a bank-grade KYC engine (which the founder cannot credibly ship to regulated FIs solo).
MVP version
A paid, continuously-updated 'GENIUS Act Compliance Requirements Tracker + Artifact Templates' — the rule crosswalk, editable policy/procedure templates, reserve-report and CIP recordkeeping schedules, and a comment-tracker for rule changes. Buildable in weeks from public Federal Register text.
30-day build
Read and crosswalk all five rules into a structured requirements database; produce a first template pack; publish a plain-English 'what the GENIUS Act CIP rule requires of issuers' explainer to attract the ~dozens of issuer/consultant compliance leads searching this.
60-day build
Sell the tracker + template pack as a subscription to issuers and compliance consultants; add a gap-assessment questionnaire that outputs a readiness report; recruit 2–3 design-partner issuers/consultants for feedback.
90-day revenue plan
Convert design partners and inbound to paid subscriptions; upsell white-label template licensing to consultancies. INFERENCE: realistic first revenue in 60–120 days from a small pool; not a fast-cash play.
Distribution path
Content/SEO on GENIUS-Act compliance, LinkedIn to fintech compliance officers and credit-union CUSO leaders, direct outreach to firms filing rule comments (comment letters are public and name the buyers), partnerships with reg-consultancies for white-label.
Pricing hypothesis
$300–$1,500/mo subscription for the tracker+templates; $5k–$25k one-time for a white-label license or a done-with-you readiness package to consultancies.
Technical difficulty
Low as a documentation/data product; HIGH and likely disqualifying if scoped as an actual KYC/reserve-attestation SaaS that banks integrate (needs SOC2, security review, vendor due diligence).
Legal / regulatory risk
Moderate: must avoid appearing to give legal/regulatory advice or guaranteeing compliance; templates only, with clear disclaimers. Content risks obsolescence as rules change (mitigated by the 'living tracker' model).
Platform dependency
None — no platform owner to deplatform it; built on public Federal Register data.
Founder fit
Partial. It rhymes with his FMCSA mandate-tooling edge (read a federal rule → serve a forced filer), but the buyer here is a sophisticated regulated financial institution, not a small compelled filer paying per upload — no per-transaction portal-submission hook, and the KYC core sits with entrenched incumbents. Fit is real for the readiness-documentation wedge, weak for the full compliance-engine framing.
Breakout potential
Moderate: could expand into a broader 'crypto/fintech charter readiness' data business, but the permitted-issuer population is small and slow to form.
Final recommendation
WEAK PASS / narrow B at best. Pursue ONLY as a lightweight, low-cost rule-tracker + template data product sold partly through consultancies — do NOT build it as a bank-grade KYC/attestation SaaS. Better founder-fit opportunities exist in mandates with large, unsophisticated, per-filing forced-buyer classes.
Next action
Spend one day crosswalking the CIP rule (id 4797) and OCC PRA forms into a requirements matrix and publish an explainer; measure inbound from issuer/consultant compliance leads before investing further. If inbound is thin, drop it.