# PIASSES Investor Presentation Transcript

15-page investor presentation. Research last verified: 2026-08-19.

Original PDF: /investor/deck/PIASSES_Investor_Presentation.pdf

## Slide 1. Canada's financial-data layer is being rebuilt.

PIASSES. Canada's financial-data layer is being rebuilt. A Canadian-controlled control plane for institution-grade financial data. Consumer-driven banking. AI and agents. Digital sovereignty. PSS is the corporate operating entity. PIASSES is the product. VC / Investor Meet | Canada First.

## Slide 2. Four shifts are converging in Canada.

Thesis. Four shifts are converging in Canada. PIASSES is built for the infrastructure layer that sits beneath applications and above raw bank pipes. Consumer-driven banking: screen scraping gives way to consented, supervised APIs. AI and financial agents: machine-readable financial facts become a new trust primitive. Digital sovereignty: control of data, keys, operations and evidence matters. Payments modernization: Canada is modernizing critical financial rails. The opportunity is the control plane for institution-grade financial data.

## Slide 3. The market is bigger than connectivity.

Market. The market is bigger than connectivity. The value is turning permissioned financial data into reliable infrastructure for institutions, developers and AI agents. About nine million Canadians estimated to rely on screen scraping today. Demand is proven, but the rail is not trusted enough for the regulated future. Stack: connectivity and consented access; source evidence; canonical records; quality and provenance; deterministic intelligence; AI-ready financial infrastructure. Where PIASSES aims to sit: above the pipe, below the product.

## Slide 4. Banks need evidence, not just APIs.

Problem. Banks need evidence, not just APIs. As financial data becomes regulated and machine-consumed, institutions need lineage, freshness, corrections, replay safety and operational accountability. Meaning shifts: pending posts, corrections supersede, balances go stale, missing is not zero. Payload control: raw institution payloads should not leak into product, audit or agent surfaces. Operational safety: conformance, restart safety, checkpointing and schema-drift handling. Explainable facts: messy outputs become financial facts with stated provenance.

## Slide 5. Canada needs infrastructure it can control.

Canada first. Canada needs infrastructure it can control. Sovereignty is not only where data sits. It is who controls the keys, operations, evidence, recovery and roadmap. Policy tailwind: Canada is prioritizing sovereign data, compute, cloud, talent and procurement. High-trust category: financial data sits close to identity, credit, payments, taxes and family security. Domestic option: foreign platforms can be partners, but should not become the whole rail. Practical sovereignty equals IP, governance, region control, key custody, auditability and recovery rights.

## Slide 6. The control plane for Canadian institutions.

Product. The control plane for Canadian institutions. PIASSES validates institution APIs, preserves source evidence, normalizes records, and delivers strict REST and MCP interfaces for trusted products and agents. Conformance: validate institution-owned read APIs. Evidence: quarantine raw payloads and preserve source observations. Canonicalization: turn fragmented records into stable financial facts. Delivery: expose REST and MCP through one shared core. Intelligence: generate deterministic signals, not black-box advice. Architecture: Institution APIs to adapter boundary to source observations to canonical records to REST plus MCP to intelligence. Implemented today: domain contracts, fail-closed consent and authorization, REST and MCP, PostgreSQL sandbox runtime, deterministic intelligence and institution conformance sandbox.

## Slide 7. More than a deck. Not yet production open banking.

Current product foundation. More than a deck. Not yet production open banking. PIASSES currently runs as a local infrastructure sandbox using synthetic data. The architecture is real; live institution connectivity is not claimed. Shared core: organizations, clients, consumers, consents, connections, accounts, balances and audit events. REST plus MCP: one capability registry aligns interfaces, business logic and authorization. Consent plus auth: deterministic lifecycle, separate client scopes and fail-closed checks. Canonical data: accounts, balances, transactions, provenance, freshness and factual quality. Persistence plus audit: PostgreSQL persistence, idempotency and transactional auditing. Institution sandbox: fictional Canadian institution lab with adapters and conformance testing. Not yet claimed: live bank connectivity, production deployment, accreditation, live consumer financial data, payment initiation.

## Slide 8. Start with trust. Expand into the data layer.

Wedge. Start with trust. Expand into the data layer. PIASSES enters through conformance and sandbox readiness, then expands into canonical delivery, intelligence and sovereign operations. Stages: conformance labs; durable ingestion; institution pilots; developer APIs; sovereign deployment. Moat: provenance model, data semantics, institutional trust, Canadian IP and sovereignty controls. Business model: B2B SaaS, institution licensing, developer usage, support and deployment services. Capital edge: non-dilutive programs can extend runway without replacing venture capital. Beachhead first, then the data layer. Each stage compounds the evidence base.

## Slide 9. The incumbent is strong. The market structure is changing.

Competition. The incumbent is strong. The market structure is changing. PIASSES is not claiming greater coverage or scale today. The thesis is independent infrastructure for the regulated era. Flinks: strongest Canadian incumbent in aggregation and enterprise distribution. Existing connectivity, bank relationships and fintech distribution PIASSES does not match today. National Bank acquired control in 2021; its 2025 annual report identifies Flinks as a subsidiary. The PIASSES thesis: Canadian-controlled and independently owned. Institution-neutral commercial alignment. Designed around standardized institutional APIs as the framework emerges. Provider-neutral canonical data, consent, provenance, freshness and quality. REST and MCP over the same core. We are not claiming a defensible advantage today. The opportunity is to build trust, integrations and commercial relationships before Canada's new rails become entrenched.

## Slide 10. Enterprise contracts plus usage-based delivery.

Business model and go-to-market. Enterprise contracts plus usage-based delivery. Revenue begins with institutions and grows with the breadth and usage of the platform. Recurring: annual platform contracts for conformance, canonical data, monitoring and support. Land: implementation services, adapters, conformance work and managed onboarding. Expand: usage-based fees tied to consented data delivery and developer or agent usage. Go-to-market wedge: target credit unions, regional institutions and regulated service providers; motion is founder-led readiness conversation; proof is conformance results and pilot evidence. Founder-led design partnerships reduce product mismatch and enterprise sales-cycle blindness.

## Slide 11. Eighteen months to a bank-ready pilot foundation.

Roadmap. Eighteen months to a bank-ready pilot foundation. The roadmap is staged so progress does not depend on a guaranteed regulatory launch date. Today: local infrastructure sandbox with shared core, REST/MCP, consent, canonical records, PostgreSQL and fictional institution lab. 0-6 months: durable institution ingestion with source observations, checkpoints, replay safety and institution-to-canonical bridge. 6-12 months: Canadian-hosted pilot environment with production-path authentication, security controls, operations and onboarding. 12-18 months: two to three design-partner pilots to validate urgency, procurement ownership, pricing, integration value and commercial model. Legal and IP hygiene, then durable data movement, then institution evidence, then pilots.

## Slide 12. Funding the institution-ready bridge.

Funding. Funding the institution-ready bridge. The next stage connects the implemented planes into a durable institution-to-intelligence pipeline, then converts progress into pilots, IP and institutional traction. Capital purpose: connect the implemented foundation to durable institution ingestion, pilot operations, and design-partner evidence. Build: durable observations, checkpointing, replay safety and canonicalization. Prove: restart safety, duplicate prevention, audit integrity and REST/MCP parity. Partner: banks, credit unions, fintech builders and Canadian infrastructure networks. Protect: IP strategy around provenance, conformance and sovereign control. Investor capital to engineering team to pilot evidence to IP filings to non-dilutive leverage. Financing structure and terms are discussed directly with prospective investors.

## Slide 13. Two founders, complementary execution lanes.

Founders. Two founders, complementary execution lanes. Product architecture and financial systems paired with strategy, fundraising, partnerships and go-to-market. Andy Shah, Founder, Product and Financial Systems. MBA, NYU Stern. BS Finance, University of Cardiff. Finance experience in Toronto. Leads product architecture and technical execution. Sarthak Tripathi, Co-Founder, Strategy and GTM. MBA, Liverpool Business School. 14+ years in growth leadership. Positioning, fundraising and partnerships. Leads institutional storytelling and GTM. Shared operating trust across fintech, AI, financial systems, GTM, fundraising and Canadian infrastructure storytelling.

## Slide 14. Investor objections and prepared answers.

Appendix. Investor objections and prepared answers. Is this just Plaid for Canada? No. Connectivity proves demand. PIASSES builds the control layer for conformance, provenance and canonicalization. Why not have banks build it? Banks can build internal pieces. PIASSES productizes shared evidence, tests and developer surfaces. Why is this not too early? The framework direction and oversight path are public. Early enough to build ahead. What is actually built? Domain contracts, consent, REST and MCP, PostgreSQL sandbox, intelligence and conformance lab. Is government support guaranteed? No. It is optional leverage, not the business model. Is sovereignty just marketing? No. It means IP, governance, processing, key control, access evidence and recovery.

## Slide 15. Evidence base and diligence folder.

Appendix. Evidence base and diligence folder. Finance Canada and Canada Gazette: consumer-driven banking. Bank of Canada: oversight path. Government of Canada: digital sovereignty framework. FCAC: open banking information. Payments Canada: modernization. Market validation: Plaid, Flinks and open-banking research. Diligence folder: product map and technical architecture memo; repository milestone summary by pull request; REST and MCP sandbox demo script; institution conformance sandbox summary; data-sovereignty architecture memo; 12-month roadmap and hiring plan; IP ownership and capitalization summary. PIASSES: Canadian-controlled infrastructure for trusted financial-data access.