Skip to main content
    The Harness Era · 01 / 08
    Full analysis

    The Harness Era

    Enterprise AI will be won by orchestration, not models.

    Published Jun 27, 2026·Full-length analysis·A KokoAI point of view

    The frontier model is the most powerful part of the enterprise AI stack, and the least defensible.

    • Your competitor can license the same model, on the same terms, by the end of the quarter.
    • The capability gap between providers narrows with every release.
    • Token prices fall on the same curve as every other input that became a commodity.

    When the strongest part of your stack is also the most evenly shared, it cannot be where your advantage comes from. That is the premise the rest of this analysis builds on. It is no longer controversial. Few companies have acted on it.

    What follows is the long-form case behind the series opener: the market conditions that created the gap, the architecture that closes it, and the evidence that the advantage has moved from the model to the harness around it.

    1. The market created three problems at once

    Most companies are carrying three AI problems at the same time, and each makes the others worse.

    • Information overload. Executives cannot keep up with model releases, product launches, regulatory shifts and what each means for their industry. The result is slow strategic response and uneven AI literacy on the leadership team: decisions made on last quarter's understanding of a market that changes monthly.
    • Agent sprawl. Teams build isolated copilots, prompts, workflows and coding agents with no shared control layer. The result is duplicate spend, uneven quality, unclear ownership and weak governance. Every team's clever automation is one more ungoverned system the company has to trust without evidence.
    • Unclear value. AI is measured by usage (seats, tokens, prompts), not by business results. The result is that nobody can prove ROI, defend the budget or scale the investment with confidence. A program that cannot show its impact will not survive its first cost review.

    These are not three issues to solve one after another. They are one failure with three faces: the company has intelligence it cannot route, work it cannot govern and spend it cannot justify.

    2. Nearly everyone uses AI; few get lasting results

    The numbers that frame the moment do not sit comfortably together:

    • Roughly nine in ten organizations now use AI in at least one function.
    • Agent deployment is still in the single digits.
    • Only a thin slice, the high performers across studies, report sustained, company-wide impact.

    Getting people to use AI is effectively solved. Turning that use into lasting value is not.

    The studies disagree on how big the gap is but agree on why it exists. Where value reliably shows up, it comes with redesigned work, mature governance and a changed operating model, not with the choice of model.

    • Research at Microsoft's scale finds that organizational conditions explain roughly twice the impact of individual effort.
    • Forrester named the "trust tax": the drag that ungoverned, unexplainable AI puts on adoption.

    The pattern holds across sources. What separates the winners is the system around the model, and the organizations that did the unglamorous work of building that system are the ones seeing returns.

    Meanwhile the money keeps moving:

    • AI sits at the top of the investment agenda.
    • Budgets keep climbing as a share of revenue.
    • Most companies plan to keep increasing spend, even though a majority admit they cannot yet see the return.

    For the office of the CFO, that tension is not a reason to wait. It is the opening to impose the discipline (measurement, attribution, governed reuse) that turns AI spend into a lasting asset instead of a recurring cost.

    3. The harness, defined

    An agent completes a task. A harness turns that task into something the whole company can rely on.

    Concretely, a harness is the engineering, governance, testing, runtime and value layer that sits between intelligence and action. It has ten jobs, and skipping any one of them is where pilots die on the way to production:

    1. Intelligence intake: sourced, dated, scored inputs, mapped to roles, industries, processes and capabilities.
    2. An intelligence graph: stories, companies, models, tools and processes linked so each one answers what changed, who cares, which process is affected and which agent can act.
    3. A persona lens: the same intelligence translated for the CFO, the CIO, the operator and the builder.
    4. A diagnostic engine: a score for where a company is exposed, behind or ready.
    5. Agent recommendation: matching tasks to agents, tools and process patterns.
    6. The agent harness itself: define, build, test, deploy, monitor, improve.
    7. Process packs: agents packaged by value stream, not sold as generic chatbots.
    8. Governance and approvals: risk tiers, a human in the loop, segregation of duties, audit evidence.
    9. Observability: quality, cost, tool use, errors, policy exceptions and outcomes.
    10. Value tracking: revenue, margin, working capital, productivity and risk impact, by agent and by process.

    The first five turn information into a recommendation. The last five turn a recommendation into governed, measurable action. The market has built plenty of the first half and almost none of the second.

    4. Why orchestration is the moat, step by step

    Three forces make orchestration, not the model, the part competitors cannot copy.

    • Models converge. As frontier capabilities bunch together and prices fall, any advantage tied to picking a model is temporary by definition. A harness that works with any model turns this from a threat into an advantage: send each task to the cheapest model that clears the quality bar, and switch providers as the frontier moves without rebuilding the workflow.

    • Agents sprawl. Left alone, every team builds its own. A harness imposes one control plane:

      • a registry of what exists,
      • a policy engine for what is allowed,
      • an approval service for what needs a human, and
      • an evidence ledger for what happened.

      Sprawl becomes a portfolio.

    • Value stays unclear until you measure it. A harness attaches a value card to every agent: a baseline, a target, a value lever, an owner and a way to attribute the benefit. The rule that makes it real is blunt: no value card, no money to scale. That rule is what turns a pile of experiments into a managed investment with a return you can defend to a board.

    5. The five value levers, in practice

    The harness only stands out if it makes value easy to see. Every agent maps to at least one of five levers, each with metrics finance and operations already track:

    LeverProcess metricsWhy it matters
    RevenueActivation velocity, churn, leakage rate, renewal expansionGrowth and retention the board already underwrites
    MarginPrice realization, cost-to-serve, cloud and SaaS utilization, supplier savingsEBITDA, defended at the unit level
    Working capitalDSO, DPO, inventory turns, dispute aging, forecast accuracyCash released without new revenue
    ProductivityCycle time, touchless rate, rework, close daysThroughput at constant headcount
    RiskControl coverage, compliance exposure, audit-adjustment rateThe trust tax, paid down

    An agent without a value card is a cost. An agent with one is an investment case. The harness is what makes every agent carry one.

    6. What it changes for each seat at the table

    • CEO: agentic AI becomes how the company runs, managed as a portfolio with a control plane, not a scatter of departmental tools.
    • CFO: fund agents like value streams. Each one carries revenue, margin, cash, productivity and risk impact. The CFO owns turning spend into a measurable, governed asset that compounds, and the value card is the funding instrument.
    • CIO / CTO: the winning architecture works with any model, is driven by policy, can be observed and connects through governed tools and APIs. Model gateways, tool registries, MCP governance, policy engines and observability are now core enterprise architecture, not experiments.
    • COO: deploy agents first where exceptions, cycle time, rework and handoffs hold back throughput. The harness is how a process improvement becomes a lasting capability instead of a one-time consulting deliverable.
    • Chief Risk / Audit: human approvals, evidence capture, traceability and control testing are built in before production. The evidence ledger is what lets you say yes to automation without losing the audit trail.

    The question changes from "Can AI answer this?" to "Can an agent safely change the outcome of this process?" The first is a model question. The second is a harness question, and it is the only one that scales.

    7. The first killer application is finance

    The best place to start is the office of the CFO, where control is highest and value is clearest. Record-to-report, FP&A, audit support and working-capital management combine clear value levers with mature controls and well-understood processes, exactly what a harness is built for.

    • A month-end close agent moves cycle time and the audit-adjustment rate.
    • A reconciliation agent moves reconciliation aging and manual effort.
    • A billing-dispute agent moves dispute aging, first-pass resolution and cash.

    Each carries a value card, runs under approvals and leaves evidence. Finance is where governed agents prove themselves, and from there the approach extends to lead-to-cash, source-to-pay, forecast-to-fulfill and plan-to-perform.

    8. The view ahead

    Over the next several quarters:

    • The gap between pilot and production becomes the metric boards ask about, and tools for cost visibility and attribution move from optional to required.
    • Agent deployment climbs out of the single digits in narrow, high-volume workflows, with the finance close and reconciliation among the first at scale.
    • The trust tax gets an explicit price, showing up in procurement terms and deal structures.

    Further out:

    • "Owned AI assets" enters the CFO's vocabulary as a reported capability, reframing AI from a cost center toward proprietary equity.
    • Model choice becomes a procurement footnote. The strategic conversation moves to data, workflow, governed reuse and evidence. In other words, the harness.

    The model was never the moat. The moat is the system you build around it and own. The organizations that act on that first will spend the next three years building a governed, measurable capability that compounds, while their competitors are still comparing benchmarks. By the time the benchmark race is settled, it will not have mattered.