Use case

Make the next R&D milestone measurable

Your grant adviser asks for work packages with measurable results. You have a prototype and an innovation description, but the technical feasibility of the next stage is still unclear.

  • The scientific lead judges the proposed test
  • The grant adviser checks funding requirements
  • CTO judgment only where your team cannot resolve the 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

Where the plan stalls

A reviewable work package names the hypothesis, baseline, resource status and stop/go decision. The founder or R&D head needs an executable technical plan before committing preparation resources. Look for the specific gap.

  • An activity without a measurable output

    A package names an activity but leaves its measurable output undefined.

  • Delivery and research treated alike

    Routine software delivery and an uncertain research claim are treated as the same work.

  • Resources assumed, not checked

    Data, equipment or specialist time are assumed rather than checked.

  • Work packages and budget disagree

    The work packages and resource budget describe different amounts of work.

Who should review first?

Use the missing contribution to choose the reviewer.

  1. Grant adviser or writer

    For application presentation or program fit: checks the call, eligibility and application requirements. If the technical plan is sound, your current team and adviser can proceed without another CTO.

  2. Scientific lead

    For scientific validity: judges, with a domain scientist where needed, whether the hypothesis and comparison are meaningful. The research team performs the agreed scientific work.

  3. A relevant CTO

    For unresolved technical feasibility or dependencies: challenges the proposed experiment, work-package relationships and resource assumptions with your technical lead and grant adviser. Your team or selected supplier executes.

  4. Then: founder or R&D sponsor

    Approves the commitment. Finance and legal review their respective budget and application matters.

  5. Then: applicant submits, funding body decides

    The applicant owns submission; the funding body decides the award. A sound technical plan can support that process, but cannot promise funding.

From an activity to a measurable work package

Stopping an unsupported route can be a useful recommendation; a planned test remains different from an observed result.

Illustrative before and after: “Develop the classifier” becomes a proposed comparison against current labeling, with agreed error limits, a per-sample output, three resource statuses and a stop/go review.
Invented planning illustration, not a test result. The scientific lead must approve the labels and error limits; conditional compute and unknown reviewer time remain gaps to resolve before the comparison.

What a technical review could produce

For a later, separately agreed engagement, proposed outputs could include these. The curator conversation explores fit; any subsequent review needs its own scope and terms, based on the evidence and contribution required.

Feasibility brief
Established findings distinguished from open technical assumptions.
Work packages
With inspectable outputs, reviewers and stop/go criteria.
Resource dependencies
Marked confirmed, conditional or unknown, with owners for gaps.

Agree acceptance with your technical or scientific reviewer and grant adviser.

Bring us your case

For the curator conversation, summarize one work package: its hypothesis, the missing technical judgment and who signs off the next commitment. Include the opportunity and decision date if known. Keep the initial inquiry nonconfidential; share research records only after agreeing authorized recipients and access.

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.

Check the expert's own contribution

An association with a funded project says little about who shaped its technical plan.

Ask:

  • Which experiment or feasibility decision did you personally shape?
  • What evidence did you inspect, and what recommendation did it change?
  • How did you connect work packages to actual equipment, people and compute?
  • What could you show us, with permission, to examine that contribution?

Your scientific lead should check the domain and method match. AI experience matters only if AI is part of the actual research question.

This page names no grant specialist or grant author; use the CTO profiles below to explore, then ask the curator to check the specific 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