# How VC Platform Teams Can Spot a Portfolio Company's CTO Gap

> Separate execution capacity from an unowned technical decision. Complete a founder-supported needs card with observations, unknowns and sharing limits.

Source: https://grandrounds.tech/insights/portfolio-cto-gap · Published 2026-11-10 · CTO Grand Rounds

A founder asks your platform team for engineers because a release keeps slipping. Another asks for an AI specialist because a pilot has not passed review. A CTO gap, in the sense used here, is a consequential technical decision that lacks an owner with relevant experience. A shortage of developers is a different problem. Before you forward a familiar contact, ask one question: **is the company short of capacity to execute an agreed plan, or is a technical decision still open?**

The answer changes the help you offer. More engineers fit when the work, dependencies and the person who accepts the result are clear. Those technical and acceptance decisions need an authorized owner first. For an operating partner, the first useful output is one founder-supported case with a short needs card and an agreed information boundary. The fund opens a route to help; the founder decides, and the client, payer and recipient of any findings are settled separately.

**In short:** check capacity first; if the plan is agreed and someone with relevant experience has accepted it, talk staffing or the current vendor. If the choice itself is open, or nobody has the authority or relevant experience to make it, bounded CTO input may help. Both can be true at once.

**Next step:** pick one real request where the founder wants help, complete the card below together and agree the minimum brief.

*Figure: Cover: two lanes of work tiles meet a dashed diamond marked ?, beside the headline More people or one decision?*

## Is this a capacity need or a missing technical decision?

Ask whether the technical approach, dependencies and acceptance are agreed. If so, examine implementation capacity. If a consequential choice remains open, identify who has authority and relevant experience to own it.

*Figure: Capacity means resourcing an agreed approach; a decision gap means resolving a choice, its evidence and its owner. Both can coexist.*

## When the founder no longer trusts delivery

Choose one missed release and separate observation, explanation and decision. Ask for inspectable milestone evidence and the owner of the next technical choice. A vendor or current lead may close a concrete request.

Signals to investigate — heuristics, not validated tests: the same release slips repeatedly with an unchanged explanation; status updates show activity but no inspectable result; nobody can say who accepts the release. Counterexample: one slip with a known cause and agreed fix points to vendor or staffing follow-up, rather than proving an open technical decision.

*Figure: Three stacked cards: Observation asks what happened, where and when; Explanation asks what is proposed and what supports it; Decision asks which choice is open and who can own it. An unknown is not a failure.*

## When an AI or enterprise pilot is not moving forward

For one AI/enterprise pilot, identify the buyer reviewer, required evidence, data boundary and unresolved acceptance condition. A model specialist, security reviewer and CTO decision owner are distinct contributions.

Signals to investigate: no named evidence owner for the buyer's security or data review; no written pilot pass condition; or uncertainty about which data the pilot may use. These identify questions to ask, not a diagnosis of the team.

## Build a needs and permitted-data card

Complete one founder-supported card together. Write Unknown where nothing is known; an unknown is not a failure.

| Field | What to write | Unknown allowed |
| --- | --- | --- |
| Next milestone | Business milestone the technical question affects. | Yes. |
| Observation | What was seen, without assigning a cause. | Yes. |
| Proposed explanation | One explanation labeled as a proposal. | Yes. |
| Open technical decision | Choice nobody owns yet, if one is identified. | Yes. |
| Current lead or vendor | Who holds the work today. | Yes. |
| Accepting owner | Who will accept and act on the result. | Yes. |
| Execution capacity | Whether people to do the work exist. | Yes. |
| Permitted first brief | What may be shared, with whom, and what is excluded. | No sharing until agreed with the founder and relevant information owners. |

**Invented example, not a real company.** A software founder shows account creation working in staging. How enterprise customers' users are provisioned is unknown. The open decision is custom integration versus the identity capability already available. No option is selected and capacity is unverified: the card records an observation, an open decision and two unknowns, not a chosen route. This case continues on the matching page.

*Figure: Invented example, not a diagnosed case: account creation shown in staging; provisioning unknown; custom integration versus an existing identity capability; no option selected and capacity unverified.*

## Permission to introduce is not permission to forward everything

Agree the minimum brief and recipients with the founder; forwarding needs its own permission. Client, payer, commercial disclosure and separate technical and partner outputs are covered in the [CTO introductions guide](https://grandrounds.tech/insights/vc-portfolio-cto-introductions).

*Figure: Sharing envelope: an agreed minimum brief for named recipients only; customer records, code, screenshots and access stay outside unless agreed; any return summary is agreed separately. Access is not permission.*

## What to settle on the card before any introduction

These are factors worth settling before a first conversation; the needs card covers most of them:

| Factor | Why it matters |
| --- | --- |
| Number of open decisions | Name one choice and the evidence behind its symptoms |
| Who accepts the result | Name the owner who will accept and act on the result |
| Execution capacity as well as a decision | Staffing and advice are separate asks; record both |
| Current lead or vendor | Ask them to resolve a concrete evidence request first |
| Data and material boundary | Decides what the first brief may contain and who may see it |
| Regulated or domain-specific content | A qualified domain owner decides; CTO input informs |
| Client, payer, recipient of findings | Settled per engagement; see the introductions guide. |

## Boundaries

Use current-team, vendor or specialist help for a well-understood fix. Before outside input, agree its purpose, an accepting owner and permitted information; an assessment can identify missing execution capacity rather than requiring it in advance. Qualified legal, security, financial and other domain owners retain their decisions. The curator conversation covers fit; availability and later scope require separate confirmation. Implementation stays with the company or its chosen provider.

Grand Rounds is an initiative of Dinarys, and a conversation may lead to cooperation with Dinarys.

## Questions and answers

### What is a CTO gap in a portfolio company?

A technical decision that matters for the next milestone and lacks an owner with relevant experience, or evidence nobody has gathered to make it. Missing headcount alone is a capacity need.

### Does a company with no CTO on LinkedIn have a gap?

A missing title is a reason to ask a question. The team may hold the decision under another role, with a vendor or an adviser; ask who owns the next technical choice.

### When do founders need engineers rather than CTO input?

When the approach, remaining work, dependencies and acceptance conditions are agreed and only resourcing is missing. If the choice is open, record both needs separately.

### Can the fund share board materials, code or customer data with an expert?

Agree the exact brief, recipients and exclusions with the founder first. Forwarding needs its own permission and recipient agreement. Confidentiality contracts and data rules may need separate advice. Keep credentials and personal records out of any initial contact form.

### Who pays for a first conversation or later work?

Set client, payer and signer per engagement; the referring fund is not the payer by default. See the [CTO introductions guide](https://grandrounds.tech/insights/vc-portfolio-cto-introductions).

## Choose one founder-supported case

Complete the needs card together, agree a minimum brief and respect a declined introduction. If the current team can answer the question, use it. Once the case is clear and you are choosing whom to introduce, read [matching a founder with a CTO](https://grandrounds.tech/insights/portfolio-founder-cto-matching). If an outside CTO view is wanted, the [curator page](https://grandrounds.tech/talk-with-the-curator) explains how to start; roles, payer and recipients are in the [CTO introductions guide](https://grandrounds.tech/insights/vc-portfolio-cto-introductions).
