The Commercial Operating System: A New Definition of Sales in 2026
What a Commercial Operating System is: data, rules and tools tied into one sales flow. Four design questions, a phased path, and when not to build one.
Table of contents
What is a Commercial Operating System?
A Commercial Operating System, abbreviated COS, is the overall framework your commercial work runs on: data, rules, tools and the agreements about who does what. The term is not a standard, and there is no single product you can buy and get a COS. We use it as a way of thinking: instead of a pile of tools that each have their own version of the truth, you build one connected flow from the first enquiry to the invoice.
The mindset is useful because most sales organisations do not have a tool problem. They have a connection problem. There is the CRM, email, calendar, telephone, spreadsheets, a quoting programme and an accounting system, and between them sit people copying.
TL;DR:
- A COS is a way of designing the flow of sales, not a product. It is about letting data and decisions flow without manual work in between.
- Four questions shape the design: where does the truth live, what may be automated, who approves, and how do we measure?
- It only works if the CRM is already used consistently. Otherwise you are just automating a gap.
Why do traditional tool stacks fail?
A typical sales organisation has bought tools one at a time, each time with a good argument. The result is a stack where:
- Data exists in several places. A customer has one phone number in the CRM, another in the invoicing system and a third on a salesperson's phone.
- People are the glue. When a meeting is over, someone has to type what was said into the CRM. When an agreement is made, someone has to type it into the accounting system.
- No one owns the whole. Marketing owns one tool, sales another, finance a third. No one is responsible for the flow between them.
- Knowledge sits in people's heads. How a customer usually has it, and what was promised last time, is known only by the salesperson who was there.
This is not a question of the tools being bad. Each of them can be good in itself. The problem arises between them.
How do you design a COS? Four questions
Instead of starting with tools, start with four questions.
1. Where does the truth live? For each type of information: where is the authoritative source? The customer's contact details, the status of the agreement, the price, the delivery date. If there is one place, everything else can read from it. If there are three, you must choose.
2. What may the system do by itself? Divide the tasks into those that are routine and rule-based, and those that require judgement. Routine can be moved to the system. What requires assessment stays with the human.
3. Who approves what? Everything that goes out to a customer, and everything that changes a price or an agreement, should require a human's yes. Make the list explicit. That is what makes the system safe to use.
4. How do we see whether it works? Decide in advance what will be measured, and what the starting point is today.
These four questions are also the way we work when we build solutions for customers: you decide what the system may do by itself. Everything else waits for your approval.
What does it look like in practice?
A COS is not one large, integrated building. It is a series of small, delimited flows, each solving one concrete thing. Here are four that many sales organisations will recognise:
| Flow | What happens today | What the system can take over | What still requires a human |
|---|---|---|---|
| The meeting is over | The salesperson types notes and fields into the CRM in the evening | Write up the notes, suggest fields and put the next follow-up in the calendar | Approving, and everything that goes to the customer |
| Old enquiries | Enquiries that were never followed up sit in the inbox | Gather them and have draft replies ready | Choosing which to follow up, and sending |
| Quotes | Quotes are written by hand once the information has been found | Gather the information and calculate a draft on your own prices | The price, if it requires assessment |
| Weekly overview | Three spreadsheets are put together before the meeting | Gather open tasks, quotes and invoices, with sources | Deciding what should be done |
Several of these can be seen as examples on the use cases page. The examples use invented names and figures. They show the structure, not a result you can count on.
How do you get started?
A phased path is safer than a large overhaul.
Phase 1: Review what you have. Map your tools and where data is moved between them by hand. Write down who does it, and how long it takes. Ask the people who are sitting with it.
Phase 2: Choose one flow. The one where the pain is greatest and the rules are clearest. Build it finished before you go further. A flow that works every day is worth more than four half-finished ones.
Phase 3: Measure and adjust. Compare with the starting point. Talk to the people who use it. Fix what does not work.
Phase 4: Add the next. When the first runs without supervision, you take the next. Over time you build a system that holds together, without anyone having to shut the company down to do it.
Which measures are worth tracking?
There are no numbers that apply to everyone. Choose measures that fit the flows you are building, and measure them before and after. Examples:
- Time from meeting to updated CRM
- The share of agreements with a recorded next follow-up
- How many enquiries are unanswered after a set time
- Time from enquiry to quote
- How much manual re-entry remains (ask the people who do it)
- The salespeople's own experience: do they use it, and do they trust it?
Be wary of measures that only measure activity, such as the number of emails or calls. Measure what matters to the business.
What distinguishes a COS from RevOps and a CRM?
CRM is a tool where customer and agreement data lives. RevOps (revenue operations) is a function, or a way of organising, in which marketing, sales and customer service share processes and data. A COS, in our use of the term, is the technical and organisational framework that binds the tools together, so that the RevOps work does not have to be done by hand.
The three do not exclude each other. A COS without a proper CRM is weak, and a CRM without anyone owning the whole becomes an archive.
What role does conversation analysis play?
Conversations are an important data source, because most of what the customer actually says never reaches the CRM. If you are allowed to record and write out conversations, the content can be used to fill in fields, discover tasks and learn from the best conversations. If you do not require recording, a salesperson can instead dictate a short status. We go through the rules and requirements in our guide to call recording in Denmark, and in the guide to conversation intelligence you can see the different routes you can take.
When is a COS not worth building?
It is just as important to say when you should not.
- If the CRM is not used today. Automation does not solve a lack of discipline. It makes the gap faster.
- If sales are very small or very special. When each deal is its own and sits with one person, there is nothing to systematise.
- If you do not know what takes the time. Then start by measuring.
- If the requirement is that the AI should decide. That is not a good starting point. Let it prepare and suggest.
What mistakes are most common?
A big plan, nothing finished. Many start with a vision of the end state and end up with five half-built flows. Build one finished first.
Tool first, process afterwards. The purchase of a new tool becomes the solution before the problem has been understood.
No clear owner. Someone must be responsible for the flow, also after the project is finished.
The salespeople are not asked. They know best where the time disappears, and they decide whether it gets used.
Data mess is not cleaned up. The AI repeats the errors in your data faster than you can correct them.
What can Agent360 contribute?
We build AI solutions in the customer's own systems. That means we build on top of what you have, not beside it. We contact your suppliers and help with access, and you are copied on everything throughout. The first flow we build is completely finished before we build further, and the price depends on the task. We can connect to HubSpot, Salesforce, Pipedrive and Microsoft Dynamics, as well as telephony and calendars.
If you would rather learn to do it yourself, there is a personal AI mentoring programme. Here you work on your own tasks and learn to plan, build, test and publish.
Frequently asked questions about the Commercial Operating System
Q: What is the difference between a COS and a CRM? A CRM is a tool where data lives. A COS is the framework around it: the rules for how data flows between the tools, and who approves what. A COS builds on your CRM; it does not replace it.
Q: Can a COS be introduced gradually? Yes, and we recommend it. Start with one flow, build it finished, and take the next one when the first runs without supervision.
Q: How do you ensure GDPR compliance when AI analyses conversations? By having a clear basis for recording, informing those who are recorded, setting retention periods and having data processing agreements with your suppliers. Read more in the guide to call recording in Denmark. Have a lawyer assess your specific setup.
Q: What is the ROI of a COS? We cannot say that in advance, and we are sceptical of anyone who can. Measure your starting point, choose one flow, and compare afterwards. Then you have your own figures.
Q: Does a COS replace my existing tools? Usually not. It is built on top of them. Sometimes it turns out that a tool is not used, and then it can be retired. But that is a consequence, not a goal.
Q: What does a COS require of IT infrastructure? Access to the systems that are to be connected, and one person in your organisation who can say yes to permissions. We can help with the rest.
Q: What does it cost? The price depends on the task: how many systems are connected, how much approval logic has to go in, and how much data has to be cleaned up. We give an estimate after a short conversation.
Conclusion: From a stack of tools to a connected flow
A Commercial Operating System is not a product, but a discipline: decide where the truth lives, what the system may do by itself, who approves, and how you measure. Build one flow at a time, and let people keep their judgement.
Book 20 minutes of free advice if you want to hear which flow in your business is worth starting with. We will also tell you if none of them are. See also examples of tasks we can help with.
#sales-strategy#revops#automation#crm#ai-implementation
Contents
Should your sales reps spend their time talking?
We have built it for our own sales: the call is transcribed, the AI suggests the outcome, and the email is ready. We look at how your sales run today.
Book a reviewShould your sales reps spend their time talking?
We have built it for our own sales: the call is transcribed, the AI suggests the outcome, and the email is ready. We look at how your sales run today.
How we built it · Sales & follow-up
Sales cockpit with AI
A call list for salespeople. The call is transcribed in Danish, AI suggests the outcome (e.g. “Call again”) and drafts the email based on what the customer said.
- The salesperson calls
- AI writes transcript and email
- The salesperson sends
Related articles

MFA: multi-factor authentication for your business – how to get started
Learn how to implement MFA securely in your organisation. Guidance on methods, costs and best practices for protecting company data.

English-language invoices: requirements for invoices to foreign customers
Invoice in English to foreign customers legally. Danish regulations, EU and international VAT rules, zero-rating, reverse charge, and automation.

Public Procurement in Denmark: how to bid for government contracts
How Denmark's Public Procurement Act works for suppliers. Threshold values, tender procedures, exclusion grounds and AI solutions for proposal management.