About PlanSurg

Built around the point where surgical intent meets technical execution.

PlanSurg was created to help close a common gap in digital surgical workflows: the space between what a clinical team intends and what a technical process ultimately delivers.

Why PlanSurg exists

Software alone does not understand the surgical setting.

Today's tools can segment anatomy, simulate procedures, and produce sophisticated designs. But software alone does not understand how those outputs will be reviewed, produced, and used in a real surgical environment.

PlanSurg brings surgical-use perspective into that space. We connect clinical objectives with technical planning, careful review, training, and workflows that make sense for the people responsible for the work.

Matheus Henkes, founder of PlanSurg
Matheus
Henkes

Founder

Experience on both sides of the workflow.

Matheus Henkes is a Brazil-trained dentist with postgraduate specialization in Oral and Maxillofacial Surgery and Traumatology. He brings more than ten years of experience in dental environments, seven years in hospital settings, and direct involvement with digital surgical workflows since 2022.

Working across dental and hospital environments showed him a recurring gap. Technically capable planning can still miss what matters in practice when it is developed without enough understanding of the surgical setting, the way teams communicate, and how the final result will actually be used.

That experience led Matheus to create PlanSurg as a bridge between clinical intent and technical execution. The company brings surgical-use perspective to planning, design, quality review, training, and workflow development while the appropriately licensed provider retains clinical authority.

His business education also informs how PlanSurg is being built: not as knowledge held by one individual, but as a disciplined and teachable company with processes that can be reviewed, improved, and carried forward as the organization grows.

Built by a surgeon. Designed for surgical teams.

How we think about the work

Provider-supportive. Software-centered. Manufacturing-light.

Responsibility should be easy to understand, technical work should reflect its intended surgical use, and growth should not depend on lowering the standard of review.

Start a conversation