Luma — CANNEX Case Study
Applies the M&A Playbooks to CANNEX.
Next steps
- Request info into our data room once NDA signed
- Request consultancy report from CANNEX
- Engage external tech DD firm
- Align internal resources
- Hire Corp Dev lead
Section 1 — Background
| Item | Detail |
|---|---|
| Target | CANNEX Financial Exchanges |
| Geography | Canada (HQ); ~50/50 Canada / US revenue split |
| Revenue / Net income | ~$10M / ~$2M (profitable, low growth) |
| Customer base | 40–50 annuity carriers; 630+ financial institution clients |
| Employees | tbd |
| Ownership | tbd (founder appetite to sell — confirmed) |
| Existing Luma relationship | Active partnership |
| Indicative price (our estimate) | $20–35M |
What's in scope. All of CANNEX, or two separable components: (a) Annuity Business US/Canada, (b) Deposits & Funds Canada. Full is our preferred.
Section 2 — Strategic Case
2.1 Why Acquire
Strategic drivers.
- Ecosystem Focus. CANNEX adds carriers and clients into the multi-sided network — each new participant raises switching costs.
- Play to Win. Annuity data coverage means buying CANNEX gives Luma a leading position in US/Canada annuity data.
Acquisition criteria.
- Network Effects. 40–50 carriers and 630+ FI clients deepen the multi-sided network materially.
- Parenting Advantage. Strong — detailed below.
- Ecosystem Lock-In. Annuity data is a critical layer competitors cannot easily replicate.
Build vs. Buy vs. Partner.
- Not Build. 40–50 carrier relationships take years to build. Annuity infrastructure is a Luma gap we don't have engineering capacity to close standalone.
- Not Partner. We already are. Continuing leaves us exposed if iCapital buys them.
- Buy. Speed, lock-in, and removal of a competitive risk.
2.2 Why Luma
How can we show that Luma is the best acquirer. CANNEX gets a different outcome under Luma vs. a financial buyer.
Modernisation. CANNEX's tech is dated — no AI, weak frontend, limited API. Luma's data architecture, AI capabilities, and integration patterns close these gaps quickly.
Distribution and pricing. CANNEX undercharges. Luma's distribution across SP, Annuities, and Life puts the same product into a larger base; multi-issuer leverage gives pricing flexibility CANNEX doesn't have standalone.
Key person retention. Unlike a financial buyer, Luma can structure earnouts and retention aligned to operational success. The team stays because the work continues to matter — addresses a concern CANNEX raised directly.
Annuity analytics. CANNEX has the data and relationships; what they lack is in-house analytics expertise. Luma has that capability and it's central to our ecosystem play.
Why not formal process.
- For CANNEX. Operational continuity and growth vs. cashflow extraction by a PE buyer.
- For the founder. Phased payout, retention-linked earnouts, upside through Luma Equity.
- Speed and certainty. Bilateral closes in 3–4 months. Formal process will take longer and risks leak to staff, customers, and carriers.
- For Luma. No competitive bidding inflation. Keeps iCapital out.
2.3 Why Now
Three factors encourage acting in the near term.
- iCapital's Hexure acquisition (March 2026) signals consolidation pressure across annuity infrastructure. CANNEX is the next logical target.
- Founder appetite to sell is currently active. That window may close.
- CANNEX's modernisation gap will only get worse and gap to those using AI will grow.
Section 3 — Five Gates Status
3.1 Gate 1 — Strategic
Status. Pass — see Section 2 Strategic Case.
Outstanding. Review EZRA consultancy findings (external report CANNEX commissioned).
3.2 Gate 2 — Commercial
Status. Open — awaiting data room and EZRA Findings report.
Deal-specific risks.
- Pricing. They've been unable to upsell — will the customer base accept higher pricing post-acquisition?
- Limited sales team. How strong are the relationships and what's critical for them to move to Luma (tech or people)?
3.3 Gate 3 — Technical
Status. Open — awaiting data room.
Known findings.
- No AI use
- Weak frontend
- Only a couple of carrier integration APIs
- Pricing calculation engine likely needs refactoring
Deal-specific risks.
- Tech debt. Need for modernisation suggests accumulated tech debt and inflexible infrastructure.
- Key engineer risk. Legacy systems with limited API development create dependency on the people who built them.
3.4 Gate 4 — Financial & Legal
Status. Open — awaiting data room.
Known findings.
- ~$10M revenue, ~$2M net income
- Profitable, solid track record, low growth
- Reinvestment of profits
Deal-specific risks.
- Cross-border. US/Canada split implications.
- Carrier contracts. Change-of-control risks on existing relationships with US parent.
- Pricing flexibility. Ability to change pricing terms to align to Luma strategy.
3.5 Gate 5 — Integration Feasibility
Status. Open.
Integration approach.
- Keep the carrier relationships
- Replace / integrate the tech with Luma (frontend rebuild)
- Identify cross-sell opportunities
- Re-price
Deal-specific risks.
- First Luma acquisition. Resource identification and allocation will take time. Potential drag on other parts of the business.
- Parallel integration capacity. Cannot do more than 1 integration in parallel — may block GenTwo in near term.
Section 4 — Deal Structuring
Preliminary positions. To be developed during DD.
4.1 Structure
| Item | Position |
|---|---|
| Asset vs share purchase | tbd — cross-border (US/Canada) implications to assess |
| Deal jurisdiction | tbd |
| Customer contract novation | Change-of-control risks flagged in Gate 4 |
4.2 Price & Payout
| Item | Position |
|---|---|
| Cash up front | tbd |
| Founder payout | Lump sum or phased installment with declining minority share — founder's preference |
| Equity component | Open — Luma Equity upside available |
| Earnout | tbd — milestones likely tied to operational targets |
| Working capital adjustment | tbd |
4.3 Retention & Transition
| Item | Position |
|---|---|
| Key talent retention | Identify critical roles and retention period |
| Founder transition / knowledge transfer | tbd |
| Non-compete / non-solicit | tbd |
| Transition services | tbd |