Use case

Buy or build AI for research and proposals?

Your staff need AI for their own research and proposals. Before a shortlist or build commitment, compare the full task through expert review—including who will operate it and, if needed, exit.

  1. ProblemFaster drafts have not released expert capacity for more client work.
  2. DecisionCompare existing tools, bought products and custom work on the same task.
  3. CTO selectionChoose experience with workflow trade-offs, staff adoption and handoff.

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

More drafts, same bottleneck

Compare what each route leaves with your people before committing budget.

  • Staff still assemble research

    As a practice lead or COO, you need capacity for more client work, but staff still assemble research.

  • Previous material still checked

    Staff still check previous material, and faster drafts have not released expert capacity.

  • Drafts return for corrections

    Proposal drafts still return for corrections, so more drafts meet the same bottleneck.

  • A platform offer, a build proposal

    A supplier offers a platform; engineering proposes custom work.

What deserves the investment?

Give every option the same permitted inputs, output requirements and review bar before comparing effort or cost.

  1. What you already have

    Can approved templates or an existing copilot complete the task without a new platform?

  2. Reuse and client boundaries

    Which sources and past proposals may be reused, and what must never cross client boundaries?

  3. Total work after review

    Does each option reduce total work after source checking, corrections and expert approval?

  4. Integration, training and support

    What integration, training and support will each route need at the expected workload?

  5. Weekly staff use

    Who will use it every week, and how will you check actual staff use beyond license counts?

  6. Export and exit

    Can you export usable sources, outputs and configurations when the tool or partner changes?

Four routes worth comparing

Compare the eligible routes, including current practice; a known unmet requirement can rule an option out.

  • Improve the process you have

    Choose templates, approved sections and clearer review when assembly or ownership is the bottleneck. The practice lead can make this operating decision with the reviewer; retain it if the whole task meets the bar.

  • Configure tools you already license

    Use this route when an approved copilot or no-code tool covers the task and data conditions. Your process and IT owners accept the configuration; the existing lead tests ordinary staff use rather than opening a CTO program.

  • Buy a specialist workflow product

    Consider a product when it closes a demonstrated gap on your materials. Your budget owner chooses whether to buy; use Technology vendor selection to challenge the resulting shortlist, not reopen the whole route decision.

    Technology vendor selection
  • Build only the missing connection

    Consider custom work for an essential source or review handoff other routes cannot meet. If that connection needs continuing technical leadership, scope Fractional CTO services; the process owner and reviewer retain acceptance.

    Fractional CTO services

A decision you can act on

Scope one task and reviewer team. A separately agreed CTO contribution may produce the following; the curator conversation identifies fit, not a completed comparison.

Shared task brief
With a permitted source pack and acceptance rubric.
Full comparison
Of full effort, quality and lifecycle cost assumptions.
Route recommendation
With evidence gaps and conditions for reconsidering it.
Named owners
Implementation, support, staff-use and exit owners for the chosen route.

Your process owner and reviewers supply examples and acceptance decisions; your team or suppliers run route trials and implement changes. The CTO designs the comparison and interprets evidence.

Bring us your case

Tell the curator which task limits capacity, which options you are weighing and what prevents a decision before the next purchase or build commitment. Share nonconfidential context, not client proposals or licensed source material.

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 operational judgment, not demos

Research/proposal workflow design and AI adoption are part of our CTO network's expertise. Select for a choice your staff can operate and, if needed, exit.

Look for a CTO who can show:

  • Bought and custom routes compared against the same expert-reviewed output.
  • Source rights, reuse exclusions and review effort treated as design inputs.
  • Ordinary staff use, support and handoff checked beyond training attendance.
  • Commercial interests in products, resale or delivery declared and addressed.

Bring whatever baseline you have: time per document, review rounds or license spend. Use it to discuss the unresolved trade-off, not restart your whole AI strategy.

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

Before you sign