Your business shouldn’t run on three screens that don’t talk, five spreadsheets, a wall of sticky notes, or one person’s memory.

I follow one real job through your business and mark every spot where it sits waiting or gets typed in twice. Then I connect the software you already have, so that stops. AI can take the busywork. Your people still make the decisions.

I don’t sell software, and I don’t take referral fees on anything I recommend.

Works with what you already run.

Nobody has to learn a new platform. The software you picked stays, and so do the logins.

  • QuickBooks
  • Excel
  • Google Sheets
  • Outlook
  • Gmail
  • Microsoft 365
  • HubSpot
  • Salesforce
  • Google Drive
  • OneDrive
  • Dropbox
  • Microsoft Teams
  • Slack
  • Shop and dispatch software
  • Text messages
  • Paper forms

Names are examples of what I connect to. I’m not partnered with or paid by any of them.

How it grows

Start with one job. Add the next piece when it holds.

Nothing gets switched over all at once. One job gets typed once, then the next piece branches off it, and over time more of the busywork plugs into the same software you started with.

One example of five. Pick the kind of work closest to yours.

Watch the shape when you switch. It stays the same, because the gaps are the same. Only the names change.

Illustrated example · made-up business

The problem

Problems buying more software won’t fix.

Seven signs your business has outgrown retyping, spreadsheets and one person’s memory.

The systems don’t talk. The same order gets typed into three screens: the form, the spreadsheet and the accounting. Your people spend more time copying between systems than doing the work.

It lives in one person’s head. If your key person is out for two weeks, half of how you run walks out the door with them.

The follow-up nobody owns. It only happens when somebody remembers.

You find out too late. To answer where one order stands, you ask three people or walk the floor. You don’t know which jobs made money until the books close.

It all runs on one spreadsheet. It breaks whenever someone edits the wrong cell.

What you can buy doesn’t fit. The software you’re sold means ripping out what you have and retraining everyone, and it still doesn’t fit how the work moves. Where a vendor does connect things, your data and logins live on their side. I know, because I shopped for it too.

The person who left still has a login. Nobody’s sure who can get into what. When someone leaves, their logins keep working until somebody remembers to shut them off, and half the office shares one admin password.

Illustrated examples. The names and numbers are made up.

How I work

One job at a time, in three steps.

The order matters. Connect things before you’ve looked, and you just wire the mess together faster. Add AI before the basics hold, and it drafts from bad numbers.

  1. 01

    Look at one job and see where it really waits.

    I follow one job from the first call to the invoice: every stop, every handoff, every place it falls through the cracks.

    • Operating Map
    • Two fixed prices
    • Yours either way
  2. 02

    Connect what you already run.

    If the fix is worth doing, I connect the tools you already use, like your accounting, CRM, spreadsheets, email or shop software.

    • Fixed price
    • Your own accounts
    • Nothing ripped out
  3. 03

    Let the software take the busywork.

    Once the basics hold, I add reminders, drafts and AI where they help.

    • Typed once
    • Drafts, not decisions
    • A person decides

Seeing it pay off

Spending real money on how your business runs can feel like a lot.

I’ve sat on the buying side of enough software demos to know that feeling. So you don’t have to take my word for what this is worth. In the X-Ray, I time how long your people take on real jobs. Once it’s live, I time the same jobs again. One page shows the difference in your own hours, and it grows with every piece we add. When you can see it paying off, the next step just makes sense. If something isn’t paying off, the page shows that too.

Below is a made-up example of that page, which I call the Payback Map. The numbers are made up to show what the page looks like, not taken from a real client. With a monthly Operating Review, it gets updated every month.

Pick the kind of work closest to yours.

Payback Map · Example CoExample screen · sample data

Example Co · 3 locations · about 140 people · month 9 after go-live

Gross margin

29.3%

was 28.4% · up 0.9 points

From your invoices

Work that used to go unbilled

988

lines now on the invoice

From your invoices

Days to get paid

22

was 34

From your invoices

Rush charges

3 a month

was 14

From your records

Work done twice

4 a month

was 11

From your records

Gross margin, month by month

29.6%28.8%28.0% Before: 28.4% (last 6 months) Build live + change + change Paid for itself 123456789

Dashed line: before, from your last six months of records. Circle: the month it paid for itself.

Not counted yet: sales growth, repeat customers, and calls that used to go unreturned. They go on the page after a year of history, and only what your own records show.

What you keep

Here’s what stays yours, whatever happens.

Ask any vendor what you’d keep if you stopped working with them. Most honest answers are “not much.” Here’s mine, spelled out in a simple agreement before anything starts.

WhatWho owns itWhere it lives
Your dataYouIn your own systems and accounts, where it already is.
Accounts and loginsYouIn your company’s name. Nothing is held hostage, by me or anyone.
The system built for your businessYouIn your accounts and on your equipment. It keeps working if we stop.
Software and hostingYour nameBilled to you directly. You see the list before the build starts.
The Operating MapYouHanded over at the end of the X-Ray, build or no build.
The methods I bringMeYou get full use of them for as long as you run the system.
Blake Thomas
Blake ThomasFounder, Operations Layer Partners LLCPoplar Bluff, Missouri

Who I am

An operator who builds, not a consultant who pitches.

Consultants hand you a binder and leave. Software vendors wait for you to tell them what to build. I find the problem and I build the fix.

17
years in operations
1
job to start
0
systems replaced

Questions

Questions that come up.

Straight answers. If yours isn’t here, ask me directly: blake@operations-layer.net.

How do engagements work, and what does it cost?

Everything starts with a paid Operations X-Ray: one part of your operation, at the same flat price for every business. From there, most work is a System Build at a fixed price. I stay in the work for 30 days after it goes live, and the build comes with its first three months of System Care. After that, the way to keep it improving is a monthly Operating Review, with System Care included. If a system is done changing, yearly care keeps it running as built, renewed only when you say yes. Ending either one never switches anything off. You always know the scope and the price first, and nothing is billed by the hour.

Do you replace our current software?

No. I connect what you have. If something can’t be connected, I’ll tell you plainly and you decide what to do about it.

What happens in the X-Ray, and how much of our time does it take?

A few working sessions with the people who know each part of the job. There’s nothing to prepare. Walk me through how the job goes on a normal day, and I’ll ask the questions. At the end you get the map, two fixed prices (a smaller fix and the full one), and a clickable preview of the smaller fix. The preview runs on made-up examples and isn’t connected to your systems. I show it at the readout so you can see the fix before you choose.

What if my people won’t use it?

That’s a big part of what I watch for in the X-Ray: how your people really work and what they’ll ignore. I’d rather build something small they use than something big they work around. If it’s slower than writing it on the pad, I built it wrong. And I’m in the work with them for the first 30 days after it goes live.

Why one person and not a firm?

Because you’re hiring the person who does the work. And because everything is built in your name, with a plain handoff, you’re never stuck with me.

Start with one job

Stop working around your software. Make it work together.

Tell me where work gets stuck between people, departments, documents or systems. I read every note myself and reply directly. No pitch and no sales sequence. Just a conversation about one job.

The email opens with four short prompts already in it. Three lines is plenty. I’ll write back myself and tell you straight whether I’m the right person for it, even if the answer is no.

blake@operations-layer.net

Your starting point

The Operations X-Ray is a paid look at one part of your operation, from where it starts to where it ends, at the same flat price for every business. The price isn’t listed here. You’ll hear it in the first conversation, before anything starts.