Healthtech · Pilot decisions

CTO for Healthtech & MedTech

Experienced CTO guidance on one unresolved technical decision: a clinical software handoff, a device/software pilot or a scientific data workflow, each calling for a different domain match.

  • One boundary, one pilot decision
  • Clinical acceptance stays with its owners
  • Experience matched to the evidence gap

Our network includes CTOs, engineering leaders,
and technical advisers with experience at and around companies such as:

IBM Stripe UBS Citi Fujitsu Wipro InHealth GSK TransUnion Deloitte J.P. Morgan
SAP NHS Marie Curie BBC Anthropic CMH Clinic SE Health Sartorius Illumina Achilles Therapeutics Prevayl

Signs your healthtech pilot needs a CTO

A fit is a working product or integrated prototype, an implementation team or vendor, a funded task and authorized access to the evidence needed.

  • Lost between draft and saved note

    A documentation product loses its fit between the draft and the saved note.

  • Outside the lab, it differs

    A prototype differs outside the lab, and it is unclear which bundle differs or what evidence is missing.

  • A computation nobody can repeat

    The author can run the prototype, but another team member cannot repeat the agreed computation.

  • Ownership across teams

    The open question needs cross-team leadership, not configuring a form or repairing one known defect.

Pilot decisions a healthtech CTO helps you make

A CTO could help clarify the operation, data boundary, receiving evidence and cross-team ownership before you commit to a route.

  1. Choose the EHR integration route

    Whether the clinic's existing connector supports the reviewed-note operation or a different permitted EHR interface is needed.

  2. Trace the reviewed version

    A data-flow map, failure cases and how omissions, corrections and failed or uncertain transfers become visible.

  3. Map one system bundle

    Hardware, calibration, firmware, data processing, model and app versions for one interface or test release.

  4. Frame failure hypotheses

    Missing inputs, connectivity loss, timing or stale display behavior, investigated under identified versions and conditions.

  5. Find the repeatability gap

    Dataset provenance, rights, environment dependencies, versions or the conditions for a repeatable run.

  6. Agree a repeatable handover

    What another person must be able to repeat and which evidence the receiving team needs.

Who decides what: clinical, technical and regulatory owners

One person may hold several roles, but each authority must be established; a technical acceptance record does not sign for the other owners.

  1. CTO or technical lead

    Specific architecture and coordination decisions; technical evidence and handover.

  2. Implementation team or vendor

    Build, configuration, testing and maintenance responsibilities.

  3. Clinical owner

    Clinical review criteria, permitted workflow and clinical interpretation.

  4. Partner IT, data, privacy and security

    Institution-specific interface and information-handling acceptance.

  5. Quality and regulatory owner

    Applicable assessment, supporting evidence and authorization within their remit.

  6. Scientific owner, where relevant

    Domain validity, experiment interpretation and limits of conclusions.

From one unresolved boundary to the right CTO

  1. Describe one decision

    Bring the product, the next milestone and the decision your current team cannot yet resolve to the curator.

  2. Explore the fit

    The curator discusses the problem, explores who in the network may fit and accompanies setting up work with a CTO.

  3. Agree a bounded contribution

    Participation and any further work are agreed separately, for one handoff, interface or workflow.

  4. Decide, then hand over

    Technical decisions and remaining limitations go to your receiving owner; implementation stays with your team or a separately agreed provider.

Bring us your case

Describe the product, the next milestone and the decision your current team cannot yet resolve. The curator explores who in the network may fit.

Discuss your healthtech pilot
What we believe

We work best with founders who believe in what they are building

Every founder brings a different challenge. What stays the same is how we approach it.

Grand Rounds video session: David Carroll with CTOs Neil Catton and Edoardo Turelli, and curator Jane Vyshnova
David Carroll Founder of Euryan David came to Grand Rounds with two open questions he wanted pressure-tested before taking them to investors: how Euryan should handle LLM and cloud strategy across different client environments, and whether the core product wedge, dynamic FMEA/8D automation, was the right foundation to build the rest of the roadmap on.
Grand Rounds video session: Susie Williams with CTOs Neil Catton and Jerome MacGillivray, and curator Jane Vyshnova
Susie Williams Founder of LinkEDtohome Susie came to Grand Rounds with two questions she wanted pressure-tested before LinkEDtohome moved beyond its first school: how to scale the team and technology without building too far ahead of real demand, and what needed to be in place around AI liability, training and governance before broader adoption.
Grand Rounds video session with Alexander Gorrie, Krupa Shankar, CTO Berkan Sesen and curator Jane Vyshnova
Alexander Gorrie Founder Alex came to CTO Grand Rounds with several important technical decisions already being actively worked through. One question from the panel reframed the discussion: “How will you know that the result is actually good?” It sharpened the conversation around how those decisions should be sequenced and prioritised.
Grand Rounds video session with Tomas Jankauskas, CTOs Neil Catton and Thomas Döhler and curator Jane Vyshnova
Tomas Jankauskas Founder of Neural DEEP Tomas came to Grand Rounds with a question he'd been wrestling with while bringing AI-driven innovation into Toyota: which ideas to pursue, and how much to build before anything was approved, in an organisation where every new idea needs to pass through many hands.
Grand Rounds video session with Dr. Lars Zimmermann, CTO Reon Smits and curator Jane Vyshnova
Dr. Lars Zimmermann Founder of Ahead Care GmbH Lars came to Grand Rounds looking for an experienced second opinion on the hardware challenges facing MOIO, Ahead Care's wearable care technology. He wanted to explore practical options for the product's development and gain a fresh perspective from someone who had navigated similar challenges in medical wearables.
  • Products with a purpose

    Technology that delivers a real outcome for people, not technology for its own sake.

  • Energy and enthusiasm

    Founders and teams with the passion and drive to address a problem they have seen for themselves.

  • The story before the numbers

    The first question is what you are trying to do and why: what you saw and why you started.

  • Listening more than talking

    Nobody walks in to say “I know better.” We ask what drives a decision and what has not been considered, then work through the options together.

  • Understanding before fixing

    First the people, the business and the why, and what has and has not worked, so the first problem found does not start constant firefighting.

  • Experience, not just knowledge

    Modern and AI tools assist. Architecture, security, recovery and user experience still need people who have built and run real systems.

CTOs in the network, healthtech experience first

As stated in Gabriel Wainmann's profile, he built an edge clinical-handover system for ambulance crews with automatic de-identification and FHIR export.

Jane Vyshnova
About us

Jane Vyshnova

Curator of Grand Rounds

I've spent 12 years building partnerships between founders, technical teams, and the people who fund them. Somewhere along the way I noticed the same pattern over and over: brilliant fractional CTOs, and founders who had no idea they existed, let alone how to reach them.

Grand Rounds is my answer to that gap. The name comes from medicine, when a case is hard, doctors don't decide alone, they bring senior specialists around the table together. I built the same thing for technology.

"People need people. Nothing else works."

I'm the one who listens to your problem, asks the questions you didn't think to ask yourself, and explores which experience in the network is relevant to it.

Jane has been working across the industry since 2014, connecting startups, retailers, B2B companies, manufacturers, and expert teams around meaningful partnership opportunities.

Her experience includes building bridges between companies and ecosystems, ready-made technology solutions, manufacturing-focused initiatives, and sustainability-driven projects. Over the years, she has helped create practical collaboration models between businesses, technology providers, and industry experts.

For Jane, partnership strategy is not just part of the work - it is the DNA of her professional experience. Her focus is on identifying where teams, platforms, products, and industries can strengthen each other and turning those connections into real opportunities.

What founders say after their Grand Rounds session

It's like a hackathon for your real business problems. You bring your challenges and bright minds work on them - with no obligation, no pressure. I walked away with perspectives on investors, encryption solutions, and a connection that could directly benefit my product. Honestly, why rely on one mind, when you can have many?

Saif Alam
Saif Alam CEO at Keepsta

It was an incredibly welcoming space to connect with senior technical minds I wouldn't normally have access to as a non-technical founder. A fantastic opportunity to get real, honest answers to the challenges I was facing - and to walk away with meaningful connections who continue to support me.

Audrey Lee
Audrey Lee Founder of Lumi

CTO Grand Rounds was the best event by far. This is where the founder world and the tech world actually merge, with real introductions instead of leaving people to stay siloed. I was deep in a conversation about cybersecurity and feedback loops - practical advice I could act on immediately.

Hélène Le Roux
Hélène Le Roux CEO at Trippin'

What I valued most was the mix of CTO styles at the table - some all-in on AI, others more measured. As a founder, you don't want someone else's answer, you want enough perspectives to make your own call. I walked away with two strong contacts - people who hit the mark on build support, strategic fit, and investor credibility. The relaxed format made room for real technical conversation, not just quick decisions. Worth coming back for.

Hew Williams
Hew Williams Founder of Zeorb

What to prepare about your boundary

Describe one boundary, the evidence you have and the people around it.

One boundary
The handoff, interface or workflow at issue
Current evidence
Existing workaround and relevant versions
Access
Permitted documentation or test access
Open question
The decision still unresolved
Implementation owner
Your team or a separately agreed provider
Specialist acceptance
Clinical, quality, partner or scientific owners
Handover
Who receives the decisions and remaining limitations

For clinical integration, name a specific clinical partner and a designated clinical reviewer first.

FAQ

Questions before you brief a healthtech CTO