Use case

Your AI product needs a credible customer pilot

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

Customer use exposes dependencies

When the author must step in, the customer promise depends on that rescue. Start with the task this customer needs and the failure that blocks it.

  • Messy input, rescued by hand

    An external pilot customer may bring an incomplete file. If the author must repair every answer, the customer promise depends on that rescue.

  • Access that depends on one person

    The customer may invite another role. Can the team enforce access without the author?

  • Recovery that needs the author

    The customer may retry after a timeout. If the author must restart the job or explain duplicate usage, the promise depends on that rescue.

  • Also: packaged work or a paid beta

    Supporting context: a paid pilot may package repeatable expert work for customers, or move a beta feature into paid use while costs remain uncertain.

Define the customer promise

Choose the failure that blocks the promised customer task first; leave unrelated AI ambitions outside the pilot.

  1. The task that must work

    Which customer task must work, on what permitted inputs, and who accepts its result?

  2. The failure to repair first

    Which customer-facing failure must be repaired before the pilot, and which promise can be smaller?

  3. Deploy, access and retry

    Can the team deploy without the author, enforce access and retry without duplicate actions?

  4. Packaged expert work

    For packaged expert work, what customer output can we promise with permitted sources and review?

  5. Paid use and its cost

    For paid use, what can we afford per accepted result, and which usage will the customer pay for?

Choose the smallest credible route

Choose what must change before the customer can rely on the pilot; retain capable existing ownership.

  • Keep a smaller reviewed promise

    Offer one reviewed output instead of unreviewed self-service. If your existing lead can cover the technical choices, keep that ownership; the service owner and customer agree the smaller promise and review capacity.

  • Test operation without the author

    When deployment or retry behavior is unknown, ask the current technical owner for a controlled operation test. Another engineer should run the agreed version and trace a repeated job; record gaps before widening use.

  • Resolve one blocking readiness choice

    If the failure is known but the repair trade-off is unresolved, an AI readiness review can focus on that decision. The technical owner accepts the recommendation and its remaining limits.

    AI readiness review
  • Lead the controlled customer pilot

    If author-led rescue keeps replacing a repeatable release, fractional CTO leadership can own the pilot's technical decisions. Agree release authority; product and customer retain their acceptance roles.

    Fractional CTO leadership

What an engagement could resolve

Scope one external customer pilot and the decisions it cannot yet support. These are the proposed outputs.

Customer promise
With unsupported inputs and operations explicitly excluded.
First blocking failure
A decision on it, and its next check.
Pilot cost boundary
With usage treatment and an accountable commercial owner.
Operable workflow
A receiving engineer's demonstration that the selected workflow can be operated.

These outputs require a separately agreed engagement. The curator conversation helps decide whether one is needed; it is not an audit and does not produce them. Your engineers or selected vendor implement and test changes; source owners confirm product-use rights and the domain reviewer accepts the customer output.

Bring us your case

Bring the curator one external customer promise, the failure blocking it and the current technical owner. Include the pilot commitment you need to make credible on the call.

Pick a time
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.

Choose a CTO for AI products

Grand Rounds connects you with experienced CTOs whose product and technical decisions form the network's expertise.

Look for a CTO who can show:

  • Taking an AI workflow from author-only operation to a receiving team.
  • Preserving source-use permissions across outputs and customer boundaries.
  • Tracing retries through jobs, usage records and the billing boundary.
  • Balancing customer-task quality, human review and the cost to serve it.

Walk through a timed-out customer request with the candidate. Ask how the receiving engineer would find its status, avoid duplicate work and explain the usage record—without the author operating it.

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
FAQ

Pilot questions