Use case

Decide what to automate—and what must stay with people

Automate a step only when its inputs are defined, its failure state is visible and a named person owns the exception.

  • Choose one lane: intake or field service
  • Process fix compared with tools and integration
  • The curator, for a technical decision your owners cannot resolve

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

Which operation is backing up?

Service intake and booking are backing up with incomplete requests. Or new field-service contracts mean more retyping, rescheduling and late work confirmations. Which handoff needs to change?

  • Intake queues behind operators

    Rising inbound volume creates a queue while operators chase required details.

  • A transcript is not a booking

    A transcript alone leaves the operational task unfinished.

  • Dispatchers chase work packs

    New contracts or geography increase dispatcher work: incomplete work packs, manual rescheduling and chasing proof.

  • Scheduled is not completed

    A scheduled visit and an uploaded report are earlier states than accepted completion evidence.

Choose the lane

Choose the lane first, then compare a process fix with tools and integration.

  • Service intake and booking

    Start with one service line, language/channel, CRM or booking destination and receiving team. Done means a correct, verified request or booking with an acknowledged destination state—or a handoff accepted by the responsible person. Count a handoff separately from a booking.

  • Field-service coordination

    Start with one job type, region and dispatch team. Check current tools, including any field service management (FSM) system, before proposing a replacement. Done means the job's required completion evidence has been accepted by the authorized reviewer. Finance/ERP then checks its own invoice-readiness prerequisites; readiness is distinct from issuing an invoice or receiving payment.

Choose the smallest adequate change

A routine fix stays with the current owner or vendor. CTO judgment becomes useful for unresolved cross-system choices, unusual rules or technical accountability.

  1. Better form, process or human support

    Choose it first when clearer fields or operator handoffs can remove the queue. The service/operations owner decides; current staff or vendor changes the process.

  2. Configure the current intake platform or FSM

    Choose it first when supported capabilities appear sufficient; demonstrate the configured path. Operations and IT accept coverage; the current team or vendor configures.

  3. Deterministic integration

    Choose it first when structured data and agreed rules exist, but re-entry or state transfer fails. Operations owns rules; IT accepts interfaces; team or supplier implements.

  4. Checked voice AI or language-model step

    Choose it first when variable speech or documents create a specific preparation gap. Operations and IT evaluate with data reviewers; team or supplier configures and tests.

  5. Adopt a ready-made platform

    Choose it first when the present setup has a demonstrated gap a supported product may cover. Operations, IT and finance compare; the authorized sponsor approves; the selected supplier delivers.

  6. Custom build

    Choose it first when a material gap remains after testing process, configuration, integration and ready-made options. The sponsor approves the justified scope with operations and IT; the selected team builds and maintains.

What must stay with people?

Privacy, security, legal and safety reviewers retain the applicable decisions in their areas. The operational owner authorizes expansion only after reviewing the result.

  1. Intake: service operations

    Service Operations/COO owns service rules and acceptance. Intake staff and the receiving escalation owner handle requests outside those rules.

  2. Intake: sponsor and IT

    Growth/marketing can identify lost demand; the actual sponsor approves spend and change. IT owns integration decisions.

  3. Field: operations and reviewers

    Operations and domain reviewers own skills, service-level agreement (SLA) and safety constraints. The authorized completion reviewer accepts work evidence.

  4. Field: finance, IT and investment

    Finance/ERP owns invoice readiness. IT accepts technical transfers; the CEO, CFO or P&L owner approves investment.

Two lanes, different accepted states

An uncertain booking reply requires reconciliation of the original action before retry; an unacknowledged handoff stays pending.

Dispatch resolves a lack of feasible assignments rather than asking a model to relax the rules.

Two state lanes: intake moves from received and verified fields through a permitted attempt and reconciled reply to one correct record with a receipt; uncertainty requires reconciliation and handoff stays pending until accepted. Field service moves from a complete work pack through rules-based scheduling, crew-reported completion and accepted evidence to finance checking readiness; an infeasible schedule goes to a person.
Proposed checkpoints, not an autonomous workflow. Intake acknowledgment, accepted field completion and finance-owned readiness are different endpoints; pending cases remain visible.

Agree a trial before live actions

A later, separately agreed readiness review could produce a fit-gap assessment and proposed trial decision. The curator conversation checks the situation and possible fit; it supplies neither a completed evaluation nor authorization for live actions. Agree these items with the lane's owners.

Boundary and baseline
One channel or job type, permitted examples and actions, accepted endpoint, waiting, corrections and full operating effort—including review and tool costs.
Intake acceptance cases
Missing or corrected details, unavailable recipients, uncertain replies and duplicate attempts.
Voice consent and retention
Declined or withdrawn recording consent, a permitted alternative path, an identified owner for retention rules and their implementation, and privacy/legal review.
Field acceptance cases
Incomplete work packs, constraint conflicts, repeated uploads, rejected proof and ERP rejection. Keep completion acceptance and finance readiness separately observable.
Control and stop authority
Monitor, manual fallback, maintenance owner and who may stop the trial or disable downstream actions.
Permitted reconciliation and rollback
Defined before rollout; disabling automation cannot undo a completed visit or an existing booking—such states need the approved human correction or cancellation process.

Grand Rounds provides assessment and, where agreed, technical leadership; your team or selected supplier implements and operates the workflow. A proposed plan ends with a decision about the next evaluation. Only observed, reviewed evidence can support acceptance and a separately authorized expansion.

Bring us your case

Name the lane, where work waits, the affected systems and who can accept a changed process. Share nonconfidential context first; permitted examples and access belong in a separately agreed scope.

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.

Test CTO fit by lane

Experience in one lane does not establish fit for the other.

Ask by lane:

  • Intake: ask which dialogue, field-validation and booking-state decisions the expert personally owned. Request a permitted walkthrough of a correction, uncertain reply and accepted human handoff.
  • Field service: ask which FSM/API architecture and work-order or completion-handoff decisions the expert personally owned. Who set the operational constraints and accepted the result? What did another team implement?

The CTO profiles below are a starting point; the curator must check specific contribution, domain fit, conflicts and availability. Field-service matching remains to be verified for your workflow.

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