Enterprise DNA

Omni by Enterprise DNA

Enterprise DNA Resources

Thought leadership & research. Practical AI operating-system thinking for owners, operators, and teams doing real work.

220k+

Data professionals

Omni

AI agents and apps

Audit

Map the manual work

Key Findings

Most firms waste money chasing model upgrades when their real problem is broken processes. Here's what actually moves the needle.

Fix Operations Before Buying Better Models
Insight ai

Fix Operations Before Buying Better Models

Sam McKay

I see this every week in discovery calls. A firm owner tells me their AI implementation isn’t delivering results. They’re using GPT-4, maybe Claude, running prompts through their team. They want to know if upgrading to the latest model will fix their problems.

The answer is almost always no.

I ask them to walk me through how their team actually uses these tools. What I hear back: someone pastes a client brief into ChatGPT. Another person runs the same brief through a different prompt they found on LinkedIn. A third team member uses their own custom instructions they’ve never shared with anyone else. Nobody knows what anyone else is doing. There’s no standard process, no quality threshold, no way to compare outputs or learn what works.

Then they ask me about GPT-5 rumors or whether they should switch to Anthropic’s latest release.

This is like asking whether premium fuel will fix your car when you haven’t changed the oil in two years.

The Problem Owners Misunderstand

The performance gap in most professional services firms isn’t model quality. It’s operational discipline.

When I audit a firm’s AI usage, I’m looking at their actual workflow documentation. I want to see their prompt libraries, their quality rubrics, their process maps for how work moves through the system. Most firms can’t show me any of this because it doesn’t exist.

What they have instead: a Slack channel where people share prompt tips. Maybe a Google Doc someone started six months ago that nobody maintains. Individual team members developing their own approaches in isolation, with no feedback loop and no institutional learning.

You cannot build reliable client delivery on top of that foundation. It doesn’t matter which model you’re running.

The firms that actually get results from AI aren’t using secret prompts or exclusive model access. They’re using the same tools everyone else has access to. The difference is they’ve built real processes around those tools.

When I look at firms generating 30-40% capacity gains with AI, here’s what I find: documented workflows, version-controlled prompts, clear quality standards, regular team reviews of what’s working. They treat AI tools like any other business system that requires maintenance and improvement.

The firms struggling to break 10% gains? They’re still operating like AI is a personal productivity hack instead of a business capability that needs management.

This isn’t about technical sophistication. I’ve seen 8-person firms with better AI operations than 40-person firms. The difference is whether someone took responsibility for building a system instead of just encouraging people to “experiment.”

What Actually Works

Process discipline beats model upgrades every time. Here’s what that looks like in practice.

First, you need documented workflows for your most common deliverables. Not aspirational process maps that nobody follows. Actual step-by-step procedures that match how work really moves through your firm. If you deliver client reports, strategy documents, technical specifications, whatever your core outputs are—you need a written process for each one.

These workflows should specify exactly where AI tools get used and what they’re expected to produce. “Use ChatGPT to help with research” is not a workflow. “Run client background through the Company Research prompt (v3.2), review output against our standard brief template, flag gaps for manual research” is a workflow.

Second, you need a prompt library that your whole team actually uses. Not a collection of interesting prompts people found online. A working library of prompts that are specific to your firm’s work, tested against your quality standards, and version-controlled so you know what changed and why.

When someone on your team creates a prompt that works well, it should go into the library with context about what it’s for and how to use it. When someone improves an existing prompt, that’s a new version with notes on what changed. This is basic knowledge management, but most firms aren’t doing it.

Your prompt library should be organized around your workflows. If you have a documented process for client onboarding, you should have a section in your prompt library with every prompt used in that process. Team members should be able to follow the workflow and grab the right prompts without hunting through random documents.

Third, you need quality standards and someone checking against them. This is where most firms completely fall apart. They’ll let team members use AI outputs without any systematic review, then wonder why client work feels inconsistent.

You don’t need complicated rubrics. You need clear thresholds. What’s the minimum acceptable quality for an AI-generated first draft? What requires human revision before it goes to a client? What can ship as-is after a quick review? Write it down. Check actual outputs against those standards. Adjust when you find gaps.

I see firms waste incredible amounts of time because they don’t have this clarity. Someone spends an hour manually rewriting an AI output that should have been flagged as below threshold in the first place. Or they send something to a client that needed another revision pass. Both problems come from the same root cause: no defined quality bar.

Fourth, you need regular process reviews where the team actually talks about what’s working. Not theoretical discussions about AI capabilities. Concrete reviews of recent work where you look at what you produced, how you produced it, and what you’d do differently.

This is how you get institutional learning instead of individual learning. When one person figures out a better way to structure a client brief, that insight should spread to everyone doing similar work. When someone discovers a prompt pattern that consistently produces better outputs, that should become part of your standard approach.

Most firms never create this feedback loop. People develop expertise in isolation, leave for another job, and take all that knowledge with them. You’re constantly relearning the same lessons because you’re not capturing and distributing what works.

Fifth, you need to actually measure what matters. Not vanity metrics about how many prompts your team runs. Real metrics tied to your business outcomes.

How long does it take to complete your core deliverables? What’s your revision rate on client work? How much time are you spending on low-value tasks versus high-value client interaction? These are the numbers that tell you whether your AI operations are actually working.

When you have baseline measurements and documented processes, you can test changes systematically. You can try a new prompt structure and see if it reduces revision time. You can adjust a workflow and measure whether it speeds up delivery. Without that foundation, you’re just guessing.

What To Do This Quarter

You don’t need to overhaul everything at once. Here’s where to focus your energy over the next 90 days.

Pick your highest-volume deliverable. The thing your team produces most often for clients. Document the current workflow for that deliverable in painful detail. Every step, every decision point, every place someone currently uses AI or could use AI. Get this out of people’s heads and into a shared document.

Then audit your team’s actual prompts for that workflow. Collect what everyone is currently using. Test them against real client work. Pick the best-performing versions and put them in a shared library with clear labels for when to use each one. Delete or archive everything else so people aren’t choosing from 47 variations.

Set a quality threshold for AI outputs in this workflow. Write down what “good enough for next step” looks like versus what “needs complete rework” looks like. Have your team review recent outputs against this standard. Adjust the standard if it’s wrong, but get something written down.

Run a weekly 30-minute review meeting focused only on this one workflow. Look at real examples from the past week. What worked? What didn’t? What would you change? Update your documentation and prompts based on what you learn. Do this for 12 weeks straight.

Measure your baseline performance now and again at the end of the quarter. Time to completion, revision rate, team member satisfaction with the process. You need to know if this disciplined approach actually improves your operations or if you need to adjust your system.

Once you’ve got one workflow running smoothly with documented processes, quality standards, and regular reviews, expand to your second-highest volume deliverable. Same approach. Build the system piece by piece instead of trying to fix everything simultaneously.

Stop spending time evaluating new models or chasing the latest AI release. The model you’re using right now is probably fine for most of your work. Your constraint isn’t model capability. It’s operational maturity.

The Real Competitive Advantage

The firms that will dominate their markets over the next few years aren’t the ones with the best AI tools. They’re the ones with the best AI operations.

Right now, while your competitors are still treating AI like a personal productivity toy, you have a window to build real operational discipline. To create systems that capture learning, maintain quality, and compound improvement over time.

That window won’t stay open forever. Eventually, someone in your market will figure this out. They’ll build the processes, document the workflows, and create the feedback loops that let them deliver faster and better than you can. At that point, you’ll be playing catch-up while they’re extending their lead.

I’ve spent the last two years running these audits with firms across professional services and trades. The pattern is consistent: process discipline creates more value than model selection. The firms that internalize this lesson early are pulling away from their competition. The firms that keep chasing shiny new models are standing still.

If you want to see where your operations actually stand, book a 60-minute Omni Audit with me. We’ll walk through your current AI usage, identify your biggest operational gaps, and map out a practical path to building real capability. No sales pitch, just a structured look at what’s working and what’s not.

You can grab a time here: https://calendly.com/sam-mckay/discovery-call?utm_source=edna-landing&utm_medium=insights&utm_campaign=insight-ops-before-models

Stop waiting for better models. Start building better operations.