Case Study - Partnership-as-Infrastructure for Cross-Border Africa

Overview

What Stripe did for payments, the Partnership Orchestration Engine is doing for partnerships. Two African companies that want to do business together across a border face a stack of problems that have nothing to do with their actual deal: which jurisdiction to incorporate in, how to appoint nominee directors, how to share revenue transparently, how to handle KYC and AML, how to settle in multiple currencies, and how to keep an auditable trail of every change. Today, forming a cross-border partnership SPV across African markets takes anywhere from a week to several months and costs thousands of dollars per setup — with the operational tail handled through spreadsheets, emails, and manual bank transfers. The highest-leverage partnerships on the continent never form, or form so slowly that the commercial window has closed by the time the entity exists.

POE — a joint venture between VGG, Baseone, and Norebase — combines six capabilities that were never meant to sit in the same system, each exposed through a single platform surface. Pre-registered shelf SPVs via Norebase with reset protocols enable 24-hour activation. Baseone-powered multi-currency wallets provide per-project lifecycle SOPs, milestone-linked payouts, and freeze/unfreeze escrow controls. Programmable cap tables track ownership in real time with nominee and beneficial-owner mapping and a cryptographic audit trail. Configurable multi-level waterfall logic releases funds only when milestone, SOP, and validation conditions align — every payout logged to an immutable ledger. A jurisdiction-specific compliance engine handles tax deadlines, regulatory calendars, and KYC/AML gates that block activation until checks clear. And a dynamic legal document engine handles versioned agreements, amendment workflows, and multi-party digital signing. On top of these, a public API plus webhooks lets third parties programmatically create SPVs — opening the door to nominee marketplaces and white-label partner flows.

POE is built around two principles. Choreography over orchestration: services publish events and downstream services react independently, giving low coupling and horizontal scalability without a brittle central workflow engine. Simulation-first development: external integrations are fronted by simulation layers matching production API contracts, so engineering velocity doesn't stall while sandbox credentials are being negotiated with regulated partners. Auth and access control are role-based; phone-number-based region detection routes users to the right currency and jurisdiction defaults; cap-table mutations are logged in an append-only ledger; sensitive documents land encrypted; the deployment path is fully automated and secrets-managed.

What we did