What is a Business Operating System – Part 1/6
What is a Business Operating System Part 1/6
Most consulting businesses grow fast and organise slowly. The result is scattered information, duplicated effort, and a founder who becomes the single point of failure for everything. In this video I walk through what a Business Operating System actually is, why you need one, and the five layers that hold it together. Built around three tools: Pipedrive, Notion, and Make.com.
Looking for support with Automation and AI – see my Business Business Operating System Page
Get the FREE Automation Audit mentioned in the video.
Transcript
Things are falling through the cracks. The founder is working harder than ever. And somehow less is getting done.
The problem isn’t the people. It’s never the people. It’s the systems or the lack of them. Today, I’m going to show you three specific warning signs that your business is outgrowing its systems, what each one is costing you right now, and exactly what to do about it without buying yet more software subscriptions.
Hi, I’m Chris Wray. I work with business owners and team leaders to build operating systems across sales, delivery, and operations. So work moves without everyone chasing each other and the numbers tell the real truth.
So sign number one, you don’t have a single source of truth. The first sign is simple. Your critical information lives in multiple places and nobody has the full picture. It usually kind of looks like this. CRM has some of the truth. The project management tool also has some of the truth. The most important context is in email threads and WhatsApp messages. Renewals, pricing, or delivery details live in spreadsheets.
So, why does this matter? Well, you cannot make good decisions with partial information. Follow-ups, you’ll find, start to slip, and clients feel it even if they never say so. So do this test right now. Pick one of your active clients and try to answer these questions in 60 seconds. So what have they bought? What’s happening next? Who owns the next step? When is the next key date? Something like a renewal, a deadline, or a payment. If you can’t answer without switching tools, your system is warning you. The practical fix. Decide where the truth lives for each thing. The sales relationship truth in your CRM, the delivery truth in your project management system, the process and knowledge truth in a knowledge base. Then connect the tools so you’re not copy pasting your business into existence.
Sign number two, you’re repeating work that should be handled by systems. You’re spending real hours every week on work that is entirely predictable. This might be writing the same onboarding email, copying details from your CRM into a proposal, manually creating tasks every time a deal is won, answering the same questions again and again. Here’s a rule of thumb. If a task takes more than 10 minutes, happens more than twice a month, and follows a predictable pattern, it’s a systems candidate.
So here’s what you can do. List your top 10 repeated tasks from the last two weeks. Say highlight the ones that directly touch revenue or client experience and just start there. I ran this exercise with a marketing agency last year. So they had eight people solid revenue in just three areas reporting, onboarding and data entry. We found around 11 hours a week of fully automatable work. That’s across the team, but still 11 hours gone every week on tasks that added zero value to a single client.
Within 6 weeks, most of it was automated. Those hours went back into client work. Revenue went up unsurprisingly and the founder got her Friday afternoons back. And this is where most people make the expensive mistake. They buy a tool or software hoping that it fixes the process. In my experience, most automation projects fail because businesses skip discovery and jump straight into implementation. They automate the wrong thing. They build something nobody ends up using and the practical fix. Document the workflow first. Even a handdrawn scribble of the flow is fine. Then automate the handoffs and only then when it genuinely helps add AI summarizing calls, drafting first pass proposals or sort of routting requests.
So, we’ve covered two signs. Information that’s scattered and work you’re repeating unnecessarily. Sign three is the one that tends to hurt the most because it’s the hardest to see from the inside.
Sign three is growth only happens if you push harder. The third sign and the most important one. You feel like growth is possible but only if you personally push harder. And that usually means you are the bottleneck for decisions. You are the bottleneck for follow-ups and you are the person holding the context that your team needs to move the work forward.
This is not a character flaw. This is a systems problem. If you leave it, the pattern is generally predictable. Response time slow down. You start to see small mistakes. You get client issues. Your best people start to get frustrated. And you spend more time managing the work than doing the high value work that actually grows the business. Again the practical fix you need a simple operating system for the business. So not software a way of doing the work with the right tools supporting that work.
The fix build a business operating system. When I say business operating system, I mean your workflows, your tools or your software and your automations all working as one system.
Here’s the framework that I use with my clients. The first step, discovery before implementation. This is the step almost everyone skips. Discovery means document how the work actually gets done, not how you wish it worked. Assess your systems honestly. Identify the highest return on investment opportunities. Prioritise by impact versus complexity and get buy in before you build a single thing. If you do this first, implementation becomes straightforward. If you skip it, you spend months fixing the wrong things.
Step two is choose your core four, as I describe them. Most service businesses need four foundations. a CRM for sales and client relationships, a project management system for delivery, a knowledge base for SOPs and some of your client context, and then an automation layer that connects all the tools together. The tools vary, but the principle stays the same.
Step three, build one clean client view. So give your team one place to see what was sold, what’s happening now, what happens next, and where the risks are.
Step four, automate the boring, but protect the human. Start with the biggest time syncs that also reduce mistakes. So onboarding, follow-ups, renewals, proposals, reporting. The common mistakes. When a system starts to feel heavy, most people do something quickly just to get that relief. That’s totally understandable, but it usually creates new problems a month later.
Before you copy someone else’s tech stack or buy a template or the next tool, just watch out for these. buying software before documenting the workflow, trying to change everything at once, choosing tools that don’t really integrate, and ignoring how clients actually communicate. If your clients live in WhatsApp or email, your workflow has to respect that. They’re not going to use your new fancy portal. If you recognised yourself in any of those three signs, don’t buy yet another tool or piece of software. Start with discovery.
I offer a free 30 minute scoping call where we look at your current workflow, your tools, and your software, and where the real friction is. If a systems diagnostic is the right next step, I’ll let you know what it looks like. And if it isn’t, well, I’ll tell you that, too.
The link is in the description below. And if you’re not ready for a call yet, I’ve also put together a free business automation audit template link in the description. It walks you through the same diagnostic I use with clients. And if you found this interesting and you’re also considering AI, you might want to watch this video next.
Prefer to talk it through ?
Book a Free Scoping Call or take a look at the main Business Automation Consultant page.
Related Posts:
The Business Operating System vs Spreadsheets
The Business Operating System vs Spreadsheets Most service businesses think they have systems. In this video I explain what a...
The knowledge layer of a Business Operating System – Part 6/6
The Knowledge Layer of a Business Operating System Part 6/6 If the answer to most questions in your business is "ask Chris",...
The Finance Layer of a Business Operating System – Part 5/6
The Finance Layer of a Business Operating System Part 5/6 Most business owners have a rough sense of their revenue. A rough...






