Health-Tech Founders // Advisor + Builder

Health-tech founders: build the AI product you can defend clinically and ship.

I help founders pressure-test the clinical logic, narrow the MVP, set responsible AI boundaries, and turn the next decision into specs, a prototype, or shipped software.

Work with an MD, Nakama Health founder, and hands-on builder for one decision session, a clinical product review, a build sprint, or retained advisor-builder support.

Dr. Marino Šabijan presenting on stage in front of a healthcare visual display.

Current build

Nakama Health — health safety net for trusted communities.

Google Calendar reserves the time only; I confirm fit and payment details before the session is locked in.

Medical doctor
Nakama Health founder
Shipped health products
Hands-on builder

Founder Bottlenecks

Where health-tech products get expensive before they get trusted.

The expensive mistakes usually happen before launch: too much scope, unclear AI behavior, weak workflow fit, and a first build that does not prove the right thing.

Scope

The platform grows before the wedge earns trust.

Most health-AI products do not need a smaller ambition. They need a first version that proves the workflow, the trust model, and the product behavior before the roadmap adds more surface area.

Trust

The risky moment is what the product does next.

The product needs to know what it can say, what needs review, what should route to a human, and what it should not answer at all.

Workflow

The user, buyer, reviewer, and risk owner may be different people.

A health-tech product has to fit the real room: the person using it, the person paying for it, the person reviewing it, and the person carrying the downside when something goes wrong.

Build

Advice is only useful if it changes the product.

The output should not be a deck of opinions. It should be a narrower product, clearer AI boundaries, a better founder narrative, and a path to the first useful build.

Founder Scope

Make the clinical product decision before it becomes engineering debt.

Use this when the product is important enough to get right: the clinical claim, the workflow, the AI behavior, the MVP slice, and the build path.

The one workflow worth proving first

The clinical claim the product can responsibly make

Where AI should answer, assist, escalate, or stay quiet

Patient, clinician, operator, and buyer realities that change the product

The founder narrative for investors, partners, and early design partners

The smallest shippable slice that creates evidence

Ways To Work

Start with the decision. Continue only when the build path is real.

Focused review

Best first step when the product feels fuzzy

Clinical Product Review

Pressure-test the idea, prototype, workflow, roadmap, or pitch before the team commits to the wrong first product shape.

  • Clinical product critique
  • AI boundary map
  • Workflow risk review

Build sprint

Prototype, MVP slice, or technical path

Health-AI Build Sprint

Turn a validated decision into a product slice the team can build, test, demo, or hand off without pretending it is the whole company.

  • Product brief
  • User journey
  • AI behavior design

Retained support

Monthly or milestone-based

Retained Advisor-Builder

Ongoing clinical product judgment, roadmap pressure, architecture review, and hands-on build support when the decisions keep compounding.

  • Founder decision support
  • Roadmap pressure-testing
  • Product and architecture review

90 minutes

Start here if the decision is unclear

Decision Session

A focused session for one product, AI boundary, MVP, launch, partner, or clinical trust decision that needs a sharper next move.

  • Decision review
  • Tradeoff map
  • Product boundary notes

Working Method

How the work turns ambiguity into a buildable next move.

A health-AI product becomes easier to build when the clinical job, AI behavior, workflow owner, and first evidence slice are separated.

01

Define the health job

We name the patient, clinician, operator, or founder workflow the product must improve first.

02

Separate help from risk

We decide where AI can answer, assist, request review, escalate, refuse, or stay quiet.

03

Cut the product to evidence

We narrow the MVP to a useful slice that can be built, tested, shown, or handed to a team.

04

Ship, hand off, or keep advising

The work can stop at decision support, continue into specs, or turn into hands-on product and build support.

Trust Boundary

Clinically serious, without pretending one page solves compliance.

This is clinical product judgment and builder-level product execution: strategy, workflow design, AI behavior, MVP scope, and implementation support. Legal, regulatory, privacy, insurance, security, and medical compliance questions should be reviewed with qualified specialists.

Product strategyClinical workflowAI boundariesMVP scopeBuild support

Open a channel

Have a health-AI product decision that should not be guessed?

Bring the product, stage, users, constraints, and the decision in front of you. If there is a fit, we use the call to turn the ambiguity into the next buildable move.

Book Decision Session Email Marino

Google Calendar reserves the time only; I confirm fit and payment details before the session is locked in.