Dassault Systèmes Spatial
Enterprise SDKs and Platform Products
Own SDK products across meshing, constraint solving, and robotic motion planning for customers building design, simulation, and robotics software.
- Role
- Product Manager, Modeling & Simulation
- Organization
- Dassault Systèmes / Spatial
- Period
- 2023 — Present
$5M
managed product portfolio
90+
enterprise customers
5+
new customer wins
Millions
downstream users through customer apps
Overview
Spatial’s SDKs sit inside other companies’ engineering software. The direct customer is often an OEM, ISV, or developer team integrating an SDK; the downstream user is the engineer, designer, analyst, or robotics programmer who depends on the final workflow.
My portfolio spans CSM/CVM for robust meshing in multiphysics simulation workflows, CDS for geometric constraint solving in design and modeling applications, and robotic path planning for robotics OEMs and ISVs.
The work is to make hidden API and architecture tradeoffs concrete: understand workflows, guide evaluations, and turn evidence into roadmap, enablement, and adoption decisions.
Spatial ecosystem
A few links for orientation in the broader SDK ecosystem. Customer demos, roadmap details, and integration artifacts remain private.
Spatial
A broader view of the 3D SDK platform behind industrial applications.
Visit Spatial
The challenge
- The buyer, integrator, and end user are often different people. A useful product decision has to account for all three without turning every customer request into a one-off roadmap item.
- Meshing, constraint solving, and path planning are evaluated through real workflows: model quality, robustness, performance, API control, integration effort, and the cost of migration.
- Business impact arrives after a long chain: evaluation, integration, customer release, downstream adoption, and expansion. Pilots, design partners, evaluation quality, and SDK usage become important leading indicators.
- The products cross several domains—simulation, CAD/modeling, robotics, GTM, support, and R&D—so the PM role is to create clarity without becoming a middle layer for status updates.
Product approach
Map both customer layers
Understand what the SDK integrator is building, how their downstream users work, where the workflow breaks, and how success will be judged during evaluation.
Make the platform decision tangible
Use C++ POCs, API sketches, customer workflows, and design-partner feedback to turn abstract SDK requests into something customers and R&D can evaluate.
Shape product lines with evidence
Translate discovery, evaluation results, pilot feedback, and commercial context into API decisions, product boundaries, roadmap priorities, documentation, and GTM enablement.
Reduce adoption risk
Treat migration paths, technology enablement, MCP/RAG workflows, compatibility, and developer experience as part of the product—not cleanup work after launch.
Outcomes
Portfolio ownership
Own roadmap, strategy, and GTM input across an approximately $5M product portfolio serving more than 90 enterprise customers.
Customer and revenue impact
Directly contributed to 5+ customer wins over three years and supported product revenue expansion across simulation, design/modeling, and robotics workflows.
Sharper adoption path
Used C++ POCs, robotics pilots, and MCP/RAG enablement work to help customers evaluate SDKs faster and reduce ambiguity before R&D scaled the work.
What I took away
Platform work has to stay close enough to real workflows to shape APIs, not just collect requirements.
The hard part is connecting customer evidence, developer experience, R&D constraints, and delayed adoption signals into decisions that hold up at enterprise scale.
Next case study