Nine frameworks. One obsession.

Composability

Build once, reuse everywhere. Can your platform compose capabilities across APIs, data, and agents — so that new use cases are assembled from existing building blocks rather than built from scratch each time?

Actionability

Agents need to act, not just retrieve. The platform must enable agents to take actions — triggering workflows, updating systems, orchestrating downstream processes — not merely surface information. Retrieval without action is a dead end.

Reusability

Maximize existing API and integration investments. The best agentic architectures are not net-new builds — they are intelligent reuse of the integration estate the enterprise already owns. Reusability is the multiplier on prior investment.

Governance

Security, compliance, and trust. In enterprise and regulated contexts, governance is not optional overhead — it is table stakes. The platform must provide guardrails that allow AI agents to operate at scale without creating unacceptable risk.

Orchestration

Coordinate agents, data, and actions across the enterprise. At scale, you are not running one agent — you are orchestrating multiple agents, multiple data sources, and multiple action surfaces. The platform must handle this complexity without requiring custom plumbing for every use case.

Time

How quickly do you earn the right to a second conversation? TTC measures the elapsed time from first contact to the moment a customer views you as a credible, valuable partner — not just another vendor seeking discovery. If you cannot lead with value in the first interaction, you are already behind.

To

Directional: what outcome does this interaction move the customer toward? TTC is not about impressing — it is about advancing. Every interaction should move the customer meaningfully closer to a decision, a realization, or a resolution. If you cannot answer what outcome this interaction serves, you are not ready to have it.

Credibility

Armed with the customer's platform usage data, value realized to date, stated business priorities, and a clear understanding of what you can solve for them — now and immediately. Credibility is not claimed. It is demonstrated through specificity: you know their situation, and you know what moves the needle.

Ideal

Evidence-based, not assumed. Ideal is not a theoretical construct — it is derived from the behavioral patterns of customers who have actually expanded, renewed, and grown. ICB starts with studying your best customers and working backward to identify the specific behaviors that predicted their trajectory.

Customer Behavior

The specific actions successful customers take that correlate with outsized adoption and expansion. Not who they are — what they do. How frequently they engage with the platform, which features they adopt first, how they onboard new teams, how quickly they move from first use case to second. Behavior is observable. Behavior is leadable.

Behavior Analytics

Use ICB as both an early warning system and an expansion signal. Customers exhibiting ICB-aligned behaviors are expansion candidates — accelerate them. Customers whose behavior is diverging from ICB patterns are at risk — intervene early. ICB turns reactive customer success into predictive commercial strategy.

Builders

The developer community who write code, build apps, integrations, and increasingly build AI agents. Builders want efficiency without losing quality — and they want platforms that meet them where they already operate. Agentic coding represents a once-in-20-year transformation for this community.

Operators

Horizontal teams that own and operate platforms — developing standards, managing observability, maintaining security posture. Operators are caught between controlling what Builders are building and having visibility over what Consumers are experimenting with. Managing agent sprawl is their defining challenge.

Consumers

Business departments that see a once-in-a-generation opportunity to transform their domain with agents — the HR Agent, the Customer Service Agent. Consumers need speed and accuracy within a finite competitive window. But information retrieval alone won't deliver exponential value; they need action-layer agents backed by governed APIs.

Thinking

Strategic and analytical reasoning — understanding the problem, exploring the solution space, developing frameworks and hypotheses. Thinking is the foundation. It is also the component most easily displaced by the pressure to produce visible output.

Doing

Execution. Delivery. The actual work. Doing has always been the cornerstone — and in an era that rewards visibility over output, it is the component most at risk of being underweighted. The most enduring innovations were built by people who put their heads down and did the work without concern for their brand. The Work is their brand.

Communicating

Sharing the thinking and the doing — with stakeholders, with teams, with the broader professional community. Communicating is critical, but it must follow Doing, not precede or substitute for it. When Communicating displaces Doing, you get the appearance of progress without the substance.

Product Mastery

Deep understanding of your product or service offering — including hands-on nuances that go beyond what's in the sales deck. You cannot advise on something you don't understand at a working level.

Customer Mastery

Deep understanding of your customer — their pain, priorities, constraints, and internal dynamics. Generic advice from people who don't understand the specific customer situation is not advisory. It's noise.

Industry Direction

Directionally accurate understanding of the industry — both your customer's and your own. Nobody has complete visibility into the future. The goal is directional accuracy: enough understanding of where things are heading to give your customer a useful perspective on what it means for them.

Humility

The most important ingredient. You will never know everything. The best advisors seamlessly context-switch between being a teacher and a student. And the most critical rule: never call yourself a Trusted Advisor — that is for your stakeholders to decide.

Reactive

Where everyone starts. You respond when called upon, learn your craft, and build foundational competence. This is table stakes — necessary but not differentiating. The goal is to move through this stage as quickly as possible.

Reactive but Dependable

Mastery of craft is established. You consistently deliver when called upon. Stakeholders know they can rely on you. This is where many professionals plateau — and where dependability is confused with credibility. Dependability is a prerequisite, not the destination.

Proactive

You anticipate needs and situations before they are surfaced to you. You bring solutions to problems that haven't been named yet. This requires mastery of your own domain plus enough situational awareness to see around corners. Anticipation is the transition from reliable executor to trusted contributor.

Point of View

The highest level. You have mastered your craft and developed deep enough understanding of your customer's (or peer's or leadership's) domain to have a specific, relevant Point of View. Not generic opinions — but informed perspectives on what they should do and why. Having a POV is a superpower and the North Star for building lasting credibility.

Platform Vision

Focused on the initial setup and future evolution of the platform — including co-existence strategy with current investments. This pillar pilots new features, design patterns, and deployment approaches to keep the platform future-proof. Without Vision, platforms drift into technical debt and irrelevance.

Platform Operations

Responsible for reliability — close to 100% uptime. Platform monitoring, infrastructure, support, patching, and incident response all live here. Operations is the least glamorous pillar and the most critical. Everything else depends on the platform being reliably available.

Platform Enablement

Focused on creating and growing a high-quality developer and architect pool for the platform. Includes traditional training, experiential education, hackathons, lunch-and-learns. The bottleneck to platform scale is almost always talent supply — Enablement is the lever.

Platform Engagement

Responsible for seamless onboarding of new projects and teams. Includes identifying platform-use case fit, overseeing initial architecture discussions, and guidance through first go-live. Many technology platforms never achieve broad adoption because organizations neglect the engagement layer between platform and project teams.

Delivery Acceleration

Not every project team has the delivery capabilities to build their use cases. When capability gaps exist, the platform team should provide Delivery Acceleration — a trained bench or preferred partner as an extended delivery arm, charged back to the project team. This removes the most common blocker to platform adoption at scale.

Product Fit

Identifying the use cases and patterns where the technology genuinely differentiates itself — and defining how it co-exists with the existing ecosystem. Product Fit is the foundation. Without a clear answer to "where does this technology specifically win?", investment debates never end and adoption stays fragmented.

Operating Model

The organizational, process, and governance changes required to support the new paradigm the technology introduces. Technology adoption without Operating Model change is the most common source of platform investment failure. The technology works; the organization hasn't changed how it works.

Value

Business and technology KPIs, value measurement, and communication. Every major platform investment faces ongoing scrutiny. The organizations that sustain investment are the ones that can clearly communicate what value has been realized — in terms that resonate with the people controlling the budget.

Commercial Model

A commercial model that scales as usage increases. Internally, this means a chargeback model that makes it easy to onboard new teams and is transparent about cost. Platforms that are opaque about cost or penalize teams for expanding usage undermine their own adoption.

Community

A grassroots fanbase for the technology — built through a thriving internal user community. Office hours, meetups, hackathons, lunch-and-learns. Community is the lowest-cost and highest-impact adoption accelerator, and the most consistently underinvested pillar.

Executive Sponsorship

No technology scales enterprise-wide without executive alignment. The best path is connecting business outcomes to technology outcomes to specific use cases — and measuring and communicating that connection continuously. Exec sponsorship secured through outcome alignment is durable. Sponsorship secured through relationship alone is fragile.