Every owner we walked into said the same three words.
"We need systems."
Sometimes it was "we need SOPs." Sometimes it was "we need to systematise the business." Sometimes, when the conversation had been going for a while, it became "we need our team to stop asking me the same questions."
All the same problem, dressed in different language. And here was the issue: the language was the problem.
If the thing you sell shares a name with twelve other companies' offering, the conversation collapses into a price comparison and a feature war. "We need systems" leads straight to a Google search that surfaces operations consultancies, SOP-writing services, process mapping firms, software vendors, and AI tools. The buyer ends up confused. The seller ends up commoditised. Everyone loses.
That's the trap of operating inside someone else's category. You compete on someone else's terms, with someone else's vocabulary, against people who can outprice you because they're solving an adjacent but different problem.
So we did something most service businesses never bother to do. We named our own category.
The problem with the existing language
Before we got to Codified Operational Intelligence™, we tried using the off-the-shelf vocabulary. It didn't fit.
"Operations consulting" missed the point. We weren't selling advice. We were producing an artifact, a documented, navigable, AI-augmented Playbook the business actually ran on, and we were guaranteeing the output. Consultants don't usually do that.
"Process documentation" missed the point in the other direction. Documentation is a deliverable. What we were producing was infrastructure, designed to update, surface, and stay accurate after the engagement ended. Calling it documentation made it sound like a binder.
"SOPs" was even worse. SOPs are the implementation, not the asset. Calling the asset "SOPs" is like calling a building "drywall."
"Knowledge management" got closer but lived in the wrong neighbourhood. The phrase carries 30 years of enterprise-software baggage. It also under-describes the work, because the most valuable knowledge in a service business isn't filed in a database. It's in the heads of three or four senior people who can't tell you what they know.
Every available word for what we were doing made the work sound smaller than it was, or pointed buyers toward a different sale entirely.
The shift: from documentation to intelligence
The reframe that opened the door was treating operational intelligence as a noun.
Every business runs on operational intelligence, the decisions, judgements, processes, standards, and tacit know-how that make the business actually work. Most of it is uncodified. It lives in people, scattered across conversations, half-written in old emails, surfaced only when someone asks the right question.
That's the asset. Not the documentation. Not the SOPs. The intelligence itself.
The work of codifying it, getting it out of heads and into structured form that survives the people who built it, is a category of work nobody else was naming clearly. Once we named it, the conversation with prospective clients changed in a single meeting:
Before: "We can help you document your processes and build SOPs."
Buyer hears: SOPs. Binder. Consultant. Probably won't work. Let me check what this costs versus other quotes.
After: "We codify your operational intelligence so it stays, even when the people who built it move on."
Buyer hears: a thing I can point to. An asset I own. A risk I'm carrying that has a name now. Tell me more.
Same work. Different conversation. The vocabulary did the lifting.
What naming a category actually buys you
"Category design" sounds like a marketing exercise. It isn't. Or rather, the marketing is downstream of a real strategic shift.
Naming a category gives you four things, in order of importance:
1. A way for the buyer to see the problem. Most buyers don't have words for their own pain. They have symptoms. "My team keeps asking me the same questions." "When my estimator left, things fell apart." A category name lets them point at the actual problem and recognise it as a thing. Before the name, the buyer thinks they need ten different services. After the name, they realise it's all one thing.
2. A way to escape commoditisation. If you sell "consulting" you compete with every consultant. If you sell "Codified Operational Intelligence™," you don't have direct competitors, because nobody else uses that vocabulary. The market hasn't sorted you against alternatives yet, so the conversation stays focused on whether the problem is real, not on whose pricing is sharper.
3. A way to align the whole delivery. Once you've named the category, the methodology, the deliverable, the team, the proposals, the case studies all line up behind it. ControlShift™ isn't the brand of our consulting service. It's the named methodology that produces Codified Operational Intelligence™. The methodology serves the category, not the other way around.
4. A way to attract the right buyer. The wrong buyer sees "Codified Operational Intelligence™" and bounces. They wanted a cheaper SOP writer. Good. The right buyer reads the phrase, recognises their own situation, and books a call. Filtering at the vocabulary level saves both sides from a bad fit.
What category creation actually takes
It's tempting to think category creation is a naming exercise. Pick a phrase, register a trademark, put it on the website. Done.
That isn't it. A category that holds requires three things, all of which take real work:
An actual underlying asset. The category name has to point at something real. If "Codified Operational Intelligence" didn't have a concrete definition, a five-layer structure, a guaranteed deliverable, and a methodology behind it, the name would be marketing fluff. It works because the asset is real. Buyers can hold it, read it, query it, use it. The name describes a thing that exists.
A repeatable methodology. Naming a category without a way to produce the outcome is selling something you can't deliver. ControlShift™ exists so that Codified Operational Intelligence™ isn't a one-off artifact dependent on the genius of the consultant. It's the structured eight-stage process that produces the asset every time, regardless of the industry or the operator. The methodology is what makes the category defensible.
Discipline to stay inside the language. The temptation, especially early, is to soften the vocabulary so prospects understand faster. "It's basically operations consulting" sounds easier in the moment. It also undoes everything the category name was built to do. Holding the language, in every conversation, in every proposal, in every piece of copy, is what eventually trains the market to recognise the category. Drift two steps back into generic vocabulary and the buyer goes right back to comparing you with consultants.
The work is years long. The payoff is owning a piece of mental real estate the market starts using on its own. When a buyer says "I think we need to codify our operational intelligence" before we ever say it to them, the category has done its job.
The deeper point
Most service businesses spend their lives competing inside categories someone else built. They compete on price, on speed, on relationship, on the small edges they can carve inside someone else's market.
The few that escape do it by naming the work they actually do, building the asset that backs the name, and refusing to drift back into the surrounding vocabulary even when it would be easier.
Expansive EDGE isn't an operations consultancy. It produces Codified Operational Intelligence™, the structural capture of how a service business actually runs, so it stays, even when the people who built it move on.
The sentence is precise on purpose. Every word in it was chosen to put us in a category of one. The work that lets us hold that position is the work we'd be doing anyway. The naming is what makes it visible.