Capability Map | Dreamineering

CAPABILITY MAP
════════════════════════════════════════════════════════════

  CAPABILITY                   MATURITY     GAP?
  ──────────────────────────   ────────     ────
  Move Protocol Engineering    ████░ (4)
  Next.js/React Frontend Dev   ████░ (4)
  Fiat Payment Rail Config     █░░░░ (1)    CRITICAL GAP
  NZ Wholesale Compliance      ██░░░ (2)
  KYC/AML API Integration      ███░░ (3)

════════════════════════════════════════════════════════════

Investment Strategy:
- Core Capabilities: Move protocol design and seamless zkLogin Next.js frontend are our proprietary differentiators. Build heavily here.
- Generic Capabilities: KYC/AML and E-signing are commodities. Buy (SumSub/DocuSign).
- Critical Gaps: We need robust local fiat integration (Stripe/Bank APIs) to handle syndication funding and dividend payouts. P1 Priority to figure out the local payment orchestrator.

Questions

Which capability in the sui real estate tokenization map is the hardest to replicate — and does that make it the moat?

Which capabilities are table-stakes (must have) vs differentiators (competitive edge) — and is the build order aligned?
If a new competitor entered with 10x engineering resources, which capabilities would they copy first and which would they build differently?
Which capability gap, once closed, would unlock the most other capabilities?

Questions​

Questions