We're all-in on AI. The question isn't whether to go aggressive. It's which version of aggressive actually produces results.
Revenue per FTE is approximately $225K. The VTO target is $300K. On paper, that's achievable through efficiency alone - AI can deliver 20-40% productivity improvement.
But that's the wrong math. The $300K/FTE target sits alongside $26.2M by 2028 and $100M by 2032. Those numbers aren't an efficiency story - they're a growth story. We need the efficiency and the new revenue lanes that come from doing things we currently can't - creating entirely new offerings, building products and services that don't exist in our portfolio today, and opening revenue streams that our current business model has no way to reach. That's not doing what we do faster. It's doing fundamentally different things.
The VTO also says WKT should be "confident and disciplined in how we build and use technology." That's a culture target alongside the revenue targets. This strategy builds toward both.
The evidence is clear: organizations that deploy AI with structure see transformative results. Organizations that deploy without structure see nothing.
BCG quantified it: AI transformation is 70% organizational, 20% process, 10% technology. Most companies invest in the inverse ratio.
The Jevons Paradox: When AI makes cognitive output cheap, demand explodes. The binding constraint shifts from "can we produce this?" to "can someone specify what to produce and make the judgment call?"
The technology works. The gap between deploying AI and generating value from AI is almost entirely about execution capability.
74% hope. 20% achieve. The question is which group we're in - and that's a question about execution, not technology.
The belief says AI can help. The bet says how - and it has two parts that are inseparable.
Part one: the move is from defensive efficiency to offensive innovation. Phase 1 efficiency - automating routine tasks, accelerating existing workflows - is necessary and valuable. It builds trust, generates quick wins, and saves as little as 11 minutes a day to create the behavioral foundation for deeper adoption. But organizations that stop at efficiency become "highly efficient dinosaurs" - doing the same work faster while the world changes around them. Phase 1 will be commoditized within years. The organizations pulling ahead are already using AI to enter markets faster, make better strategic decisions, and build entirely new capabilities. We're betting that the transition from Phase 1 to Phase 2 - from doing the same things faster to doing fundamentally different things - is the strategic move that separates first movers from the rest.
Part two: we make that move through people, not around them. Organizations don't make transitions. People make transitions. The technology is available to everyone - the same models, the same platforms, the same capabilities. The differentiator is the people who can specify what to build, evaluate whether it's good enough, iterate toward better, and ultimately use freed capacity to create things that didn't exist before. AI augments human capability - it doesn't replace human judgment. The more effectively we use AI, the more valuable our people become.
These two parts can't be separated. The research is consistent: organizations that invest in technology and capability simultaneously outperform those that invest in either alone (MIT, BCG, McKinsey all converge). Technology without skilled operators produces the 88% failure pattern. Capability without technology leaves value on the table. That's why the four pillars that follow operate as a single system - and why the competitive moat isn't the AI tools (everyone has access to those), but the compounding organizational capability to aim them well.
People are the point. AI is the lever.
AI is a tool that amplifies whatever it's aimed at. Aimed by skilled people at well-understood problems, it compounds. Aimed without human judgment, it produces the 88% failure pattern - tools everywhere, outcomes nowhere.
The competitive moat isn't the technology. Everyone has access to the same models, the same platforms, the same capabilities. The moat is people who can specify what to build, evaluate whether it's working, and imagine what to do next. That's what turns AI from an expense line into a growth engine.
If we're betting on people, we need to mean it. AI introduces a tension about where humans fit that we haven't fully resolved - and every organization, whether they name it or not, is operating somewhere on a spectrum:
Each position is a legitimate business choice with real trade-offs. The question is not which one is morally correct - it's which one WKT's leadership team genuinely believes in, and whether that belief will hold when pressure tests it: when a key role opens up and AI could cover it, when quarterly numbers are tight, when a competitor achieves the same output with half the headcount.
This matters operationally, not just philosophically. The highest-value AI deployments require people to actively teach the systems what good looks like - to share expertise, build specifications, document their judgment. People will not do this if they believe, even partially, that they are training their own replacements. That calculation is rational, not paranoid. And BCG's finding that adoption stalls at 50% when the organizational message is ambiguous is directly about this pattern - ambiguity about what happens when you succeed at AI adoption reads as threat. Clarity reads as invitation.
Before this strategy can be executed with integrity, the leadership team needs to genuinely determine - together, not as a checkbox exercise - where WKT stands on the spectrum. This likely requires a formal people strategy: a clear position on natural attrition, role evolution, headcount philosophy, and what AI-driven productivity gains mean for the humans who produce them. The VTO speaks to people. Our values speak to people. This strategy speaks to people. The unresolved question is whether the organization's actions will match - and people will build their future at WKT (or choose not to) based on that answer.
The bet is clear: move from efficiency to innovation, through people. But a bet is just words until it becomes work. These four pillars are the system that converts the bet into measurable organizational change. Each pillar exists because the research - and our own experience - shows a specific failure mode when it's missing:
AI only generates value when it's aimed at real problems with clear ownership and feedback loops. Without disciplined deployment, we join the 88% of organizations seeing zero financial return from AI - tools everywhere, outcomes nowhere. This pillar establishes the operational standard that separates productive deployment from expensive experimentation.
Core Value Connection: Driven and Accountable. Deployment demands the discipline to name real problems, own specific outcomes, and close feedback loops - not just experiment, but follow through until value is measurable.
Technology alone doesn't produce outcomes - people aiming technology at the right problems do. Without deliberate capability development, adoption stalls, deployments underperform, and the organization can't see what's possible beyond automating what it already does. This pillar builds the specification, evaluation, and imagination muscle that unlocks value from every deployment.
Core Value Connection: Curious and Relationship-focused. Capability grows through genuine curiosity about what AI makes possible, and it scales through the relationships that turn individual learning into organizational knowledge - champions teaching peers, teams sharing what works.
Effective deployment frees capacity. Capable people can see where to aim it. But without intentional redirection, freed hours silently disappear back into existing work - the efficiency trap. This pillar ensures that every hour freed by AI becomes fuel for the Phase 2 work that creates growth, not just a quieter version of the same day.
Core Value Connection: Curious and Driven. Redirection requires the curiosity to imagine what doesn't exist yet and the drive to actually build it - to treat freed capacity as fuel for growth, not permission to coast.
Moving aggressively without guardrails creates risk that can undo everything the other three pillars build - regulatory exposure, client trust erosion, ethical missteps, security gaps. This pillar provides the frameworks that let us move fast sustainably: clear policy, stakeholder-calibrated communication, and the infrastructure that makes responsible use the default, not an afterthought.
Core Value Connection: Accountable and Nimble. Governance embodies accountability - owning the consequences of how we use AI, not just the benefits - paired with the nimbleness to adapt frameworks as the technology and our capability evolve, rather than locking down policies that become obstacles.
These pillars are sequential in logic but parallel in execution. You don't finish one and start the next - you run all four simultaneously, because each one feeds the others. Deployment creates the context for capability development. Capability enables smarter redirection. Redirection produces the innovation outcomes that governance protects. And governance builds the trust that makes people willing to deploy, develop, and redirect in the first place.
Every piece of research on AI at scale references "effective deployment" as the differentiator. But that phrase does enormous heavy lifting - and most organizations never define what it actually means in practice. For WKT, it means five conditions are in place for every AI initiative. Not aspirationally. Operationally. This is our deployment standard - the checklist that determines whether an initiative is ready to run, and the lens we use to diagnose why something isn't working.
Most failed AI initiatives start with "let's use AI for X" instead of "X costs us 12 hours a week and produces inconsistent results." If someone can't articulate success in business terms, the deployment isn't ready.
Someone accountable for the outcome who understands the problem domain, can evaluate output quality, and has the authority to iterate. When an initiative has no owner, it has no feedback loop - and without a feedback loop, it can't improve.
This is the one most organizations skip. They assume people will figure out how to use the tools. The research says they don't. This is also where Pillar 1 directly depends on Pillar 2 - deployment without capability development produces the 88% failure pattern.
Before and after measurement. Someone reviewing on a weekly cadence, not quarterly. The automation ledger exists for exactly this reason - every deployment has a before, an after, and someone watching the gap.
People will slow-roll adoption if making themselves more productive makes them more vulnerable. Leaders must be explicit and consistent about what happens when AI absorbs tasks. This connects directly to the people question in the bet: clarity about the spectrum position isn't optional, it's an operational requirement for adoption velocity.
The pattern is already visible at WKT: The teams that have seen the strongest AI results had all five conditions in place, even informally - a named problem, clear ownership, growing specification skill, active feedback loops, and a team culture where experimentation was safe. The question is whether we can make this systematic rather than dependent on having the right people in the right conditions by accident.
Deployment creates demand for capability ↓
The ability to specify, evaluate, and orchestrate AI output is the binding constraint on organizational scale. Our production teams have already seen this firsthand: second iterations of AI-assisted work are dramatically faster - not because the technology improved between iterations, but because the people got better at specifying what they needed. That's the muscle this pillar develops.
But specification skill alone isn't enough. There's a harder question underneath it, one that surfaced directly from our executive team: How do we imagine what's possible if we don't know what we don't know?
This is the deeper challenge. When department leaders sit down to identify AI opportunities, they will naturally default to automating what they already do - making the familiar faster. That's Phase 1, and it's valuable. But the Phase 2 opportunities - the ones that create new revenue, new offerings, new ways of working - require seeing possibilities that don't exist in today's workflows. You can't automate your way to something you haven't imagined yet.
This means capability development has to go beyond training people to use AI tools. It has to build the organizational imagination - the ability for everyone, not just leaders, to look at their work and ask "what could be fundamentally different?" That requires exposure to what AI can do across industries and functions, structured time for creative exploration, cross-pollination between teams who would never otherwise share ideas, and a culture where proposing something that doesn't work yet is valued, not penalized. Deliberate exposure to how other organizations are using AI and a problem-focused lens - starting from real constraints rather than available tools - can support this. But this isn't everything. How to systematically cultivate organizational imagination is something the organization needs to fully explore and define as part of this pillar.
The WKT Fluency Program, a custom capability development program, will provide the structured path - designed specifically around our organizational needs, including intentionally developing the capability for innovation and imagination that Phase 2 requires. But that program alone won't cover everything. There are broader learning and development needs across the organization - tool-specific training, AI ethics fundamentals, data handling, and potentially vendor-provided programs - that need to be identified, sourced, and planned alongside it.
Adoption stalls at 50% when the organizational message is ambiguous (BCG). Clear, specific communication about how roles evolve with AI is what breaks through that ceiling. But communication alone isn't enough - people need to see the possibilities in their own work, which is why this pillar invests in exposure and imagination alongside technical skill development.
Capable people can see where to aim freed capacity ↓
This is the pillar that converts efficiency into growth. Every AI deployment that works (Pillar 1) frees capacity. People with the right capabilities (Pillar 2) can see where that capacity should go. But without intentional, visible redirection, freed hours silently disappear - absorbed into more of the same work, lost to the Jevons Paradox (when cognitive output becomes cheaper, demand for it explodes), or extracted through headcount reduction. Either way, the organization gets more efficient without getting any closer to Phase 2.
The connection between the pillars is the point. You can't redirect capacity you haven't freed (that's Pillar 1). You can't redirect it intelligently if people can't see the possibilities (that's Pillar 2). And you can't redirect it at all if people don't trust that their productivity gains work for them rather than against them (that's the people question in the bet). All three must be working for this pillar to function.
Pillar 2 builds the organizational imagination to see what doesn't exist yet. This pillar ensures those possibilities don't stay ideas - it provides the structure, the investment decisions, and the accountability to turn them into new products, services, and revenue. That requires an innovation framework - a deliberate process for capturing ideas, investing in the ones with real potential, testing them with clear success criteria, and making honest decisions about what to scale and what to stop. Without this structure, even the best ideas stay on whiteboards.
| Destination | What It Means | Phase |
|---|---|---|
| Volume Growth | Same people, more output. Revenue grows without proportional headcount growth. | Phase 1 |
| Capability Building | Freed time invested in learning - fluency program, cross-pollination, skill development. | Phase 1 → 2 |
| Innovation Projects | Phase 2 exploration - new product prototyping, market research, new service development. The imagination built in Pillar 2 produces the ideas; this is where they get real investment and real outcomes. | Phase 2 |
| Revenue Generation | Freed capacity into sales, business development, or new market entry. | Phase 2 |
As capacity opens up, leaders need to identify where that time goes - for individual roles and for the department as a whole. The table above provides the framework for those decisions. Leadership must be explicit about the distribution. When AI frees 10 hours per person per week, the first question is not "do we need fewer people?" but "what could our people create with 10 more hours of high-value work?" The answer to that question - and whether people believe the answer - determines whether the efficiency-to-innovation transition actually happens.
The 25-30% new-source revenue target (new customers and customers lapsed 2+ years) is the proof point of the entire strategy. It tells us whether freed capacity is actually redirecting into growth rather than being absorbed back into existing work. If Rev/FTE is moving but new-source revenue isn't, we're getting more efficient at our current business without building the new revenue lanes the VTO requires.
All of this needs guardrails to be sustainable ↓
The first three pillars push the organization to move fast: deploy, develop, redirect. This pillar ensures that speed doesn't create risk that undoes the progress. WKT operates in regulated spaces, serves clients who depend on accuracy and trust, and employs people whose relationship with AI is still forming. Governance isn't a compliance exercise bolted on at the end - it's the set of decisions, policies, and infrastructure that determine whether the organization can sustain aggressive AI adoption over years, not just quarters.
This means technology governance (what tools we use, how data flows, who approves what), people governance (clear roles, updated job descriptions, the formal people strategy that resolves the spectrum question), external governance (how we communicate AI use to clients, regulators, and the public - calibrated by sector, not one-size-fits-all), and operational infrastructure (the automation ledger, champion network, specification library, and protected experimentation time that make the other three pillars function).
At the activity level, risk is a function of three factors: autonomy (whether a human reviews output before it leaves the organization), blast radius (the financial, reputational, or regulatory consequences if something goes wrong), and investment (the time or capital commitment required). The same activity can carry different risk depending on who is doing it and their capability to evaluate the output - which is why governance and capability development are inseparable. The companion operations playbook provides the detailed approval framework built on these factors.
AI Program Owner to run operational infrastructure. AI/Technology Capability Lead (new hire) for the technology side. Role evolution conversations across every function. Updated job descriptions reflecting AI fluency expectations. The formal people strategy that resolves where WKT stands on the spectrum.
Technology governance for tool evaluation and data security. Ethical guidelines for AI in regulated content. Decision rights framework. Data handling and privacy policies for AI workflows. Quality assurance standards for AI-assisted outputs.
AI disclosure policies calibrated by sector - regulators, B2B clients, B2C learners, and the public each require different approaches. Client-facing messaging. Contract language reflecting AI-enabled delivery. Marketing positioning AI capability as a differentiator.
Fluency progression program. Automation ledger for feedback loops. Champion network for peer-driven scaling. Specification library for institutional knowledge. Protected experimentation time. Tool licensing and secure integration environments.
Not all of this needs to be in place before we start. But we need to acknowledge the full scope and build toward it deliberately rather than discovering gaps as we go. The companion operational document details the specific artifacts, processes, and sequencing for each requirement.
Each pillar makes the others stronger. That's the competitive moat - not any single pillar, but the compounding effect when all four operate together. Organizations that invest in technology alone hit the 88% failure rate. Organizations that invest in people alone leave value on the table. The system works because the cycle never stops turning.
Deploy creates demand for capability - you can't use the tools if you can't specify what you need. Develop builds people who see where to aim freed capacity - not just at more of the same, but at what's fundamentally possible. Redirect turns that vision into growth - new offerings, new markets, new revenue. Govern makes the whole thing sustainable - trust lets the organization move faster and bolder. And bolder deployment starts the cycle again at a higher level.
This is why the competitive moat isn't the AI tools. Everyone has access to those. The moat is the compounding organizational capability to aim them well - and that capability only compounds when all four pillars are turning together.
If the strategy is working, we should be able to see it. Each pillar can be reduced to a single question - and each question to a single word - that tells us whether the bet is activating. Together, the four questions form a complete diagnostic: if all four are trending positively, the strategy is working. If any one isn't, we know exactly where to look.
Leading: Active deployments with closed feedback loops. Hours redirected from routine to higher-value work. Deployment cycle time (how quickly a new initiative goes from problem identification to measurable outcome).
Lagging: Revenue per FTE trend. Process cycle time reductions on specific workflows (measured individually, not as a general average). Before/after metrics documented in the automation ledger for each deployment.
Leading: Fluency assessment progression (Explorer → Practitioner → Navigator distribution). Champion network participation. Cross-team solution transfers. Ideas surfaced through structured exploration (the "art of the possible" pipeline).
Lagging: Specification quality improving over time (fewer iterations to good output). Teams independently identifying and solving AI-applicable problems without central direction. AI sentiment score trending positive.
Leading: Freed capacity visibly redirected (tracked and categorized: volume, capability, innovation, revenue). Phase 2 initiatives launched with ownership and outcomes defined. New revenue opportunities in pipeline that didn't exist before.
Lagging: New-source revenue (new customers + lapsed 2+ years) trending toward 25-30% of annual revenue. Phase 1 to Phase 2 initiative ratio shifting over time. Revenue-generating activities that are only possible because of AI-enabled capacity.
Leading: Percentage of deployments meeting the full 5-condition standard. Policy frameworks published and adopted. Ethics reviews completed on schedule. Stakeholder communication frameworks in use by sector.
Lagging: Zero AI-related incidents impacting client relationships. Governance operating without central bottleneck. Client satisfaction stable or improving. External reputation as a responsible AI adopter.
Many of these metrics don't have baselines yet - we can't measure improvement without knowing where we started. The first operational priority this quarter is establishing those baselines: running the fluency assessment, documenting current process cycle times for key workflows, capturing the current Rev/FTE and new-source revenue figures, and setting up the automation ledger to begin tracking. Some metrics (like freed capacity redirected) require infrastructure to be in place before they can be meaningfully tracked - you can't measure redirection if there's no system capturing where freed hours are going. The companion operational document sequences what can be measured immediately versus what needs to be built first.
| Horizon | Target |
|---|---|
| 90 Days | All baselines captured and documented. Fluency assessment complete. First deployments with closed feedback loops running. Automation ledger live. Champion network active. Capacity tracking mechanism in place. |
| 6 Months | Measurable movement on deployment-specific metrics (not just general Rev/FTE). 25%+ adoption with visible fluency progression. First Phase 2 initiative launched. Freed capacity being tracked and categorized. Governance frameworks operational. |
| 12 Months | Past the 50% adoption ceiling. Multiple Phase 2 initiatives producing results. Each deployment cheaper and faster than the last (compounding visible). Rev/FTE trend clearly positive. New-source revenue pipeline active. AI embedded in how we work, not a separate initiative. |
Review cadence: Weekly (deployment owners review their feedback loops). Monthly (champion network, fluency progress, capacity tracking). Quarterly (leadership scorecard - four questions, four answers, specific numbers). If we can't show a compounding trajectory at 12 months, we reassess. This is a bet with checkpoints, not an open-ended commitment.
This strategy asks the organization to invest in four areas simultaneously. If any of these feels uncomfortable, it's useful to name that discomfort rather than underinvest and watch the strategy underperform.
| Area | What It Involves | Magnitude |
|---|---|---|
| Time | Leader time for alignment, coaching, role evolution conversations. Staff time for experimentation and fluency. | Significant - the largest investment. Replaces existing work patterns, not additive. |
| Tools | AI platform subscriptions, token/API costs, governance infrastructure. | Moderate and growing. Experimentation tokens don't always produce direct ROI - that's the cost of learning. |
| Talent | AI Program Owner (internal). AI/Technology Capability Lead (new hire). | Essential. Without them, the strategy runs on goodwill - the research shows that doesn't work. |
| External | Implementation consultant (optional). Time-bounded with exit criteria. | Optional. External for setup, internal for operation. |
The cost of inaction is not zero. It is remaining in the 88% without measurable return while competitors compound capability. The catch-up disadvantage grows every quarter we delay structured adoption.
| Horizon | Focus |
|---|---|
| Q2 2026 | Baselines & Fast Wins. Establish all measurement baselines. Every department ships at least one AI improvement with measurable outcomes. Build the automation ledger. Begin stakeholder communication planning. Start closing loops. |
| Q3-Q4 2026 | Momentum to 25%+ Adoption. Spread proven use cases. 2-3 production-scale deployments with ownership. Train Practitioners and Navigators. Technology governance established. Capacity redirection tracking operational. |
| Q1 2027 | Capability Scales. Past 50% adoption. Shift from new deployments to depth. Improving existing solutions, building orchestration. Phase 2 initiatives producing visible results. Behavior change clear. |
| 2027+ | AI-Native Operations. The flywheel is spinning. Every deployment improves future deployments. Revenue per FTE is moving. New markets are viable. "Confident and disciplined" in how we build and use technology. |
What happens next: A companion operations playbook details the pillar-level work - ownership requirements, approval frameworks, support structures, and what needs to be built first. That playbook is a starting point for leadership discussion, not a finished plan - it becomes real when the team commits to it, assigns ownership, and shapes it to fit. This document defines the bet. The playbook begins converting it into action.
74% of organizations hope AI will grow their revenue. Only 20% are achieving it. The difference is execution - the right problems solved, measured, and scaled by people who are empowered and equipped.
Destination → Belief → Bet → Four Pillars → Metrics
$100M by 2032. $26.2M by 2028. $300K Rev/FTE. This is how we get there.