GLEMO - Partner Fallback / Regulated Rails Plan

Purpose: show that the current bank partner accelerates the first implementation but does not define the business. Glemo owns the operating layer. Regulated partners provide replaceable rails.

Core Position

The bank partner is an accelerator, not a single point of failure.

Glemo should position the RWA layer as partner-agnostic infrastructure. The initial bank relationship can help validate the first deployment, but the system should support alternative regulated providers.

Provider Categories

Provider Type Role Priority Status Evidence Needed
Digital bank / fintech Accounts, payment rails, distribution, KYC support High Current anchor + alternatives needed LOI, scope, technical terms
Custodian / trustee Custody or representation support High To source Licensing review, term sheet
FIDC / securitization partner Brazil regulated structure High To source Mandate letter, legal fit
KYC/geofencing vendor User eligibility and jurisdiction controls High To source Vendor quote, policy fit
Market maker Token market depth and launch support Medium-high To source Terms, track record
DEX/CEX partners Listing and liquidity venues Medium In progress / to confirm Relationship status, criteria
Legal counsel BVI / US / Brazil memo High To confirm Engagement letter

Bank Exit Scenarios

Scenario Impact Mitigation
Bank delays pilot RWA launch shifts by 3-6 months Launch AI Agent, brokerage, marketplace, token governance first
Bank exits RWA layer must switch provider Use custodian/trustee/FIDC/securitization/payment alternatives
Bank limits jurisdiction RWA access narrower than expected KYC/geofenced launch and jurisdiction matrix
Bank cannot support token-related flow Token and RWA remain economically separated Token remains utility/incentive layer only

Diligence-Ready Message

Glemo owns demand, workflow, data, product, token governance, and reporting. Regulated rails can be provided by a bank, custodian, trustee, FIDC/securitization partner, KYC/geofencing vendor, or payment provider. The first bank partner accelerates the path, but the architecture is multi-provider by design.

Open Inputs Needed From Founder

  1. Current bank name and status:
  2. signed contract;
  3. LOI;
  4. verbal relationship;
  5. technical pilot;
  6. strategic conversation.

  7. Alternative provider candidates:

  8. digital bank / fintech;
  9. custodian / trustee;
  10. FIDC/securitization partner;
  11. KYC/geofencing vendor;
  12. market maker.

  13. Which partner functions are mandatory for TGE vs seed vs mature stage.