Context
The situation

The company: an identity and access management (IAM) startup — a market that was already crowded with established players like Okta, Auth0, and Microsoft Entra before the AI era made it even more complex. The founder was technically sophisticated and sharp, but facing a fork in the road: double down on the core product, or make a serious bet on AI capabilities before a funding round.

We found a more interesting problem underneath. The CEO had personally reached what AI practitioners were calling Level 4 or 4.5 on the five-level AI maturity framework — actively using agentic workflows, building with AI as a core tool. His team was averaging around 2.5. That gap was, in Mike's words, "horrifying."

The Core Diagnostic

An AI-forward CEO running a team at mid-level AI maturity is like a Formula 1 driver stuck behind his own pit crew on the track. The bottleneck isn't strategy — it's organizational capability. The competitive risk isn't that competitors will out-AI you. It's that your CEO will burn out trying to compensate for a team that isn't moving at the same speed.

The Conversation
How we worked through it
Mike I think he is making a mistake by not being more aggressive about using AI for their product. He is at something like 4.5 but his team is at 2.5. That gap is horrifying to me. I think his team and he should be at 4.5 and pushing to five. Also they are going for another round of funding — if they were up at five and had evidence of it, that would be great.
Claude The gap between where Alex is personally and where his team is isn't just an efficiency problem — it's a strategic liability. An AI-native CEO running a team at 2.5 means he's either doing too much himself, compensating in ways that don't scale, or making decisions his team can't execute at the speed he's thinking. For a funding round, that's actually a story worth telling — but you need to tell it right. The pitch isn't "we use AI." The pitch is "our CEO is already operating at the frontier and here's the roadmap to bring the whole organization there."
Mike The skill that you and I had been building using Suno.ai is our test case. It would be really useful if we could harden it so that Yesh-ID could have APIs to any SaaS application by going through the user interface. Let's talk about how to present this before you go to work on it. As always, you're my thinking partner, not a tool.
Claude The Suno.ai work is a perfect proof case — not because it's an IAM use case, but because it demonstrates something more important: the methodology. We built a skill that navigates a web UI, extracts structured data, and wraps it in an accessible interface — without a formal API. The implication for Yesh-ID is significant: if you can build UI automation as an API layer, you're no longer dependent on vendors who won't give you programmatic access. That's a differentiated capability in identity management, where SaaS integration breadth is a constant customer objection.
Key Findings
What the assessment surfaced

The Maturity Gap Is the Real Risk

A CEO at Level 4.5 running a team at 2.5 creates organizational drag. Closing that gap is more valuable than any single AI feature.

UI Automation as API Strategy

Building browser automation as an integration layer removes dependency on third-party API availability — a genuine differentiator in fragmented SaaS markets.

AI Velocity as a Funding Signal

Demonstrable Level 4–5 capability converts from a talking point into evidence: faster iteration cycles, lower build costs, higher leverage per engineer.

Ship the Proof, Not the Pitch

The strongest fundraising asset isn't a slide about AI strategy — it's working demos of capabilities competitors don't have, built at a speed investors can measure.

What Made This Work
The methodology, not just the output

What ESR brought to this wasn't a framework template. It was the ability to sit alongside the founder — as a thinking partner rather than an outside consultant — and work through the real problem rather than the presenting problem.

The presenting problem was: "How do we build an AI strategy for our funding round?" The real problem was: "How do we close a maturity gap that's silently constraining everything we're trying to do?" Those are different documents. The first gets filed away. The second changes how a team works.

We produced both — a strategy memo built for investor audiences, and an internal roadmap for closing the organizational gap. Mike's four decades of watching technology promises collide with engineering reality meant the recommendations were grounded. Claude's ability to synthesize the competitive landscape across IAM incumbents, emerging players, and AI-native entrants meant the framing was sharp and current.

The Collaboratory in Practice

This engagement is a direct demonstration of the ESR model: Mike and Claude working through a client's real problem in real time. The strategy document that came out of it wasn't drafted by a consultant who interviewed the founder for two hours and then disappeared. It was produced through a genuine back-and-forth — which is why it reflected what the company actually needed, not what looked good in a deck.