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.

The layer

Your operation, connected into something your people actually use.

Not a new platform with your logo on it. Dashboards, connections and small AI-assisted steps, built around how your work moves and running in your own accounts.

One screen every morning.

Everything that needs attention today, pulled from the systems you already have. No more checking three places to answer one question, and nobody rebuilds it in Excel on Monday.

Ask a plain question. Get an answer you can check.

An example of what I could build on top of the software you already run. It shows where every answer came from and drafts the next step. Nothing goes out until a person approves it.

Ask the officeExample screen · sample data
Kim asked

Where’s order 1042?

  1. Looked in the job sheetHose kits, 2 sets, for Dale
  2. Looked in accountingSupplier invoice: shipped Monday
  3. Looked in textsDale asked for Thursday

Waiting on parts, still on time. The hose kits shipped Monday and are due Wednesday. Dale was promised Thursday.

from job sheetfrom accountingfrom texts

Draft text to Dale

“Your hose kits arrive Wednesday. Still on for Thursday pickup.”

ApproveEditNothing sends until Kim clicks.

Built around your business, not the other way around.

Bring me an “I wish this could do that…” or the spot where work keeps getting stuck, and most of the time it can be built, connected or layered onto the software you already run.

By kind of work

Different yard. Same gaps.

A parts counter, a dispatch office and a front office don’t talk alike. Work still gets typed twice, and it still waits on one person.

Your people can fix almost anything. Nobody can say where the part is.

Where I’d look first

A job sits in the shop waiting on a part, and the counter, the shop and the customer each have a different answer about where it is. A repair quote waits on the one person who knows what that job usually runs.

I’d start with one repair, from the customer’s first call to the paid invoice.

Keep what you run. Your shop software and your parts lists stay. I connect what’s around them.

Don’t see your business here? It’s probably the same gap. Email me what you do, and I’ll tell you straight whether I’m the right fit.

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.

One person, and you hold the keys. Hiring one person can feel risky if that person holds the keys. So I don’t hold them. Your people run it day to day, and every build ends with a plain handoff: what’s running, where, how to restart it, and the logins in your name.

Everything I build lives in your operations layer. It’s yours: you can remove me with one step, and it keeps running. The first build sets it up: one login per person instead of shared ones, a written checklist for when someone leaves, and a practice run at handoff where we remove a test login and mine, then check that the work keeps moving.

Here’s the kind of page you’d get at the end. One page your people can run from without me.

I stay in the work for 30 days after it goes live, and the first three months of System Care come with the build. After that, a monthly Operating Review keeps it improving, with care included. If a system is done changing, yearly care alone keeps it running as built, renewed only when you say yes. Ending either one never switches anything off.

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.