Every AI feature you have bought or built is two things stacked. A foundation model that reasons, and a harness that tells it what to work on, what to read, which tools to call, and which limits to hold. The model layer is becoming a commodity, interchangeable and cheaper every quarter. The harness is where durable advantage lives, and almost every harness running in production today was engineered by a vendor and calibrated to an average buyer.
Anything an AI vendor can sell you, your competitor can buy at the same price and the same depth. The one capability no one can sell you is the one built from your rubrics, your standards, your institutional history, and the way your firm actually decides. When you engineer that logic into a harness, you gain a massive competitive advantage.
Whose logic runs your AI?
A harness is the engineered environment around a model: the instructions, retrieval, tools, memory, evaluation, guardrails, and human checkpoints that turn a general reasoner into a capability that does highly specific work.
A vendor's harness encodes a vendor's idea of best practice for a representative company. That is the right design choice for a product sold to thousands of buyers, and generic logic produces generic results. Logic built from how your firm actually operates produces results calibrated to your firm, and that caliber of capability is not for sale anywhere.
The one layer that doesn't commoditize
Pull a harness (or agentic AI system) apart and you find some combination of dozen or so working parts: triggers, schedulers, automations, classification, retrieval, tools, state and context, observability, guardrails, human-in-the-loop checkpoints, orchestration, and logic.
All agentic/harness componenets are commoditized infrastructure, available to anyone and rapidly improving. All except one. The logic layer that carries encoded judgment, is a massive moat when engineered correctly. It is the one part a vendor cannot ship to you, because a vendor has never sat inside your operation.
Why owned capability compounds
Not only do commercial AI products have generic logic, but they also create "islands of intelligence" and tech sprawl. Each arrives with its own login, its own contract, its own pricing. Stack ten of them and you have ten islands rather than a system. A harness you own can architect across these islands, can read from and write to them, or can stand apart. You have endless flexibility.
As you build successive custom logic layers to power different use cases, these can pull from a common infrastructure and can inform each other. This is a core aspect of Talbot West's Cognitive Hive AI (CHAI) framework.
Each capability sits on shared architecture and inherits from other logic layers, so the second build is cheaper than the first and the tenth is cheaper still. The exact proportions depend on how many capabilities you eventually deploy and how much of your existing stack the harness composes against rather than replaces, and the direction holds under any reasonable assumptions.
The work with no compile step
Some AI work has cheap ground truth. Code either compiles and passes its tests or it does not, so a harness for a coding agent can catch failure after the output exists. Most enterprise work has no such check. If you think about a brief, a disclosure, an analysis, or a proposal, nothing automatically tells you the output is shallow, off-standard, or subtly wrong.
The failure mode is fluent shallowness, and a thin tool will produce it with confidence. A harness for this kind of work has to structure the reasoning before the output exists, moving the model through the standards and steps your experts would apply. This is the harder discipline, and it covers most of the valuable judgment work in a company.
A well-built harness moves a model reliably upward. On judgment-bound work, the last stretch still belongs to a person, and anyone promising full autonomy on taste-bound work is selling against a wall that has not moved yet and is unlikely to.
Where a harness lives
The discipline of harness engineering is agnostic to tech stacks and environments. Harnesses can take infinitely many configurations, and this flexibility intimidates the uninitiated while providing those with mastery an endless set of options.
Here are some of the many instances of a custom harness.
- 05-A
The harness exists completely inside a single piece of software. For example, business logic encoded as Skills inside the Claude app.
- 05-B
The harness lives inside a single cloud service or productivity suite (e.g., AWS Bedrock, Microsoft 365, Google Cloud) and spans multiple apps or software surfaces in the same family.
- 05-C
The harness spans several dissimilar software surfaces, with handoffs or integrations between them. Example: a set of documents in Sharepoint, reasoned over with Claude, with Zapier triggering actions and events.
- 05-D
The harness lives in a dedicated surface, and integrates to external systems. Example: A complex build-out in AWS Bedrock that reads from (and selectively is able to write to) Salesforce, Workday, Sage Intact, and other systems.
This flexibility accommodates every conceivable use case, enterprise tech stack, budget, timeline, compliance environment, and set of priorities. There's a perfect harness for every situation. Some can be deployed in a day, others may take several months. Some require no code at all, while others involve extensive custom development. Some involve extensive tooling, triggers, sequences, and integrations, while others need only a reasoning layer.
Some categories of work where harnesses deliver
The most non-commoditizable, high-value harnesses tend to be those that optimize high volume processes that involve nuanced judgment, carry a heavy cost of error, and require senior people whose hours are the bottleneck. Here are a few of the general categories we've seen.
- Regulated and high-stakes writingFilings, disclosures, regulatory submittals, and capital-markets materials, where voice and accuracy both carry weight.
- Engineering and operational documentationBriefs, specifications, and technical reports that encode senior judgment and look similar from one to the next.
- Institutional knowledge codificationThe rubrics and decision patterns held in a few heads, captured in a form the operation can query after those people leave.
- High-volume document workflowContracts, leases, and clause work where most items are routine and the rare exception is what needs a human.
- Revenue and sales reasoningAccount research, call coaching, and outreach that reason from your playbook and your wins rather than generic market data.
- Templated communication at scaleStakeholder, customer, and community correspondence in your voice and branding.
A harness use cases addendum takes several of these categories and shows what a harness for each one looks like inside a specific kind of business.
What to ask before your next AI purchase
The next AI tool you buy will arrive with someone else's logic already inside it, tuned for a company that is not yours. That serves commodity work well enough. For the work that actually distinguishes your firm, the more useful question is what your own logic is worth once it is encoded into a system that can run it at scale, and who you want engineering that system. Advanced custom harnesses will be the most durable competitive advantage of the next few years for the firms that build them, because they are the one capability a competitor cannot acquire by signing the same contract you did.
