Engageably

05 — Journal

← Back to Journal

What your AI committee should bring to a first studio conversation

May 12, 2026 · 9 min read · Notes · Benjamin Rodriguez

Executive TL;DR

  • The title hides the first problem. A committee is not what should walk into a studio conversation. An operator with a thesis is.
  • A first studio conversation is a strategy stress test. Not a vendor briefing. Most companies arrive prepared for the wrong meeting.
  • Two documents separate a productive first hour from scoping fog: a constraint map and a capability gap statement. Without them, the studio writes your strategy for you.
  • Arriving without a thesis funds a pilot queue instead of a capability. That mistake compounds for two years.

The Macro Picture

AI governance bodies are multiplying faster than AI deployment results. The committee built to speed up the decision is now the most common source of delay.

The adoption numbers make the gap plain. 78% of organizations now use AI in at least one business function, up from 55% two years earlier (McKinsey State of AI, 2025). Yet more than 80% of those same organizations report no tangible EBIT impact from generative AI (McKinsey State of AI, 2025). Adoption is near-universal. Value is not.

Here is what that produces in practice. Companies arrive at outside conversations as procurement exercises, not strategy conversations. Studios read the room in the first ten minutes and price the work to match. You get the proposal the committee asked for, not the one the business needs.

My Thesis

The first studio conversation is a strategy stress test. The job of the people in the room is to bring a point of view worth stress-testing. Not a ranked list of use cases worth pricing. When the thesis is absent, the studio fills the vacuum. That is not a service problem. It is a sequencing problem the buyer created.

Arriving without a thesis means you are asking the studio to write your strategy for you. You will pay for that twice. Once in fees. Once in misalignment.

Default Behavior Versus Effective Practice

The default looks like this. A committee builds a slide deck of use cases ranked by department enthusiasm, attaches a budget range, and treats the first conversation as discovery. The committee asks the studio to do the thinking. The proposal comes back calibrated to what the committee said, not what the business needs.

This inverts the expertise relationship. The buyer should hold the thesis about the business. The studio should hold the thesis about what is buildable. When the buyer outsources the first half, the second half loses its anchor.

Effective practice is narrower and harder. You arrive with three things written down. A constraint map naming what the business cannot afford to get wrong. A capability gap statement describing what the company must be able to do in eighteen months that it cannot do today. And a defined decision the first engagement must enable. That is enough. The studio will sharpen it. But the studio cannot generate it for you, and any studio that offers to is selling something other than partnership.

P&L Impact in the Next 12 to 24 Months

The quality of the first conversation sets the cost structure of the next two years. Not the contract signed at the end of it. The framing set inside it. Four lines on the P&L move based on how that hour goes.

1. Pilot accumulation cost. Underprepared conversations produce scoped pilots with no consolidation path. The pilots stack. Each one carries its own data setup, its own vendor overhead, its own change management. 42% of companies scrapped most of their AI initiatives in 2025, up from 17% the year before (S&P Global, 2025). That write-down is the bill for pilot accumulation, paid in arrears.

2. Delayed time-to-capability. Misaligned scoping adds quarters to the deployment timeline. You funded the initiative to deliver a productivity or revenue lift. That lift slips by the same amount. 95% of generative AI pilots fail to deliver measurable P&L impact (MIT NANDA, 2025). The 5% that work are not smarter. They scoped the first conversation correctly.

3. Renegotiation exposure. A studio that scoped to your stated use cases, not your actual constraint, holds pricing leverage when the constraint surfaces mid-engagement. You find the gap in month four. You lose price leverage to close it. Gartner expects more than 40% of agentic AI projects to be canceled by the end of 2027, citing escalating costs and unclear value (Gartner, 2025). The first meeting priced in most of those cancellations.

4. Opportunity cost of internal attention. The hours your senior team spends managing a misaligned engagement are hours not spent on the operating decisions that compound. This cost never shows up on the invoice. It is the largest of the four.

Structural Risks and Governance Gaps

Confusing Governance Readiness with Strategic Readiness

A committee with a charter, a risk rubric, and an approval workflow is not the same thing as a leadership team with a thesis. Most AI committees exist to say no safely. A first studio conversation requires someone authorized to say yes provisionally, and to spell out what yes commits the company to.

The data on who holds the pen makes this concrete. Only 28% of organizations using AI report that the CEO oversees AI governance. On average, two leaders are jointly in charge (McKinsey State of AI, 2025). Joint ownership of governance is fine. Joint ownership of a thesis inside a ninety-minute meeting is not. Someone has to carry the position into the room.

The Use-Case List as a Risk Vector

Arriving with a ranked use-case list and no capability model creates a specific failure. The studio scopes to the list. Delivery begins. Then the dependencies the list quietly assumed turn out to be unresolved. Access to data. The right to connect systems. Authority over how the work gets done. The project stalls at a boundary nobody knew existed. The stall is expensive because the contract already locked in the wrong shape of work.

Vendor Relationship Versus Strategic Partnership Framing

When the committee shows up in procurement mode, the studio answers with a proposal built for that mode. Fixed deliverables. Defined scope. Limited strategic exposure. This shuts off the iterative, trust-based working relationship that produces durable capability. Specialized vendor-led AI projects succeed roughly twice as often as internal builds (MIT NANDA, 2025), but only when both sides set the relationship up as a partnership from the start. Finding out after signature that you locked in the wrong shape of contract is expensive to unwind. The unwind itself becomes the next quarter’s distraction.

Operating Model and Talent Shifts

A well-run first studio conversation accelerates a specific shift. The company moves from AI as a project portfolio managed by a committee to AI as an operating capability owned by functional leaders.

This requires an operator in the room. Not only approvers. Someone who can speak to workflow, sequence, and the order in which two teams will actually change how they work on Monday. The evidence is unusually direct. Of twenty-five organizational attributes tested, redesign of workflows has the largest effect on whether a company sees EBIT impact from generative AI. High performers are 2.8 times more likely to have redesigned their workflows fundamentally (McKinsey State of AI, 2025). The studio cannot redesign a workflow it has never seen.

The companies that get the most from studio relationships early bring the person who will live with the output. Not the person who will sign the invoice.

The Playbook

Five moves separate a productive first conversation from an expensive one. None of them are about the studio. All of them are about what the company brings through the door.

1. Produce a constraint map before the meeting. Owner: CEO and CAIO Horizon: Pre-meeting KPI: Two to three things the business cannot afford to get wrong, with named operational owners.

2. Replace the use-case list with a capability gap statement. Owner: CAIO Horizon: Pre-meeting KPI: One page describing what the company must be able to do in eighteen months and why an internal build is not enough.

3. Designate one decision-maker with provisional authority. Owner: CEO KPI: One named person able to confirm framing in the room without a two-week internal loop.

4. Map your data and system connections before you walk in. Owner: CAIO and CTO KPI: A documented view of the data you govern, how access gets approved, and which system connections are already in progress.

5. Define the decision the first engagement must enable. Owner: CEO KPI: A written statement of what leadership must be able to commit to, or rule out, at the end of phase one.

Executive Next Step

If your committee is scheduled for a first studio conversation and cannot yet produce the constraint map and capability gap statement, move the meeting. Sixty days of internal clarity is worth more than an early proposal built on ambiguity you will spend the next year unwinding.

Sources

← Back to Journal