If you are reading this from inside a large MedTech organization, you may be thinking: we have ten times the engineering staff. Why can’t we just build this ourselves?

We-Should-Just-Build-This-Ourse…

It is a fair question.

But software has a well-known paradox. Adding more people to a complex project does not make it go faster. It usually makes it go slower. More coordination. More handoffs. More meetings about meetings. More surface area for misalignment

A large IT organization is optimized for breadth — supporting dozens of systems, managing infrastructure, keeping the lights on across the enterprise

That is valuable work.

But it is fundamentally different from building and sustaining a deep vertical product over a decade.

The people on your team have day jobs. They run devices through regulatory pathways, manage quality systems, support manufacturing, and commercialize products globally

Building a regulated platform is not a side quest.

It is a second company

What the Numbers Actually Look Like

When people compare license fees to internal builds, they stop at the wrong baseline

The real comparison is:

Licensing a specialized platform
versus
Standing up and operating a regulated software company inside your enterprise

Product management.
UX research.
Engineering.
Regulatory SMEs.
Validation and QA.
Security operations.
Compliance programs.
24/7 support.
Infrastructure.
Multi-year modernization

AI makes some of that faster.

It does not make any of it optional

With a specialized vendor, that investment is amortized across an entire customer base.

With an internal build, the full long tail of ownership falls on you

And most of that spend ends up recreating the 80 percent that has already been solved — all because someone decided the remaining 20 percent justified building from scratch

The return on that 20 percent rarely survives honest scrutiny.

‍

The Questions That Should Keep You Honest

It is easy to get excited about how fast something can be built.

The harder exercise is asking what happens in year three, year five, year eight

When your VP of Regulatory Affairs leaves, who maintains validation documentation?

When regulations change across jurisdictions simultaneously, who redesigns workflows and pushes a validated release before the deadline?

When an auditor asks for change control history and disaster recovery test results, who is accountable?

Internal initiatives often stumble not because engineers cannot prototype, but because sustaining them for a decade is brutally hard

Sponsors move on. Budgets change. Teams reorganize.

Regulatory systems do not get to pause.

They must remain inspection-ready through acquisitions, divestitures, and leadership turnover

Systems of record are commitments, not experiments

AI Changed the Tools, Not the Gravity

I am genuinely excited about what AI enables. It will reshape regulatory operations, reduce headcount growth, compress timelines, and raise expectations for every vendor in this space

What it has not done is repeal gravity.

Most of what AI replaces today is busy work. That is enormously valuable. But busy work was never the strategic bottleneck

The hard parts remain.

‍
Deciding submission strategy.
Interpreting regulator feedback.

‍
Designing defensible workflows.
Staying inspection-ready.
Running global rollouts

Agents help teams move faster.

They do not decide what is safe, defensible, or durable

In MedTech, software is not just built.

It is designed, governed, operated, and defended

And gravity still applies.