The difference between building a product and building a platform

There is a decision that shapes every downstream architectural choice in a health tech company, and most teams make it without realising.

The decision: product or platform?

A product optimises for the user in front of you. It solves a specific problem well. The architecture serves that interaction — a consult, a prescription, a booking. It works. Users like it.

A platform optimises for composability. The question shifts: can another service build on top of this? Can a new brand, a new care pathway, a new clinical context use the same infrastructure without rebuilding it?

The difference matters because healthcare is not one product. A patient's journey crosses consults, prescriptions, dispensing, follow-ups, multiple providers, sometimes multiple brands. A product handles one of those moments. A platform connects them.

The platform decision has to be made early. Not because multiple brands exist from day one — but because clinical infrastructure built for a single use case becomes technical debt the moment the second use case arrives. And the second use case always arrives.

The cost of the platform choice is speed in the short term. The cost of the product choice is coherence in the long term.

For anyone building clinical infrastructure, the question isn't which is easier to ship. It's which one survives the second year.