Skip to content
All guidesAI systems

The harness matters more than the model

Businesses agonise over which AI model to pick. After months of running AI daily, we think the bigger lever is everything around the model: the playbooks, the memory, the checks and the guardrails. Here is what a harness is and how to build one.

5 min read

Ask which AI model is best and you will get a different answer every month. Here is the thing we learned running AI across our own business every day: the model matters less than what you wrap around it. Two companies can use the identical model and get wildly different results, because one hands it a blank chat box and the other hands it a harness.

A harness is everything around the model that shapes its work: the standing instructions, the playbooks it follows, the memory it keeps, the checks its output must pass, and the hard limits on what it may touch. Models improve every few months and you should be able to swap them like a part. Your harness is the part you own, and it is where the compounding gains live.

Playbooks: teach it how your business does things

The single most useful component is a library of playbooks, sometimes called skills. A playbook is a short written procedure for one job, in the same spirit as the standard operating procedures a good operations manager writes: how we quote, how we structure a proposal, what our tone sounds like, what a finished piece of work must include. The AI loads the relevant playbook when the job comes up, follows it, and the output lands close to right the first time.

The comparison that made it click for us is a new employee. Without written procedures, a capable new hire produces plausible work in their own style and you spend the week correcting it. With them, the same person is useful on day one. AI is the same hire, minus the ability to absorb your standards by sitting in the office. Write the procedure down once and every job that follows benefits.

Start with the corrections you make repeatedly

You do not need fifty playbooks. Notice the three corrections you make most often to AI output and write each one into a short procedure. Every playbook you add is a correction you stop making by hand. Ours grew one lesson at a time, and each one was paid for by a mistake we only had to make once.

Memory: stop re-explaining your business

A model remembers nothing between sessions unless you arrange otherwise. The fix does not need to be exotic. A well kept set of notes the AI reads at the start of each session, who you are, what you sell, what was decided last month, gets you most of the value. The discipline that matters is keeping it current: when a decision changes, the note changes the same day. A memory that quietly goes stale is worse than no memory, because the AI acts on it with full confidence.

Checks: define what good looks like, then test for it

The most reliable AI setups we know treat quality as a test the output must pass, not a hope. Before the AI does a job, you write down what a good result looks like in checkable terms: the quote includes every line item, the email contains no banned phrases, the figures reconcile to the source. Then the output is checked against that list automatically, every single time, and failures bounce back for another pass before a human ever sees them.

The habit that makes this compound: every time the AI gets something wrong in real use, that mistake becomes a new check. Slowly you accumulate a net woven from your actual failures, and the same mistake cannot reach a customer twice.

Guardrails: decide what it may never do

The final component is the set of hard limits, and these should be boring, mechanical rules rather than polite requests in a prompt. In our own harness three have earned their keep.

  • A human approval queue for anything outward facing. The AI drafts the email, the post, the invoice. A person sends it. No exceptions, however routine it feels.
  • Closed lists of what it can act on. Where the AI touches business records, it works from a fixed menu of allowed actions, and anything off the menu is refused automatically rather than improvised.
  • No AI in the path of a reported number. Figures a customer or a decision relies on come from ordinary deterministic code. The AI writes the commentary, never the number.

Everything above is how our own company runs day to day, so when we build a harness for a client we are handing over something we trust our own operation to. If you would like AI that works your way rather than its way, we can help you build the harness around it.