Use case

Set technical priorities after an acquisition

The board needs comparable group reporting, a shared process lacks an owner, and the system decision is parked to protect operations. Which post-acquisition dependency should move first?

  • Prioritize the cross-business decision blocking a dated outcome or continuity
  • Then establish who may take that decision
  • Name the shared outcome and its sponsor

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

What is blocking integration?

An application inventory helps explain dependencies; the sponsor and business owners still have to decide which rules and priorities apply. Start with the evidence needed for one stuck decision.

  • Missing shared inventory

    CIO and local system owners identify the applications, contracts and dependencies affecting the chosen process.

  • Figures fail to reconcile

    Finance and business owners agree the definitions; technical owners trace the source data and mappings.

  • Common or separate systems

    The sponsor needs comparable continuity, risk and cost evidence for the same business outcome.

  • Decisions bounce between businesses

    The sponsor must delegate authority and name an escalation owner.

Who can authorize the shared change?

The board, CEO or authorized integration sponsor sets the outcome and delegates decision rights. Put the division in writing before treating a CTO recommendation as authority to act.

  1. Board, CEO or integration sponsor

    Retains shared priorities, mandate and escalation. Technical leadership frames the trade-off requiring that authority.

  2. Business/process owners

    Retain operating requirements and process acceptance. Technical leadership shows the effect of each technical choice.

  3. CIO and local IT owners

    Retain system dependencies, access and technical acceptance. Technical leadership compares architectures and sequences dependencies.

  4. CFO/finance

    Retains reporting definitions, economic assumptions and approval. Technical leadership makes data paths and technical cost assumptions inspectable.

  5. Legal, procurement and security

    Retain their contract, purchasing, data and security approvals. Technical leadership identifies dependencies requiring those decisions.

  6. Appointed CTO

    Retains only the technical decisions explicitly delegated, and advises or leads within the agreed mandate and handover boundary.

Advice, interim mandate, or current integrator?

Grand Rounds offers a route to discuss relevant CTO judgment or an explicitly delegated technical leadership mandate.

  • Sponsor first

    If nobody can authorize a shared outcome or provide permitted material from both businesses, establish those prerequisites before appointing a technical leader.

  • Current team or integrator

    If the plan, evidence and authority already exist, the current owner directs execution. A routine migration alone calls for delivery, not a new CTO mandate.

  • Advisory review

    If a specific technical choice is unresolved but your leadership can make it, agree a CTO review of that choice; the sponsor retains the decision.

  • Interim CTO mandate

    If decisions repeatedly stall because continuing technical authority is missing, the sponsor can consider a temporary, expressly delegated role. Interim CTO support explains authority, escalation and handover.

    Interim CTO support

Route the post-acquisition mandate gap

Your teams or chosen suppliers implement the work. Grand Rounds' contribution is technical judgment and agreed leadership, rather than transaction valuation, legal diligence or financial-synergy assurance.

Decision tree: without an authorized sponsor, establish the sponsor first; with an adequate plan and authority, use the current integrator; otherwise choose interim CTO leadership for a continuing authority gap or advisory review for a bounded choice.
Route the responsibility gap before appointing a role. A proposed interim mandate still needs explicit agreement; the diagram grants no authority.

Agree the evidence for the next decision

A later, separately scoped CTO engagement could propose these. Relevant inputs include permitted inventories and contracts, reporting definitions, TSA constraints and contacts in both businesses. Any subsequent review or mandate needs separately agreed participants, scope and terms.

Dependency map
A dependency map for the selected process.
Options record
Common or separate systems, kept distinct from the transition path.
Decision queue
A decision queue with owners and checkpoints.

Any transition plan should state feasible containment and reconciliation: reverting a system change may leave business actions or changed data to resolve. The owners should accept the review when they can trace its reasoning and authorize, revise or defer the proposed next step.

Bring us your case

For the curator conversation, name the shared outcome, the decision date and the disagreement blocking it. Say whether you need advice on a choice or someone with continuing delegated authority. Use nonconfidential context first.

Talk with the Curator
Illustrative example and counterexample · not a reported result

Example: TSA access ends before a group report is due

Apply the priority rule proportionately. These are editorial illustrations, not reported integration results or a scoring model.

The situation

Access under a transition services agreement (TSA) ends before a required group report is due.

What to settle first

  • Who decides on access once the TSA ends?
  • Who owns the required group report?
  • Can replacing an unrelated local tool wait?

The priority, and a counterexample

Resolve the access and reporting-ownership decision ahead of replacing an unrelated local tool. A routine account migration with an approved playbook and authorized owner can stay in the existing delivery queue.

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 personal cross-business decision experience

Look for decision records and accepted responsibilities, rather than treating a large employer or consolidation project as proof of acquisition leadership.

Ask a prospective CTO for an authorized example of what they personally owned:

  • A decision between businesses: what conflicted, who delegated authority and how it was resolved.
  • An architecture or governance choice: the evidence considered and the responsibilities left with local owners.
  • An advisory or interim mandate: the decisions it covered, its escalation path and what the permanent owner received.

Explore the CTO network; the curator checks the relevant contribution, conflicts and availability before a specific role is proposed.

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