Aspects:

• Technical

  • Based on CTrack

    • Support for using CAD files

    • Use VTK

    • Incorporate AI via ONXX

      • Possibility to specify own models

    • Edge deployment

      • CTrack engine model

  • Niche applications

    • Sail shape measurement

      • Camera used as photogrammetric device

        • Eliminate motions

• Commercial

  • CTech as technical partner NOT Reseller

• Partnership

  • Conditions
  • Get leads / projects
  • Mutual transfer discounts

  • Initial step maximized risk at CTech side

    • Invest in development

    • Invest in Xavia device

  • How about upgrades / expensive mandatory upgrades ?

Claude

What you can skip:

• Explaining what CTrack does or your technical credibility — he knows
• Formal positioning and "selling" yourself — the trust baseline is already there
• Dancing around sensitive topics — you can be direct

What you can leverage:

1. Candid conversation about where Xenomatix actually stands — you can ask directly about their financial runway, what the buy-and-build strategy really means, and whether they're under pressure from investors to show growth
2. His honest assessment of the opportunity — does he genuinely see a fit, or is this more exploratory? Former colleagues tend to be straight with each other
3. The real story behind the Xavia launch — is it on track, are there issues, what's the actual market reception been?
4. His take on the lidar market shakeout — he mentioned in earlier interviews that many lidar companies didn't survive. What's his view on long-term sustainability?

One thing to be careful about:

The personal relationship cuts both ways. Make sure the business terms are properly documented and fair, regardless of the friendship. It's worth being explicit early on: "Filip, we've known each other a long time, which is why I want to be extra clear about expectations on both sides so this works professionally."

How long has it been since you last spoke with him? And do you know if he reached out to you specifically, or did this come through another channel?

The real questions for this call:

1. Why now? What's driving the formalization? Is it the Xavia launch, investor pressure to show ecosystem, or genuine strategic vision?

2. What does "partner" actually mean to them vs. continuing as a contractor?

   • More projects guaranteed?
   • Co-marketing / joint customer calls?
   • Revenue share on solutions vs. hourly billing?

3. The investment asymmetry you flagged is the key issue:

   • You invest in development (your time, opportunity cost)
   • You invest in Xavia hardware (cash outlay)
   • What's their skin in the game beyond "we'll send you leads"?
4. Formalize what you've learned informally — you probably already know their financial health, internal priorities, and where they're headed. The question is whether the partnership terms reflect that reality.

Given you know Alain (CFO) and Johan too, is this call with Filip alone or are the other founders involved in the partnership decision?

After phone call

No direct investment other than Xavia sensor

No direct competition

Their involvement in Coseyn is undefined at the moment, maybe not important

Partnership Exploration - Deep Dive (Dec 2025)

Partnership Overview

Mermaid Code:

mindmap
  root((Xenomatix Partnership))
    Company
      Founded 2012 Leuven
      ~50 employees
      CEO Filip Geuens
      €10-22M funding
      Buy-and-build strategy
    Products
      XenoLidar Xavia
        20Hz solid-state
        AI processing
        Sensor fusion
        Sept 2025 launch
    Applications
      Sail shape measurement
      Wind turbine blades
      Livestock volume
      Ship positioning
    CTech Role
      Technical partner
      NOT reseller
      CTrack integration
      Development investment

Company Research Summary

• Founded: 2012 in Leuven, Belgium
• Size: ~50 employees
• Leadership: Filip Geuens (CEO), Alain (CFO), Johan (co-founder)
• Funding: €10-22M total raised
• Strategy: Buy-and-build approach, survived lidar market shakeout
• Key Product: XenoLidar Xavia (20Hz solid-state, AI processing, Sept 2025 launch)

Technical Architecture

Mermaid Code:

flowchart TD
    subgraph Input["Input Sources"]
        CAM[Cameras/Photogrammetry]
        XAVIA[Xavia Lidar]
        TRACKER[Optical Tracker]
    end
    
    subgraph CTrack["CTrack Core Engine"]
        SYNC[Time Synchronization]
        CALIB[Multi-Sensor Calibration]
        FUSION[Sensor Fusion]
        VTK[VTK Visualization]
        ONNX[ONNX AI Models]
    end
    
    subgraph Output["Outputs"]
        MESH[Dynamic Mesh]
        DEFORM[Deformation Maps]
        REPORT[Reports/Analytics]
    end
    
    CAM --> SYNC
    XAVIA --> SYNC
    TRACKER --> SYNC
    SYNC --> CALIB
    CALIB --> FUSION
    FUSION --> VTK
    FUSION --> ONNX
    VTK --> MESH
    ONNX --> DEFORM
    MESH --> REPORT
    DEFORM --> REPORT

Identified Application Domains

1. Racing Sail Shape Measurement

• Challenge: Dynamic deformation at 10-20Hz with boat motion compensation
• Solution: Photogrammetry + lidar fusion, eliminate platform motion via tracker
• Market: America's Cup teams, Olympic sailing programs

2. Wind Turbine Blade Inspection

• Challenge: Large-scale deformation during operation
• Solution: Ground-based or drone-mounted scanning with CAD comparison
• Market: Wind farm operators, blade manufacturers

3. Livestock Volume Measurement

• Challenge: Non-contact weight/health estimation
• Solution: Overhead lidar scanning with AI body condition scoring
• Market: Agricultural tech, livestock management

4. Ship Positioning & Deformation

• Challenge: Hull flex measurement, docking precision
• Solution: Multi-sensor fusion for 6DOF tracking + surface analysis
• Market: Shipyards, port authorities

CTrack Building Blocks (Already Available)

• ✅ VTK visualization pipeline
• ✅ Multi-camera photogrammetry
• ✅ 6DOF tracking algorithms
• ✅ CAD import/comparison
• ✅ Time synchronization framework
• ✅ ONNX runtime integration

Development Needs

• ⬜ Xavia SDK integration
• ⬜ Point cloud to mesh pipeline
• ⬜ Deformation colormap visualization
• ⬜ Motion compensation algorithms
• ⬜ AI model training for specific applications

Strategic Decision Framework

Option A: Integrate into CTrack Core

Pros: Single codebase, leverage existing infrastructure, broader market appeal
Cons: Longer development, complexity increase

Option B: Standalone Application

Pros: Faster to market, dedicated UX per application
Cons: Code duplication, maintenance overhead

Recommendation: Start with core integration, create application-specific "profiles" within CTrack

Investment Analysis

Next Steps

1. Obtain Xavia sensor and SDK access
2. Build proof-of-concept with sail measurement use case
3. Validate motion compensation approach
4. Define formal partnership terms based on results

Last updated: December 2025 via Claude conversation