Use case

Is your scientific prototype reproducible?

Your scientist can demonstrate the result. Can the next person reproduce the agreed run, understand its limits and use the output for a specific task?

  • A scientific claim needs scientific review
  • A reproducible transfer needs software/data judgment
  • Buyer usefulness needs commercial evidence

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

Why the prototype transfer stalls

This page fits a team with an existing scientific prototype, a named customer or partner use, and resources for a next stage. Each difficulty points to a different expert.

  • The run stays with its author

    The immediate difficulty may be a run only its author can perform.

  • The comparison is disputed

    The difficulty may be a comparison your scientific lead disputes.

  • The buyer task is unclear

    The difficulty may be an unclear buyer task.

  • Before any review: who accepts it?

    Before an external review, identify who can accept the transfer and confirm rights to the required data.

Which expert fits the blocked decision?

Use this as a routing aid, not a sequence every scientific product must follow. When several gaps remain, the scientific, technical and product owners should agree which one blocks the next commitment.

  1. Scientific owner

    Leads the check, with a domain specialist as needed, when the intended scientific claim or its comparison is uncertain. Closing it takes a justified claim boundary and suitable comparison accepted by that owner; a CTO title alone supplies neither.

  2. Technical lead

    Leads the check when a named recipient cannot repeat the agreed run. Closing it takes an agreed transfer check and a clear software/data responsibility; your team or supplier performs the engineering and rerun.

  3. Domain-matched CTO

    Added when architecture, support or handover decisions exceed the team's experience. A one-off notebook fix can stay with your current scientist or software specialist.

  4. Product/commercial owner

    Leads, with a commercial-validation adviser if needed, when nobody can explain the buyer's task or commitment. Closing it takes a named task, current comparator and evidence from a person able to commit to a trial or purchase. CTO review does not establish demand.

A blank transfer receipt

A technical transfer is accepted when the named recipient can repeat the agreed result on defined, permitted data, with known limits, a named owner and agreed support after handoff.

Agree meaningful tolerances with the scientific and technical owners before the attempt.

Blank transfer receipt with fields for recipient and task, data and run version, expected result, observed differences, known limits, owner and support, followed by a recipient decision to accept, investigate or defer.
A blank handover record: expected and observed results occupy different fields. The recipient's decision stays open until the agreed check has been performed and reviewed.

Agree one transfer acceptance record

For a later, separately agreed technical engagement, a matched CTO could propose these for that transfer. The curator conversation describes the situation and checks fit; it is distinct from this review. Scope and terms must be agreed before work begins.

Execution baseline
A review of the existing execution baseline.
Software/data decisions
Proposed decisions the transfer needs.
Handover plan
The proposed handover plan needed for that transfer.

Pipeline changes, production engineering and continuing support remain with your team or chosen supplier. Scientific validity stays with the scientific owner, and any commercial-validation work needs its own purpose and acceptance.

Bring us your case

Tell the curator who needs the result and for which task, what that person cannot yet repeat or use, and which decision your existing scientific and technical leads need help making. Use nonconfidential context first. Run instructions, outputs and datasets belong in later work only with agreed permissions and recipients.

Talk with the Curator
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.

Ask for evidence of a handoff

When considering experience in the Grand Rounds CTO network, test the person's own contribution.

Questions to ask:

  • Which comparable research-to-use transfer did you personally guide, and which decisions were yours?
  • What authorized run record or handover artifact could show what the recipient received and accepted?
  • Who owned unresolved differences and support afterward, and what stayed with the scientist or implementation team?

Your scientific lead should assess the domain, method and data match. Explore the CTO profiles below as a starting point, then ask the curator to verify the relevant contribution, conflicts and availability.

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