ERP or accounting, email, shared drives, shop tools, CRM, spreadsheets, forms, scheduling, and whatever else the work touches. I map the path between them so the business can run as one operation.
Manufacturers | Ag and equipment | Construction | Family-run
You don't have to know what to call it. If you've caught yourself saying any of these, that's the work.
I wish these two systems just talked so we weren't keying everything in twice.
Half of what I need is already in the other software. I just can't get the two to line up.
Our website form dumps into an inbox, then somebody retypes it into the CRM.
It'd save us hours if this just generated the quote on its own.
We pay for this software and use maybe a third of it. Nobody's got time to fill it all out.
I want my people doing the work, not typing the same thing into three screens.
We've got piles of good data and no clue what to actually do with it.
I'd love a dashboard that tells me how we're doing, without me rebuilding it in Excel every Monday.
Somebody asks "where's that order" and we go walk the floor to find out.
I can't tell you which jobs actually made money until the books close.
I've got a process in my head I've never been able to hand off.
If our key person ever leaves, half of how we run walks out the door.
I'm always the one filling in the gaps and chasing the loose ends.
The follow-up nobody owns, so it only happens when somebody remembers.
Different business, different list. Same fix: I make your systems talk and take the busywork off your people, so the business runs as one operation, instead of living in your head.
I map one live workflow: a quote, repair, job, order, delivery, customer request, or report. We follow where it stalls, who carries context in their head, and which gap is costing the most attention. Fixed scope, before anything gets built.
One workflow, followed end to endI connect the systems you already run. Nothing gets ripped out, nobody relearns their job. The path sits on top, on infrastructure you control, and the work starts moving between departments with less chasing.
Connect what exists. Replace nothing.I stay in the work with your team until it holds. We adjust the path as the business moves, instead of dropping a binder and disappearing. You own the system. I help keep it sharp.
Stay close enough to see the work
years running regional operations: sales, service, and P&L.
Operations Layer is led by Blake Thomas. Seventeen years in agriculture and equipment operations (sales, precision ag, store management, P&L) gave me a deep, hands-on read on how regional businesses actually run. I'm a problem-solver first; AI just changed how fast I can turn that operational knowledge into systems that work. The work here is hands-on, bounded, and shaped around how your business already moves, built on the systems you already run and on infrastructure you control, never from a template. Good people get buried by bad systems. I build the systems that dig them out, not replace them.
Before I built operating systems, I went shopping for them. Sitting in the seat with a real problem, I scoured the internet for the one tool, or the handful I could stitch together, that would finally fit. Some promise you the world. Others you look at and think, maybe I can make this work. So you book the demo, sit through the web call, and it doesn't quite fit the bill. Then the sales team finds you and won't quit. Every channel, every week, by any means they can. That was me, hunting for a fit that didn't exist. Now I build it instead, for any kind of operation, shaped around the way the work actually moves.
Not in the off-the-shelf sense. It is a custom operating layer shaped around one workflow, the systems you already use, and the decisions your team needs to make.
We look at one real workflow, talk through who is involved, review the information people rely on, and identify where handoffs, lookup, review, or decision-making are harder than they should be.
The workflow, the people involved, the source material, the review points, boundaries around private information, and the outcome that would make the work meaningfully easier.
Usually no. Most businesses already have accounting software, shared drives, email, spreadsheets, and job folders. The opportunity is often the layer between those systems.
No. The goal is not to force one tool on the company. The goal is to connect the communication around the workflow. That may involve Slack, email, forms, shared files, dashboards, or the systems your team already uses.
Often, yes. When it is useful and appropriate, it can use APIs, automations, secure connectors, or custom integration points to connect existing systems, documents, communication tools, and workflow data.
Quoting, estimating, customer requests, parts or support lookup, project handoffs, internal approvals, service follow-up, and repeat decisions that depend on tribal knowledge.
AI is useful only when the source material, workflow, review points, and human decision are clear. The goal is not automation for its own sake; it is better access to the right context at the right moment.
No. The first step is usually understanding what exists, where people already look, and what information is trusted. The pilot should be shaped around that reality.
You own your data, your accounts, and the system built for your business, and it runs on infrastructure you control, so you are never locked into me or held hostage by a vendor. The reusable methods and building blocks I bring to every engagement stay mine; you get full use of them, sharpened by the work I have done before. The specifics are spelled out in a simple agreement before anything starts.
Everything starts with a paid Operations X-Ray, a focused, fixed-fee look at one part of the business. From there, most work is a fixed-scope build, with optional ongoing support if it makes sense. You always know the scope and the price before anything begins.
Tell me where work is getting stuck between people, departments, documents, or systems. I read every note myself and reply directly.
blake@operations-layer.net