Innovation
Insights · Innovation

Why we built an operating system for our AI

Point a capable model at a messy business and it hands you confident nonsense. Here's the foundation we built first, and the rules it runs on.

Everyone’s racing to bolt AI onto their business right now. The ones who get burned are usually the ones who skipped the unglamorous part first.

That part is knowledge. Not the model, not the prompt, not the tool you added to your inbox last week. Point a capable model at a messy business, and it hands you confident, well-written nonsense. It answers with a document that’s three versions out of date. It repeats a number that stopped being true last quarter. It fills in whatever it can’t find with a convincing guess. We know, because we watched it happen to us before we fixed it.

The problem nobody wants to talk about

When AI gets it wrong like that, look underneath the model before you blame it. The trouble is almost always the knowledge it’s standing on. The model does exactly what you asked, on top of a foundation nobody built to be trusted.

Most companies hit this and blame the AI. But the gap sits upstream. If what you know lives in dozens of slightly different copies, scattered across drives and inboxes and a few people’s memory, no model can tell you which copy is right. It just picks one and sounds certain.

Why we built it in the first place

Honestly, AI wasn’t even the first reason. Our own way of working had quietly stopped scaling.

For years, a lot of what kept Counterpart moving lived in a few people’s heads. What a client had actually agreed to. Why a decision went the way it did. How we price the genuinely hard problems. That holds up at ten people. At twenty, it starts to bind, and when those few people were heads-down or out of office, everyone else waited on them.

So the first goal was pretty ordinary. Get what a handful of people knew out of their heads and into something the whole team could reach. Pointing AI at it came later, once we finally had a foundation worth pointing anything at.

What we built

We built a layer that sits between the AI and the company, and we run our own business on it. We call it our AI operating system.

Underneath is one governed knowledge base: a single, current record of who we are, how we work, what we’ve promised clients, and how the place actually runs. The AI sits on top and reads from that record instead of improvising. We can replace the model whenever a better one shows up. The discipline underneath is the part we protect, and it comes down to a handful of rules we don’t bend.

One home for every fact. Anything true lives in exactly one place, and everything else points back to it. The second you keep copies, one gets updated, and the others quietly go stale.

Nothing sticks without a source. Every durable fact records where it came from. If the system can’t show you where it learned something, we don’t rely on it, and neither should you.

A person approves anything that matters. The AI drafts, proposes, and preps all day, but it doesn’t send the email, bill the invoice, or change a record on its own. Those moments stop and wait for a human. That single rule separates a useful assistant from an expensive mistake.

Roles, not free rein. The system knows what each person is actually cleared to decide, and it hands everything else to whoever owns it.

Some things stay off limits. There are whole categories it will never write down, no matter who’s asking. A guardrail you set once, in plain words, holds up better than good intentions you have to remember every time.

The model is ours to swap. The data stays ours.

We built the operating system so it never leans on a single AI vendor. The knowledge, the rules, the guardrails: all ours. The model is just the engine we point at, and we can switch engines without rebuilding the company around whatever’s new. That keeps us out of the trap a lot of leaders are quietly losing sleep over, where the whole business rides on one provider’s pricing, terms, and roadmap.

It also lets us be strict about something that gets more important every month. Everything we know, and everything our clients have handed us in confidence, lives in that layer. So we run it only on team and business licenses that contractually bar AI companies from training on our data. What we put in stays with us. We don’t leave that to a default setting.

What we get out of it

Mostly, trust. Because the foundation is clean and the guardrails actually hold, we can give the AI real work. It drafts a quote off our own history instead of a hunch. It answers with today’s number and points you to exactly where that number lives. And when something genuinely needs a human, it says so rather than quietly deciding for you.

That’s a long way from typing questions into a chat box and hoping. It only works because the boring part came first.

The same discipline shows up in the complex systems we build for clients. The hard part of custom software is the structure underneath, the part that keeps everything honest as it grows. AI has only raised the stakes on that structure. A clean, well-governed foundation is worth more today than ever, and a messy one is far more dangerous. If you’re planning to lean on AI, most of the work that matters happens before the AI ever runs.

Talk to us

Bring us the hard version of your challenge.

Thirty minutes with a senior engineer, no pitch and no pressure. Whatever you decide, you'll leave with a clearer map of what you're about to do.

Start the conversation Keep reading