Product and business development at a payments-API SaaS firm carries d224 and the CPMI brief series through three standing artefacts: the regulatory-positioning deck used in bank and PSP sales calls, the 18-month product roadmap on ISO 20022 readiness, and the FPS-API addressable-market TAM deck used in board and investor reviews. Three AI failures on this regulation hit those three artefacts directly.
Opus 4.7 returned a reconstructed stakeholder taxonomy that misroutes the positioning deck, Sonnet 4.6 manufactured a November 2026 ISO 20022 cutover that misframes the roadmap, and Opus 4.7 returned a 57-FPS count with no operator mix that undersizes the TAM. Every one is caught fast by an externally-facing reader: a customer counsel, a customer compliance officer, or a board reviewer.
What the AI got wrong, and why it matters here
Three failures, three different customer-facing or investor-facing artefacts. Every one will be caught quickly by an external reader the SaaS firm cannot control.
Finding 1: Reconstructed stakeholder taxonomy
Opus 4.7 returned a clean stakeholder taxonomy across d224's 10 recommendations, built from category labels rather than the recommendation text. A SaaS regulatory-positioning deck built on that taxonomy targets the wrong buyer persona for each recommendation.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47.
Finding 2: Fabricated November 2026 ISO 20022 cutover
Sonnet 4.6 committed to a hard November 2026 structured-address-only cutover for ISO 20022 cross-border payment messages, framed as a d230 commitment. The d230 source does not state that date. A product roadmap or customer pitch deck quoting the AI line will be contradicted the moment a customer compliance officer reads d230 directly.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009-Sonnet46.
Finding 3: Compressed FPS count, operator mix dropped
Opus 4.7 cited the 2025 monitoring survey at 57 operational FPS with no operator-type breakdown. sp231115 gives 70-plus operational, 14 cross-border-enabled, 24 in the planning pipeline, 40% central-bank and 35% private. A TAM deck built on the AI count undersizes the addressable rail universe and drops the operator-type signal that drives partner-versus-direct channel strategy.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q010-Opus47.
When this hits the product calendar
Product and bizdev pulls CPMI material on four standing artefacts: the regulatory-positioning deck, the ISO 20022 product roadmap, the FPS-API TAM deck, and the board investment case.
| Standing artefact | Where the AI risk surfaces | Failure mode |
|---|---|---|
| Regulatory-positioning deck | Stakeholder-to-recommendation buyer-persona mapping | Finding 1 |
| ISO 20022 product roadmap | Cutover-date commitments | Finding 2 |
| FPS-API TAM deck | FPS count and operator mix | Finding 3 |
| Board investment case | All three | All three |
Aggregate impact on the team
Together the three errors corrupt the positioning, the roadmap and the TAM in one product pack. The downside is an externally caught misstatement: the customer compliance officer, the board reviewer or the prospect's counsel reads the deck before the SaaS firm's second line does.
| Risk Impact | Count | Affected findings |
|---|---|---|
| 0 |
What this team should do
Tag the d224 stakeholder taxonomy, the d230 ISO 20022 cutover date and the FPS count plus operator mix as known-failure outputs. Any AI draft for a customer-facing or investor-facing deck must be returned through a primary-source check before it ships externally.
Detection patterns to add to AI-review
- Stakeholder-to-buyer-persona mappings on d224 must be verified against the recommendation text.
- ISO 20022 cutover-date assertions must be verified against the d230 source text and technical annex.
- FPS counts and operator-mix percentages must trace to sp231115 or to a numbered CPMI brief.
How RLB can help
RLB tracks AI failures on d224, d230, the CPMI brief series and the Tara Rice November 2023 speech, refreshed against live AI subjects on rotation. SaaS product teams can wire the catalogue into the customer-deck review step so the three failure shapes are caught before the deck ships to a bank, PSP or investor audience.